Re: JAX-WS client and service with Rampart module for signing messages

2012-07-16 Thread Andreas Veithen
r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Ftwbs_thirdparty.html > > I'll be back :) > > > -- > View this message in context: > http://old.nabble.com/JAX-WS-client-and-service-with-Rampart-module-for-signing-messages-tp34070987p34096102.html > Sent from the

Re: JAX-WS client and service with Rampart module for signing messages

2012-06-30 Thread Megadeth
Hi Amila, At first I think I need to study this: http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Ftwbs_thirdparty.html I'll be back :) -- View this message in context: http://old.nabble.com/JAX-WS-client-and-service-with-Ra

Re: JAX-WS client and service with Rampart module for signing messages

2012-06-29 Thread Megadeth
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:386) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:171) at $Proxy28.sendOutgoingInvoice(Unknown Source) at hr.fina.jax

RE: JAX-WS client and service with Rampart module for signing messages

2012-06-26 Thread Martin Gainty
uot;main" javax.xml.ws.soap.SOAPFaultException: > > java.lang.RuntimeException: The service class cannot be found for this > > AxisService. > > I am not quite sure why you are getting above error message. (Service > class not deployed properly ?) > > Thanks > A

Re: JAX-WS client and service with Rampart module for signing messages

2012-06-26 Thread Amila Jayasekara
.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:577) >        at > org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:520) >        at > org.apache.axis2.jaxws.clie

JAX-WS client and service with Rampart module for signing messages

2012-06-26 Thread Megadeth
nt.WebServiceClient.main(WebServiceClient.java:92) Do I need to comment some of this features in axis2.xml ? I read on web that this is some problem between axis2 engine, jdk 1.6 and Websphere 6.1. What to do next ? Please, help me. Thanks. -- View this message in context: