Problem with WSDL

Hai,
I created an EJB Project , I created web services for Session beans . I deployed it . this web services are working very fine in navigator. but when i use this web services in a third party tool its giving problem.
in that tool it recognize only one wsdl file. but in my case webAS is generating 3 wsdls
- one WSDL that defines the concrete endpoint
- one WSDL that defines the binding
- one WSDL that defines the abstract interface (with operations and
My requirement is to generate a singlw wsdl file using those 3 wsdls . please help me out to solve this problem.
regards,
Naga Raju

Hi John,
I don't have a direct solution for your problem.
But, using Axis in conjunction with Castor, for serialisation/deserialisation, it was mandatory to server just the types schema to Castor (in a separate file) and import them into the everything encompassing wsdl. A, then used xml import statement follows, and might be useful to indirectly solve your wsdl problem too:
<xsd:import namespace="urn:x.y.com"schemaLocation="file:///C:/projects/ws/x.y.xsd"/>
Best Regards
Gregor

Similar Messages

Problem with WSDL generated with wscompile JAX-RPC

Ok well I have successfully built a Web Service (From an existing wsdl) and Static Stub Client they work perfectly. I then I tried to connect to it using a Delphi Web Service Client. The client cant change, the problem I am getting is it is requesting using the variable name I am using and the WSDL has String_1.
Ie. it gives me:
unexpected element name: expected=String_1, actual= {targetNameSpace} [Variable Name]
I suspect this is a problem with how the WSDL is generated any suggestions?

THanks for the response, I originally used axis WSDL2Java. And only used the interface class. I think this is where my whole thing fell down. Although this worked with a static stub client that I used.
I have now generated the server side java files using wscompile and am l looking how to implement the server. It doesn't look like it has a implementation class there. And there isn't much information on how to do it.

Problem with WSDL file generated by PI for sender SOAP

I have a scenario SOAP to idoc that I am trying to test in PI7.1. I have created my objects in the ESR and completed the configuration in IB. When I test the configuration in IB, the data passes through PI to ECC correctly.
Now I want to export the WSDL file from the Sender Service Interface being used for this scenario and test it using SOAPUI. However, when I look at the WSDL file proposed by PI, there is no SOAP URL proposed in the WSDL. My understanding from looking at other threads in the the forum is that the URL should be proposed in the WSDL file, and I can then export this WSDL file to my PC, and upload it into SOAPUI for testing.
Why is the URL not being proposed in my WSDL file?
Thanks in advance for any help.
Terri

Thanks Baskar that solved part of the problem.
When I use this newly generated WSDL file for testing in SOAPUI, I now get an error 401, which I believe has something to do with needing a user id and password. However, my scenario is not setup to require a userid or password. Any other help would be appreciated.
Below is the actual results from SOAPUI:
HTTP/1.1 401 Unauthorized
server: SAP NetWeaver Application Server 7.11 / AS Java 7.11
www-authenticate: Basic realm="XISOAPApps"
connection: close
pragma: no-cache
content-type: text/html;charset=ISO-8859-1
content-encoding: gzip
date: Thu, 03 Mar 2011 22:49:56 GMT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
     <title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link
A:visited
A:active
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
    <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  401 &nbsp Unauthorized</b></font></td>
</tr>
<tr bgcolor="#3F73A3">
    <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
    <td height="23"><img width=1 height=1 border=0 alt=""></td>
    <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP NetWeaver Application Server 7.11 / AS Java 7.11 </b></font></td>
</tr>
<tr bgcolor="#9DCDFD">
    <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
<br><br><br><br><br><br>
<p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  Error: Unauthorized<p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><b>  Troubleshooting Guide <a href="https://sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home">https://sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home</a></p><p></b></font></p>
<p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>No details available</PRE></font></td></tr></table></font></p>
</body>
</html>

Problem with WSDL file

Hi,
I'm new with web services and want to publish a stateless Java class as web service.
I've created the WSDL file by means of the Web Service Publishing Wizard.
when I run the "Web service stub/Skeleton Wizard" in step 1 of 2 appears the following warning message:
"WSDL validation failed with the following exception:
oracle.xml.parser.v2.XML.ParseException:
Withespace required".
Some idea ??
Thanks in advance
Alejandro von Eckenbrecher
[email protected]

Mike,
I'm working with the example of OTN "Publish a Stateless Pure Java Web Service".
I've find that the WSDL file is not being generated correctly, the latest two lines are:
<binding name="HelloImplBinding" type="tns:HelloImplPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"
If I manually correct them as these:
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
</definitions>
(add the tags in bold),the XML parser don't report erros and can run the stub/skeleton wizard but in step 2 of 2 don't find any service.
I believe that the problem this in the WSDL file but them
are generated automatically from the example files.
below will find the complete file for reference.
Thanks
Alejandro
<?xml version = '1.0' encoding = 'UTF-8'?>


<definitions
name="HelloImpl"
targetNamespace="http://HelloImpl.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://HelloImpl.wsdl"
xmlns:ns1="http://IHelloImpl.xsd">
<types>
<schema
targetNamespace="http://IHelloImpl.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"/>
</types>
<message name="sayHello0Request">
<part name="param" type="xsd:string"/>
</message>
<message name="sayHello0Response">
<part name="return" type="xsd:string"/>
</message>
<portType name="HelloImplPortType">
<operation name="sayHello">
<input name="sayHello0Request" message="tns:sayHello0Request"/>
<output name="sayHello0Response" message="tns:sayHello0Response"/>
</operation>
</portType>
<binding name="HelloImplBinding" type="tns:HelloImplPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"

Output Variable - Type: Date - Problem with WSDL in Designer

Greetings,
We are seeking some information about the following:
We have a process in Process Designer that has and output variable of the type: Date. When the process is activated and we connect to a WSDL in LC ES Designer we get both a DATE and CALENDAR in the Data View.
Hope that is at least somewhat clear. Please respond with any help or questions.
Thanks,
Rick Kuhlmann
Tech-Pro

This is to distinguish between java.util.Date and java.util.Calendar types. If the date is returned as java.util.Date, it will be in the DATE.date field. If the date is returned as java.util.Calendar, it will be in the DATE.calendar field.
There are a bunch of xPath dates function in the xPath builder you can use.
Jasmin

Problem with wsdl publishing

Hi,
I have been able to generate a wsdl file, added a wsdl.location property name-value pair in xxx_config.properties file. Now I am able to see wsdl file published at http://localhost:7001/testwebservices/test?WSDL
The problem i am facing is - only a part of wsdl file is getting published. It shows me an error after publishing a part of it.
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Reference to undeclared namespace prefix: 'wsdl'. Error processing resource 'http://localhost:7001/testwebservices/test?WSDL'. Line 183, Position 170
<attribute xmlns:tns="http://java.sun.com/jax-rpc-ri/internal" xmlns="http://www.w3.org/2001/XMLSchema" ref="soap-enc:arrayType" wsdl:arrayType="anyType[]"/></restriction></complexContent></complexType>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------^
The part wsdl file to which it refers to it is --
<complexType name="collection">
<complexContent>
<restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="anyType[]"/></restriction></complexContent></complexType>
Could u please help in solving this..
Thanking u in anticipation,
tinu

This element was already present. Here is my wsdl file.
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="TestService1" targetNamespace="http://dam.org/wsdl" xmlns:tns="http://dam.org/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns2="http://dam.org/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<types>
<schema targetNamespace="http://dam.org/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal" xmlns:tns="http://dam.org/types" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="http://java.sun.com/jax-rpc-ri/internal"/>
<complexType name="WorkflowSerial">
<sequence>
<element name="opFlag" type="string"/>
<element name="actions" type="ns2:vector"/>
<element name="busObjTypeId" type="long"/>
<element name="status" type="long"/>
<element name="states" type="ns2:vector"/>
<element name="roleUsers" type="ns2:vector"/>
<element name="lockedBy" type="string"/></sequence></complexType>
<complexType name="WFException">
<complexContent>
<extension base="tns:UserException">
<sequence>
<element name="messages" type="string"/></sequence></extension></complexContent></complexType>
<complexType name="UserException">
<sequence>
<element name="maxSeverity" type="int"/>
<element name="errors" type="ns2:collection"/>
<element name="data" type="anyType"/>
<element name="message" type="string"/>
<element name="localizedMessage" type="string"/></sequence></complexType></schema>
<schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://java.sun.com/jax-rpc-ri/internal" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="http://dam.org/types"/>
<complexType name="vector">
<complexContent>
<extension base="tns:list">
<sequence/></extension></complexContent></complexType>
<complexType name="list">
<complexContent>
<extension base="tns:collection">
<sequence/></extension></complexContent></complexType>
<complexType name="collection">
<complexContent>
<restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="anyType[]"/></restriction></complexContent></complexType></schema></types>
<message name="WorkFlowManagerIF_init"/>
<message name="WorkFlowManagerIF_initResponse"/>
<message name="WorkFlowManagerIF_wfGetDetailInstActionsOnly">
<part name="long_1" type="xsd:long"/>
<part name="String_2" type="xsd:string"/></message>
<message name="WorkFlowManagerIF_wfGetDetailInstActionsOnlyResponse">
<part name="result" type="ns2:WorkflowSerial"/></message>
<message name="WFException">
<part name="WFException" type="ns2:WFException"/></message>
<portType name="WorkFlowManagerIF">
<operation name="init" parameterOrder="">
<input message="tns:WorkFlowManagerIF_init"/>
<output message="tns:WorkFlowManagerIF_initResponse"/></operation>
<operation name="wfGetDetailInstActionsOnly" parameterOrder="long_1 String_2">
<input message="tns:WorkFlowManagerIF_wfGetDetailInstActionsOnly"/>
<output message="tns:WorkFlowManagerIF_wfGetDetailInstActionsOnlyResponse"/>
<fault name="WFException" message="tns:WFException"/></operation></portType>
<binding name="WorkFlowManagerIFBinding" type="tns:WorkFlowManagerIF">
<operation name="init">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://dam.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://dam.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="wfGetDetailInstActionsOnly">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://dam.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://dam.org/wsdl"/></output>
<fault name="WFException">
<soap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://dam.org/wsdl"/></fault>
<soap:operation soapAction=""/></operation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/></binding>
<service name="TestService1">
<port name="WorkFlowManagerIFPort" binding="tns:WorkFlowManagerIFBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>

Problems with WSDL file from Webservice definition

Hi all,
I trying to import into XI the WSDL file from a web service. I´m doing it following the blog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
But I do not why but it is not creating the messages.
Any Idea,
Many thanks and Regards
Noelia

Hi thnaks for your help!!
this is the wsdl file. I think this is correct,but i´m not very familiar with this!
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:WS_ExtraccionNombramientoVi" targetNamespace="urn:WS_ExtraccionNombramientoWsd/WS_ExtraccionNombramientoVi/document" xmlns:tns="urn:WS_ExtraccionNombramientoWsd/WS_ExtraccionNombramientoVi/document">
<wsdl:types>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:WS_ExtraccionNombramientoVi" xmlns:tns="urn:WS_ExtraccionNombramientoVi" elementFormDefault="qualified">
      <xs:element name="ejecutarExtraccionNS">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="fechaExplotacion" type="xs:string" nillable="true"/>
            <xs:element name="tipoXML" type="xs:string" nillable="true"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="ejecutarExtraccionNSResponse">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Response" type="xs:string" nillable="true"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:schema>
</wsdl:types>
<wsdl:message name="ejecutarExtraccionNSIn_doc">
    <wsdl:part name="parameters" element="ns0:ejecutarExtraccionNS"/>
</wsdl:message>
<wsdl:message name="ejecutarExtraccionNSOut_doc">
    <wsdl:part name="parameters" element="ns0:ejecutarExtraccionNSResponse"/>
</wsdl:message>
<wsdl:portType name="WS_ExtraccionNombramientoVi_Document">
    <wsdl:operation name="ejecutarExtraccionNS">
      <wsdl:input message="tns:ejecutarExtraccionNSIn_doc"/>
      <wsdl:output message="tns:ejecutarExtraccionNSOut_doc"/>
    </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Regards Noelia

Problem with Composition Tutorial

Hi at first,
I am new to this forum as well as new to the SAP composition application topics
Since I want to learn how to build composite applications with the Netweaver Developer Studio/ Process Composer I started with the tutorial "Getting Started with Composite Designer" included in the Studio.
If I follow the instructions up to modeling of data objects the final step of generating the tables of the emplserv.bl.caf package fails with the error message:
com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
Problem with WSDL file parsing. See nested message.
IO Exception occurred while parsing file:unknown protocol: c
unknown protocol: c
Can anyone help me with this problem?
Thanks in advance

Hi Felixw,
You are probably using JDK 1.6 instead of JDK 1.5.
Please adjust the startup -vm parameter to be the javaw.exe of JDK 1.5 and you are just fine!
For instance:
C:\IDE\eclipse\SapNetweaverDeveloperStudio.exe -vm "c:\jdk1.5.0_18\bin\javaw.exe"
Kind regards,
Ivan

Problem with old namespace in WSDL file

I have a problem with my WSDL file. My scenario is SOAP to IDOC.
Originally the ESB data types were configured under namespace urn:test1:xxx for development purposes. When it came time to implement and test, we copied the data types from the old name space to a new namespace http://company.com:interface.
After the new objects were created, all the old test objects were deleted, including the old namespace definition. Now when I generate the WSDL file, the top part of the WSDL file looks correct, but toward the bottom, there are references to the old namespace.
Does anyone know why these reference are appearing, and is there any way to correct this without deleting all my objects and rebuilding everything?
Thanks in advance for any help. Will award points for help.
Terri

Found the problem....the XML namespace in the Message type still contained the old namespace. When this was changed to the new namespace, second target namespace was no longer generated.

Problem with RPC/encoded WSDL

I'm having trouble calling a web service that is based on an RPC-encoded WSDL. I've already made slight changes to the WSDL, so that I get a work-able message type for mapping purposes. These changes are based on <a href="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272"><b>soapenc:Array</b> recommendations in WSDL 1.1 Section 2.2</a> for declaration of array types.
Here's a snippet of the WSDL:
<wsdl:definitions ...>
<wsdl:types>
    <schema ...>
      <complexType name="ArrayOf_tns1_ServiceOption">
        <complexContent>
          <restriction base="soapenc:Array">
            <attribute ref="soapenc:arrayType"
              wsdl:arrayType="tns1:ServiceOption[]"
              xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
          </restriction>
        </complexContent>
      </complexType>
    </schema>
    <schema ...>
      <complexType name="ServiceOption">
        <sequence>
          <element name="key" nillable="true"
                    type="xsd:string"/>
          <element name="value" nillable="true"
                    type="xsd:string"/>
        </sequence>
      </complexType>
    </schema>
</wsdl:types>
</wsdl:definitions>
I've changed it to:
<wsdl:definitions ...>
<wsdl:types>
    <schema ...>
      <complexType name="ArrayOf_tns1_ServiceOption">
        <sequence>
          <element name="ServiceOption"
                    type="tns1:ServiceOption"
                    minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </complexType>
    </schema>
    </schema>
    <schema ...>
      <complexType name="ServiceOption">
        <sequence>
          <element name="key" nillable="true"
                    type="xsd:string"/>
          <element name="value" nillable="true"
                    type="xsd:string"/>
        </sequence>
      </complexType>
    </schema>
</wsdl:types>
</wsdl:definitions>
The above changes have allowed me to make message mappings. But the I still get an error when sending a request to the web service. It seems that it requires the <b>xsi:type</b> and <b>soapenc:arrayType</b> attributes for arrays.
<b>How can I create these attributes? How does XI handle RPC-encoded WSDLs?</b> I haven't encountered these problems with document-literal WSDLs.
Thanks in advance.

Hi Lorenzo,
the extended support of rpc-style does <b>not</b> include the support of soapenc:array. It just addresses the root of the message and its direct children (as discussed in the thread where I added this hint).
In the documentation of External Definitions you can find a hint where to find a list of supported XSD/DTD/WSDL-features. However, also there you will find no hint on the fact that soapenc:array is not supported. The reason for this is, that soapenc:array is specified in none of these standards. It is some artifact that SOAP smuggled into XSD. For good reasons WS-I prohibits the use of this artifact.
Hence, if you need support for argumentation I can only point out the WS-I document I already linked.
Greetings
Stephan

Problems getting Reader (9.4 and up) to interact with WSDL, rights-enabled or not

Somehow I must be doing something wrong - My form works just fine in Designer,
Preview, Acrobat Pro, etc as expected. When I open the form in Reader, I am not gett
ing my data back. I have rights-enabled the form, still no go. Am I mis
sing something? Any suggestions appreciated!

Thanks - Adobe is certainly misleading about what & where they are calling
Reader Extension. Grrr. Thanks so much for your answer!
Tabi Freedman
Developer
BTS-PAS
P. 212-919-3135 M. 917-370-7229
7 Hanover Square H-4-A, New York, NY 10004
The Guardian Life Insurance Company of America
GuardianLife.com
From:   pguerett <[email protected]>
To:     Tabi M Freedman <[email protected]>
Date:   07/29/2011 01:42 PM
Subject:        Problems getting Reader
(9.4 and up) to interact with WSDL, rights-enabled or not
Thats your issue .....Acrobat does not add the right to enabe Web Services
in Reader. That can only be done via LiveCycle Reader Extensions.
Paul

Problem with Consuming ABAP Server Proxy WSDL in InfoPath

Tried to design a InfoPath (MS Office 2003) form from a WSDL file of a web service generated from an ABAP Server Proxy in a NW2004s SP10 system. InfoPath rejected this WSDL with error InfoPath cannot use the selected Web service method for receiving data because the method does not provide valid XML data. Tried other WSDL files from other web services from ABAP Proxy with InfoPath, all got rejected.
Validated the WSDL file with XMLSPY, no error. Tried to import the WSDL into XI 3.0, no error. Also tried the WSDL in .NET C#, also worked fine. It seemed only InfoPath does not like this WSDL from ABAP Proxy.
Created a similar web service in XI 3.0 and InfoPath had no problem with its WSDL. Then I compared the two WSDL files. There are differences. After try and error on changing the differences, I have nailed down to the XML tag that caused the problem. Please see the extracted WSDL line attached at the end. In the XI 3.0 generated WSDL the wsdl:message and the wsdl:part have the same name. In the ABAP Proxy generated WSDL the wsdl:part has the name Parameters which is different from the wsdl:message. After I copied the wsdl:message name to the wsdl:part name, InfoPath accepted the WSDL file without any problem.
I know the fix but I like to find out the root cause. Is this a known issue? Did we miss some configuration setting thats causing this issue? Any help will be much appreciated.
WSDL from NW2004s SP10 ABAP Proxy
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="Parameters" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name=" Parameters" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>
WSDL from XI 3.0 Interface
<wsdl:message name="RegionR3GetList_Req_MT">
    <wsdl:part name="RegionR3GetList_Req_MT" element="tns:RegionR3GetList_Req_MT"/>
</wsdl:message>
<wsdl:message name="RegionR3GetList_Resp_MT">
    <wsdl:part name="RegionR3GetList_Resp_MT" element="tns:RegionR3GetList_Resp_MT"/>
</wsdl:message>

Anne Tarnoruder has pointed out to me that her SDN article "Consuming SAP Enterprise Services in a Microsoft Office InfoPath Form" has described the the cause and workaround of this issue on page 9. I am extracting it below and mark this thread as answered. Thanks to Anne but not sure how I can award point to her.
Currently SAP supports only the Document style of WSDL, and not the Microsoft-specific RPC style, which causes a problem when consuming SAP services in the Microsoft environment. In this example, you need to apply a workaround that involves a minor correction of locally-stored WSDL files:
a. In the Project Explorer toolbar, click the Show all files icon and expand the Web reference folder.
b. For each Web reference in the project, perform the following steps:
c. Open the WSDL file, replace all instances of <wsdl:part name="parameters" with <wsdl:part name="parameter" (remove the s in parameters) and save the file.
d. Right-click the Reference.map file and choose Run Custom Tool to invoke a utility that generates code for XML Web services. This recreates the local proxy.

PI - Problem with a receive WSDL message with encode (envelope)

Hello,
I'm having a ploblem with a PI interface with the scenario below (synchronous):
ECC (proxy) <-> PI <-> 3rdParty (soap)
The WSDL provided has a kind of envelope (soapenc:arrayType). Here's the structure declaration:
         <xs:complexType name="TTUDResultArray">
            <xs:sequence>
               <xs:element name="Success" type="xs:boolean" />
               <xs:element name="ErrorDescription" type="xs:string" />
               <xs:element name="Count" type="xs:int" />
               <xs:element name="Accounts" type="ns1:TTUDInquiryResultArray" />
            </xs:sequence>
         </xs:complexType>
         <xs:complexType name="TTUDInquiryResultArray">
            <xs:complexContent>
               <xs:restriction base="soapenc:Array">
                  <xs:sequence />
                  <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TTUDInquiryResult[]" />
               </xs:restriction>
            </xs:complexContent>
         </xs:complexType>
When I import this WSDL as a External Definition, the field Accounts is displayed with error (in red), as the PI was incapable to read this kind of type definition.
Testing in SoapUI, the response message is displayed with a different structure than it's possible to see in the PI Operation Mapping:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:NS2="urn:TUDIntf">
      <NS1:InquireDateRangeResponse xmlns:NS1="urn:TUDIntf-ITUD">
         <return href="#1"/>
      </NS1:InquireDateRangeResponse>
      <NS2:TTUDResultArray id="1" xsi:type="NS2:TTUDResultArray">
         <Success xsi:type="xsd:boolean">true</Success>
         <ErrorDescription xsi:type="xsd:string"/>
         <Count xsi:type="xsd:int">2</Count>
         <Accounts xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="NS2:TTUDInquiryResult[2]">
            <item href="#2"/>
            <item href="#3"/>
         </Accounts>
      </NS2:TTUDResultArray>
      <NS2:TTUDInquiryResult id="2" xsi:type="NS2:TTUDInquiryResult">
         <AvailableAmount xsi:type="xsd:double">49</AvailableAmount>
         <PaymentAmount xsi:type="xsd:double">49</PaymentAmount>
         <PaymentStatus xsi:type="xsd:string">AC</PaymentStatus>
         <PaymentNbr xsi:type="xsd:string">110201</PaymentNbr>
         <Success xsi:type="xsd:boolean">false</Success>
      </NS2:TTUDInquiryResult>
      <NS2:TTUDInquiryResult id="3" xsi:type="NS2:TTUDInquiryResult">
         <AvailableAmount xsi:type="xsd:double">50</AvailableAmount>
         <PaymentAmount xsi:type="xsd:double">50</PaymentAmount>
         <PaymentStatus xsi:type="xsd:string">AC</PaymentStatus>
         <PaymentNbr xsi:type="xsd:string">123456</PaymentNbr>
         <Success xsi:type="xsd:boolean">false</Success>
      </NS2:TTUDInquiryResult>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I`ve tried to map the WSDL inside my interface, but always I test (on SPROXY or Runtime Workbench) an error message is displayed:
Error While Sending Message: Error stack from response: Runtime exception occurred during application mapping com/sap/xi/tf/_mmInquireEZCashtoEcc_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:mtInquireEcc_response. Values missing in queue context. Targe~
Someone knows if that's some tip of how to use this kind of WSDL?

Hello,
Looks like an RPC style WSDL to me. Can you ask the third-party to provide you with a document-literal wsdl? You can refer to the points mentioned by Stephan in this thread.
Problem with RPC/encoded WSDL
Thanks to Raj for pointing out that I did not have the thread link
Hope this helps,
Mark
Edited by: Mark Dihiansan on Dec 12, 2011 2:34 AM

Problem with axis2 and Tomcat

Hello,
I am having a strange problem with Tomcat and axis. I have a webservice that uses axis2 for wsdl2java class generation. When I compile my project in maven a Test is performed. During the test a glassfish server is established and the project is deployed -everything work great with the expected results. However when I try to deploy the webservice on tomcat it has some problems.
At first I tried to call axis code in a POST method that takes a MultiPart message. The code is as below:
*@Path("identifyWavestream")*
*@POST*
*@Consumes(MediaType.MULTIPART_FORM_DATA)*
*@Produces(MediaType.APPLICATION_XML)*
*public String multipartTest(com.sun.jersey.multipart.MultiPart multiPart) throws Exception {*
*// get first body part (index 0)*
*//tomcat shows that the first error is here (line 122 is the nest one with bodypart)*
BodyPart bp = multiPart.getBodyParts().get(0);
BodyPartEntity bodyPartEntity = (BodyPartEntity) bp.getEntity();
InputStream stream = bodyPartEntity.getInputStream();
*//the rest of the code either saves the incoming file or implements the wsdl2java axis interface - neither works.*
And the tomcat error is:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
java.util.ArrayList.RangeCheck(Unknown Source)
java.util.ArrayList.get(Unknown Source)
com.webserv.rest.resources.SearchResource.test.multipartTest(SearchResource.java:122)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$TypeOutInvoker._dispatch(EntityParamDispatchProvider.java:138)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:124)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:71)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:63)
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:555)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:514)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:505)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:359)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
It was strange to me since this simple approach of handling a Multipart method worked for me earlier. Then I decided skip the handling of multipart method and just call the axis code. But the results also caused an error. I then tried to call the axis code in a simple @GET method (to cross out any issues regarding the multipart) and the result where the same. Again everything works on the maven- glassfish test. In this case the tomcat error is the following:
javax.servlet.ServletException: java.lang.NoSuchMethodError: org.apache.commons.httpclient.HttpConnectionManager.getParams()Lorg/apache/commons/httpclient/params/HttpConnectionManagerParams;
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:361)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
root cause
com.sun.jersey.api.container.MappableContainerException: java.lang.NoSuchMethodError: org.apache.commons.httpclient.HttpConnectionManager.getParams()Lorg/apache/commons/httpclient/params/HttpConnectionManagerParams;
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:74)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:124)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:71)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:63)
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:555)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:514)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:505)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:359)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
root cause
java.lang.NoSuchMethodError: org.apache.commons.httpclient.HttpConnectionManager.getParams()Lorg/apache/commons/httpclient/params/HttpConnectionManagerParams;
org.apache.axis2.transport.http.AbstractHTTPSender.initializeTimeouts(AbstractHTTPSender.java:454)
org.apache.axis2.transport.http.AbstractHTTPSender.getHttpClient(AbstractHTTPSender.java:514)
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:156)
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
com.webserv.rest.webapp.IntSoapServiceStub.getServerData(IntSoapServiceStub.java:2447)
com.webserv..rest.resources.AIntSoapImpl.getServerData(AIntSoapImpl.java:112)
com.webserv..rest.resources.SearchResource.test.pingTest(SearchResource.java:167)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$TypeOutInvoker._dispatch(EntityParamDispatchProvider.java:138)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:67)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:124)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:71)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:111)
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:63)
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:555)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:514)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:505)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:359)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
I think it is also a good ide to post the pom.xml file :
Edited by: 803864 on 2010-10-21 00:30

I think it is also a good ide to post the pom.xml file:
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"+
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+<modelVersion>4.0.0</modelVersion>+
+<groupId>com.myProjects</groupId>+
+<artifactId>audioid-rest-interface</artifactId>+
+<packaging>war</packaging>+
+<name>AudioID Rest Interface</name>+
+<version>0.1</version>+
+<dependencies>+
++
+<dependency>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>jersey-multipart</artifactId>+
+<version>1.0.1</version>+
+</dependency>+
+<dependency>+
+<groupId>com.sun.jersey</groupId>+
+<artifactId>jersey-client</artifactId>+
+<version>1.0.1</version>+
+</dependency>+
+<dependency>+
+<groupId>com.sun.jersey</groupId>+
+<artifactId>jersey-bundle</artifactId>+
+<version>1.0.1</version>+
+</dependency>+
+<dependency>+
+<groupId>commons-logging</groupId>+
+<artifactId>commons-logging</artifactId>+
+<version>1.0.4</version>+
+</dependency>+
+<dependency>+
+<groupId>commons-collections</groupId>+
+<artifactId>commons-collections</artifactId>+
+<version>3.1</version>+
+</dependency>+
+<dependency>+
+<groupId>org.slf4j</groupId>+
+<artifactId>slf4j-log4j12</artifactId>+
+<version>1.5.6</version>+
+</dependency>+
+<dependency>+
+<groupId>junit</groupId>+
+<artifactId>junit</artifactId>+
+<version>3.8.2</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>org.glassfish.distributions</groupId>+
+<artifactId>web-all</artifactId>+
+<version>10.0-build-20080430</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>org.glassfish.embedded</groupId>+
+<artifactId>gf-embedded-api</artifactId>+
+<version>1.0-alpha-4</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>com.sun.jersey</groupId>+
+<artifactId>jersey-server</artifactId>+
+<version>1.0.3.1</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>maven-wadl-plugin</artifactId>+
+<version>1.0.3.1</version>+
+</dependency>+
+<dependency>+
+<groupId>org.hibernate</groupId>+
+<artifactId>hibernate</artifactId>+
+<version>3.2.5.ga</version>+
+<exclusions>+
+<exclusion>+
+<groupId>javax.transaction</groupId>+
+<artifactId>jta</artifactId>+
+</exclusion>+
+<exclusion>+
+<groupId>cglib</groupId>+
+<artifactId>cglib</artifactId>+
+</exclusion>+
+</exclusions>+
+</dependency>+
+<dependency>+
+<groupId>org.apache.axis2</groupId>+
+<artifactId>axis2</artifactId>+
+<version>1.4.1</version>+
+</dependency>+
++
+<dependency>+
+<groupId>org.apache.axis2</groupId>+
+<artifactId>axis2-aar-maven-plugin</artifactId>+
+<version>1.4.1</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>org.apache.axis2</groupId>+
+<artifactId>axis2-java2wsdl</artifactId>+
+<version>1.4.1</version>+
+<scope>test</scope>+
+</dependency>+
+<dependency>+
+<groupId>org.apache.axis2</groupId>+
+<artifactId>axis2-xmlbeans</artifactId>+
+<version>1.4.1</version>+
+</dependency>+
++
+<dependency>+
+<groupId>com.sun.xml.bind</groupId>+
+<artifactId>jaxb-impl</artifactId>+
+<version>2.1.12</version>+
+</dependency>+
+<dependency>+
+<groupId>cglib</groupId>+
+<artifactId>cglib-nodep</artifactId>+
+<version>2.1_3</version>+
+</dependency>+
+</dependencies>+
+<build>+
+<finalName>audioid-rest-interface</finalName>+
+<plugins>+
+<plugin>+
++
++
+<groupId>com.sun.tools.xjc.maven2</groupId>+
+<artifactId>maven-jaxb-plugin</artifactId>+
+<version>1.1</version>+
+<executions>+
+<execution>+
+<phase>generate-sources</phase>+
+<goals>+
+<goal>generate</goal>+
+</goals>+
+</execution>+
+</executions>+
+<configuration>+
+<generatePackage> com.webserv.wsparameters</generatePackage>+
+<schemaDirectory>../audioid-rest-interface/src/main/resources+
+</schemaDirectory>+
+<includeSchemas>+
+<includeSchema>**/*.xsd</includeSchema>+
+</includeSchemas>+
+<extension>true</extension>+
+<strict>false</strict>+
+<verbose>false</verbose>+
+</configuration>+
+</plugin>+
+<plugin>+
+<groupId>org.apache.maven.plugins</groupId>+
+<artifactId>maven-javadoc-plugin</artifactId>+
++
+<executions>+
+<execution>+
+<goals>+
+<goal>javadoc</goal>+
+</goals>+
+<phase>compile</phase>+
+</execution>+
+</executions>+
+<configuration>+
+<encoding>UTF-8</encoding>+
+<verbose>false</verbose>+
+<show>public</show>+
+<subpackages> com.webserv.rest.rest.resources: com.webserv.rest.rest.commons: com.webserv.wsparameters+
+</subpackages>+
+<doclet>com.sun.jersey.wadl.resourcedoc.ResourceDoclet</doclet>+
+<docletPath>${path.separator}${project.build.outputDirectory}+
+</docletPath>+
+<docletArtifacts>+
+<docletArtifact>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>wadl-resourcedoc-doclet</artifactId>+
+<version>1.0.3.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>com.sun.jersey</groupId>+
+<artifactId>jersey-server</artifactId>+
+<version>1.0.3.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>xerces</groupId>+
+<artifactId>xercesImpl</artifactId>+
+<version>2.6.1</version>+
+</docletArtifact>+
+</docletArtifacts>+
+<additionalparam>-output+
+${project.build.outputDirectory}/resourcedoc.xml</additionalparam>+
+<useStandardDocletOptions>false</useStandardDocletOptions>+
+</configuration>+
+</plugin>+
+<plugin>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>maven-wadl-plugin</artifactId>+
+<version>1.0.3.1</version>+
+<executions>+
+<execution>+
+<id>generate</id>+
+<goals>+
+<goal>generate</goal>+
+</goals>+
+<phase>compile</phase>+
+</execution>+
+</executions>+
+<configuration>+
+<wadlFile>${project.build.outputDirectory}/application.wadl+
+</wadlFile>+
+<formatWadlFile>true</formatWadlFile>+
+<baseUri>http://192.168.2.149:8080/${project.build.finalName}+
+</baseUri>+
+<packagesResourceConfig>+
+<param> com.webserv.rest.resources</param>+
+</packagesResourceConfig>+
+<wadlGenerators>+
+<wadlGeneratorDescription>+
+<className>com.sun.jersey.server.wadl.generators.WadlGeneratorApplicationDoc+
+</className>+
+<properties>+
+<property>+
+<name>applicationDocsFile</name>+
+<value>${basedir}/src/main/doc/application-doc.xml</value>+
+</property>+
+</properties>+
+</wadlGeneratorDescription>+
+<wadlGeneratorDescription>+
+<className>com.sun.jersey.server.wadl.generators.WadlGeneratorGrammarsSupport+
+</className>+
+<properties>+
+<property>+
+<name>grammarsFile</name>+
+<value>${basedir}/src/main/doc/application-grammars.xml</value>+
+</property>+
+</properties>+
+</wadlGeneratorDescription>+
+<wadlGeneratorDescription>+
+<className>com.sun.jersey.server.wadl.generators.resourcedoc.WadlGeneratorResourceDocSupport+
+</className>+
+<properties>+
+<property>+
+<name>resourceDocFile</name>+
+<value>${project.build.outputDirectory}/resourcedoc.xml</value>+
+</property>+
+</properties>+
+</wadlGeneratorDescription>+
+</wadlGenerators>+
+</configuration>+
+</plugin>+
+<plugin>+
+<groupId>org.codehaus.mojo</groupId>+
+<artifactId>exec-maven-plugin</artifactId>+
+<version>1.1</version>+
+<executions>+
+<execution>+
+<goals>+
+<goal>java</goal>+
+</goals>+
+</execution>+
+</executions>+
+<configuration>+
+<mainClass>com.sun.jersey.samples.generatewadl.Main</mainClass>+
+</configuration>+
+</plugin>+
+<plugin>+
+<groupId>org.apache.maven.plugins</groupId>+
+<artifactId>maven-compiler-plugin</artifactId>+
+<inherited>true</inherited>+
+<configuration>+
+<source>1.5</source>+
+<target>1.5</target>+
+
+
+</configuration>+
+</plugin>+
+<plugin>+
+<groupId>org.jvnet.jaxb2.maven2</groupId>+
+<artifactId>maven-jaxb2-plugin</artifactId>+
+<executions>+
+<execution>+
+<goals>+
+<goal>generate</goal>+
+</goals>+
+</execution>+
+</executions>+
+</plugin>+
+<plugin>+
+<groupId>org.apache.axis2</groupId>+
+<artifactId>axis2-wsdl2code-maven-plugin</artifactId>+
+<version>1.4.1</version>+
+<executions>+
+<execution>+
+<id>generate reco core</id>+
+<goals>+
+<goal>wsdl2code</goal>+
+</goals>+
+<configuration>+
+<packageName>com.webserv.rest.webapp</packageName>+
+<wsdlFile>src/main/java/com/webserv/wsdl/web.wsdl</wsdlFile>+
+<databindingName>adb</databindingName>+
+</configuration>+
+</execution>+
+</executions>+
+</plugin>+
+<plugin>+
+<groupId>com.sun.tools.xjc.maven2</groupId>+
+<artifactId>maven-jaxb-plugin</artifactId>+
+<version>1.1</version>+
+<executions>+
+<execution>+
+<goals>+
+<goal>generate</goal>+
+</goals>+
+</execution>+
+</executions>+
+<configuration>+
+<generatePackage>com.webserv.wsparameters</generatePackage>+
+<schemaDirectory>src/main/xsd</schemaDirectory> <includeSchemas>+
+<includeSchema>**/*.xsd</includeSchema> </includeSchemas>+
+<extension>true</extension>+
+<strict>false</strict>+
+<verbose>true</verbose>+
+</configuration>+
+</plugin>+
+</plugins>+
+</build>+
+<profiles>+
+<profile>+
+<id>jdk-1.5</id>+
+<activation>+
+<jdk>1.5</jdk>+
+</activation>+
+<dependencies>+
+<dependency>+
+<groupId>com.sun.xml.bind</groupId>+
+<artifactId>jaxb-impl</artifactId>+
+<version>2.1.10</version>+
+</dependency>+
+</dependencies>+
+<build>+
+<plugins>+
+<plugin>+
+<groupId>org.apache.maven.plugins</groupId>+
+<artifactId>maven-javadoc-plugin</artifactId>+
+<configuration>+
+<docletArtifacts>+
+<docletArtifact>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>maven-wadl-plugin</artifactId>+
+<version>1.0.3.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>com.sun.jersey.contribs</groupId>+
+<artifactId>wadl-resourcedoc-doclet</artifactId>+
+<version>1.0.3.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>com.sun.jersey</groupId>+
+<artifactId>jersey-server</artifactId>+
+<version>1.0.3.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>xerces</groupId>+
+<artifactId>xercesImpl</artifactId>+
+<version>2.6.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>javax.xml.bind</groupId>+
+<artifactId>jaxb-api</artifactId>+
+<version>2.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>javax.xml</groupId>+
+<artifactId>jaxb-impl</artifactId>+
+<version>2.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>javax.activation</groupId>+
+<artifactId>activation</artifactId>+
+<version>1.1</version>+
+</docletArtifact>+
+<docletArtifact>+
+<groupId>javax.xml.stream</groupId>+
+<artifactId>stax-api</artifactId>+
+<version>1.0</version>+
+</docletArtifact>+
+</docletArtifacts>+
+</configuration>+
+</plugin>+
+</plugins>+
+</build>+
+</profile>+
+<profile>+
+<id>xsltproc</id>+
+<activation>+
+<file>+
+<exists>../xsltproc_win32/xsltproc.exe</exists>+
+</file>+
+</activation>+
+<build>+
+<plugins>+
++
++
+<plugin>+
+<groupId>org.codehaus.mojo</groupId>+
+<artifactId>exec-maven-plugin</artifactId>+
+<version>1.1</version>+
+<executions>+
+<execution>+
+<id>copy-docs-to-builddir</id>+
+<goals>+
+<goal>exec</goal>+
+</goals>+
+<phase>compile</phase>+
+<configuration>+
+<executable>copy</executable>+
+<commandlineArgs>src\\main\\doc\\*.* target\\classes+
+</commandlineArgs>+
+</configuration>+
+</execution>+
+<execution>+
+<id>prepare-xsltproc</id>+
+<goals>+
+<goal>exec</goal>+
+</goals>+
+<phase>package</phase>+
+<configuration>+
+<executable>copy</executable>+
+<commandlineArgs>..\\audioid-rest-interface\\src\\main\\resources\\*.xsd+
target\\classes</commandlineArgs>
+</configuration>+
+</execution>+
+<execution>+
+<id>exec-xsltproc: target/application.html</id>+
+<goals>+
+<goal>exec</goal>+
+</goals>+
+<phase>package</phase>+
+<configuration>+
++
+<executable>../xsltproc_win32/xsltproc.exe</executable>+
+<commandlineArgs>-o target/application.html+
src/main/doc/wadl_documentation.xsl
target/classes/application.wadl</commandlineArgs>
+</configuration>+
+</execution>+
+</executions>+
+</plugin>+
+</plugins>+
+</build>+
+</profile>+
+</profiles>+
+<pluginRepositories>+
+<pluginRepository>+
+<id>maven2-repository.dev.java.net</id>+
+<name>Java.net Repository for Maven</name>+
+<url>http://download.java.net/maven/2/</url>+
+<layout>default</layout>+
+</pluginRepository>+
+<pluginRepository>+
+<id>maven-repository.dev.java.net</id>+
+<name>Java.net Maven 1 Repository (legacy)</name>+
+<url>http://download.java.net/maven/1</url>+
+<layout>legacy</layout>+
+</pluginRepository>+
+</pluginRepositories>+
+<repositories>+
+<repository>+
+<id>maven2-repository.dev.java.net</id>+
+<name>Java.net Repository for Maven</name>+
+<url>http://download.java.net/maven/2/</url>+
+<layout>default</layout>+
+</repository>+
+<repository>+
+<id>maven-repository.dev.java.net</id>+
+<name>Java.net Maven 1 Repository (legacy)</name>+
+<url>http://download.java.net/maven/1</url>+
+<layout>legacy</layout>+
+</repository>+
+<repository>+
+<id>glassfish-repository</id>+
+<name>Java.net Repository for Glassfish</name>+
+<url>http://download.java.net/maven/glassfish</url>+
+</repository>+
+</repositories>+
+</project>+
Can anyonr contribute?

Problem with attachment in web service

I'm writing a WebService under WebLogic 9.2 . My WebService API needs to recive and return an attachment. I'm tring to use a javax.activation.DataHandler object for the attachment, but for some reason in the WSDL file that being created, the DataHandler isn't being recognize and the "http://www.bea.com/servers/wls90/wsee/attachment" namespace is being associated with it (I'm using "jwsc" in the build.xml).
Does anyone encounter with problem ? and does the DataHandler is the right object to use for attachment (i want to avoid using base-64 String)?

duplicate problem with a secured web service

Problem with WSDL

Similar Messages

Maybe you are looking for