Generating Web Service with SOAP Header

Question

Hello,
I have a WSDL for a web Service using document encoding and with a soap header.
I generate a jws file using WL Workshop 81.SP4 but I always have this error message :
ERROR: AjoutContactService.jws:13: The binding for AjoutContact does not declare one part.
ERROR:      SUGGESTION: A document literal binding must have at most one part. Make sure you have a WSDL that declares just one part for each message with a document literal binding.
The header is a recent adding on an existing Web Service, and I can't change the wsdl definition. I also need to use data contained by the header in conjunction with data in the body.
Is it a limitation with workshop or a problem with with my binding file ?
I give sample of my two wsdl files.
Given wsdl file
     <wsdl:message name="inputAjoutContact">
          <wsdl:part name="body" element="xsdin:NouveauContact"/>
<wsdl:part name="header" element="xsdinhead:EnTeteRequete"/>          
     </wsdl:message>
     <wsdl:message name="outputAjoutContact">
          <wsdl:part name="body" element="xsdout:StatutAjoutContact"/>
     </wsdl:message>
     <wsdl:message name="faultAjoutContact">
          <wsdl:part name="body" element="xsdfault:Exception"/>
     </wsdl:message>
     <wsdl:portType name="AjoutContactPortType">
          <wsdl:operation name="AjoutContact">
               <wsdl:input name="ParametresEntree" message="tns:inputAjoutContact"/>
               <wsdl:output name="ParametresSortie" message="tns:outputAjoutContact"/>
               <wsdl:fault name="ParametresException" message="tns:faultAjoutContact"/>
          </wsdl:operation>
     </wsdl:portType>
binding file
          <wsdl:operation name="AjoutContact">
               <soap:operation soapAction="urn:#AjoutContact"/>
               <input>
<soap:header part="header" use="literal"/>
<soap:body parts="body" use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
<fault name="ParametresException">
<soap:fault use="literal" name="ParametresException" />
</fault>
     </wsdl:operation>

Answer 1

Hi,
This appears to be a known limitation and is addressed by CR227689
which has a workaround that needs the wsdl to be modified.
I am not sure if this is possible given that we don't control the wsdl most times.
Could you please open a BEA support case and refer to CR227689?
Vimala-
p.s:
I found some info on the issue which could help:
1) Refer to <http://lists.oasis-open.org/archives/regrep/200306/msg00071.html>
you will see that only one part is allowed in the message part for doc/literal webservices Snippet from the above link
"Also, keep in mind that WS-I BP permits only one <part> on document/literal messages, so to be WS-I compliant, you would have to include it in the message structure. "
2) Refer to http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html#refinement35722968 <http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html>
below R2208)
"For document-literal bindings, the Profile requires that at most one part, abstractly defined with the element attribute, be serialized into the soap:Body element."
This implies Soap body contains message which contains a at most one part.