Wsdl2service and document style

Hello everybody.
This is very urgent so any help will be really appreciated.
I have a WSDL which uses document/literal style/encoding. I am running wsdl2service on it to generate java classes, and then proceeding successfully to generate and deploy a web service. The weblogic test page also works successfully.
But when I look at the SOAP on-the-wire message, it is not document style SOAP compliant, for example, for the operation CreateNewAccount, that takes in the schema Customer.xsd, I get the following message :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:m0="http://www.schema.com/Bank">
     <SOAP-ENV:Body>
          <m:CreateNewAccount xmlns:m="http://www.telcordia.com/TestWebServices/Bank.wsdl">
               <m0:Name></m0:Name>
               <m0:SSN></m0:SSN>
               <m0:Balance>0</m0:Balance>
               <m0:Address>
                    <m0:Number></m0:Number>
                    <m0:Street></m0:Street>
                    <m0:State></m0:State>
                    <m0:Zip></m0:Zip>
               </m0:Address>
          </m:CreateNewAccount>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The way I understand, if this were document styled web-service, the operation name in above should be replaced by Customer.xsd root element name. (Pls see the attached WSDL).
I tried the same WSDL with the Systinet server, and it produced a SOAP message that I was expecting.
If I changed this WSDL to rpc mode, the CreateNewAccount node is followed by the Customer node, which is fine.
So my question is, is this a WLS 81 SP2 bug, or am I doing something wrong or missing something?
The WSDL :
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.telcordia.com/TestWebServices/Bank.wsdl" xmlns:ws="http://www.telcordia.com/TestWebServices/Bank.wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:sch="http://www.schema.com/Bank" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.telcordia.com/TestWebServices/Bank.wsdl">
     <import namespace="http://www.schema.com/Bank" location="Customer.xsd"/>
     <import namespace="http://www.schema.com/Bank" location="Ack.xsd"/>
     <types>
          <xs:schema xmlns:tns="http://www.telcordia.com/TestWebServices/Bank.wsdl"/>
     </types>
     <message name="CreateNewAccountRequest">
          <part name="body" element="sch:Customer"/>
     </message>
     <message name="CreateNewAccountResponse">
          <part name="body" element="sch:Ack"/>
     </message>
     <portType name="CreateNewAccountPortType">
          <operation name="CreateNewAccount">
               <input message="tns:CreateNewAccountRequest"/>
               <output message="tns:CreateNewAccountResponse"/>
          </operation>
     </portType>
     <binding name="CreateNewAccountBinding" type="tns:CreateNewAccountPortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="CreateNewAccount">
               <input>
                    <soap:body parts="body" use="literal"/>
               </input>
               <output>
                    <soap:body parts="body" use="literal"/>
               </output>
          </operation>
     </binding>
     <service name="AccountService">
          <port name="ws:CreateNewAccountPort" binding="tns:CreateNewAccountBinding">
               <soap:address location="http://taste.mk.telcordia.com:45000/TWS/NewAccountRequest"/>
          </port>
     </service>
</definitions>
=======================================================
The schemas :
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.schema.com/Bank" targetNamespace="http://www.schema.com/Bank" elementFormDefault="qualified">
     <xsd:element name="Customer">
          <xsd:complexType>
               <xsd:all>
                    <xsd:element name="Name"/>
                    <xsd:element name="SSN"/>
                    <xsd:element name="Balance" type="xsd:integer"/>
                    <xsd:element name="Address">
                         <xsd:complexType>
                              <xsd:all>
                                   <xsd:element name="Number"/>
                                   <xsd:element name="Street"/>
                                   <xsd:element name="State"/>
                                   <xsd:element name="Zip"/>
                              </xsd:all>
                         </xsd:complexType>
                    </xsd:element>
               </xsd:all>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>
++++++++++++++++++++++++++++++++++++++++++++++++++++++
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.schema.com/Bank" targetNamespace="http://www.schema.com/Bank" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xsd:element name="Ack">
          <xsd:complexType>
               <xsd:all>
                    <xsd:element name="SSN"/>
                    <xsd:element name="AccountNumber"/>
               </xsd:all>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>

