Javax.jwsWebMethod documentation on WSDL - how?

Question

Hi experts,
On WebLogic 8.1, we put our Web Service documentation in the javadocs of the JWS files. That's very handy since the generated WSDL contains the documentation about the operations. So anyone that imports the WSDL is able to read the generated documentation. We do someting like:
     * This service does this and that and that. Detailed description that lives with the code.
     * @common:operation
     public void doTheThing(ThingInDocument inDoc) {
     delegate.doItInTheRoad(inDoc);
And the generated WSDL contains something like:
<s0:operation name="doTheThing">
<s0:documentation>
This service does this and that and that. Detailed description that lives with the code.
</s0:documentation>
Question: I'm not being able to do this in Weblogic 10.3. I put the javadoc next to the @WebMethod annotation, but nothing was generated in the WSDL.
Is there a way to do this or customize the WSDL generation?
Thank you!

Answer 1

Hi Massimo,
Quiet a few points here.
1. Oracle Type objects do not map to XML Complex type
2. Oracle Type objects do not map to Apex Page Item Types
3. Apex Page Item types are substituted into the WS Request XML by a process which is part of the Web Service Reference creation through the Wizard in Apex.
>
After created the web service (without any errors), I click on test.
- I can select the Operation --> CREATE_LINGUA
- I can input data for Basic Authentication
- I can't view Input Parameters --> Report returned no rows.
I've tried with normal type like Varchar2 and all was ok.
Is possible in Apex to use web services based on complex type, tipically an Array?
>
As you have guessed the Wizard driven Web Service Reference definition process cannot handle complex types of input parameters required by a Request. By definition the number of complex types possible are infinite, so they are not likely to come built in.
Passing an array is no solution because finally the values passed have to be plugged into the right SimpleTypes inside a ComplexType in the Request.
Based on your WSDL your Request will be
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cre="http://xmlns.oracle.com/orawsv/GRIMALDI/PKG_WEBSERVICES/CREATE_LINGUA">
   <soapenv:Header/>
   <soapenv:Body>
      <cre:SNUMBER-CREATE_LINGUAInput>
         <cre:PLINGUA-LINGUAT-CIN>
            <cre:LINGUAT>
               <cre:CODICE>?</cre:CODICE>
               <cre:DESCRIZIONE>?</cre:DESCRIZIONE>
            </cre:LINGUAT>
         </cre:PLINGUA-LINGUAT-CIN>
      </cre:SNUMBER-CREATE_LINGUAInput>
   </soapenv:Body>
</soapenv:Envelope>However, all is not lost. You can always use the UTL_HTTP package API to construct your Request.
Regards,