weblogic 10.3 setup with ejb booking example
mdurant.mark.durant.fiserv.com Nov 17, 2009 4:09 PMHi,
I'm having some problems getting the EJB version of the booking example in Seam 2.1.2 working with WebLogic 10.3, and I'm hoping that someone here has some advice. I followed the instructions in Chapter 39 of the community documentation (http://docs.jboss.org/seam/2.1.2/reference/en-US/html/weblogic.html), worked through a few dependency issues, and got the application to the point where it deployed cleanly into WLS. When I go to http://localhost:7001/seam-booking, though, I get lots of exceptions, each of whose root cause is this:
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'jboss-seam-booking.EjbSynchronizations/local' didn't find subcontext 'jboss-seam-booking'. Resolved ''; remaining name 'jboss-seam-booking/EjbSynchronizations/local' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.Component.instantiateSessionBean(Component.java:1400) at org.jboss.seam.Component.instantiate(Component.java:1364) at org.jboss.seam.Component.newInstance(Component.java:2122) ... 48 more
I'm able to get rid of these errors by commenting out the <transaction:ejb-transaction/> line from components.xml, and that gets me to the home page of the booking application fine, but then I get similar errors for other beans when I try to use the site.
If I look at the WLS JNDI tree in the WLS admin console for the server that this is running on, I don't see any of these EJBs listed, so it looks like they're just not deploying. I do see them identified as EJB jars in the deployments
section, though, when I expand the booking app deployment in there. I'm fairly new to EJBs, too, so I may just not be understanding where/how it should be shown.
Thanks for any help!
Mark