Looks like servlet filter is the way to go. See related discussion: http://archive.xfire.codehaus.org/user/45D34502.4030804%40fluid.com
First need to change HTTP return code to 200 and after that presumably Flex would be able to get into SOAP body and extract exception info. Didn't have chance to try it out yet, but based on comments it should work for XFire or Axis. Regards, rd --- In [email protected], "Chua Chee Seng" <[EMAIL PROTECTED]> wrote: > > How about Axis? Is it possible for me to get the custom application > exception info thrown? I check the wsdl it is well describe > by 'fault', any idea how flex web service handle the custom 'fault' > complex type describe in wsdl? > > Thanks > Chee Seng > > --- In [email protected], "lepusmars" <paul@> wrote: > > > > throw new XFireFault("Fault String", XFireFault.SENDER); > > > > This is how we do it. There are also methods for adding more details > > to the Exception that get passed on the response. Check out the > > javadoc for more details. > > > http://envoisolutions.com/xfire/api/org/codehaus/xfire/fault/XFireFaul > t.html > > > > pd > > > > --- In [email protected], "roman_dolgov" <roman_dolgov@> > > wrote: > > > > > > Does anybody has an example (using XFire WS implementation but > really > > > any similar env would be helpful too) how to properly pass > exception > > > information from web services to flex and make sure that "fault" > > > handler receives faultDetail/faultString populated with meaningful > > > data (some application specific error code/messages)? > > > > > > Thanks > > > rd > > > > > >
