1. The DataClasses configuration point doesn't exist anymore. With the "squeezer pipeline", this is unnecessary. The EntitySqueezerFilter checks to see if it can squeeze the object. If it can't it just sends it on down the line (the regular squeezer framework picks it up).
2. The transaction interceptors aren't really needed in transaction-per-request mode. -----Original Message----- From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Bulling Sent: Saturday, June 03, 2006 11:23 AM To: Tapestry users Subject: Re: Tapernate-example and the former jars On 03. Jun 2006 - 10:54:22, James Carman wrote: | Well, you can just download the war file if you want... | | www.carmanconsulting.com/mvn/com/carmanconsulting/tapernate-example/0.1 | | Just unzip that and it will contain all dependencies you need. Thanks a lot, that's what I wanted! :-) Without having testet it just two short questions (as I know the different Tapernate hivemodule.xml files quite well in the meanwhile *g): 1) Is the <contribution configuration-id="DataClasses"> not needed anymore? 2) Are the <interceptor service-id="spring.transaction.TransactionInterceptor"> <method name="find*" attribute="PROPAGATION_REQUIRED,readOnly"/> <method name="insert*" attribute="PROPAGATION_REQUIRED"/> <method name="update*" attribute="PROPAGATION_REQUIRED"/> <method name="delete*" attribute="PROPAGATION_REQUIRED"/> <method name="get*" attribute="PROPAGATION_REQUIRED,readOnly"/> </interceptor> not needed or not available anymore? Thanks and kind regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
