Re: Parameter sequence to invoke a service

you should be sending the parameters in same sequence. On Thu, Jun 24, 2010 at 12:05 PM, Chinmoy Chakraborty wrote: > Hi All, > > Is it mandatory to send params in the same sequesnce as the params are > defined in the WSDL in sequence tag? Is it possible to invoke a service by > sending params wi

Parameter sequence to invoke a service

Hi All, Is it mandatory to send params in the same sequesnce as the params are defined in the WSDL in sequence tag? Is it possible to invoke a service by sending params with any sequence but in right param name? I am using Axis2 1.4.1. Chinmoy

Re: How to mention mandatory parameters in services.xml?

You did not get my question. My service is deployed as .aar and the WSDL is autogenerated. Is there any way to mention mandatory parameter in services.xml. I also noticed there is already JIRA entry for this bug. https://issues.apache.org/jira/browse/AXIS2-3300

How to mention mandatory parameters in services.xml?

Hi All, I ahve a service "authenticate" which has three parameters username, password, and serviceName. First two parameters are mandatory and the last parameter is optional. Here is the WSDL portion of the service: .. -

Re: CXF vs Axis2

Hi Srini, Metro has a small performance advantage over CXF and Axis2, though that's mostly significant for small messages. Generally the performance with large messages is going to be more of a concern, and there the three are pretty close (as long as WS-Security isn't involved). Personally,

Re: CXF vs Axis2

Hi; Metro can also work with .NET clients. I had no hands on experience with Metro but my firends are using it with .NET clients. I had .NET clients and my services were handled by Axis2. There was no problem also. Axis2 was doing well. So reading the system requirements can also be a point for

Re: CXF vs Axis2

Hi Dennis, Thank you very much for the details that you provided. When we reviewed your article, it seems Metro is good in performance point of view - compare to CXF and Axis2. Do you suggest to go with Metro? At this point of time we are looking for the best one in overall performance and impleme

Log all http request

Hello, we've a web service that receives SOAP RPC-encoded xml requests on HTTP through axis and tomcat 5.5. We'd like to log every xml rq we receive using a Filter, because we've to write the xml to a file whose name depends on the xml request. The problem is that one can call SevletRequest.getR

Re: Axis2 ConnectionTimeout Problem

Did you try to set the connection timeout value, try that one too. Deepal On Tue, Jun 22, 2010 at 11:52 PM, naren wrote: > Hi, > I am using Axis2 1.5.1 for creating a webservice client. > I am getting a ConnectionPoolTimeoutException with concurrent threads. > > So far I have tried the below