> For
> now, it is "\n" for backward compatibility, but do not rely on that!
It's only perfectly compatible for folks working on platforms for which
the line.separator System property is \n. This changes things for those
on others, such as Windows where it is \r\n.
What I really meant is tha
snichol 2002/11/18 13:52:06
Modified:java/src/org/apache/soap Body.java Envelope.java Fault.java
Header.java
java/src/org/apache/soap/encoding/literalxml
XMLParameterSerializer.java
java/src/org/apache/soap/enc
snichol 2002/11/06 07:11:08
Modified:java/samples/stringarray StringArrayClient.java
java/src/org/apache/soap AttributeHandler.java Body.java
Envelope.java Fault.java Header.java
java/src/org/apache/soap/encoding SOAPMappingRegistry.j
sanjiva 2002/10/28 08:50:53
Modified:java/src/org/apache/soap/encoding SOAPMappingRegistry.java
java/src/org/apache/soap/encoding/soapenc
BeanSerializer.java SoapEncUtils.java
java/src/org/apache/soap/rpc RPCMessage.java
Log:
chan
snichol 2002/10/02 07:05:52
Modified:java/src/org/apache/soap/rpc RPCMessage.java
Log:
Do not emit a line separator after closing the response element. This was
being parsed as a text node child of the SOAP Body element by some
implementations (SilkPerformer for .NET and Sun's
rubys 02/01/20 16:07:25
Modified:java/src/org/apache/soap/rpc RPCMessage.java
Log:
Pass the actual encoding style on the Call constructor. Solves a
literal XML interop problem with pocket soap.
Submitted by: Simon Fell <[EMAIL PROTECTED]>
Revision ChangesPath
1.16
