RE: [Axis2] Axis-fault
Could you give some more description how to use rampart at both end (server or client). Regards, Shailendra Singh -Original Message- From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:18 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Axis-fault Hi Aditya, Yes, can you please try with Rampart 1.3. Go through the basic samples to get an understanding about the concepts. But don't worry too much about the configurations. There are two approaches to configure Rampart. 1.) Parameter based configuration 2.) Policy based configuration Basic samples explore the parameter based configuration where as policy samples explore the policy based configuration. And it is always recommended to use the policy based configuration as parameter based configuration is deprecated. So use policy based samples to learn about the configuration. thanks, /nandana On Fri, Feb 15, 2008 at 10:00 AM, Aditya Anad <[EMAIL PROTECTED]> wrote: > 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, > 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. Can you tell me where I am going wrong. > > > > > > > > Request: > > > > > > > > POST /axis2/services/sample02 HTTP/1.1 > > > > > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > > > > > SOAPAction: "urn:echo" > > > > > > > > User-Agent: Axis2 > > > > > > > > Host: 127.0.0.1:8081 > > > > > > > > Transfer-Encoding: chunked > > > > > > > > > > > > > > > > 49a > > > > > > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-s ece= > > > > xt-1.0.xsd" soapenv:mustUnderstand=3D"1"> > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-u til= > > > > ity-1.0.xsd" wsu:Id= > > > > =3D"Timestamp-25610032">2008-02-14T07:30:23.018Z= > > > > 2008-02-14T07:35:23.018Z > > > ernameToken xmlns:wsu= > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-u til= > > > > ity-1.0.xsd" wsu:Id= > > > > =3D"UsernameToken-3860801">bob > > > Type= > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-tok en-= > > > > profile-1.0#PasswordDigest">Ojbn0fGTA3w6A9MMdCGAI4w+7D4= > > > > =3DIayhqO7tNWK2XtGnI2G3CQ=3D= > > > > =3D2008-02-14T07:30:23.002Z > > > sernameToken> > > > xmlns:ns1=3D"http://sample02.samples.rampart.apache.org/xsd";>Hel lo= > > > > world > > > > > > > > 0 > > > > > > > > > > > > > > > > Response: > > > > > > > > HTTP/1.1 500 Internal server error > > > > > > > > Date: Thu, 14 Feb 2008 07:30:23 GMT > > > > > > > > Server: Simple-Server/1.1 > > > > > > > > Transfer-Encoding: chunked > > > > > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > > > > > Connection: Close > > > > > > > > > > > > > > > > 6d0 > > > > > > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > /> > > > string>org.apache.axis2.AxisFault > > > > at= > > > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceive r.= > > > > java:100) > > > > at= > > > > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) &#= > > > > xd; > > > > at= > > >
Re: [Axis2] Axis-fault
Hi Aditya, Yes, can you please try with Rampart 1.3. Go through the basic samples to get an understanding about the concepts. But don't worry too much about the configurations. There are two approaches to configure Rampart. 1.) Parameter based configuration 2.) Policy based configuration Basic samples explore the parameter based configuration where as policy samples explore the policy based configuration. And it is always recommended to use the policy based configuration as parameter based configuration is deprecated. So use policy based samples to learn about the configuration. thanks, /nandana On Fri, Feb 15, 2008 at 10:00 AM, Aditya Anad <[EMAIL PROTECTED]> wrote: > 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, > 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. Can you tell me where I am going wrong. > > > > > > > > Request: > > > > > > > > POST /axis2/services/sample02 HTTP/1.1 > > > > > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > > > > > SOAPAction: "urn:echo" > > > > > > > > User-Agent: Axis2 > > > > > > > > Host: 127.0.0.1:8081 > > > > > > > > Transfer-Encoding: chunked > > > > > > > > > > > > > > > > 49a > > > > > > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > > > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece= > > > > xt-1.0.xsd" soapenv:mustUnderstand=3D"1"> > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > > > ity-1.0.xsd" wsu:Id= > > > > > =3D"Timestamp-25610032">2008-02-14T07:30:23.018Z= > > > > > 2008-02-14T07:35:23.018Z > > > ernameToken xmlns:wsu= > > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > > > ity-1.0.xsd" wsu:Id= > > > > > =3D"UsernameToken-3860801">bob > > > Type= > > > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-= > > > > profile-1.0#PasswordDigest">Ojbn0fGTA3w6A9MMdCGAI4w+7D4= > > > > =3DIayhqO7tNWK2XtGnI2G3CQ=3D= > > > > > =3D2008-02-14T07:30:23.002Z > > > sernameToken> > > > > xmlns:ns1=3D"http://sample02.samples.rampart.apache.org/xsd";>Hello= > > > > world > > > > > > > > 0 > > > > > > > > > > > > > > > > Response: > > > > > > > > HTTP/1.1 500 Internal server error > > > > > > > > Date: Thu, 14 Feb 2008 07:30:23 GMT > > > > > > > > Server: Simple-Server/1.1 > > > > > > > > Transfer-Encoding: chunked > > > > > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > > > > > Connection: Close > > > > > > > > > > > > > > > > 6d0 > > > > > > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > > /> > > > string>org.apache.axis2.AxisFault > > > > at= > > > > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.= > > > > java:100) > > > > at= > > > > > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)&#= > > > > xd; > > > > at= > > > > org.apache.axis2.engine.Phase.invoke(Phase.java:383) > > > > at= > > > > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) > > > >
RE: [Axis2] Axis-fault
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, 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. Can you tell me where I am going wrong. > > > > Request: > > > > POST /axis2/services/sample02 HTTP/1.1 > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > SOAPAction: "urn:echo" > > > > User-Agent: Axis2 > > > > Host: 127.0.0.1:8081 > > > > Transfer-Encoding: chunked > > > > > > > > 49a > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece= > > xt-1.0.xsd" soapenv:mustUnderstand=3D"1"> =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > ity-1.0.xsd" wsu:Id= > > =3D"Timestamp-25610032">2008-02-14T07:30:23.018Z= > > 2008-02-14T07:35:23.018Z > ernameToken xmlns:wsu= > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > ity-1.0.xsd" wsu:Id= > > =3D"UsernameToken-3860801">bob > Type= > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-= > > profile-1.0#PasswordDigest">Ojbn0fGTA3w6A9MMdCGAI4w+7D4= > > =3DIayhqO7tNWK2XtGnI2G3CQ=3D= > > =3D2008-02-14T07:30:23.002Z > sernameToken> > xmlns:ns1=3D"http://sample02.samples.rampart.apache.org/xsd";>Hello= > > world > > > > 0 > > > > > > > > Response: > > > > HTTP/1.1 500 Internal server error > > > > Date: Thu, 14 Feb 2008 07:30:23 GMT > > > > Server: Simple-Server/1.1 > > > > Transfer-Encoding: chunked > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > Connection: Close > > > > > > > > 6d0 > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > /> > string>org.apache.axis2.AxisFault > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.= > > java:100) > > at= > > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)&#= > > xd; > > at= > > org.apache.axis2.engine.Phase.invoke(Phase.java:383) > > at= > > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) > > at= > > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) > > at= > > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(= > > HTTPTransportUtils.java:279) > > at= > > org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:216)&#x= > > d; > > at= > > org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpS= > > ervice.java:275) > > at= > > org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisH= > > ttpService.java:184) > > at= > > org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServic= > > eProcessor.java:74) > > at= > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.r= > > unTask(ThreadPoolExecutor.java:665) > > at= > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.r= > > un(ThreadPoolExecutor.java:690) > > at java.lang.Thread.run(Thread.java:534) > > Caused by: java.lang.NullPointerException > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.ja= > > va:329) > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.= > > java:91) > > ... 12 more > > > > > > 0 > > > > CAUTION - Disclaimer * > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely > for the use of the addressee(s). If you are not the intended recipient, > please noti
Re: [Axis2] Axis-fault
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. Can you tell me where I am going wrong. > > > > Request: > > > > POST /axis2/services/sample02 HTTP/1.1 > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > SOAPAction: "urn:echo" > > > > User-Agent: Axis2 > > > > Host: 127.0.0.1:8081 > > > > Transfer-Encoding: chunked > > > > > > > > 49a > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sece= > > xt-1.0.xsd" soapenv:mustUnderstand=3D"1"> =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > ity-1.0.xsd" wsu:Id= > > =3D"Timestamp-25610032">2008-02-14T07:30:23.018Z= > > 2008-02-14T07:35:23.018Z > ernameToken xmlns:wsu= > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-util= > > ity-1.0.xsd" wsu:Id= > > =3D"UsernameToken-3860801">bob > Type= > > =3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-= > > profile-1.0#PasswordDigest">Ojbn0fGTA3w6A9MMdCGAI4w+7D4= > > =3DIayhqO7tNWK2XtGnI2G3CQ=3D= > > =3D2008-02-14T07:30:23.002Z > sernameToken> > xmlns:ns1=3D"http://sample02.samples.rampart.apache.org/xsd";>Hello= > > world > > > > 0 > > > > > > > > Response: > > > > HTTP/1.1 500 Internal server error > > > > Date: Thu, 14 Feb 2008 07:30:23 GMT > > > > Server: Simple-Server/1.1 > > > > Transfer-Encoding: chunked > > > > Content-Type: text/xml; charset=3DUTF-8 > > > > Connection: Close > > > > > > > > 6d0 > > > > =3D"http://schemas.xmlsoap.org/soap/envelope/";> > /> > string>org.apache.axis2.AxisFault > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.= > > java:100) > > at= > > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)&#= > > xd; > > at= > > org.apache.axis2.engine.Phase.invoke(Phase.java:383) > > at= > > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) > > at= > > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) > > at= > > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(= > > HTTPTransportUtils.java:279) > > at= > > org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:216)&#x= > > d; > > at= > > org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpS= > > ervice.java:275) > > at= > > org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisH= > > ttpService.java:184) > > at= > > org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServic= > > eProcessor.java:74) > > at= > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.r= > > unTask(ThreadPoolExecutor.java:665) > > at= > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.r= > > un(ThreadPoolExecutor.java:690) > > at java.lang.Thread.run(Thread.java:534) > > Caused by: java.lang.NullPointerException > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.ja= > > va:329) > > at= > > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.= > > java:91) > > ... 12 more > > > > > > 0 > > > > CAUTION - Disclaimer * > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely > for the use of the addressee(s). If you are not the intended recipient, > please notify the sender by e-mail and delete the original message. Further, > you are not to copy, disclose, or distribute this e-mail or its contents to > any other person and any such actions are unlawful. This e-mail may contain > viruses. Infosys has taken every reasonable precaution to minimize this > risk, but is not liable for any damage you may sustain as a result of any > virus in this e-mail. You should carry out your own virus checks before > opening the e-mail or attachment. Infosys reserves the right to monitor and > review the content of all messages sent to or from this e-mail address. > Messages sent to or from this e-mail address may be stored on the Infosys > e-mail system. > ***INFOSYS End of Disclaimer INFOSYS*** -- Nandana Mihindukulasooriya Software Engineer WSO2 inc. http://nandana83.blogspot.com/ http://nandanasm.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Axis fault addressing versions
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 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 birtles" <[EMAIL PROTECTED]> wrote on 22/01/2007 10:23:38: > 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 in the http header the action is set to: > SOAPAction: "http://www.w3.org/2005/08/addressing/soap/fault"; > This causes problems when communicating with .net services which expect them > to be the same > > _ > Get Hotmail, News, Sport and Entertainment from MSN on your mobile. > http://www.msn.txt4content.com/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _ MSN Hotmail is evolving check out the new Windows Live Mail http://ideas.live.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Axis fault addressing versions
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 birtles" <[EMAIL PROTECTED]> wrote on 22/01/2007 10:23:38: > 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 in the http header the action is set to: > SOAPAction: "http://www.w3.org/2005/08/addressing/soap/fault"; > This causes problems when communicating with .net services which expect them > to be the same > > _ > Get Hotmail, News, Sport and Entertainment from MSN on your mobile. > http://www.msn.txt4content.com/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [Axis2] Axis Fault
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 doesn't accept HTTP 1.1. So, inside the stub i added: _operationClient.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.HTTP_PROTOCOL_VERSION,org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10); which made its trick :) - hope it helps :P emerson On 19/01/07, schalk <[EMAIL PROTECTED]> wrote: 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 Cause: HTTP Transport error : '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad Request'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '400' - 'Bad Request' Thanks! Schalk -- Open WebMail Project (http://openwebmail.org) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Axis Fault
Do you know which jars I should update? Just the axiom jars or all of the axis jars? Also, what was the exact problem? Roshan Punnoose Phone: 301-497-6039 -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2006 3:09 PM To: axis-user@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: > > 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 > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] BEGIN:VCARD VERSION:2.1 N:Punnoose;Roshan FN:Punnoose, Roshan ADR;WORK:;2115 LABEL;WORK:2115 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050413T183207Z END:VCARD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
