Transaction manager not bound with embedded-ejb container &

[andrew.rw.robinson]

I am still unable to get the seam extended persistence manager working with the embedded ejb container in tomcat.
Output on startup:

INFO 23-01 21:22:12,414 (SettingsFactory.java:buildSettings:283) -Default entity-mode: pojo
INFO 23-01 21:22:12,557 (SessionFactoryImpl.java::153) -building session factory
INFO 23-01 21:22:13,391 (SessionFactoryObjectFactory.java:addInstance:82) -Not binding factory to JNDI, no JNDI name configured

I have specified the 'org.jboss.seam.core.init.managedPersistenceContexts' and the 'entityManager.persistenceUnitJndiName' in the web.xml

I have specified the "jndiName" as set to the data source in the jboss-beans.xml.

I have set the 'jta-data-source' tag, and the "jboss.entity.manager.factory.jndi.name" property in the persistence.xml.

What else can there possibly be? I am just about ready to give up on seam altogether and use Shale or have to run jbossAS which I REALLY don't want to do (for a relatively small site, JBoss is major overkill and takes way too long to start and debug on).

Can the issues example be configured to work on tomcat with the embedded container, or can the booking example be changed to use seam managed persistence managers? I am shocked to see that most of the examples don't use the extended manager, as the reasons mentioned in the reference documentation seem to make the point that seam managed persistence should always be used (for lazy loading for example).

A full solution would be very greatly appreciated (examples of all the configuration files) unless you know for sure what is wrong.

Sorry once again for the hassle, but there is no documentation on using the seam extended persistence manager that I can use to learn from except for the issues example which is not setup for any platform but JBossAS.

Thank you very much

[christian.bauer]

The log output means that the Hibernate SessionFactory isn't bound to JNDI. Has nothing to do with the "seam extended persistence manager". And is also completely unrelated to the subject of your posting the "transaction manager". What is your actual problem?

[gavin.king]

Oh, currently the Embeddable EJB container is NOT working with seam-managed persistence contexts.

Sorry if I did not pick up on that earlier, I only just became aware of this myself.

The trouble is that Embeddable EJB is not binding the TransactionManager to JNDI, as you have observed.

So your options are:


(1) Use JBoss
(2) Use Embeddable EJB + EJB-managed txns
(3) Use plain Hibernate + microcontainer + Seam-managed txns

ie. Any of the combinations that are working in the example apps. It is only

* Embeddable EJB + Seam-managed txns

that is not working.

I'll work with Bill to get that problem fixed in EEJB.

[gavin.king]

Ignore my last post. If you are working against CVS, I believe that this has already been solved. Let me try to get this working in the booking demo. (I'll get back to you later today.)

[andrew.rw.robinson]

Thanks a lot Gavin, I really appreciate your effort. Don't mean to be so negative, its just that I'm trying to get a site developed by the middle of next month and I haven't even started it yet, been spending the entire time just trying to configure Seam.

[gavin.king]

OK, thanks for helping me find this bug. Turns out I was missing some stuff from jboss-embedded-beans.xml.


If you add these lines:

<bean name="UserTransaction" class="org.jboss.ejb3.embedded.UserTransactionImpl">
 <demand>TransactionManagerInitializer</demand>
 </bean>

 <bean name="UserTransactionBinding" class="org.jboss.ejb3.embedded.JndiBinder">
 <property name="jndiProperties"><inject bean="InitialContextProperties"/></property>
 <property name="target"><inject bean="UserTransaction"/></property>
 <property name="bindTo">java:comp/UserTransaction</property>
 <property name="serializable">false</property>
 </bean>

It will work.

I've tested on tomcat/embeddable ejb3.

I'll commit that to CVS now.

[gavin.king]

"andrew.rw.robinson" wrote:
Thanks a lot Gavin, I really appreciate your effort. Don't mean to be so negative, its just that I'm trying to get a site developed by the middle of next month and I haven't even started it yet, been spending the entire time just trying to configure Seam.

Yes, configuration is a bitch, especially when the thing you are configuring has been a moving target.

I'm trying to make it easy. It's a nontrivial problem when we are targetting such diverse environments. Well, stuff is more stabilized now.

[gavin.king]

OK, the Seam issues demo can now be deployed on Tomcat, which shows this stuff working :-)

[andrew.rw.robinson]

I got an application exception. AWESOME! Never thought I would be so happy to see my own code fail. Thanks so much for your hard work Gavin. Now to start writing/fixing my own code :0

[gavin.king]

Great, at last :)