Hi,
I have been trying to port some XML based config to programmatic configuration lately. In my XML I had
<bean id="abean" class="com.zfabrik.springframework.ComponentFactoryBean">
...
Type: Posts; User: gnomie2000; Keyword(s):
Hi,
I have been trying to port some XML based config to programmatic configuration lately. In my XML I had
<bean id="abean" class="com.zfabrik.springframework.ComponentFactoryBean">
...
well... that was an example to illustrate how I expected Spring to work. Never mind. Obviously the actual question didn't come across and I am ok with assuming that Spring requires it's own TX...
hmm... I think I am rather well aware about how JTA works.
I was not asking for automatic registration of transactional resources. I was asking for a less intrusive way of having Spring resources...
Right. And it works, if I do that. The actual question was, if I can use pure JTA transaction demarcation instead.
Or, put differently, is there a way to set up the Spring transaction manager...
In a Web app of mine that uses Spring's
a) org.springframework.transaction.jta.JtaTransactionManager as Spring TX Manager
over an external JTA implementation and
b)...
Just saw this post. I had a similar problem. Could it be you relied on managing TX boundaries without using Spring? I.e. just via the JTA transaction manager, tyically using the UserTransaction...