[JBoss Seam] - EJBs in muliple JARs with Seam (JNDI issue?)
by d1g
Hi. I'm looking for advice on how to use multiple EJB JAR files within a Seam application running with JBoss Embeddable EJB 3.0. The problem relates to EJB JNDI locations and how Seam discovers the EJB components.
I have several libraries of JavaBean and EJB3 Seam components. Each library lives in it's own JAR file. This works fine in JBoss AS but I'm having trouble using multiple JARs with JBoss Embeddable EJB 3.0.
I know that my application works fine if all the beans are in the same classpath / JAR file. However when I rebuild and run the app with multiple JARs Seam does not pick up the EJBs in the JARs that are not the main/home JAR.
I can see that the EJBs have been deployed properly by the container and that the problem is that Seam is looking in the wrong place for the EJBs in other JARs.
What is the best way to tell Seam to look in different JNDI locations when EJBs are deployed in multiple JARs?
Here is a snapshot of my JNDI tree when the EJBs are deployed in *separate* JARs. There are two 'JARs', one named 'project' and the other named 'templating-ejb'.
GLOBAL JNDI
| +- UserTransaction (class: org.jboss.ejb3.embedded.UserTransactionImpl)
| +- UserServiceBean (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy39 implements interface org.restlet.seam.UserService,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
|
|
| -------------
| java:/ Namespace
| +- comp.ejb3 (class: javax.naming.Context)
| | NonContext: null
| +- TransactionPropagationContextImporter (class: org.jboss.tm.TransactionPropagationContextImporter)
| +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
| +- TransactionPropagationContextExporter (class: org.jboss.tm.TransactionPropagationContextFactory)
| +- TransactionManager (class: org.jboss.tm.TxManager)
|
|
| -------------
| EJB ENCs
| jboss.j2ee:jar=templating-ejb,name=SkinServiceBean,service=EJB3
| +- env (class: org.jnp.interfaces.NamingContext)
|
| jboss.j2ee:jar=project,name=UserServiceBean,service=EJB3
| +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
| +- env (class: org.jnp.interfaces.NamingContext)
| | +- org.restlet.seam.UserServiceBean (class: org.jnp.interfaces.NamingContext)
| | | +- em (class: org.jboss.ejb3.entity.TransactionScopedEntityManager)
|
Here is a snapshot of my JNDI tree when the EJBs are deployed in the *same* JAR. There is one JAR named 'production'.
GLOBAL JNDI
| +- UserTransaction (class: org.jboss.ejb3.embedded.UserTransactionImpl)
| +- UserServiceBean (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy41 implements interface org.restlet.seam.UserService,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
| +- SkinServiceBean (class: org.jnp.interfaces.NamingContext)
| | +- localStatefulProxyFactory (class: org.jboss.ejb3.stateful.StatefulLocalProxyFactory)
| | +- local (class: java.lang.Object)
|
|
| -------------
| java:/ Namespace
| +- comp.ejb3 (class: javax.naming.Context)
| | NonContext: null
| +- TransactionPropagationContextImporter (class: org.jboss.tm.TransactionPropagationContextImporter)
| +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
| +- TransactionPropagationContextExporter (class: org.jboss.tm.TransactionPropagationContextFactory)
| +- TransactionManager (class: org.jboss.tm.TxManager)
|
|
| -------------
| EJB ENCs
| jboss.j2ee:jar=production,name=UserServiceBean,service=EJB3
| +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
| +- env (class: org.jnp.interfaces.NamingContext)
| | +- org.restlet.seam.UserServiceBean (class: org.jnp.interfaces.NamingContext)
| | | +- em (class: org.jboss.ejb3.entity.TransactionScopedEntityManager)
|
| jboss.j2ee:jar=production,name=SkinServiceBean,service=EJB3
| +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
| +- env (class: org.jnp.interfaces.NamingContext)
| | +- com.jellymold.templating.SkinServiceBean (class: org.jnp.interfaces.NamingContext)
| | | +- em (class: org.jboss.ejb3.entity.TransactionScopedEntityManager)
|
And here you can see the relevant section from my startup logs (separate JARS).
17:55:17,720 DEBUG [EJB3StandaloneBootstrap] !!loadMBeanServer servers 0
| 17:55:17,720 DEBUG [EJB3StandaloneBootstrap] !!loadMBeanServer creating...
| 17:55:19,691 WARN [BeanSchemaBinding] You should use the 2.0 version of the Microcontainer xml. xmlns='urn:jboss:bean-deployer:2.0'
| 17:55:20,087 DEBUG [BeanXMLDeployer] Parsing file:/Development/rest/classes/production/project/embedded-jboss-beans.xml took 2062 milliseconds
| 17:55:20,970 DEBUG [UserTransactionImpl] new UserTx: org.jboss.ejb3.embedded.UserTransactionImpl@3c96a9
| 17:55:21,305 INFO [LocalTxDataSource] Bound datasource to JNDI name 'java:/DefaultDS'
| 17:55:21,308 DEBUG [BeanXMLDeployer] Deploying file:/Development/rest/classes/production/project/embedded-jboss-beans.xml took 3284 milliseconds
| 17:55:22,707 DEBUG [BeanXMLDeployer] Parsing file:/Development/rest/classes/production/project/META-INF/jboss-beans.xml took 32 milliseconds
| 17:55:22,708 DEBUG [BeanXMLDeployer] Deploying file:/Development/rest/classes/production/project/META-INF/jboss-beans.xml took 33 milliseconds
| 17:55:22,709 DEBUG [EJB3StandaloneBootstrap] !!! deployment.getInstalledContexts() []
| 17:55:22,794 DEBUG [JaccHelper] Initialising JACC Context for deployment: templating-ejb
| 17:55:23,177 DEBUG [EjbJarDDObjectFactory] found ejb-jar.xml file:/Development/rest/classes/production/templating-ejb/META-INF/ejb-jar.xml
| 17:55:24,704 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to com.jellymold.templating.SkinServiceBean org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@60b68a
| 17:55:24,705 DEBUG [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to com.jellymold.templating.SkinServiceBean org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@60b68a
| 17:55:24,717 DEBUG [Ejb3AnnotationHandler] found EJB3: ejbName=SkinServiceBean, class=com.jellymold.templating.SkinServiceBean, type=STATEFUL
| 17:55:24,740 DEBUG [ProxyDeployer] no declared remote bindings for : SkinServiceBean
| 17:55:24,815 INFO [Ejb3Deployment] EJB3 deployment time took: 2034
| 17:55:24,816 DEBUG [JaccHelper] Initialising JACC Context for deployment: project
| 17:55:24,820 DEBUG [EjbJarDDObjectFactory] found ejb-jar.xml file:/Development/rest/classes/production/project/META-INF/ejb-jar.xml
| 17:55:25,258 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to org.restlet.seam.UserServiceBean org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@573f80
| 17:55:25,259 DEBUG [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to org.restlet.seam.UserServiceBean org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@573f80
| 17:55:25,260 DEBUG [Ejb3AnnotationHandler] found EJB3: ejbName=UserServiceBean, class=org.restlet.seam.UserServiceBean, type=STATELESS
| 17:55:25,260 DEBUG [ProxyDeployer] no declared remote bindings for : UserServiceBean
| 17:55:25,404 INFO [Ejb3Deployment] EJB3 deployment time took: 588
| 17:55:25,702 DEBUG [JaccHelper] Initialising JACC Context for deployment: templating-ejb
| 17:55:25,715 INFO [Ejb3Deployment] EJB3 deployment time took: 13
| 17:55:25,846 DEBUG [EJBContainer] Initialising interceptors for SkinServiceBean...
| 17:55:25,847 DEBUG [EJBContainer] Default interceptors: [InterceptorInfo{class=class org.jboss.seam.ejb.SeamInterceptor}]
| 17:55:25,849 DEBUG [EJBContainer] Class interceptors: []
| 17:55:25,851 DEBUG [EJBContainer] All applicable interceptor classes: [InterceptorInfo{class=class org.jboss.seam.ejb.SeamInterceptor}]
| 17:55:25,872 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:jar=templating-ejb,name=SkinServiceBean,service=EJB3 with dependencies:
| 17:55:25,875 INFO [MCKernelAbstraction] AbstractDependencyMetaData@8c6ad{dependency=persistence.units:unitName=custdb}
| 17:55:26,019 DEBUG [Ejb3Deployment] Bound ejb3 container jboss.j2ee:service=EJB3,jar=templating-ejb,name=SkinServiceBean
| 17:55:26,020 INFO [MCKernelAbstraction] installing bean: persistence.units:jar=project.jar,unitName=custdb with dependencies:
| 17:55:26,021 INFO [MCKernelAbstraction] AbstractDependencyMetaData@1bc475{dependency=DefaultDS}
| 17:55:26,050 DEBUG [PersistenceUnitDeployment] Found persistence.xml file in EJB3 jar
|
As a sweetener for you (yes you!) helping me I have (adapted from the original JSP) contributed a Seam component for printing the JNDI tree in Embeddable EJB. See here: http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddableJNDIView
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979430#3979430
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979430
19 years, 8 months
[JBossWS] - Re: Endpoint Operation metadata error
by jelda
Hi,
Please help me.Anyone solved this problem.
I am also getting similar exception..
at
org.jboss.ws.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:175)
at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:110)
at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:234)
at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.ciao.ws.ciaoogle.filters.PerformanceFilter.doFilter(PerformanceFilter.java:62)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
Regards,
Jelda
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979429#3979429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979429
19 years, 8 months
[JNDI/Naming/Network] - Porting 4.0.0 to 4.0.4 / 4.0.5
by Frintrop
We port our application from 4.0.0 to 4.0.4/5.
If we deploy our war in a seperate tomcat 5.5 and communication to a jboss 4.0.4/5 everything works perfect.
if we deploy (as in 4.0.0 done ) the war in the jboss-tomcat container we got a exception:
ERROR [STDERR] javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
18:14:18,687 ERROR [STDERR] at org.jnp.interfaces.NamingContext.discoverServ
r(NamingContext.java:1317)
18:14:18,687 ERROR [STDERR] at org.jnp.interfaces.NamingContext.checkRef(Nam
ngContext.java:1446)
8:14:18,687 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(Namin
Context.java:594)
8:14:18,687 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(Namin
we have checked the jar version. the seemed to be the same. jnp is running on port 1099.
any suggestions ?
thx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979416#3979416
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979416
19 years, 8 months