Alexander Daniel wrote: > In Cocoon 2.2 the file generator is defined directly as Spring component > whereas the XSLT transformer is still defined in a xconf via the Avalon > bridge. A definition via the Avalon bridge also creates a pool for the > component visible as xsltPooled. > > Does this have any performance reasons or are there any other reasons > why the XSLT transformer is not defined as Spring component? The reason is (I think) much simpler: noone ported the Avalon code so far.
Without measuring it, I think we can't really tell which approach is faster. Java used to be slow when it comes to object creation and deleting them, but that has changed. So today, pools are considered slower. On the other hand, the xslt transformer is not just one simple small java object, there is "a lot" going on when an instance is created. But I guess if programmed correctly, the non-pool version should be at least as fast as the pooled version if not faster. HTH Carsten -- Carsten Ziegeler [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
