> Jeff Winter wrote: > > > Why does TransformerFactory.newTemplates() have to compile the input > > stylesheet if there is already a stored class definition for the translet? > > Here's my two cents: I'm not sure why it would necessarily "have" to compile > the input each time, but the benefit is that you can change the stylesheet on > the fly. We do this all the time when debugging the live application. For > debug builds we call newTemplates() each time. In production we cache the > resultant Templates and use that each time. I like the separation. This is a valid point, but you can still change your stylesheets if we add some translet class caching mechanism. All you'd have to do would be to delete the translet class from the cache (a directory), change your stylesheet, and then call newTemplates(). Morten
- Re: Transparent caching with JAXP/TrAX Scott_Boag
- Re: Transparent caching with JAXP/TrAX Padraig O'hIceadha
- Re: Transparent caching with JAXP/TrAX Morten Jorgensen
- Re: Transparent caching with JAXP/TrAX Gary L Peskin
- Re: Transparent caching with JAXP/TrAX Morten Jorgensen
- Re: Transparent caching with JAXP/TrAX Padraig O'hIceadha
- Re: Transparent caching with JAXP/TrAX Padraig O'hIceadha
- Re: Transparent caching with JAXP/TrAX Scott_Boag
- RE: Transparent caching with JAXP/TrAX Jeff Winter
- RE: Transparent caching with JAXP/TrAX Paul O'Neill
- Re: Transparent caching with JAXP/TrAX Morten Jorgensen
- Re: Transparent caching with JAXP/TrAX Joseph_Kesselman
- RE: Transparent caching with JAXP/TrAX Joseph_Kesselman
- RE: Transparent caching with JAXP/TrAX Paul O'Neill
- Re: Transparent caching with JAXP/TrAX Scott_Boag
- Re: Transparent caching with JAXP/TrAX Morten Jorgensen
- Re: Transparent caching with JAXP/TrAX Scott_Boag
- Re: Transparent caching with JAXP/TrAX Morten Jorgensen
- Re: Transparent caching with JAXP/TrAX Shane Curcuru
- RE: Transparent caching with JAXP/TrAX Scott_Boag
- Re: Transparent caching with JAXP/TrAX Scott_Boag
