Mihindukulasooriya [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 14, 2008 10:29 PM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] Axis-fault
>
> Hi Aditya,
> Are you using Rampart 1.3 release ?
>
> regards,
> /nandana
>
> On 2/14/08, Aditya
Mihindukulasooriya [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 14, 2008 10:29 PM
> To: axis-user@ws.apache.org
> Subject: Re: [Axis2] Axis-fault
>
> Hi Aditya,
> Are you using Rampart 1.3 release ?
>
> regards,
> /nandana
>
> On 2/14/08, Aditya Anad
Hi Nandana,
No I am using Rampart1.2... should I try with rampart 1.3?
Regards
Aditya
-Original Message-
From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 14, 2008 10:29 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Axis-fault
Hi Aditya
Hi Aditya,
Are you using Rampart 1.3 release ?
regards,
/nandana
On 2/14/08, Aditya Anad <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am new to axis2 and web services. I was trying to execute the the basic=
> sample example given with Rampart. I am getting following request and=
> responses.
Hi,
I am new to axis2 and web services. I was trying to execute the the basic=
sample example given with Rampart. I am getting following request and=
responses. Can you tell me where I am going wrong.
Request:
POST /axis2/services/sample02 HTTP/1.1
Content-Type: text/xml; charset=3DU
done:
https://issues.apache.org/jira/browse/AXIS2-2011
From: Brian De Pradine <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: [axis2] Axis fault addressing versions
Date: Mon, 22 Jan 2007 11:50:35 +
Hello Alan,
Please raise a jira to
Hello Alan,
Please raise a jira to cover this problem. Thanks.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
"alan birtle
If I set the addressing version using:
_messageContext.setProperty(AddressingConstants.WS_ADDRESSING_VERSION,
AddressingConstants.Submission.WSA_NAMESPACE);
then when a fault message is sent the action is correctly set to:
http://schemas.xmlsoap.org/ws/2004/08/addressing/fault
but i
Hi schalk.
I had the same problem, and after some days of investigation (arghh
:)) i found it, i posted in a previous message, but here it goes:
-
I found out that the problem is the load balances in one of the
servers, which d
Greetings All,
What might cause the following error:
INFO - [org.apache.commons.httpclient.HttpMethodBase] - Discarding unexpected
response: HTTP/1.1 100 Continue
INFO - [org.apache.commons.httpclient.HttpMethodBase] - Response content
length is not known
ERROR - [soap-service] - AxisFault Cau
@ws.apache.org
Subject: Re: [Axis2] Axis Fault
My hands are aching typing the same thing :)
Use Nightly, If you still see the problem, log a bug with your
wsdl/xsd, soap request/response, code to recreate the problem.
thanks,
dims
On 9/19/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote:
>
>
My hands are aching typing the same thing :)
Use Nightly, If you still see the problem, log a bug with your
wsdl/xsd, soap request/response, code to recreate the problem.
thanks,
dims
On 9/19/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote:
Hi,
When my client is parsing a SOAP fault, he gener
Hi,
When my client is parsing a SOAP fault, he generates this error:
org.apache.axiom.om.OMException: java.lang.IllegalStateException:
Current state not START_ELEMENT
It seems like Axiom doesn't parse the soap fault well. Any ideas?
Roshan Punnoose
Phone: 301-497-6039
BEGIN:VCARD
VERSION:2.1
13 matches
Mail list logo