The generated web-services.xml from wsdl2service can have either style="rpc" or
style="document". And in order to accomodate doc/lit operations that have multiple
params you would need to edit the web-services.xml to have style="documentwrapped".
Regards
Shridhar
Laxman Siyani <[email protected]> wrote:
Hi,
I have been using the autotype and wsdl2service ant tasks to generate
firstly a complex data type from the .xsd, associated with a .WSDL.
Then I use the wsdl2service to generate a Interface class which I implement.
When I deploy this and try to use it from the test page in the Console,
I get an error in the Weblogic.log:
ERROR: Backend components for Document style webservice can only accept
methods with one input parameter.
Does anyone know how I can get wsdl2service to generate documentwrapped
webservice.xml.
Many thanks,
Laxman

Similar Messages

  • Problem in Jdeveloper 10.1.3, web services and document style.possible bug?

    Hello!
    I would like to generate a document-style web service from a wsdl file. The problem is that when I use it I get the following error:
    "operation echoStruct must have exactly one parameter as part of the SOAP body when used with a document-bare binding. All other parameters must be mapped to headers."
    A similar message is shown with other wsdl file that I'm using.
    I'm attaching the file that use to test it.
    Could you help me and tell me how I can fix it, please? or is it a bug?
    Regards,
    Antonio.
    <definitions xmlns:s1="http://soapinterop.org" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://soapinterop.org/xsd" xmlns:s2="http://soapinterop.org/AbstractTypes" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapinterop.org">
         <types>
              <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org/xsd">
                   <s:import namespace="http://soapinterop.org"/>
                   <s:element name="echoStructParam" type="s0:SOAPStruct"/>
                   <s:complexType name="SOAPStruct">
                        <s:sequence>
                             <s:element minOccurs="1" maxOccurs="1" name="varFloat" type="s:float"/>
                             <s:element minOccurs="1" maxOccurs="1" name="varInt" type="s:int"/>
                             <s:element minOccurs="0" maxOccurs="1" name="varString" type="s:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="echoStructReturn" type="s0:SOAPStruct"/>
                   <s:element name="echoStringArrayParam" type="s1:ArrayOfString"/>
                   <s:element name="string" type="s:string"/>
                   <s:element name="echoStringArrayReturn" type="s1:ArrayOfString"/>
                   <s:element name="echoStringParam" type="s:string"/>
                   <s:element name="echoStringReturn" type="s:string"/>
              </s:schema>
              <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org">
                   <s:import namespace="http://soapinterop.org/xsd"/>
                   <s:complexType name="ArrayOfString">
                        <s:sequence>
                             <s:element minOccurs="0" maxOccurs="unbounded" ref="s0:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="ArrayOfString1" nillable="true" type="s1:ArrayOfString1"/>
                   <s:complexType name="ArrayOfString1">
                        <s:sequence>
                             <s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="string" nillable="true" type="s:string"/>
              </s:schema>
              <s:schema targetNamespace="http://soapinterop.org/AbstractTypes">
                   <s:complexType name="StringArray">
                        <s:complexContent mixed="false">
                             <s:restriction base="soapenc:Array">
                                  <s:sequence>
                                       <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string"/>
                                  </s:sequence>
                             </s:restriction>
                        </s:complexContent>
                   </s:complexType>
              </s:schema>
         </types>
         <message name="echoStructSoapIn">
              <part name="echoStructParam" element="s0:echoStructParam"/>
         </message>
         <message name="echoStructSoapOut">
              <part name="echoStructResult" element="s0:echoStructReturn"/>
         </message>
         <message name="echoStringArraySoapIn">
              <part name="echoStringArrayParam" element="s0:echoStringArrayParam"/>
         </message>
         <message name="echoStringArraySoapOut">
              <part name="echoStringArrayResult" element="s0:echoStringArrayReturn"/>
         </message>
         <message name="echoStringSoapIn">
              <part name="echoStringParam" element="s0:echoStringParam"/>
         </message>
         <message name="echoStringSoapOut">
              <part name="echoStringResult" element="s0:echoStringReturn"/>
         </message>
         <portType name="WSDLInteropTestDocLitSoap">
              <operation name="echoStruct">
                   <input message="s1:echoStructSoapIn"/>
                   <output message="s1:echoStructSoapOut"/>
              </operation>
              <operation name="echoStringArray">
                   <input message="s1:echoStringArraySoapIn"/>
                   <output message="s1:echoStringArraySoapOut"/>
              </operation>
              <operation name="echoString">
                   <input message="s1:echoStringSoapIn"/>
                   <output message="s1:echoStringSoapOut"/>
              </operation>
         </portType>
         <binding name="WSDLInteropTestDocLitSoap" type="s1:WSDLInteropTestDocLitSoap">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="echoStruct">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
              <operation name="echoStringArray">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
              <operation name="echoString">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
         </binding>
         <service name="WSDLInteropTestDocLit">
              <port name="WSDLInteropTestDocLitSoap" binding="s1:WSDLInteropTestDocLitSoap">
                   <soap:address location="http://mssoapinterop.org/asmx/wsdl/InteropTestDocLit.asmx"/>
              </port>
         </service>
    </definitions>

    Dev update: WSDL file seems fine. The problem is that it's for a document-bare service and, by default, the Unwrap Wrapped Parameters option on step 2 of the top-down wizard is enabled and checked. This means that we try to pick apart the input message into a series of parameters, yielding the error shown because a document-bare operation must have only one input parameter.
    If the Unwrap Wrapped Parameters option is unchecked, creation of the top-down service will succeed. In future, we ought to disable the option completely for everything but document-wrapped services, as that's the only time it applies.
    This is covered by bug 4630382.

  • What is the RPC and Document Type binding

    Hi Gurus,
      Do any one know what is the difference betwen
    "Soap binding sytle = Rpc" and "Soap Binding Style= Document".
    Do Netweaver Studion supports Document style for creating portal Application and components.
    Thanks
    venkata

    Hi
    I think you could have a look to this:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/the difference between rpc and document style wsdl.article
    And Portal application support rpc literal, rpc encoded and document literal
    Regards,
    Frederic

  • Differences between Document Style vs RPC style WS.

    Hello All,
    Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received.
    In either way of writing services using JAX-WS, I currently annotate the service with @Webservice, generage the WSDL and from that WSDL I generate the client side artifacts.
    Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.
    Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here.

    user13126996 wrote:
    Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received. no, asynchronous vs. synchronous responses have nothing to do with rpc style vs. document style. they are two orthogonal concepts.
    Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.the difference is basically in how the data is encoded over the transport layer. in theory, you can encode some complex data structures more efficiently in the rpc style. in reality, no one ever uses these features. and since the document style is more strongly typed and much more "straightforward", most people tend to prefer the document style to the rpc style these days. (in fact, i don't think jaxws actually supports rpc style).
    Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here. none really. SOAP over HTTP is XML over HTTP. XML over HTTP has no strong specification, whereas SOAP puts lots of specs around what the XML should look like. also, obviously, SOAP can theoretically be sent over other transport layers besides HTTP (not that i've ever seen that).

  • In Pages 09 we can do Mail Merge and Import Styles from a document. Can someone please explain how we can do this with the new version of Pages 5.1. Even Apple solutions are only valid for Pages Version 09. What a DOWN GRADE!

    In Pages 09 we can do Mail Merge and Import Styles from a document. Can someone please explain how we can do this with the new version of Pages 5.1. Even Apple solutions are only valid for Pages Version 09. What a DOWN GRADE! Thank god Pages 09 is still there.

    …and the other 98 missing features.
    Just use Pages '09, which should be in your Applications/iWork folder.
    Rate/review Pages 5 in the App Store.
    Peter

  • How can I export table and cell styles to use in another InDesign document?

    I've been looking…and looking but can't find out how to export table styles within InDesign CC. If there is a load table styles option within the panel, it stands to reason there should be an export. Any help would be appreciated, thanks.

    Frank,   John's solution is it.    But that also requires that you have those old files easily on hand to access.  Maybe even searching for them in the future, 3 months down the road, could be a pain.   You can always save a Library for that file and drag some of those styled elements into that library.   Save the library in a place that you will keep access to and readily pull assets from.   In the future doc open that library and drag the styled element into your new document and the styles are now in the new doc to reuse.   I have a library saved just for tables.

  • AxisFault seen while invoking document style web service

    I am seeing the following stacktrace when I try to invoke a document-style web service.
    <partnerRole name="MyWebService1_Role">
    <ServiceName>{http://idm.oracle.com/}MyWebService1</ServiceName>
    <PortType>{http://idm.oracle.com/}MyWebService1</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/ProvisioningFromDAS~1.0/4202-BpInv0-BpSeq0.3-3</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2005-09-06 09:23:37,650> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
    faultSubcode:
    faultString: caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
    at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
    at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
    at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    What could this mean ?

    Hi,
    I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
    java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
    failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
    class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
    ENTRY 1:
    class: java.lang.Object
    xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
    ENTRY 2:
    class: java.lang.Object
    xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
    ENTRY 3:
    class: java.lang.Object
    xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c

  • How do you have the bottom stroke of a table show up using Table Styles and Cell Styles only?

    I am using InDesign CS6, and I want to create a Table Style that has the bottom stroke show up, but does not have a table border, such as:
    However, whenever I try to change the Table or Cell strokes so that the last stroke shows up, I get the entire table border, or some strange combination of borders:
    Does anyone have any insight on how I can get the bottom stroke to show up while preserving my other stroke properties? Since I work with long documents, it's necessary to be able to control all of my tables through Table Styles and Cell Styles, and not by manually changing each and every table with the Stroke palette.
    For reference, here are the my current Table Style properties and the resulting table:

    Michael Murphy is the InDesign style-meister. He wrote "Adobe InDesign Styles" for Adobe Press, and did a great Lynda.com title on InDesign styling. Here's what he says in the book:
    "As mentioned at the beginning of this chapter, with all the power of table and cell styles, it is important to understand not only how they work and what they can do for you, but also to understand their limitations.
    "Two formatting features missing in table and cell styles have already been discussed: You will always have to set the column width and row height of cells when applying a table style for the first time, and you will always have to convert body rows to header and/or footer rows every time you apply a table style for first time or update the table's data....
    "But there's another kind of limitation that's important to keep in mind as you are designing tables: It is very easy to design a table that cannot be completely defined by a table style. In many cases, you'll need to define an extra cell style or two that lets you complete for formatting. [my emphasis]."
    So I think that's what you have to do: Apply another cell style on top of the cells at the bottom of the table after applying the table style.

  • [JS InDesign CS3] Style groups, begone! (or: How do I take paragraph and character styles out of style groups?)

    Sorry for this question (and my terrible English, by the way), I'm a javascript noob and I know when I've reached my limits.
    Well, I'm trying to take a set of paragraph and character styles out of the style groups they are placed in, in hundreds of InDesign documents (that cannot be treated as a book). As far as I've tried (thanks to the invaluable help of previous posts in this forum) I've been able to move a style into a group and change it's position inside the group, inside the root level or even between groups. But it doesn't matter how I try, I don't know which move reference should I try in case I want to take every style out of their style group and place them after their original group folder, at the [Root] style level .
    I have tried:
    var doc=app.activeDocument;
    var pGroups=doc.paragraphStyleGroups;
    for (i=pGroups.length-1; i>=0; i--){
         var pStylesInGroup=pGroups[i].paragraphStyles;
         for (j=pStylesInGroup.length-1; j>=0; j--){
    // Here I am, trying to move a style outside the folder that contains it, and failing miserably.
              pStylesInGroup[j].move (LocationOptions.after, pGroups[i]);
    It didn't work, the script sent an invalid parameter value in the reference field, so I cant use the group folder itself as reference.
    Tried other (obviously wrong) solutions, like use the first available style as reference. Therefore, my second script was
    var doc=app.activeDocument;
    var pStyles=doc.allParagraphStyles;
    var pGroups=doc.paragraphStyleGroups;
    for (i=pGroups.length-1; i>=0; i--){
         var pStylesInGroup=pGroups[i].paragraphStyles;
         for (j=pStylesInGroup.length-1; j>=0; j--){
    // Now I try placing the styles after the [Basic Paragraph], that is, the second paragraph style in the document style list
              pStylesInGroup[j].move (LocationOptions.after, pStyles[1]);
    It didn't work either, another invalid parameter in the reference field. Similar results with my other attempts (I even tried "[Root]" as literal with similar luck).
    So, my question is: Which command (or script, in case my whole approach is utterly wrong) should I use to achieve my goal?
    Thanks in advance to whoever decides to spend more than a minute thinking about my humble worries, and my apologies for shamelessly ripping some of your lines of code for my purposes.

    Okay, tried a few things and got really weird results!
    1. You can move a style around inside its group.
    2. You can move a style out of a group "to" another, but it will appear 'inside' that style. I got my test style as a sub-item of [Basic Paragraph], using index #1. With index #0 ([No Paragraph Style]) InDesign crashed.
    3. You can duplicate the style, but then you get a copy in the same group. Still no luck.
    4. Finally! What is the parent of a paragraph style?
    Document | Application | ParagraphStyleGroup
    "Application" is easy -- that's when you make a style global. So what's the difference between 'Document' and 'paragraphStyleGroup'? Simple -- well, when you finally get it...
    pStylesInGroup[j].move (LocationOptions.AT_END, doc);
    moves the style out of the group and to the end of the list in the document. I don't think it's possible to move it directly to a specific position into the main style list -- you first have to move it out of a group, then move it around in its own list.
    Fortunately, it returns its new position as a ParagraphStyle again, so if needed, you can use
    newStyle = pStylesInGroup[j].move (LocationOptions.AT_END, doc);
    newStyle.move (LocationOptions.AFTER, pStyles[1]);
    -- I didn't really try that out, but it should work.

  • Calling a document style web service using a pl/sql wrapper method

    Just wanted to find out if anybody has a working example of invoking a document style web service from Oracle 10g database on a Unix environment.
    We have java test class that invokes the web service, and we are trying to use a pl/sql wrapper to invoke a Java Web Service client. So far, we are encountering an End of File Communication error from Oracle which essentially terminates the session with the database.
    On the Oracle application server side we are able to see a successful HTTP request made to the application server via server log, which is hosting the web service, since we are registering HTTP 200 success codes. However, we do not see any other errors from the application in the server logs. Most likely since the client side fails, before actually getting a chance to invoke the web service. This has been verified by commenting the client code leaving the print statements. The first call to the Service Factory method (XFire) to look up the service is where the PL/SQL procedure fails with an End of File communication error.

    Remove the when others section and see the actual error and post that.
    http://tkyte.blogspot.com/2008/06/when-others-then-null-redux.html
    http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html

  • Document style Problem

    We have three issues when trying to implement a document-style service. I will
    document them all but I'd suggest you go through them all before attempting to
    answer any of them.
    We are trying to implement a service that has the following signature:
    public void echoDom(Document doc)
    We want the delivery of our message to be of style ("document"). Therefore, we
    modified our servicegen entry to include the style="document" under the service.
    It looks like the following:
    <servicegen
    destEar="${appDir}/dom.ear"
    warName="dom.war">
    <service
    javaClassComponents="examples.dom.EchoDom"
    targetNamespace="http://examples.org"
    serviceName="dom"
    serviceURI="/EchoDomService"
         generateTypes="True"
    expandMethods="True"
    style="document">
    <client
    packageName="examples.dom"
    clientJarName="client.jar"
    />
    </service>
    <classpath>
    <pathelement path="${temp_dir}"/>
    <pathelement path="${java.class.path}"/>
    </classpath>
    </servicegen>
    1. FIRST PROBLEM:
    The first problem we're having is that it does not compile with the combination
    of our signature being of type void (as shown above) and the style="document"
    in build.xml.
    The error is the following:
    [servicegen] Generating service "dom" ...
    [servicegen] Generating XML types and serializers from java classes (examples.do
    m.EchoDom) ...
    [servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[  void:
    null ]
    [servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
    [servicegen] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:111)
    [servicegen] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:88)
    [servicegen] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:183)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
    .mapComponent(ComponentAutoTyper.java:155)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
    JavaAutoTyper.java:80)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
    te(AutoTypeTask.java:353)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
    enerateService(ServiceGenTask.java:251)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
    xecute(ServiceGenTask.java:146)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
    [servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
    2. SECOND PROBLEM
    If we change the signature to become:
    public Document echoDom(Document doc)
    then the build works but when we try to test our service, it gives us the following:
    [java] java.rmi.RemoteException: web service invoke failed; nested exceptio
    n is:
    [java] javax.xml.soap.SOAPException: failed to serialize xml:weblogic.
    xml.schema.binding.SerializationException: type mapping lookup failure on class=
    class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPING SIZE=6
    [java] ENTRY 1:
    [java] class: org.w3c.dom.Document
    [java] xsd_type: ['http://examples.org']:p3:echoDom
    [java] ser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@5973ea
    [java] deser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@49131c
    [java] ENTRY 2:
    [java] class: java.lang.Object
    [java] xsd_type: ['http://examples.org']:p1:echoDomResponse
    [java] ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    5b99f
    [java] deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    3. THIRD PROBLEM:
    Now, when we revert back to style="rpc" and everything works fine and dandy (although
    not as we want it because, as I mentioned above, we want a void signature and
    a document style), we get the following added tag around our body content, which
    we did not add ourselves, nor are we sure yet why it shows up:
    We pass it the following argument:
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    We get the following (notice the <document> tag around it):
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    4. PROBLEM FOUR (just remembered this one):
    If we use the standard test page (provided with WLS), with (3) above, it chops
    off the "those" and it still wraps it within this new <document> element as show
    below:
    <!--REQUEST.................-->
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Header>
    </env:Header>
    <env:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    We're not so worried about the fourth because it seems like a bug but the first
    three (especially the first) are most important. Any ideas would be appreciated.
    Thanks
    sami

    Ok I tried it out, DOM with document style web
    service is not working in WLS 7.0.2. I filed
    CR104719. Please contact support with this case
    number to get a patch.
    Sorry for the trouble.
    http://manojc.com
    "sami titi" <[email protected]> wrote in message
    news:[email protected]...
    >
    We're using WLS7 SP2, patch: CR102544_70sp2_v2.jar
    thanks
    "manoj cheenath" <[email protected]> wrote:
    Quick question, before i try this out.
    Which version of WLS? SP?
    http://manojc.com
    "sami titi" <[email protected]> wrote in message
    news:[email protected]...
    We have three issues when trying to implement a document-style service.I
    will
    document them all but I'd suggest you go through them all beforeattempting to
    answer any of them.
    We are trying to implement a service that has the following signature:
    public void echoDom(Document doc)
    We want the delivery of our message to be of style ("document").Therefore, we
    modified our servicegen entry to include the style="document" underthe
    service.
    It looks like the following:
    <servicegen
    destEar="${appDir}/dom.ear"
    warName="dom.war">
    <service
    javaClassComponents="examples.dom.EchoDom"
    targetNamespace="http://examples.org"
    serviceName="dom"
    serviceURI="/EchoDomService"
    generateTypes="True"
    expandMethods="True"
    style="document">
    <client
    packageName="examples.dom"
    clientJarName="client.jar"
    />
    </service>
    <classpath>
    <pathelement path="${temp_dir}"/>
    <pathelement path="${java.class.path}"/>
    </classpath>
    </servicegen>
    1. FIRST PROBLEM:
    The first problem we're having is that it does not compile with thecombination
    of our signature being of type void (as shown above) and thestyle="document"
    in build.xml.
    The error is the following:
    [servicegen] Generating service "dom" ...
    [servicegen] Generating XML types and serializers from java classes(examples.do
    m.EchoDom) ...
    [servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED*****[  void:
    null ]
    [servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
    [servicegen] atweblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:111)
    [servicegen] atweblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:88)
    [servicegen] atweblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:183)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
    mapComponent(ComponentAutoTyper.java:155)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
    JavaAutoTyper.java:80)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
    te(AutoTypeTask.java:353)
    [servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
    enerateService(ServiceGenTask.java:251)
    [servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
    xecute(ServiceGenTask.java:146)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [servicegen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [servicegen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [servicegen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
    [servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
    2. SECOND PROBLEM
    If we change the signature to become:
    public Document echoDom(Document doc)
    then the build works but when we try to test our service, it givesus the
    following:
    [java] java.rmi.RemoteException: web service invoke failed; nestedexceptio
    n is:
    [java] javax.xml.soap.SOAPException: failed to serializexml:weblogic.
    xml.schema.binding.SerializationException: type mapping lookup failureon
    class=
    class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPINGSIZE=6
    [java] ENTRY 1:
    [java] class: org.w3c.dom.Document
    [java] xsd_type: ['http://examples.org']:p3:echoDom
    [java] ser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@5973ea
    [java] deser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@49131c
    [java] ENTRY 2:
    [java] class: java.lang.Object
    [java] xsd_type: ['http://examples.org']:p1:echoDomResponse
    [java] ser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    5b99f
    [java] deser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    3. THIRD PROBLEM:
    Now, when we revert back to style="rpc" and everything works fine anddandy (although
    not as we want it because, as I mentioned above, we want a void
    signature
    and
    a document style), we get the following added tag around our body
    content,
    which
    we did not add ourselves, nor are we sure yet why it shows up:
    We pass it the following argument:
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    We get the following (notice the <document> tag around it):
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    4. PROBLEM FOUR (just remembered this one):
    If we use the standard test page (provided with WLS), with (3) above,it
    chops
    off the "those" and it still wraps it within this new <document>
    element
    as show
    below:
    <!--REQUEST.................-->
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Header>
    </env:Header>
    <env:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    We're not so worried about the fourth because it seems like a bug butthe
    first
    three (especially the first) are most important. Any ideas would beappreciated.
    Thanks
    sami

  • SOAP in XI: message use="encoded" and binding/@style="rpc"

    Hi
    Hope somebody who is familiar with XIs SOAP implementation could give the answer for my questions. Problem is that the SOAP server is not working but I am afraid that the reasons are not really simple.
    In our company we have to provide some SOAP services. I have entered as much as I could in IR ... including a simple scenario. Then imported the scenario to ID and the wizard created a number of agreements and determinations...
    As I need to describe the service to external parties, then I used IDs Web Service definition tool to generate the WSDL.
    But as the external messaging framework (for us a preprogrammed SOAP client) is fixed, I noticed that there are some differences that might matter.
    XI generated WSDL where SOAP binding has
    wsdl:binding/soap:binding/@style="document" but I would need it to be "rpc"
    And the second thing is that in binding message bodies have attribute @use="literal" but as the messages should have several parts then it should be "encoded" (and encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    also is needed then).
    Could somebody explain if these may be the reasons why the soap server does not work. And if there is a way to define soap interface so that it would have above mentioned properties as needed.
    A easy question also... I would need for a method to have an empty message... inside soap body there should be just a tag with the message name and no content. But I can not figure out how to create a message type with no datatype.
    Thanks for any input!

    Hi, Stefan
    Thanks for the answer. To clear my questions: we want to deploy XI as the SOAP server (sry I have not figured out if it is a sender or receiver channel by name - all this inbound-outbound naming in XI is quite complex). Our SOAP server/XI is actually  just one part of a big SOAP network and MAFIA it uses rpc styled SOAP messages.
    The note is really useful, but still it does not give any hint how to make a RPC styled SOAP interface. So the problem is still up for me. As I am not very familiar with WSDL bindings and SOAP... for the message it self, is there any difference as for the RPC vs DOCUMENT style is discussed? Is it possible that the physical structure of a SOAP envelope could be the same?
    And the second question: is there a way in IR to define several parts for a message. Something like:
    <message name="isiku_andmed">
      <part name="paring" type="tns:isiku_andmed_paring" />
      <part name="keha" type="tns:isiku_andmed_keha" />
    </message>

  • Problem in Web service - document style

    Hi,
    I want to create document style webservices using axis tool.
    so i need any sample codes and procedure for creating document style web services using axis tool . If any one help me in regarding this i will be thankfull to u.
    regards
    tuty.richard

    WSADMIN transaction is obsolete from SAP NetWeaver AS 7.00, SP14. and help documentation says following: The same you can get it from information pop-up.
    Start of Help Doc***************
    From SAP NetWeaver AS 7.00, SP14, new service definitions in the ABAP development environment are no longer administered using transactions WSADMIN and WSCONFIG.
    The transactions WSADMIN and WSCONFIG will remain active until all old web service configurations have been migrated, which means you can continue to configure web services from SAP NetWeaver AS 6.40, 7.00, and web service definitions from the XI 3.0 environment. You can also continue to access the runtime configurations of old service definitions using these transactions.
    However, new service definitions created in the ABAP development environment will be hidden in these transactions.
    End of Help Doc***************
    So, You have to use SOAMANAGER transaction if your release is more than whatever specified above.
    Regards,
    Siva.

  • Copy and paste style in pages

    I select one paragraph, tap on Copy Style, it seems to work.
    I go laterr in the document, select another paragraph, and look for a Paste Style command. Frequently, perhaps usually, it is there and works. Other times, for no discernible reason, it simply does not and will not. All I can do is Copy Style for that new paragraph, and nothing seems to work to enable the paste style function.
    Does anyone have any idea of why this should be and perhaps some approach to use when this happens? TIA.

    This happens to me all the time as well!
    I work in Pages daily (as a professional writer no less) and virtually everytime Copy and Paste Style fails completely.
    It simply ignores the request, or sometimes it changes only the font but not the color.  Still other times it change steh font to anotehr type entirely!
    It's beyond frustrating.
    I notice also that whether or not you copy from a paragraph mark it sometimes affects it.
    There is no consitency that I can find.
    I will note I am using the latest Pages for the latest Lion, but my documents were imported from MS Word 2004.

  • Copy and paste styles do not work in toolbar

    I cannot get the copy and paste style functions in the toolbar to work properly for Pages 5.5.   is this something not available in 5.5?
    Do I need to export my document back to Pages 4.3 to have that feature available?

    Hi Pcenginefx,
    This is expected behavior. Marking In and Out points in clip thumbnails is not supported directly in the Media Browser, you must import the clips to the Project panel first. Clips in the Media Browser cannot have metadata added to them to them (like In and Out points) until they are in the project.
    You can still open the clips from the Media Browser into the Source Monitor to set In and Out points before importing them into the project if that workflow is important to you.

Maybe you are looking for

  • Recaptcha not working blank associated values

    I have two issues it seems and any help would be appreciated.  on the page www.socalda.org/meetfrm.php I built a form in Dreamweaver to add meeting changes and then the information is sent to me and one other person in charge of the material.   The f

  • Payment processing temporarily unavailable

    I Cant Update or download any Apps and Im using IOS7,,,,Am i The only one getting this msg ?

  • Problems with Taxonomy and Classification

    We are currently on EP6 SP2 and are going live in a couple of weeks. Currently, we are stuck on our solution to one of the requirements and cannot seem to find a way out of it. I would really appreciate anyone's help in this regard. We have a web rep

  • Trying to update Indesign.

    Have CS5, and downloaded CS5.5 patch. It won't install and I'm getting a "error loading updating workflow" message. The file I downloaded had three zipped files within a zipped file, so I took the content of those and put them loose in the main unzip

  • Hi every one. My iPhone does not connect wi-fi - the icon just stay static. Some helpful tip?

    Hello everyone! my iPhone does not accept the wi-fi function. Trying to switch it on, the icon just stays static. Some helpful idea?