snichol 2003/06/20 22:24:08
Modified:java/src/org/apache/soap/server DefaultConfigManager.java
ServiceManager.java XMLConfigManager.java
Log:
Distinguish between the inability to open a config file ("assume fresh
start") and the inability to read its content
I recently tried upgrading to the latest nightly build of SOAP (June 20,
2003) from 2.2. I needed this to support HTTPS over a proxy server.
The problem I had was that it suddenly started using a different SOAP
serializer type for byte[] content (Base64Serializer instead of Base64).
I had to chan
Perhaps more to the point is what the xsi:type attribute is set to for
the byte[] element I'm trying to send:
SOAP 2.2:
http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="ns2:base64">
SOAP 2.3.1 June 20 Nightly Build:
Can I force it to use the old ns2:base64 type?
-Original Message
History:
When Apache SOAP (actually, IBM SOAP4J) started, it was based on the
SOAP and XML Schema specs of the day. Since XML Schema did not
define a type for Base64 encoded data, the SOAP spec defined one, and
that was the type Apache SOAP used. By Apache SOAP 2.2, there were
also 2000 and
Thanks for the detailed explanation. I've set my clients to use the
1999 schema. This seems to work.
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 1:45 PM
To: [EMAIL PROTECTED]
Subject: RE: Base64 --> Base64Serializer - Why?
History:
Wh
