I have been trying without success to configure my Spring application to use the Geronimo JTA Transaction Manager via Jencks. I have run into a few problems/questions which hopefully someone here can help me with. Please bear in mind that I am a JTA/Jencks neophyte and hence I may not understand some things which may be obvious to an experienced Jencks/Geronimo developer.
1. Because the documentation for deploying a JTA Transaction Manager is so sparse I assumed that this is all that necessary to have the application use global/XA transactions -- just wire in a JTA Transaction Manager to use as the application's transactionManager bean (referenced in the declarative transaction management AOP configuration) and everything else works like magic. Unfortunately this isn't appearing to be the case based on my tests. Perhaps I have written the wrong type of tests, or I don't know how to properly decipher the log messages, but if not then it appears that there's more to it than this. Am I right in this assumption? 2. Assuming that I am correct in that I need to do some more wiring of my DataSource and JMS components then I probably need to follow the instructions in the Jencks Documentation for Outbound JDBC, Outbound JMS, and Message-Driven POJOs. I started down this path and I soon ran across a big problem -- in both the Outbound JDBC and Outbound JMS documentation sections the example configuration for the connectionManager bean includes a transactionManager property, but when I run my application Spring complains that such a property doesn't exist for this bean's class (org.jencks.factory.ConnectionManagerFactoryBean): Caused by: org.springframework.beans.NotWritablePropertyException: Invalid property 'transactionManager' of bean class [org.jencks.factory.ConnectionManagerFactoryBean]: Bean property 'transactionManager' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter? Is this another example of the documentation only being relevant to the new 2.0-SNAPSHOT development release, and there is some wrapper trick needed if using the latest stable 1.3 release of Jencks? If not then is the documentation incorrect in that there's actually another class that should be used for this bean? 3. The Outbound JMS section of the documentation specifies the class org.jencks.factory.ConnectionFactoryFactoryBean for the jmsConnectionFactory bean, however this class doesn't exist in the Jencks 1.0 API as far as I can tell, and I can't find another class to use which may have been the intended class for the example. Can anyone clarify and/or suggest how I can work around this? 4. I haven't gotten around to applying the Message Driven POJOs section of the documentation to my application's configuration, and I'm hesitant to do so because I already have the Message Driven POJOs part of my application working well using Spring's DefaultMessageListenerContainer. Do I really need to modify my configuration according to the Jencks documentation, or could I just specify my DefaultMessageListenerContainer to use the JTA Transaction Manager from the Jencks configuration and call it good? (I'm afraid that this would be too simple of a configuration modification, based on my experience up to this point.) Thanks in advance for any help. --James -- View this message in context: http://www.nabble.com/Problems-configuring-my-application-for-JTA-transaction-management-of-Hibernate-%2B-JMS-tf2834029.html#a7912152 Sent from the jencks - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
