Hello,
I am working on POC for Axis 2 1.5 & Jibx 1.21. Following are the environment
details:-
Application Server: Bea 10.3
Engine: Axis2 1.5
Binding: Jibx 1.2.1
Ant: 1.7
Java: 1.6.015
With the WSDL & schema ready I am following Top Down Approach.
Firstly I run the binding on schemas & compiled the classes to create compiled
jar file using ANT. Then using wsdl2java tool i generated provider source code.
Then I copied the compiled jar into the classpath of generated source & then
again run the build to generate provider jar file.
Now I have two jar file
1> Jar file of XSD compilation
2> Provider Jar
I copied these two files in my test application classpath, then I updated axis2
services.xml to specify bean that actually implements the skeleton interface.
I deployed the application & tested the url.. It successfully displays the wsdl
of the service.
But when I test the provider using Soap UI by passing sample request then it
gives the following error:
Make sure classes generated by the binding compiler are available at runtime
org.apache.axis2.AxisFault: Unable to access binding 'binding'
Make sure classes generated by the binding compiler are available at runtime
at
com.xx.xxx.xxx.xxx.EntityProfileJibxServicesMessageReceiverInOut.fromOM(EntityProfileJibxServicesMessageReceiverInOut.java:203)
at
com.xx.xx.xx.xx.jibx.EntityProfileJibxServicesMessageReceiverInOut.invokeBusinessLogic(EntityProfileJibxServicesMessageReceiverInOut.java:78)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Please let me know what could be done to avoid getting this message.
Thanks in Advance
Manish
_________________________________________________________________
We all see it as it is. But on MSN India, the difference lies in perspective.
http://in.msn.com------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
