Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

faultCode argument for createFault was passed NULL -with Metro 2.3

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using Metro 2.3 and invoking webservice request using JAX-WS. As part of the one of the flow, we are getting faultResponse, but while handling that I am getting the below exception


From tcpdump, this is the response we are getting back,

I went through the forums and suspect this could be some namesapce issue. So. I just simulated the response from SOAP UI for different combinations and the below response works fine. The system is able to parse it properly and displayed the error response.


Basically I removed, "SOAP-ENV" from "faultcode" and "faultstring" xml tags. I am new to this XML part and finding it difficult what is really the problem here. I have even went through this link reg. faultResponse spec. http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383510. But still I am not very clear as I am new to this. This reponse comes to me from a 3rd party system. Is it that the reponse is not complaint to the standards ? Could you please help me to find the reason for this behavior ?
 
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic