status of bug no 21930(Interoperability of axis with .net)

Hello, There is an open bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21930. The bug is about interoperability between .net and axis in case of wrappped literal. Can somebody please tell me what is the latest activity on this. It has become a blocker for a web service I am trying to develop

Re: MustUnderstand faults

Hi Chris, Srianth, and folks, It seems to me that we reache a consensus on a part of this matter. Chris, and I have made an equivalent response to Srianth, despite with two different point of views as "Acutial condition with Axis implementation" and "Idealized vision to accord with several speci

Re: MustUnderstand faults

Hi Cris Thanks for the posting... What you mean is if the handler want he can make the header added to be processed in down stream. Am quite agree with you. But what does SOAP spec say ... Should that handler process in the downstream or next handler..I feel the spec does not provide a clear cut

DO NOT REPLY [Bug 22209] - Content-Type: text/html; charset=ISO-8859-1 - cannot generate

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Possible date serialization bug

Hi all, I posted this on the axis-user list, but didn't get too much help. I think this may be a bug so I thought that I would post it here. What do you think? Thanks, Whitney _ According to the XML Schema 1.1 spec, the date datatype does not contain a time value: 3.2.9.1 Lexical repres

DO NOT REPLY [Bug 20294] - Axis doesn't maintain more than one cookie with http

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: MustUnderstand faults

In Axis... if you place the header in the request message and don't qualify the actor/role, then a handler will assume that it should be processed. I do not believe there is a facility for a handler to distinguish between the original headers sent by the client and headers added during proces

DO NOT REPLY [Bug 22507] - Request Headers not generated by WSDL2Java

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu