JBoss Community

WS-Adresssing not working in Jboss-5 webservice client

created by Arun Kumar in JBoss Web Services Development - View the full discussion

Am using java webservice client. I ran the below code as a main program and it is working fine

 

VASWCF vas = new VASWCF();
System.out.println(" Trying to get contract ") ;
IRequestUnifiedVASContract contract = vas
                .getWSHttpBindingIRequestUnifiedVASContract(new AddressingFeature(true,true));
System.out.println(" Trying to send SOAP request ") ;
contract.notify(inputXml, null);
System.out.println(" SOAP message sent successfully ");

 

But when i run the same code in Jboss-5, exceptions are occuring

 

2013-08-09 19:09:35,264 WARN  [org.jboss.ws.tools.wsdl.WSDL11Reader] (http-127.0.0.1-8080-1) UsingAddressing extensibility element not supported yet.
2013-08-09 19:09:35,317 INFO  [STDOUT] (http-127.0.0.1-8080-1)  Trying to get VAS contract
2013-08-09 19:09:35,581 INFO  [STDOUT] (http-127.0.0.1-8080-1)  Trying to send SOAP request
2013-08-09 19:09:35,797 ERROR [org.jboss.ws.core.CommonClient] (http-127.0.0.1-8080-1) Exception caught while (preparing for) performing the invocation:
javax.xml.ws.soap.SOAPFaultException: The message with To '' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher.  Check that the sender and receiver's EndpointAddresses agree.
    at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
    at org.jboss.ws.core.jaxws.binding.SOAP12BindingJAXWS.throwFaultException(SOAP12BindingJAXWS.java:115)
    at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
    at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
    at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
    at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
    at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
    at $Proxy276.notify(Unknown Source)
    at com.arun.sartest.LogTestMbean.kickStartSMS(LogTestMbean.java:57)
    at com.arun.sartest.LogTestMbean.getLogValue(LogTestMbean.java:44)
    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:597)
    at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
    at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
    at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
    at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
    at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
    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:597)
    at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
    at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

 

 

When the same code runs as main program, it works fine. Wondering how it is not working in jboss-5 . I suspect that Jboss's JAXWS jar files are causing this. If so how to avoid that and make Jboss-5 use Java's classpath ?

Please help me on this

Reply to this message by going to Community

Start a new discussion in JBoss Web Services Development at Community