Yes, please post the fixes or send directly to me and I can then merge in 
the fixes for all to share.  It would be appreciated.

Nadir K. Amra


Franz Fehringer <[EMAIL PROTECTED]> wrote on 10/20/2006 03:46:00 AM:

> I sent the email direct to the original poster.
> Was there any reaction om John Hawkins answer?
> 
> Franz
> 
> 
> -------- Original-Nachricht -------- 
> 
> Betreff: 
> 
> RE: Apache Axis 1.6b
> 
> Datum: 
> 
> Tue, 10 Oct 2006 12:38:46 +0100
> 
> Von: 
> 
> John Hawkins <[EMAIL PROTECTED]>
> 
> 
> [email protected]
> 
> Wow ! Excellent - well done and thanks ! 
> I suggest you create a JIRA and attach the files to that. 
> 
> 
> 

> 
> "Haiping Zhao" <[EMAIL PROTECTED]> 
> 09/10/2006 18:06 
> 
> Please respond to
> [email protected]
> 
> To
> 
> <[email protected]> 
> 
> cc
> 
> Subject
> 
> RE: Apache Axis 1.6b
> 
> 
> 
> 
> Hi, 
> 
> We have adopted Apache Axis C++ 1.6b since around Februry of this 
> year, and we have made quite a few bug fixes and improvements. Where
> can I submit those? 
> 
> Here are some of them, 
> 
> 1. Fixed incorrect large packet handling in three transports: apache
> 2.0 transport, simple axis transport and axis client transport. 
> 2. Fixed XML unrepresentable character handling on outbound. 
> 3. Fixed a crash on apache shutdown from module unloading. 
> 4. Fixed some bugs from code generation tool wsdl2ws: 
> 
>     (1) incorrect <all> parsing; 
>     (2) weak <choice> parsing; 
>     (3) missing required element checking; 
>     (4) bad header include when array is xsd__string_array; 
>     (5) wrong xsd__int enumeration code; 
>     (6) memory leaking code. 
> 
> 5. Fixed bugs in XMLParserXerces.cpp: 
> 
>     (1) not throwing SAX parser exceptions; 
>     (2) incorrect end tag handling. 
> 
> 6. Supporting JSON and XML input and output, in addition to SOAP ones. 
> 7. Supporting pretty print of SOAP/XML/JSON formats. 
> 8. Supporting getting IP address and HTTP cookies from transport layer. 
> 
> 
> 
> Haiping Zhao 
> 
> Computer never make mistakes.
> 
> 赵海平
> Server Architect 
> 
> Plaxo, inc. 
> 

Reply via email to