This document was generated from CDN thread
Created by: null on 13-10-2004 09:21:37 PM
Hi,
We are trying to call a webservice request from Audium application which is running on Webshere 5.0 to the webserver runing on the same webshpere server. We are getting helper class not found error message (see below). However, we can able to call the same webservice from the webaplication.
Also, whenever I make a new call, the websphere SystemOut file created newly.
10/13/04 17:10:10:047 EDT 72ac3c6f InternalExcep F com.ibm.ws.webservices.engine.InternalException TRAS0014I: The following exception was logged java.lang.Exception: WSWS3028E: Error: A _Helper class was not found for net.wachovia.retail.crosschannelbusinessservice.message.retailaccount.v1x0.ResolveDuplicateAccountsRequest.
at com.ibm.ws.webservices.engine.InternalException.<init>(InternalException.java:124)
at com.ibm.ws.webservices.engine.encoding.ser.BeanSerializerFactory.getSerializerMethod(BeanSerializerFactory.java:155)
at com.ibm.ws.webservices.engine.encoding.ser.BaseSerializerFactory.<init>(BaseSerializerFactory.java:115)
at com.ibm.ws.webservices.engine.encoding.ser.BeanSerializerFactory.<init>(BeanSerializerFactory.java:103)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.ws.webservices.engine.encoding.ser.BaseSerializerFactory.createFactory(BaseSerializerFactory.java:301)
at net.wachovia.retail.crosschannelbusinessservice.service.retailaccount.v1x0.RetailAccountBindingStub.initTypeMapping(RetailAccountBindingStub.java:418)
at net.wachovia.retail.crosschannelbusinessservice.service.retailaccount.v1x0.RetailAccountBindingStub.<init>(RetailAccountBindingStub.java:20)
at net.wachovia.retail.crosschannelbusinessservice.service.retailaccount.v1x0.RetailAccountServiceLocator.getRetailAccountPort(RetailAccountServiceLocator.java:45)
at net.wachovia.retail.crosschannelbusinessservice.service.retailaccount.v1x0.RetailAccountServiceLocator.getRetailAccountPort(RetailAccountServiceLocator.java:40)
at net.wachovia.retail.crosschannelbusinessservice.service.retailaccount.v1x0.GetInterestDividendsBRK.doAction(GetInterestDividendsBRK.java:48)
at TryItOnClasspath.doAction(TryItOnClasspath.java:35)
at com.audium.server.voiceElement.ActionElementBase.service(Unknown Source)
at com.audium.server.controller.Controller.int(Unknown Source)
at com.audium.server.controller.Controller.for(Unknown Source)
at com.audium.server.controller.Controller.a(Unknown Source)
at com.audium.server.controller.Controller.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Subject: RE: Problem in calling java webservice from Audium application
Replied by: Michael Bochynski on 14-10-2004 04:58:18 PM
Hi,
We are currently working with other customer on the exact same issue. As soon as we will have the exact solution, I will post it here.
Thanks,
Michael
Subject: Post subject: Problem in calling java webservice from Audium application
Replied by: null on 19-06-2006 02:25:04 PM
How was this issue resolved? I am having a very similar issue with my application.
Subject: RE: Post subject: Problem in calling java webservice from Audium applicatio
Replied by: Michael Bochynski on 26-06-2006 08:32:05 PM
Julie,
Customer of ours was able to replicate the same issue without Audium Call Services, with a regular servlet. It seems that the issue is related to WebSphere configuration and JAR files location. Unfortunately we do not have the information how the issue was resolved, since this customer worked directly with IBM to remove this error.
Since this issue can be replicated without Audium Call Services, and might happen with a regular servlet, I would suggest contacting IBM's support for details and help in addressing this issue.
Regards,
Michael
Subject: RE: Post subject: Problem in calling java webservice from Audium applicatio
Replied by: null on 27-11-2006 07:00:54 PM
We ran into a similar problem using WebLogic as the container. The problem was classpath levels. The classpath is a tree structure wth the 3 default (VM, Extensions, application) layers of Java extended by the 3 layers of Audium (Audium base, Common, Application). In our case, we found that the object being passed was instantiated in layer 3 by the container but the helper classes had been defined in layer 5 (common) or 6 (application) and were not visible to the shorter classpath of layer 3.
We chose to package the helper classes and Audium.war into an ear file that we deployed. That way the helper classes were visible to the same classpath layer that instantiated the object being passed to/from the web service. We are using Audium CS v3.4. Unfortunately, our method of resolving the issue eliminated the ability to use Audium's hot-update capability for extension class files since they had to be incorporated at a higher classpath level than those managed by Audium itself.
While we chose packaging you could try any number of alternatives as long as the class definitions are visible to the layer instantiating the object.
