That's strange that this would have an affect on it. I'm not sure how Spring
transactions tie into the jbpm stuff since you're using a seperate
hibernate.cfg.xml (that stuff is configured in the applicationContext.xml for
Hibernate with Spring). What you can do, to try it out, is (without re-running
andromda of course), change your applicationContext-dataSource.xml to use the
HibernateTransactionManager again (instead of the JtaTransactionManager), so
change it to this:
<bean id="transactionManager"
class="org.springframework.orm.hibernate3.HibernateTransactionManager">
<property name="sessionFactory"><ref bean="sessionFactory"/></property>
</bean>
Just do "maven core deploy" with that change and see if it works. We should
be able to use the JtaTransaction manager as well however because that just
ties into the container's transactions...however maybe its needs additional
configuration on the jbpm end.
--
Chad Brandon - [EMAIL PROTECTED]
http://www.andromda.org
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2527#2527
Posting to http://forum.andromda.org/ is preferred over posting to the mailing
list!
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
