RE: Axis2-1.5.1 and user exceptions

Thanks for your response Michael!!! That may be useful and I was not aware of that setting however I was trying to get axis2 to work pretty much the same way it was doing it in previous versions. Let me explain. Axis1 whenever you expose an operation as a web service (bottom up) it generates the

RE: Axis2-1.5.1 and user exceptions

In the axis2.xml file on the server/service side, you should see this line: false Set that parameter to "true". Additionally, you might want to change this parameter as well: false Setting that to "true" should force more stack trace detail to be sent along with it, including the details

Axis2-1.5.1 and user exceptions

Hi, I'm using axis2 v1.5.1 as it is stated in the subject of this message and I've found that user exceptions are not being reported as they used to be with axis1. If one declare an operation throwing an exception, whenever the exception is thrown the detail part of the soap fault element used to

Re: Receive WSSecurityException (The signature verification failed)

Hans, Can you post the stacktrace too. Might be helpful to figure out what exactly is happening. regards, Nandana On Mon, Feb 15, 2010 at 7:17 PM, Hans-Bernhard Friedrich < h.friedr...@levigo.de> wrote: > Hi, > > I work on a webservice client and I always receive the same error when I > try

Data Binding in axis2

I want to create a simple webservice wherein i require: 1. interoperability 2. interact with custom objects Do i require to use any data bindings or using POJO is sufficient? do we have enough documentation for the Data binding? Because Axis2 quick start guide has some text for how to create webser

Is it normal that my cypher in has blanks instead of returns

Hello, This is related to my previous mail "Receive WSSecurityException (The signature verification failed)". But I think this should be discussed seperatly. When I examine my requests with wireshark my looks has no return and ist just one string with blanks every 78 characters. When I compa

Receive WSSecurityException (The signature verification failed)

Hi, I work on a webservice client and I always receive the same error when I try to make a request to our clients webservice. "org.apache.ws.security.WSSecurityException (The signature verification failed)" - Our client's webservice is axis-based, more I don't know - I use rampart 1.3 and Ax

RE: Please help on Axis2 Exception handling

the client needs to disable setExceptionToBeThrownOnSOAPFault ServiceClient.setExceptionToBeThrownOnSOAPFault now the client is free to handle any exception.. you will need to configure the client method to throw your exception which you can do at the phase level ConfigurationContext ctx=UtilSe

RE: Please help on Axis2 Exception handling

Actually, I also faced a similar problem while throwing a RemoteException from POJO. Couldn't get a solution for that. Does anybody have a guide for exception handling or the best practices for this? -Sandeep From: Li Ma [mailto:lim...@gmail.com] Sent: Monday, Fe

Please help on Axis2 Exception handling

Dear All, I ran into a very weird problem with Axis2 exception handling, which puzzled me for long time. Any help from you Axis2 expert will be greately appreciated! This is what I did: 1. Get my service POJO ready. All method throws a customized MyException which is derived from java.lang.Excep

RE: Interoperability of Axis2

I tried the reverse way. Generated the java server side classes from the generated WSDL (from the POJO deployed webservice) and then deployed the WS (using this new generated code). Now I was able to get the custom object as a parameter in the web method. But I am still not getting why the reve