Re: VOTE: submission to 1.0 branch: cvs commit: xml-axis/java/src/org/apache/axis/encoding/serArraySerializer.java

Rick Rineholt wrote: > This seems to be a fairly safe fix and brings back functionality we had in > B3 and before. +1 - Sam Ruby

Re: VOTE: submission to 1.0 branch: cvs commit: xml-axis/java/src/org/apache/axis/encoding/serArraySerializer.java

+1 -Dug Rick Rineholt/Raleigh/IBM@IBMUS on 10/01/2002 11:12:48 AM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:VOTE: submission to 1.0 branch: cvs commit: xml-axis/java/src/org/apache/axis/encoding/ser ArraySerializer.java This seems to be a fairly

VOTE: submission to 1.0 branch: cvs commit: xml-axis/java/src/org/apache/axis/encoding/serArraySerializer.java

This seems to be a fairly safe fix and brings back functionality we had in B3 and before. Rick Rineholt "The truth is out there... All you need is a better search engine!" [EMAIL PROTECTED] -- Forwarded by Rick Rineholt/Raleigh/IBM on 10/01/2002 11:10 AM ---

Re: cvs commit: xml-axis/java/src/org/apache/axis/encoding/serArraySerializer.java

The "literal" encoding that you describe below matches how the current bean serializer/deserializer deals with indexed properties. So instead of changing the array serializer/deserializer, you just may need to change the bean serializer to treat arrays like indexed properties when the "literal" f

Re: cvs commit: xml-axis/java/src/org/apache/axis/encoding/serArraySerializer.java

Thanks for repairing this code. Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115) [EMAIL PROTECTED]