Document/literal messaging with OAS 9.0.4

please let me know if i have this right...
my understanding is that if i want to do document/literal soap messaging to a wrapped pl/sql function with OAS 9.0.4 then i have to go rpc/endcoded and use a string for my xml document payload?
any input would be most appreciated.
thanks in advance.
Message was edited by:
user521233

If you are new to Web Services, you should really consider using the latest version of the OAS stack. With 9.0.4, you should only work with RPC/Encoded and the basic data type supported out of the box.
Using 10.1.3.2 (or any 10.1.3) is really where you want to start.
This is just my personnal opinion, and I do understand that it's not always possible to move to the latest release. However, pushing back may be your best option.
Best,
-Eric

Similar Messages

How to create Document / Literal WSDL with axis 1.3

Dear All,
1. How to create Document / Literal WSDL from java interface ?? or how to create Java 2 WSDL using Document/ Literal.
2. from document/literal WSDL to java classes(stub, skelton, serivces).
I am using Axis 1.3 , tomcat-5.5.20 and eclipse.
Please provide the command and arguments for java2wsdl and wsdl2java for doc/lit.
is there any tool that help to generate java2wsdl and wsdl2java for doc/lit.

That would be the <web-service> element in the web-services.xml file, of course.
"Michael Wooten" <[email protected]> wrote:
>
Hi Rich,
Try adding a style="document" attribute to the starting <web-service>
element.
The might be a way to get <servicegen> to do this for you, but I haven't
found
it yet :-)
Regards,
Mike Wooten
"Rich Muth" <[email protected]> wrote:
How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried
this yet
- Is there another mechanism?

Document/literal style wsdl with more than one port

Recently I have changed wsdl style from rpc/encoded to document/literal as BPEL does not handle soapenc:arrayType. The wsdl contains 2 operations and few complex type definitions.
In BPEL Designer I have created a process that invokes all operations defined in the wsdl, but only one of them will have some data in the response message and the other one will have an empty message. On the other hand, when I use stub generation to invoke Web Service everything is working fine.
If I provide separate wsdl for each operation (in BPEL process I would have two partnerLinks instead of one) than it works fine.
Does this mean that BPEL does not handle document/literal style endpoints with more than one port (operation)?
I have tested this with the orabpel_2.0_J1_win32.exe and orabpel_2.0rc9_win32.exe. Web Services, used for this test, are deployed in Jboss 3.2.3 and axis-1_2beta3.
WSDL used as partnerLink:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions targetNamespace="http://test" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://test" xmlns:intf="http://test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema elementFormDefault="qualified" targetNamespace="http://test" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="CardId">
<sequence>
<element name="cardType" nillable="true" type="xsd:string" />
<element name="number" nillable="true" type="xsd:string" />
</sequence>
</complexType>
<complexType name="CardIdArray">
<sequence>
<element maxOccurs="unbounded" name="item" nillable="true" type="impl:CardId" />
</sequence>
</complexType>
<element name="getCardsReturn" type="impl:CardIdArray" />
<complexType name="CardholderCards">
<sequence>
<element maxOccurs="unbounded" name="cards" nillable="true" type="impl:CardId" />
<element name="serialNumber" nillable="true" type="xsd:string" />
</sequence>
</complexType>
<element name="retrieveChReturn" type="impl:CardholderCards" />
</schema>
</wsdl:types>
<wsdl:message name="retrieveChRequest" />
<wsdl:message name="getCardsRequest" />
<wsdl:message name="retrieveChResponse">
<wsdl:part element="impl:retrieveChReturn" name="retrieveChReturn" />
</wsdl:message>
<wsdl:message name="getCardsResponse">
<wsdl:part element="impl:getCardsReturn" name="getCardsReturn" />
</wsdl:message>
<wsdl:portType name="TestService">
<wsdl:operation name="getCards">
<wsdl:input message="impl:getCardsRequest" name="getCardsRequest" />
<wsdl:output message="impl:getCardsResponse" name="getCardsResponse" />
</wsdl:operation>
<wsdl:operation name="retrieveCh">
<wsdl:input message="impl:retrieveChRequest" name="retrieveChRequest" />
<wsdl:output message="impl:retrieveChResponse" name="retrieveChResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="TestServiceSoapBinding" type="impl:TestService">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="getCards">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="getCardsRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="getCardsResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="retrieveCh">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="retrieveChRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="retrieveChResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TestServiceService">
<wsdl:port binding="impl:TestServiceSoapBinding" name="TestService">
<wsdlsoap:address location="http://localhost:8080/axis/services/TestService" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Hi Dragana,
We definitely support the ability to call a web service that exposes two operations (document/literal or not).
Glancing through your WSDL, it looks good.
Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
Thank you,
Edwin
[email protected]
please rename .zip to .zap

