Hi guys, Thanks for the input. I'm still confused about a few things though. I'm fairly new to this (SOAP on JBoss), so I apologize in advance if I ask stupid questions. :) We're in the process of migrating off of Weblogic to JBoss (yippee!) and we've relied on Weblogic for the generation of web services from SS EJBs, and for the generation of client code. That client code does somehow map back to the service specific exceptions thrown by the EJB methods, so I'm struggling to find something comparable to reduce the amount of code rework necessary.
I've been reading the JAXRPC spec to see what to expect, and I'm using the TCPMonitor to actually see the messages going back and forth. Here's the exceprt from the WSDL: | <binding name="TestEndpointBinding" type="tns:TestEndpoint"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; style="rpc"/> | <operation name="divide"> | <soap:operation soapAction=""/> | <input> | <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; use="encoded" namespace="webservice.test.sipstorm.com"/> | </input> | <output> | <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; use="encoded" namespace="webservice.test.sipstorm.com"/> | </output> | <fault name="TestException"> | <soap:fault name="TestException" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; use="encoded" namespace="webservice.test.sipstorm.com"/> | </fault> | </operation> | </binding> | >From what I've read, that seems like a reasonable mapping from the exception >(TestException) to a SOAP fault. Here's the response back to the client when the exception is thrown: | HTTP/1.1 500 Internal Server Error | X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418) | Content-Type: text/xml;charset=utf-8 | Date: Sun, 24 Oct 2004 01:49:29 GMT | Server: Apache-Coyote/1.1 | | Connection: close | | <?xml version="1.0" encoding="UTF-8"?> | <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> | <soapenv:Body> | <soapenv:Fault> | <faultcode>soapenv:Client</faultcode> | <faultstring>MBeanException: null Cause: com.sipstorm.test.webservice.TestException</faultstring> | <detail/> | </soapenv:Fault> | </soapenv:Body> | </soapenv:Envelope> | Without parsing the text out after the MBeanException part, there's really nothing meaningful in the AxisFault that the client catches. Is there something I'm missing? Any pointers / best practices would be greatfully accepted. Greg View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852448#3852448 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852448 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
