Create Neutral EJB3 Provider

Is it possible to create a client that accesses the EJB3 bean without the client depending on the vendor JAR or configuration? Currently, we need to support scenarios in which our service is deployed to a WebSphere or JBoss server, and the client is deployed as an application in either WAS or JBoss or runs as a stand-alone application.

I used to do this using EJB2.x beans, I just needed to create stubs using RMIC.

But with EJB3, if I connect to WebSphere, I have to include JQ queries, and I have to pre-generate stubs using WAS tools. For JBoss, I have to use jboss-client.jar.

+3
source share
2 answers

No, It is Immpossible. This has been made clear in section 10 of the EJB 3.2 specification:

This chapter describes interoperability support for accessing an enterprise bean through the look of an EJB 2.1 remote client from networked clients and distributed interoperability requirements for enterprise beans calling from remote clients that are components of the Java Platform, Enterprise Edition (Java EE). Distributed compatibility is not defined to represent the remote EJB 3.x client.

Also pay attention to section 10.5.5:

, javax.ejb.Handle, javax.ejb.HomeHandle, javax.ejb.EJBMetaData, java.util.Enumeration, java.util.Collection java.util.Iterator . EJB . JAR , bean. , runtime, Deployer , , bean, . , , , .

WebSphere Application Server EJB thinclient , IBM JNDI, CosNaming. thinclient , , JVM ORB CosNaming.

+3

: , , :

  • .
  • AS (, )
  • , /jndi (qa, prod ..)

(, JBoss JBoss-), . /, , .

, , 1 jar/lib, , . , -, InitialContext, JBoss, Websphere .

, , AS, "".

+2

All Articles