Document/literal web service with WSDL

Hi
I is so hard to get an easily written example of how to do a Document/literal web service in java, to generate a WSDL descripbing it and then deploying it on Apache.
I first belived that I should use JAXM. But I think it is just SOAP and there is no way to generate a WSDL file for the JAXM service, or??
It seems that u can to document/literal style using JAX-RPC, but this is VERY strange since RPC style is the direct opposite of Document style.
well, well
I would be very greatful for information here.
regards
/Rassol

JWSDP 1.2 includes the WS-I sample application in JWSDP_HOME/wsi-sampleapp. Several components of
this application use document-literal operations. The architecture of the application is described
here http://ws-i.org/SampleApplications/SupplyChainManagement/2003-04/SCMArchitecture1.0-BdAD.pdf
The WSDL for the services is availabe from URLs in the document.
As you say, the trick is generating the WSDL for a new service. You have two options: 1. Modify
existing WSDL yourself. This might be fairly easy, since the only major changes will be in the
schema. Then use a tool to generate Java source code from the WSDL. 2. Use a tool to generate WSDL
from source files.
I prefer option 1 myself, since that gives me total control over the schema. It allows me to
serialize certain parts of the SOAP message as body elements, others as attributes, and others as
header elements. Then I use the Apache Axis tool WSDL2Java with the "-s" option to generate skeleton
service files. One big advantage to this approach is that WSDL2Java generates JavaBean class for the
types in the WSDL schema, so I don't need to build the SOAP message with SAAJ. A service client
generates stubs and calls the service exactly as it would for an rpc/encoded service.
wscompile also generates service files from WSDL if you give the "-gen:server" option, but I've only
used Axis for my services.
Here's a sample WSDL for a document/literal service you can modify as you need. I checked it with
the WS-I testing tools to be sure it conforms to the WS-I Basic Profile 1.0a (available at www.ws-
i.org). Notice that the processPo operation is a request-response type operation, even though it has
a document/literal style. This follows the recommendations in the Basic Profile.
Cheers,
Mike
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://www.ltree.com/wsdl/po" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:impl="http://www.ltree.com/wsdl/po" xmlns:intf="http://www.ltree.com/wsdl/po" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.ltree.com/types/po" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:tns1="http://www.ltree.com/types/po"
          xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
          targetNamespace="http://www.ltree.com/types/po"
          elementFormDefault="qualified">
     <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
                 location="http://schemas.xmlsoap.org/soap/envelope/"/>
     <xsd:complexType name="LineItem">
         <xsd:sequence>
             <xsd:element name="itemId" type="xsd:string"/>
             <xsd:element name="quantity" type="xsd:int"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="PurchaseOrder">
         <xsd:sequence>
             <xsd:element name="customerName" type="xsd:string"/>
             <xsd:element name="lineItem" type="tns1:LineItem"
                      minOccurs="1" maxOccurs="unbounded" />
         </xsd:sequence>
         <xsd:attribute name="purchaseOrderId" type="xsd:string" use="required"/>
     </xsd:complexType>
     <xsd:element name="purchaseOrder" nillable="true" type="tns1:PurchaseOrder"/>
     <xsd:complexType name="CallbackEndpoint">
         <xsd:attribute name="location" type="xsd:anyURI" use="required"/>
     </xsd:complexType>
     <xsd:element name="callbackEndpoint" nillable="false" type="tns1:CallbackEndpoint"/>
     <xsd:complexType name="PurchaseOrderAck">
         <xsd:sequence>
             <xsd:element name="poId" type="xsd:string"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="purchaseOrderAck" nillable="true" type="tns1:PurchaseOrderAck"/>
     <xsd:complexType name="InvalidCustomerNameException">
      <xsd:sequence>
       <xsd:element name="message" nillable="true" type="xsd:string"/>
       <xsd:element name="customerName" type="xsd:string"/>
      </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="invalidCustomerNameException" nillable="true"
                  type="tns1:InvalidCustomerNameException"/>
