/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Well, I'd have to see the two alternatives side-by-side since the difference here is mostly a matter of taste regarding how the error handling code is structured. In general, I'd probably be happy with either approach.Originally posted by Jean-Louis Marechaux:
What do you think about always returning SOAPFaults ?
I mean, a SOAPFault when a real error occurs, and business XML message contained in a SOAPFault (Element detail) when a business error occurs
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Pradeep Bhat:
I have a question, how do I send SOAP fault message from the web service? Do I need to throw an exception so that it gets propagated as SOAP fault message? Can some one give me code sameple to send SOAP fault message.
I don't know whether there's a standard way of mapping SOAPFaults to exception classes, but the specification certainly makes it possible (the fault element in SOAP allows using custom "details" of which namespace/element name could be mapped to a Java exception class, for example).Originally posted by Pradeep Bhat:
Is it possible to translate the SOAP fault message to a specific Exception at the client?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Balaji Loganathan:
An example is available here http://cvs.apache.org/viewcvs.cgi/ws-axis/java/samples/faults/ for apache axis, which you can re-use for other implementations as well.
Originally posted by Lasse Koskela:
I don't know whether there's a standard way of mapping SOAPFaults to exception classes, but the specification certainly makes it possible (the fault element in SOAP allows using custom "details" of which namespace/element name could be mapped to a Java exception class, for example).
My guess would be that the team who created the specification didn't think it would be necessary to allow such flexibility for SOAP faults...Originally posted by Pradeep Bhat:
Why does the SOAP fault message have only one part?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]