[JBossWS] - Problem deploying WebServices
by thenewmexican
JBoss Appserver version: 4.0.5
When testing the the deployment of a test echo WS. I get the following on the client side:
Cannot unmarshall SOAPMessage
javax.xml.soap.SOAPException: Failed to create SOAPFactory: org.jboss.axis.soap.SOAPFactoryImpl
at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:48)
at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:113)
at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:87)
at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:76)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:253)
at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75)
at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:463)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:299)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:133)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1544)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.ws.core.soap.SOAPConnectionImpl.callInternal(SOAPConnectionImpl.java:192)
at org.jboss.ws.core.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:109)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:309)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:185)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:163)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:149)
at $Proxy8.echo(Unknown Source)
at com.htg.tests.WebServicesTest.testEcho(WebServicesTest.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.lang.ClassNotFoundException: org.jboss.axis.soap.SOAPFactoryImpl
I didn't realize that the org.jboss.axis.soap classes were still being used.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102056#4102056
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102056
18 years, 5 months
[JBossWS] - Can I point a wsconsume-generated client to a local WSDL fil
by Brad Marshall
I am calling an Axis/Tomcat web service with a JAX-WS client proxy generated by wsconsume (from JBossWs 2.0.1 GA) run against our hand-coded WSDL file. When we execute the client, the constructor of the xxxService class is obtaining the WSDL from the Web service (via the ?WSDL command) and performing a dynamic element binding at run-time (at least we think that?s what happening).
The problem is that the Axis Web service is returning a WSDL with syntax errors and outright mistakes. This isn?t a problem with a client proxy generated by the Axis WSDL2Java from the hand-coded WSDL. The WSDL2Java client classes are statically bound and do not access the service?s WSDL at run time. WSDL2Java-generated clients have been in production for more than a year without any difficulty. The wsconsume-generated client throws an exception and terminates when it encounters the first error in the WSDL generated by the Axis run-time ? I never get out of the constructor of the xxxService class.
Yet wsconsume had no difficulty digesting the hand-coded WSDL. We?ve studied the WSDL for a very long time now, and do not believe there is an error in its design. Indeed, the fact that it works with WSDL2Java-generated clients shows that the WSDL is designed properly. We are convinced that the AXIS Web Service run-time is making an error generating the WSDL on demand.
Can I easily override the Service class?s retrieval of the WSDL from the Web service and point it instead at a local copy of the WSDL file? In out environment, every caller of the Web service also implements their own Web service with the identical interface, so we can enforce a rule that they have a copy local of the valid WSDL file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101985#4101985
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101985
18 years, 5 months
[JBossWS] - service-name-pattern
by Sefai
I have to call more than one web service in my web application. Each of the web services I call have different authentication mechanisms,some have none.I am trying to configure the clients using javaee:service-name-pattern.
<post-handler-chains>
| <javaee:handler-chain>
| <javaee:service-name-pattern xmlns:ns1="http://someUri/">ns1:SomeService</javaee:service-name-pattern>
| <javaee:handler>
| <javaee:handler-name>WSSecurity Handler Client (Some Service)</javaee:handler-name>
| <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient</javaee:handler-class>
| </javaee:handler>
| </javaee:handler-chain>
| </post-handler-chains>
This gives me the error org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'post-handler-chains'. One of '{"urn:jboss:jaxws-config:2.0":feature, "urn:jboss:jaxws-config:2.0":property}' is expected. @ *unknown*[26,28].
I looked at the schema definitons in jbossws,there is javaee_web_services_client_1_2.xsd which defines service-name-pattern, but it is not imported in any other schema, all the samples I have seen use xsi:schemaLocation='urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd' which imports javaee_web_services_1_2.xsd but not the client xsd.
Is this a bug, or am I missing something? How can I configure each web service to use different authentication mechanisms?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101957#4101957
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101957
18 years, 5 months