</xsd:schema>
</wsdl:types>
   <wsdl:message name="processPoRequest">
      <wsdl:part name="callbackEndpoint" element="tns1:callbackEndpoint"/>
      <wsdl:part name="purchaseOrder" element="tns1:purchaseOrder"/>
   </wsdl:message>
   <wsdl:message name="processPoResponse">
      <wsdl:part name="purchaseOrderAck" element="tns1:purchaseOrderAck"/>
   </wsdl:message>
   <wsdl:message name="invalidCustomerNameException">
      <wsdl:part name="fault" element="tns1:invalidCustomerNameException"/>
   </wsdl:message>
   <wsdl:portType name="PurchaseOrderHandler">
      <wsdl:operation name="processPo">
         <wsdl:input message="impl:processPoRequest" name="processPoRequest"/>
         <wsdl:output message="impl:processPoResponse" name="processPoResponse"/>
         <wsdl:fault message="impl:invalidCustomerNameException" name="invalidCustomerNameException"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="PurchaseOrderHandlerPortSoapBinding" type="impl:PurchaseOrderHandler">
      <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="processPo">
         <wsdlsoap:operation soapAction="" style="document"/>
         <wsdl:input name="processPoRequest">
            <wsdlsoap:header message="impl:processPoRequest" part="callbackEndpoint" use="literal"/>
            <wsdlsoap:body parts="purchaseOrder" use="literal"/>
         </wsdl:input>
         <wsdl:output name="processPoResponse">
            <wsdlsoap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="invalidCustomerNameException">
            <wsdlsoap:fault name="invalidCustomerNameException" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="PurchaseOrderHandlerService">
      <wsdl:port binding="impl:PurchaseOrderHandlerPortSoapBinding" name="PurchaseOrderHandlerPort">
         <wsdlsoap:address location="http://localhost:8080/po/services/PurchaseOrderHandlerService"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Problem with document/literal web services

Hi,
I need to publish a document\literal WSDL for a web service on my OC4J 10.1.2.2 because my app has an interface with a .NET system.
I generated the WSDL with JDEV 10.1.3.3 and tried to deploy it on an OC4J 10.1.2 using JDEV 10.1.2.
The deployment worked fine but when I'm trying to access the web service with the generated stub I'm getting the following message:
"These methods do not conform to the restrictions imposed by the web service implementation"
and then a list of these methods.
Later I tried to remove the parameters from the methods and regenerated the WSDL and it worked fine, but I need the methods with the parameters.
What can I do?
Thanks

Jason, have you made any progress with CF7 and WS Security?
It doesn't seem like enough information on this is available. Is it
even possible? and how?

I just upgraded my iMac to Lion, and a few seconds ago, I upgraded the iWork package and now I'm having some problems with the new version of Pages (4.1) When I try to change something in a document, a message says "the program is not responding"

I just upgraded my iMac to Lion, and a few seconds ago, I upgraded the iWork package and now I'm having some problems with the new version of Pages (4.1) When I try to change something in a document, a message says "the program is not responding", so I have to force it to close. By the way, the SAVE botton stays the same even I change erverything in my document. Please, a have a work to finish, **** me. What I can do abou it?

I just upgraded my iMac to Lion, and a few seconds ago, I upgraded the iWork package and now I'm having some problems with the new version of Pages (4.1) When I try to change something in a document, a message says "the program is not responding", so I have to force it to close. By the way, the SAVE botton stays the same even I change erverything in my document. Please, a have a work to finish, **** me. What I can do abou it?

How to associate a test message with a change document

I am using solution manager 7.01.
accessing my change documents through the workcenter I need to create a new test message - so I use the Create transaction button on the button bar, Service Process, Test Message
Then I am in the create test message screen. However from here I cannot see how to associate my test message with either the change document that I was processing or to the maintenance cycle.
Ideally I want to link the test message to the change document however at least to the maintenance cycle.
How do I do this?
Am I creating the test message in an incorrect way?
regards
Marina

Anyone? Does no one use Test Messages?

