Status of enableMTOM=optional and Axis Faults / JIRA AXIS2-3340
Hi, about 10 month ago I filed a JIRA (AXIS2-3340) which describes a malfunctioning of Axis2-13. in error message creation when enableMTOM=optional and the input message is MTOM-formatted. JIRA indicates that there was no activity on this. Is this fixed in Axis2-1.4? In my opinion this is a serious issue because it prevents proper interaction of WSE3 client with axis2 services. I know that the true cause is at Microsoft which makes invalid assumptions about the type of message expected, but Microsoft apparently is not going to fix this reported bug in WSE3. Has anybody updates on this? Thanks, -Rainer
Re: Status of enableMTOM=optional and Axis Faults / JIRA AXIS2-3340
Hi Rainer, As I replied to Mark, may be you can start a thread in the dev list proposing to make Axis2 wrap the error messages with MIME when MTOM is enabled. Let's see the reaction of the community.. Personally I'm not a big fan of been bug compatible. But let's see the community reaction.. We have to think of interoperability with other web service stacks too... thanks, Thilina On Fri, Sep 5, 2008 at 6:03 AM, Menzner, Rainer [EMAIL PROTECTED] wrote: Hi, about 10 month ago I filed a JIRA (AXIS2-3340) which describes a malfunctioning of Axis2-13. in error message creation when enableMTOM=optional and the input message is MTOM-formatted. JIRA indicates that there was no activity on this. Is this fixed in Axis2-1.4? In my opinion this is a serious issue because it prevents proper interaction of WSE3 client with axis2 services. I know that the true cause is at Microsoft which makes invalid assumptions about the type of message expected, but Microsoft apparently is not going to fix this reported bug in WSE3. Has anybody updates on this? Thanks, -Rainer -- Thilina Gunarathne - http://thilinag.blogspot.com
Axis faults
Hi,
I have questions about SOAPFault generated by Axis that might be related:
1) When I throw my application exception (which is declared in the WSDL and SEI, and has
been generated by WSDL2Java) , Axis appends some elements like {http://xml.apache.org/axis/}exceptionName
with the server stack trace included it. Is it possible to disable this behaviour and configure Axis to not
append this ?
2) Axis put in the faultcode element a message like Server.* when I throw my custom exception.
Is is possible to control what's in the faultcode in my case it should be only Server ?
3) My input parameters are strongly typed and associated beans have been generated by WSDL2Java
task. When a deserialization error occurs an AxisFault is sent and I would like to throw my
custom fault. I guess the strategy for this is to write a handler which intercepts the soapfault
detach the AxisFault of the SOAPEnvelope and throw mine but is there a better way to do this ?
Thanks
Luc
Thanks
Luc
Log any/all Server Axis Faults
Is there any way that I can capture and log any/all Axis Fault messages on the server? These can come from any place, from serialization errors, to signature verification, etc. Is there a way to place a handler somewhere where these can be caught? Or some code to catch the fault? any way that I can do this, short of putting a TCP Monitor on it? I'm returning Axis faults to my Customer and I'd like to know what they look like? Any suggestions will be appreciated.
Re: Log any/all Server Axis Faults
aren't they all logged in your server logs (log4j or jdk1.4 logging)?
i see mine logged to the category org.apache.axis.EXCEPTIONS at DEBUG level:
0929:13:43:42 DEBUG org.apache.axis.EXCEPTIONS :AxisFault:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
com.amgen.seattle.appdev.freezer.webservice.server.SOAPHTTPBindingImpl.literalTest(SOAPHTTPBindingImpl.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
...
hth.
ron.
Is there any way that I can capture and log any/all Axis Fault messages
on the server? These can come from any place, from serialization
errors, to signature verification, etc. Is there a way to place a
handler somewhere where these can be caught? Or some code to catch the
fault? any way that I can do this, short of putting a TCP Monitor on
it?
I'm returning Axis faults to my Customer and I'd like to know what they
look like?
Any suggestions will be appreciated.
