Packaging/deploying a webapp client to already deployed EJBs

Question

I have a webapp/ejb deployed on WLS 6.1. If it matters, the EJBs are
deployed in jar files but the webapp component is deployed in exploded
directory format.
Now I want to deploy another webapp that uses the same EJBs. At this
point in development, I am attempting to deploy this in exploded
directory format as well. I have run ejbc manually against the original
jars to create the EJB deployable units containing generated WL classes.
This also created a ejb-client.jar, but it does not contain any impl
classes for the home or remoted interfaces.
I tried placing the ejb-client.jar in my WEB-INF/lib but it doesn't seem
to be able to find the interface classes. Perhaps the exception I'm
getting does not mean what I think it does. It is included below.
I also tried adding the generated impl classes to the ejb-client.jar
manually, but this didn't work either. I have read the
packaging/deploying docs but don't seem to find this issue addressed
directly. From all I know, I have done this correctly, but obviously I
am missing something somewhere.
Thanks in advance for your consideration.
<May 10, 2002 1:53:57 PM CDT> <Error> <HTTP>
<[WebAppServletContext(9605583,adminApp,/adminApp)] Servlet failed with
Exception
java.lang.ExceptionInInitializerError
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:42)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:30)
at java.lang.reflect.Constructor.newInstance(Constructor.java:277)
at java.lang.Class.newInstance0(Class.java:301)
at java.lang.Class.newInstance(Class.java:254)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:342)
at javax.rmi.CORBA.Util.<clinit>(Util.java:54)
at
javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
at
javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:61)
at
net.verizon.storm.util.DataBroker.initialize(DataBroker.java:102)
at
net.verizon.storm.util.DataBroker.getInstance(DataBroker.java:158)
at
net.verizon.storm.util.OrderDispatcher.<init>(OrderDispatcher.java:70)
at
net.verizon.storm.admin.OrderService.startOD(OrderService.java:159)
at
net.verizon.storm.admin.OrderService.processRequest(OrderService.java:104)
at
net.verizon.storm.admin.OrderService.doPost(OrderService.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Caused by: java.lang.RuntimeException: could not find or instantiate any
UtilDelegate class
at
weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:72)
... 24 more

Answer 1

Hi.
I tried placing the ejb-client.jar in my WEB-INF/lib but it >>doesn't seem to beable to
find the interface classes. Perhaps
the exception I'm getting does not mean what I think it does. >>It is includedbelow.
It seems fine since it is the way your webapp always to use its EJB client jar.
I also tried adding the generated impl classes to the ejb-
client.jar manually, but this didn't work either.Nope, you should never do this since Impl classes are used on Server Side ( webapp
treated as client of EJB in this case ) only.
It is so hard for us to analyze the problems without a test case, I would suggest
you to create a support case via http://support.bea.com/welcome.jsp to BEA support
for detailed work.
Thanks.
Ji Zhang
Developer Relations Engineer
BEA Support