JAX RPC extension: Problem with document/literal and MyType[]

Hi,
I have installed the JAX RPC extension and want to generate a stub from my WSDL file. The WSDL describes a document/literal binding.
Problem:
A webservice server method like:
public wineshop.model.common.SimpleProducer[] getSimpleProducerList() throws RemoteException;
is translated into a stub method like:
public UnknownType getSimpleProducerList() throws Exception {..}
Is an array of own types with the binding style "document/literal" not supported in JAX RPC 1.4 or is it just a bug?
The WSDL file is generated by JAX RPC 1.4.
I have installed JWSDP-1.5 and generated a stub with wscompile from the WSDL file. The generated stub has the correct method return type:
public wineshop.ws.client.SimpleProducer[] getSimpleProducerList()
throws java.rmi.RemoteException
It there a workaround like replacing some JDev JARs with JWSDP-1.5 to solve the problem?
Any hints are welcome.
Thanks Markus

repost.....

How to create document/literal web services with WLS7

How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried this yet
- Is there another mechanism?

That would be the <web-service> element in the web-services.xml file, of course.
"Michael Wooten" <[email protected]> wrote:
>
Hi Rich,
Try adding a style="document" attribute to the starting <web-service>
element.
The might be a way to get <servicegen> to do this for you, but I haven't
found
it yet :-)
Regards,
Mike Wooten
"Rich Muth" <[email protected]> wrote:
How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried
this yet
- Is there another mechanism?

I was writing a very important document; I saved it and I closed pages, now when I try to open it, I have a message with "it's impossible to open this document". How can i fix it?

I was writing a very important document; I saved it and I closed pages, now when I try to open it, I have a message with "it's impossible to open this document". How can i fix it?

When you have 2 versions of Pages on your Mac:
Pages 5 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.01 can not open Pages 5.1 files and you will get the warning that you need a newer version.
Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Once opened and saved in Pages 5.1 files can not be opened in Pages 5.
Anything that is saved to iCloud is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed over 95 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
Peter

Since Maverick download, pages update, I can't send a gmail message with a pages document attached. Any advise?

Any solution to this baffling and frustrating problem. Since Maverick update and pages update, gmail won't let me send a message with a pages document attached???
Please help

When i send mail to contacts who use gmail, I get this in a failure notice "
Recipient address: [email protected]
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;552-5.7.0 This message was blocked because its content presents a potential issue. Please visit http://support.google.com/mail/bin/answe to review our message content and attachment content guidelines. tr4si424804pab.34 - gsmtp
Remote system: dns;gmail-smtp-in.l.google.com (TCP|17.164.72.160|64923|173.194.79.26|25) (mx.google.com ESMTP tr4si424804pab.34 - gsmtp)"
I have a gmail account supposedly synced in and I get the same results.

Issue with generation of document/literal type WSDL using Axis

Hi All,
I am trying to convert some Java code into WSDL using Axis 1.2 framework. I used Document/Literal style for binding.
One of the methods in my Java code returns an array. This array is described in Axis generated WSDL as follows:
<complexType name="ArrayOfThings">
<complexContent>
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="impl:Things[]"/>
</restriction>
</complexContent>
</complexType>
But the end user(client for the web service I am hosting) says " .NET won't allow him to consume my webservice (or generate the proper reference classes) for types that derive from encoded types".
So my question is "Would it be possible to change the webservice so that it doesn’t use that(soapenc) implementation of the array?"
The end user is expecting something more like this:
<s:complexType name="ArrayOfThings">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="Things" nillable="true" type="tns:Things" />
</s:sequence>
</s:complexType>
I am new to Web Services. So any help or guidance would be greatly appreciated.
Thanks,
Scott.

Hi Dragana,
We definitely support the ability to call a web service that exposes two operations (document/literal or not).
Glancing through your WSDL, it looks good.
Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
Thank you,
Edwin
[email protected]
please rename .zip to .zap

Document literal with JAX-RPC?

Hi folks,
I want to create a service that uses document literal. I'm at a loss as to how to specify this to wscompile or xrpcc.
Any help would be greatly appreciated.
Regards,
Rajesh

