Document type service

Question

We are trying to create a document type service meaning we want to transmit a document
as is. The webservices documentation states:
"RPC-oriented WebLogic Web service operations use SOAP encoding. Document-oriented
WebLogic Web service operations use literal encoding."
Our service method signature is:
public void processCreditApp(String document)
We change our web-services.xml to include: style="document" in the web-service
element and invocation-style="one-way" in the operation element.
The client generated builds a SOAP message with the body content typed as a string:
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<xsd:string>HelloWorld</xsd:string>
</env:Body>
</env:Envelope>
We had expected the content of the body not to be typed with <xsd:string> tags.
Likewise
the generated web service is expecting this typing.
Have the corect assumptions about "literal encoding"? Have we left out any necessary
steps or settings?
We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.

Answer 1

I am not sure I understand. The SOAP body we receive does not have a type designation:
<SOAP:Body>
<diag:Diagnostic
xmlns:diag="http://www.someName.com/namespace.messaging.diag#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<diag:DiagnosticMessage>
     <diag:RequestMessage>HelloWorld</diag:RequestMessage>
</diag:DiagnosticMessage>
     <diag:SourceIdentifier>MySource</diag:SourceIdentifier>
</diag:Diagnostic>
</SOAP:Body>
How can we map types for this?
Steve
"Karthik V" <[email protected]> wrote:
Just by changing "rpc" to "document" in web-services.xml will not help.
You missed <types> and <type-mapping> elements.
I guess your <operation> still has input param type as xsd:string.
You should change this to new type that you create to represent your
document.
Alternatively, you could servicegen with style="document" and take a
look
at the generated web-services.xml.
That will give you a better idea.
/k
"Steve Watson" <[email protected]> wrote in message
news:[email protected]...
We are trying to create a document type service meaning we want totransmit a document
as is. The webservices documentation states:
"RPC-oriented WebLogic Web service operations use SOAP encoding.Document-oriented
WebLogic Web service operations use literal encoding."
Our service method signature is:
public void processCreditApp(String document)
We change our web-services.xml to include: style="document" in theweb-service
element and invocation-style="one-way" in the operation element.
The client generated builds a SOAP message with the body content typedas
a string:
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<xsd:string>HelloWorld</xsd:string>
</env:Body>
</env:Envelope>
We had expected the content of the body not to be typed with <xsd:string>tags.
Likewise
the generated web service is expecting this typing.
Have the corect assumptions about "literal encoding"? Have we leftout
any necessary
steps or settings?
We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.