>> 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. Shouldnt the application look after whether or not the stylesheet has changed or not. i.e. is the cache up to date? if not, compile source again and dump it in the cache?
- Transparent caching with JAXP/TrAX Morten Jorgensen
- 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... 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