Hi Rajesh,
I had the same problem last year when writing my master-degree paper. :>
My solution is to serialize/deserialize every XML files before and after the parameters sent and received.
However,this may be the most intuitive way to do it, but not the best way.
If you have enough time, you may try to register your own encoding style,
and assign the serialization job to your own serializer,
to make the follow-up jobs easier.
As I knew, some application servers would support literal-XML in their encoding style;One is MS-soap, and I forgot the other one.
You may also migrate your ap. to the MS-soap to use the literal-XML as the input/output paras.
Hope that would do help to your work.
Regards,
Jack

Ebservice with SOAP DOCUMENT/Literal encoding, method with out arguments

The webservice deployed as a DOCUMENT/literal encoding,If the method in the webservice is not havng any arument then is there any proplem while invoking. ?

Hi Dragana,
We definitely support the ability to call a web service that exposes two operations (document/literal or not).
Glancing through your WSDL, it looks good.
Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
Thank you,
Edwin
[email protected]
please rename .zip to .zap

Netbeans creating wsdl file having message with more than one part...

Hi,
I am using netbeans 6.0.1. I made an xml schema, then I wanted to make an wsdl that uses that schema.
I wanted to put in a message more parts(3), and it would not let me. Then, i made the message with just one part, and added the other parts afterwards.
But now, when I try to make a web service from that wsdl, it says that there is no service in the specified wsdl file.
And if i let that message with just one part, it will make the Web Service.
here is the xml schema and the wsdl file:
XML Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://xml.netbeans.org/schema/Abruf38"
xmlns:tns="http://xml.netbeans.org/schema/Abruf38"
elementFormDefault="qualified">
<xsd:complexType name="FormRequest">
<xsd:sequence>
<xsd:element name="newRequest" type="xsd:boolean"/>
<xsd:element name="requestNumber" type="xsd:int"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehiclesNumber" type="xsd:int"/>
<xsd:element name="prefferedType" type="xsd:string"/>
<xsd:element name="kombi" type="xsd:boolean"/>
<xsd:element name="usageMission" type="xsd:boolean"/>
<xsd:element name="usageEducation" type="xsd:boolean"/>
<xsd:element name="usageGeneral" type="xsd:boolean"/>
<xsd:element name="usageOthers" type="xsd:string"/>
<xsd:element name="eqVehicle" type="xsd:boolean"/>
<xsd:element name="eqDangerous" type="xsd:boolean"/>
<xsd:element name="eqPlaneSpriegel" type="xsd:boolean"/>
<xsd:element name="eqBegrstll" type="xsd:boolean"/>
<xsd:element name="eqMSitzBTruck" type="xsd:boolean"/>
<xsd:element name="eqVerzurrAusst" type="xsd:boolean"/>
<xsd:element name="eqOthers" type="xsd:string"/>
<xsd:element name="bringService" type="xsd:boolean"/>
<xsd:element name="holService" type="xsd:boolean"/>
<xsd:element name="chauffService" type="xsd:boolean"/>
<xsd:element name="otherService1" type="xsd:string"/>
<xsd:element name="otherService1Chk" type="xsd:boolean"/>
<xsd:element name="otherService2" type="xsd:string"/>
<xsd:element name="otherService2Chk" type="xsd:boolean"/>
<xsd:element name="otherService3" type="xsd:string"/>
<xsd:element name="otherService3Chk" type="xsd:boolean"/>
<xsd:element name="activity" type="xsd:string"/>
<xsd:element name="costPayer" type="xsd:string"/>
<xsd:element name="costCenter" type="xsd:string"/>
<xsd:element name="vehicleCost" type="xsd:float"/>
<xsd:element name="chauffServiceCost" type="xsd:float"/>
<xsd:element name="holBringServiceCost" type="xsd:float"/>
<xsd:element name="totalCost" type="xsd:float"/>
<xsd:element name="tripPurpose" type="xsd:string"/>
<xsd:element name="fixTermin" type="xsd:boolean"/>
<xsd:element name="justificationFix" type="xsd:string"/>
<xsd:element name="requestID" type="xsd:string"/>
<xsd:element name="rentalPeriod" type="tns:RentalPeriod"/>
<xsd:element name="carPool" type="tns:CarPool"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CarPool">
<xsd:sequence>
<xsd:element name="poolID" type="xsd:string"/>
<xsd:element name="poolName" type="xsd:string"/>
<xsd:element name="orgNumber" type="xsd:string"/>
<xsd:element name="vehicle" maxOccurs="unbounded" type="tns:Vehicle"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RentalPeriod">
<xsd:sequence>
<xsd:element name="rentalPeriodID" type="xsd:string"/>
<xsd:element name="startDate" type="xsd:date"/>
<xsd:element name="endDate" type="xsd:date"/>
<xsd:element name="startTime" type="xsd:time"/>
<xsd:element name="endTime" type="xsd:time"/>
<xsd:element name="startLocation" type="xsd:string"/>
<xsd:element name="endLocation" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Vehicle">
<xsd:sequence>
<xsd:element name="vehicleID" type="xsd:string"/>
<xsd:element name="vehicleClass" type="xsd:string"/>
<xsd:element name="vehicleRegisterNo" type="xsd:int"/>
<xsd:element name="vehicleType" type="xsd:string"/>
<xsd:element name="seatsNumber" type="xsd:int"/>
<xsd:element name="cost" type="xsd:float"/>
<xsd:element name="available" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Contact">
<xsd:sequence>
<xsd:element name="contactID" type="xsd:string"/>
<xsd:element name="contactName" type="xsd:string"/>
<xsd:element name="telNumber" type="xsd:int"/>
<xsd:element name="faxNumber" type="xsd:int"/>
<xsd:element name="loNo" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Person">
<xsd:sequence>
<xsd:element name="personID"/>
<xsd:element name="department" type="xsd:string"/>
<xsd:element name="serviceNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Department">
<xsd:sequence>
<xsd:element name="departmentID" type="xsd:string"/>
<xsd:element name="fundsDepartment" type="xsd:string"/>
<xsd:element name="mvwdst" type="xsd:int"/>
<xsd:element name="distributionNumber" type="xsd:int"/>
<xsd:element name="contact" type="tns:Contact"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="formRequestElement" type="tns:FormRequest"/>
<xsd:element name="personElement" type="tns:Person"/>
<xsd:element name="departmentElement" type="tns:Department"/>
<xsd:element name="vehicle" type="tns:Vehicle"/>
<xsd:element name="loadFormReturn" type="xsd:boolean"/>
<xsd:element name="editFormReturn" type="xsd:boolean"/>
</xsd:schema>
Wsdl File:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="userWS" targetNamespace="http://j2ee.netbeans.org/wsdl/userWS"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://xml.netbeans.org/schema/Abruf38" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:tns="http://j2ee.netbeans.org/wsdl/userWS" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/userWS">
<xsd:import namespace="http://xml.netbeans.org/schema/Abruf38" schemaLocation="Abruf38.xsd"/>
</xsd:schema>
</types>
<message name="loadFormRequest">
<part name="formRequest" element="ns:formRequestElement"/>
<part name="person" element="ns:personElement"/>
<part name="department" element="ns:departmentElement"/>
</message>
<message name="loadFormReply">
<part name="retVal" element="ns:loadFormReturn"/>
</message>
<portType name="userWSPortType">
<operation name="loadForm">
<input name="input1" message="tns:loadFormRequest"></input>
<output name="output1" message="tns:loadFormReply"/>
</operation>
</portType>
<binding name="userWSBinding" type="tns:userWSPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="loadForm">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="userWSService">
<port name="userWSPort" binding="tns:userWSBinding">
<soap:address location="http://localhost:18181/userWSService/userWSPort"/>
</port>
</service>
<plnk:partnerLinkType name="userWS1">

<plnk:role name="userWSPortTypeRole" portType="tns:userWSPortType"/>
</plnk:partnerLinkType>
</definitions>
The message that Netbeans says when trying to put more parts to the message is:
WS-I Basic Profile Rule R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
Please...I am desperate, cause I am pressed by time!
Can anyone tell me how can I make it work. Cause it is very common to use a Web service operation that has more than ONE parameter.
I am waiting for your replys!

Hi,
Change the <soap:binding style="document"... to <soap:binding style="rpc"... and see if that works.
I'm not sure how to get <soap:binding style="document"... working yet - I'm not that experienced in web services yet.
Hope this helps and is not too late.
Regards,
Greg Nye

Document/literal messaging with OAS 9.0.4

Similar Messages

Maybe you are looking for