Are there any known problems in using xsd:base64Binary as a return type
for a service operation call? For example, this service :
<service name="urn:CasperService" provider="java:RPC">
<operation name="execute" returnQName="returnqname"
returnType="xsd:base64Binary" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >
<parameter name="versionInfo" type="xsd:string"/>
<parameter name="className" type="xsd:string"/>
<parameter name="methodName" type="xsd:string"/>
<parameter name="minMemory" type="xsd:string"/>
<parameter name="maxMemory" type="xsd:string"/>
<parameter name="arg" type="xsd:base64Binary"/>
<\operation>
...
<\service>
used to work under axis1.2 but after moving to axis 1.4 a
SAXParseException (XML document structures must start and end within
the same entity) occurs on the return of the service cal, when
apparently, the response is being parsed. Any insight, knowledge or
feedback would be appreciated.
thanks.
rp johns
software factotum
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
