ibm.com/developerWorks
Presented by developerWorks, your source for great tutorials
EJB provider (
java:EJB
,
org.apache.axis.providers.java.EJBProvider
)
extends the RPC provider by looking up the EJB component with JNDI, getting its
home method, and invoking the no argument
create
method on its home interface; it
then takes the object returned from the home and treats it like
java:RPC
treats the
POJO.
Here is the class hierarchy for the EJB Provider.
java.lang.Object
|
+ org.apache.axis.handlers.BasicHandler
|
+ org.apache.axis.providers.BasicProvider
|
+ org.apache.axis.providers.java.JavaProvider
|
+ org.apache.axis.providers.java.RPCProvider
|
+ org.apache.axis.providers.java.EJBProvider
If you have a few minutes, download the Axis source code and look at the EJBProvider
and the RPCProvider. (Note there are other providers for RMI, CORBA, COM, and the
Bean Scripting Language or BSF.)
2) Where to look for the service?
The JNDI Context factory class for your EJB application server
...
...
value="com.caucho.hessian.HessianContextFactory"/>
...
...
The
jndiContextClass
parameter specifies the JNDI Context factory class for you
EJB server. The example uses the one for Resin EE. Note this will vary from EJB
application server to EJB application server. For example, when using JBoss,
jndiContextClass
would be
org.jnp.interfaces.NamingContextFactory
.
You need to find this value for your application server of choice.
2) Where to look for the service?
Page 12 of 33
Service enable EJB SessionBeans with the IBM ETTK
footer
Our partners:
PHP: Hypertext Preprocessor Best Web Hosting
Java Web Hosting
Jsp Web Hosting
Cheapest Web Hosting
Visionwebhosting.net Business web hosting division of Web
Design Plus. All rights reserved