|
| Re: soap:headerFault not properly serialized? [message #195249 is a reply to message #195239] |
Sat, 30 June 2007 00:38  |
Eclipse User |
|
|
|
Originally posted by: valentinbaciu.hotmail.com
Yes, this appears to be similar to the MIME bug. It appears the
serialization code is missing. I'm speculating this stayed hidden because
the main client for the model is the WSDL editor and the editor is
manipulating the underlying DOM directly for all extensibility elements.
Please open a bug. Until we get a chance to fix it (best case scenario WTP
1.5.5 and/or 2.0.1) you can use the same approach to add the soap header
faults: manipulate the DOM directly.
Valentin
"Johann" <td_jbrun@yahoo.com> wrote in message
news:f642a2$vt6$3@build.eclipse.org...
> I'm programmatically generating a WSDL document using the
> org.eclipse.wst.wsdl libraries. I set up my
> soap:header object and add a soap:headerFault object to it. But when I
> serialize the WSDL document to a file, all I get
> is the soap:header element and no soap:headerFault element. I'm adding the
> soap:headerFault like so
>
> SOAPHeader soapHeader = SOAPFactory.eINSTANCE.createSOAPHeader();
>
> ...
>
> SOAPHeaderFault soapHeaderFault =
> SOAPFactory.eINSTANCE.createSOAPHeaderFault();
>
> ...
>
> soapHeader.getHeaderFaults().add(soapHeaderFault);
>
>
> Here's the result that I get.
> <wsdl:input>
> <soap:header encodingStyle="soapheaderencodingstyle style2"
> message="tns:m1" namespace="soapheadernamespace" part="part1"
> use="literal"/>
> </wsdl:input>
>
>
> Before serialization, I am able to browse into my Definition object in the
> debugger and confirm that the soap:HeaderFault object is contained in the
> soap:Header object.
>
> My org.eclipse.wst.wsdl plugin is v1.0.102.
>
> Is this an serialization problem similar to mime:multipartRelated, or am I
> doing something wrong?
>
> Thanks.
>
> Johann
>
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02314 seconds
] 
Search
Help
Register
Login
Home
