InstantiationException when trying to reference an external jar in my web service sample

Question

Dear all,
I'm working with Weblogic 6.1 SP3 (on NT platform) and, starting from weather
weblogic web service sample, I'm trying to build my first web service sample.
I developed a simple EJB (called OrderManager) that exposes the following functionalities
in its remote:
import com.bosslab.abs.beb.sci.ServiceHeaderVO;
public interface OrderManager extends EJBObject {
public OrderManagerServiceResponseVO
     submitOrder(
ServiceHeaderVO header,
     OrderManagerServiceVO data) throws Throwable;
the ServiceHeaderVO interface is in another package and it is included in an external
Beb.jar.
This Beb.jar is located under serverclasses in mydomain directory and it is included
in the classpath set in startWeblogic.cmd.
Using wsgen weblogic task & ant I created my WSOrderManager.ear and I deployed
it.
Now no problem testing the EJB (OrderManager) with a simple client (in order to
verify that classpath is correct and also the EJB is running properly).
Also no problem pointing out to this URL "http://localhost:7011/ordermanager/com.bosslab.abs.mediator.OrderManager/com.bosslab.abs.mediator.OrderManager.wsdl"
to see the WSDL of my web service.
But when I run the web service client I got the following error:
Exception in thread "main" ------------- Remote Stack Trace ------------
Server side error:
java.lang.InstantiationException: com.bosslab.abs.beb.sci.ServiceHeaderVO
at weblogic.soap.codec.SimpleSoapEncodingCodec.newInstance(SimpleSoapEncodingCodec.java:198)
at weblogic.soap.codec.SimpleSoapEncodingCodec.decode(SimpleSoapEncodingCodec.java:178)
at weblogic.soap.codec.SimpleSoapEncodingCodec.decode(SimpleSoapEncodingCodec.java:151)
at weblogic.soap.codec.CodecFactory.decode(CodecFactory.java:96)
at weblogic.soap.codec.Operation.read(Operation.java:100)
at weblogic.soap.codec.SoapMessage.readOperation(SoapMessage.java:200)
at weblogic.soap.codec.SoapMessage.read(SoapMessage.java:130)
at weblogic.soap.server.servlet.StatelessBeanAdapter.getInputMessage(StatelessBeanAdapter.java:162)
at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:105)
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:2546)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
------------- Local Stack Trace ------------
weblogic.soap.SoapFault:
org.xml.sax.SAXException
at weblogic.soap.codec.FaultOperation.getException(FaultOperation.java:16)
at weblogic.soap.WebServiceProxy.processResult(WebServiceProxy.java:487)
at weblogic.soap.WebServiceProxy.invoke(WebServiceProxy.java:434)
at weblogic.soap.SoapMethod.invoke(SoapMethod.java:186)
at weblogic.soap.wsdl.WebServiceInvocationHandler.invoke(WebServiceInvocationHandler.java:27)
at $Proxy0.submitOrder(Unknown Source)
at StaticWSOrderManagerClient.main(StaticWSOrderManagerClient.java:30)
It seems that there is a problem to instantiate the com.bosslab.abs.beb.sci.ServiceHeaderVO
class included in the Beb.jar, so I thought the problem was related to the classpath
setting, maybe Beb.jar is not set properly in some place ...
To try solving this problem I did these steps:
-> exploded my WSOrderManager.ear
-> created a lib directory and put into it the Beb.jar
so now the ear structure is:
lib/Beb.jar
MediatorOrderManager.jar
META-INF
web-services.war
-> modified the application.xml, adding:
<module>
<java>lib/Beb.jar</java>
</module>
-> modified the Manifest.mf, adding:
Manifest-Version: 1.0
Created-By: 1.3.1_03 (Sun Microsystems Inc.)
Class-Path: lib/Beb.jar
-> regenerate the WSOrderManager.ear
jar cvf WSOrderManager.ear lib MediatorOrderManager.jar ...
-> and redeployed the ear
But after stopping/starting my instance, I got yet the same error when I run my
client.
Could you please help me to understand how solving this problem ?
I thank you in advance
Kind regards

Answer 1

The WSDL is generated from my web service. I made heavy revisions to my web service which, in turn, affected the resultant WSDL. The changes I made to my web service were almost exclusively related to object substitution. For example, prior to the change I was referencing object A from my web service; after the change, I was referencing object B. The objects that I'm referring to are XMLBeans, if that matters. I can't really describe it more than that without actually showing you the WSDL.
I would post the WSDL file here to allow you to try to create a types jar out of it, but the WSDL exceeds the 30000 character limit for this field. There is no way for me to attach the WSDL to this post.