[Home] [By Thread] [By Date] [Recent Entries]
Colin Paul Adams wrote:
opps.....didnt realise the 2.0 requirement, otherwise saxon as servlet really is the only way to go (I use jetty/tomcat) , though I tend to have a continous integration process; obviating the need for real time xslt processing...on source change a publishing process kicks off, which generates final formats...."James" == James Fuller <jim.fuller@xxxxxxxxxxxxxx> writes: and where I need dynamic processing provide via different port or through url rewriting fun, in closed environments where the browser is known I tend to use client side xslt processing. if speed is an issue, its easy enough to create a standalone java webserver specifically for this....and I have heard of folks using ROXEN's java support to avoid J2EE servlet requirements....though never tested. gl, Jim Fuller
|

Cart



