Does DII support document based web service?

Hi,
I am writing a web service cleint DII, the web service is document based. I followed the sample in
https://bpcatalog.dev.java.net/nonav/soa/standalone-client/
Everything seems correct. When I call call.invoke, I got an exception saying "operation style: \"document\" not supported".
Here is the code fragment, can anyone tell me what's wrong or does DII support document based service?
Thanks a lot!
Y. Zhao
try {
ServiceFactory factory = ServiceFactory.newInstance();
service = factory.createService(new QName(EXTRACTURLSERVICE));
port = new QName(EXTRACTURLPORT);
} catch (Exception se) {
// throw new Exception("Can not create stock service: " + se.getMessage());
_endPointAddr = "http://www.atomic-x.com/xmlservices/HyperlinkExtractor.asmx";
_qnameNamespaceURI = new QName("ExtractUrl");
requestQname = new QName(NAMESPACE_URI, "ExtractUrl");
responseQname = new QName(NAMESPACE_URI, "ExtractUrlResponse");
Call call = null;
     try {
call = service.createCall(port);
call.setTargetEndpointAddress(_endPointAddr);
call.setProperty(Call.SOAPACTION_USE_PROPERTY,
Boolean.TRUE);
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://www.atomic-x.com/xmlservices/HyperlinkExtractor/ExtractUrl");
call.setProperty("javax.xml.rpc.encodingstyle.namespace.uri", "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "literal");
call.addParameter("parameters", requestQname, ExtractUrl.class, ParameterMode.IN);
call.setReturnType(responseQname, ExtractUrlResponse.class);
result = (ExtractUrlResponse)call.invoke((Object[])params);
     } catch (Exception ex) {
//throw new ServiceException("Can not get service: " + ex.getMessage());
String msg = ex.getMessage();
ex.printStackTrace();
     }

There shouldn't be any restriction on the type of payload that's specific to DII.
I did come across a similar message, but I found the cause back in the WSDL rather than the client code. Have a look at the WSDL and see if it mentions "RPC" meaning the web service is making available a remote procedure call interface.

Similar Messages

  • Document-based web services - WebLogic 8.1

    Hi all,<br>
    I'm exposing a stateless session bean method as a web service. The in/out parameters are XML documents so my method signature looks as follows:
    <br><br>
    public Document collectMessages( Document request )
    <br><br>
    Accordingly I want to use document-based web services. I use <b>servicegen</b> to create all server-side classes required for the web service.
    <br><br>
    I'm testing the service from the WebLogic provided test page. For document-based services, the text-area is initially populated with the following content
    <br><br>
    <pre><!-- Do not know how to create a sample instance for this part due to the following exception:java.lang.InstantiationException: org.w3c.dom.Document. Pls replace this with the correct XML before invoking the service. --->
    <['http://www.revenue.ie/webservices/ris/rcm/webservices']:RcmCollectRequest/></pre>
    <br><br>
    When I invoke the service I get the following error:
    <br><br>
    <pre><!--RESPONSE.................-->
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <env:Body>
    <env:Fault>
    <faultcode>Client</faultcode>
    <b><faultstring>Unable to find a matching Operation for this remote invocation <RcmCollectRequest>
    </RcmCollectRequest>. Please check your operation name. </faultstring></b>
    </env:Fault>
    </env:Body>
    </env:Envelope></pre>
    <br><br>
    I've searched for this error and seen it in the forum only a number of times. It seems as though some manual manipulation of the web-services.xml document can solve it. Does anyone have an example? My <b>web-services.xml</b> document looks as follows:
    <br><br>
    <pre><?xml version="1.0" encoding="UTF-8"?>
    <web-services>
         <web-service useSOAP12="false" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices" name="rcmmessageservices" style="document" uri="/">
              <types>
                   <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="http://www.revenue.ie/webservices/ris/rcm/webservices" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices">
                        <xsd:element type="xsd:anyType" name="RcmCollectRequest" nillable="true">
    </xsd:element>
                        <xsd:element type="xsd:anyType" name="RcmCollectResponse" nillable="true">
    </xsd:element>
                   </xsd:schema>
                   <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:ie.revenue.rcm.ejb.session" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:ie.revenue.rcm.ejb.session">
                        <xsd:element type="stns:InvalidRequestException" name="InvalidRequestException">
    </xsd:element>
                        <xsd:element type="stns:SystemUnavailableException" name="SystemUnavailableException">
    </xsd:element>
                        <xsd:complexType name="InvalidRequestException">
    </xsd:complexType>
                        <xsd:complexType name="SystemUnavailableException">
    </xsd:complexType>
                   </xsd:schema>
              </types>
              <type-mapping>
                   <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
    </type-mapping-entry>
                   <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" serializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException">
    </type-mapping-entry>
                   <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" serializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException">
    </type-mapping-entry>
                   <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:anyType" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
    </type-mapping-entry>
                   <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
    </type-mapping-entry>
              </type-mapping>
              <components>
                   <stateless-ejb name="ejbcomp0">
                        <ejb-link path="rcm-ejb-1.0.jar#CustomerMessageController">
    </ejb-link>
                   </stateless-ejb>
              </components>
              <operations>
                   <operation name="collectMessages" method="collectMessages(org.w3c.dom.Document)" component="ejbcomp0">
                        <params>
                             <param style="in" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" location="body" name="document" class-name="org.w3c.dom.Document">
    </param>
                             <return-param xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" location="body" name="result" class-name="org.w3c.dom.Document">
    </return-param>
                             <fault xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException" name="SystemUnavailableException">
    </fault>
                             <fault xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException" name="InvalidRequestException">
    </fault>
                        </params>
                   </operation>
              </operations>
         </web-service>
    </web-services>
    </pre>
    <br><br>
    Thanks in advance,<br>
    Eoin

    Hi Eoin,
    I had the exact problem. Struggled a lot and still couldn't figure out. I think its a problem in 8.1. Not sure. Might want to check with the support guys. If you are struck with 8.1 and still couldn't figure out, AXIS would be a option for you. Just an FYI. Thats what we are doing now.
    Luckily for us we are migrating to 9.1 and I just completed a POC for doc oriented webservices in 9.1. It works like a charm.
    Thanks and good luck
    - Aspert

  • Document based Web Services

    Can any one help me finding the example of document based web serives developed
    using plain java classes.
    I tried the way mentioned in documentation, if I use rpc style and pass xml as
    string it is working fine. but if I use document base, it is not working.

    The example dom.zip doesn't work properly.
    I got following error when I was running the example on JDeveloper 9.0.3. Any
    suggestion ?
    C:\JDEV903\jdk\bin\javaw.exe -ojvm -classpath C:\MyStudy\java\WS3\classes;C:\JDEV903\jdev\lib\jdev-rt.jar;C:\MyStudy\java\1\dom\client.jar;D:\bea\weblogic700\server\lib\webserviceclient+ssl.jar;D:\bea\weblogic700\server\lib\weblogic.jar;C:\JDEV903\jdev\lib\jdev-rt.jar;C:\JDEV903\soap\lib\soap.jar;C:\JDEV903\lib\xmlparserv2.jar;C:\JDEV903\jlib\javax-ssl-1_2.jar;C:\JDEV903\jlib\jssl-1_2.jar;C:\JDEV903\j2ee\home\lib\activation.jar;C:\JDEV903\j2ee\home\lib\mail.jar;C:\JDEV903\j2ee\home\lib\http_client.jar;C:\JDEV903\lib\xmlparserv2.jar;C:\JDEV903\lib\xmlcomp.jar
    -Dhttp.proxyHost=proxy.ouhk.edu.hk -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=localhost|ouhk-15msmdomah|sun17.ouhk.edu.hk|sun18.ouhk.edu.hk|www.ouhk.edu.hk|www4.ouhk.edu.hk
    wl.client.wsServletClient
    java.rmi.RemoteException: web service invoke failed; nested exception is:
         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=0
    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=0
         void weblogic.webservice.core.DefaultPart.toXML(javax.xml.soap.SOAPElement, java.lang.Object,
    weblogic.xml.schema.binding.SerializationContext, boolean, javax.xml.rpc.encoding.TypeMapping)
              DefaultPart.java:260
         void weblogic.webservice.core.DefaultMessage.toXML(javax.xml.soap.SOAPMessage,
    java.lang.Object[])
              DefaultMessage.java:455
         java.lang.Object weblogic.webservice.core.DefaultOperation.invoke(java.util.Map,
    java.lang.Object[], java.io.PrintStream)
              DefaultOperation.java:403
         java.lang.Object weblogic.webservice.core.DefaultOperation.invoke(java.util.Map,
    java.lang.Object[])
              DefaultOperation.java:359
         java.lang.Object weblogic.webservice.core.rpc.StubImpl._invoke(java.lang.String,
    java.util.Map)
              StubImpl.java:225
         java.lang.Object examples.dom.EchoDomServicePort_Stub.echoDom(java.lang.Object)
              EchoDomServicePort_Stub.java:33
         void wl.client.wsServletClient.main(java.lang.String[])
              wsServletClient.java:76
    Process exited with exit code 0.
    Rajesh Mirchandani <[email protected]> wrote:
    See if this helps
    http://dev2dev.bea.com/direct/webservice/index.html
    kaushik wrote:
    Can any one help me finding the example of document based web serivesdeveloped
    using plain java classes.
    I tried the way mentioned in documentation, if I use rpc style andpass xml as
    string it is working fine. but if I use document base, it is not working.--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • How to make Service Callout to Document (XML) Based Web Service Proxy

    Hi,
    I am receiving a String which is basically XML via MQ.
    I want to do a Web Service Callout using the String based XML to a Proxy Service that is a Document Based Web Service.
    When I make the call using the String as the input parameter, I get many PipeLine Exception errors on the console and it does not reach the Web Service.
    Based on my readings, I believe that I need to place an XMLObject variable in the Service Callout instead of a String.
    How do I do this?
    I've tried the fn-bea:inlinedXML function but that does't seem to work.
    Regards
    Aziz

    Hi Anuj, seems that the problem was an invalid character in the Mq Message when I tried to apply the inlinedXML method to it.
    This is resolved now.
    The solution:
    1) Assign Mq $Body to variable
    2) Use Java Callout to remove special characters fn:string(body)
    3) convert Java Output String to XML using inlinedXML xquery function
    4) Do a replace on the $body node contents using the XML variable
    5) Call Web Service.
    if you dont do the XML conversion, the web service throws a Pipeline Exception.

  • DII client for accessing a document style web service

    Hi All,
    I try to access a document style web service using DII JAX-RPC client and used the wscompile tool to produce wrapper classes .
    The following code I used for my work:
    import java.rmi.RemoteException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.encoding.XMLType;
    import javax.xml.rpc.ParameterMode;
    import java.net.URL;
    import nutrient.*;
    public class NuDII{
    private static String endpoint =
    "http://www.strikeiron.com/webservices/usdadata.asmx?wsdl";
    private static String qnameService = "USDAData";
    private static String qnamePort = "USDADataSoap";
    private static String BODY_NAMESPACE_VALUE =
    "http://www.strikeiron.com/";
    private static String ENCODING_STYLE_PROPERTY =
    "javax.xml.rpc.encodingstyle.namespace.uri";
    private static String NS_XSD =
    "http://www.w3.org/2001/XMLSchema";
    private static String URI_ENCODING =
    "http://schemas.xmlsoap.org/soap/encoding/";
    private static String TYPE_NAMESPACE_VALUE =
    "http://www.strikeiron.com/";
    private static QName returnType = new QName(NS_XSD, "string");
    public static void main(String[] args) {
    try {
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(new QName(BODY_NAMESPACE_VALUE,qnameService));
    QName port = new QName(BODY_NAMESPACE_VALUE,qnamePort);
    QName operation = new QName(BODY_NAMESPACE_VALUE,"SearchFoodByDescription");
    Call call = service.createCall(port,operation);
    call.setTargetEndpointAddress(endpoint);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY,"http://www.strikeiron.com/SearchFoodByDescription");
    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,"");
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    QName REQUEST_QNAME = new QName(TYPE_NAMESPACE_VALUE,"SearchFoodByDescription");
    QName RESPONSE_QNAME = new QName(TYPE_NAMESPACE_VALUE, "SearchFoodByDescriptionResponse");
    call.setReturnType(RESPONSE_QNAME, nutrient.SearchFoodByDescriptionResponse.class);
    //call.setReturnType(stringArray);
    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,"SearchFoodByDescription"));
    call.addParameter("FoodKeywords", REQUEST_QNAME,nutrient.SearchFoodByDescription.class,ParameterMode.IN);
    call.addParameter("FoodGroupCode", REQUEST_QNAME, nutrient.SearchFoodByDescription.class,ParameterMode.IN);
    SearchFoodByDescription sfd = new SearchFoodByDescription("BabyFoods","1900");
    //Object[] params = new Object[2];
    //params[0]= new String("BabyFoods");
    //params[1]= new String("1900");try
    Object[] params = {sfd};
    Object result = call.invoke(params);
    System.out.println(result);
    } catch (Exception ex) {
    ex.printStackTrace();
    when I start to execute the client I got the following error:
    java.rmi.RemoteException: Server was unable to process request. --> Object refer
    ence not set to an instance of an object.
    at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:462)
    at NuDII.main(NuDII.java:68)
    Shall any body assist me to solve problem.

    you may have a little better luck in the JNI forum.

  • How do I create a "document-centric" Web Service?

    By document-centric I'm talking about receiving a SOAP message on the server-side, where the initial parsing and security processing (this aspect is very important) is performed but then allowing the developer to access the delivered "payload", i.e. the XML, and perform whatever mapping/processing that is required without automatically mapping to the "standard" auto-generated Java objects.
    It is important that the client receives the "full" complex WSDL and can therefore generate their proxy classes with whatever tool (or language) that is appropriate.
    On the server side we do not want to create hundreds (if not thousands) of Java Bean clases as we already have the legacy code to map XML to Java. The idea is that JAX-RPC only instantiates the SOAPElements that represent the "raw" message, or, if possible, doesn't instantiate any objects whatsoever.
    I've spent many days now trying to find a single well-worked example for this type of Web Service without success - many, many references of the style "..and you can then create a document style web service.." but without the all important "how".
    From what I've read a custom type-mapping and/or serializer/deserializer could be the answer but again no good, solid examples are forthcoming.
    Another alternative seems to be to create the server side stub-classes using a "dummy" WSDL with the elements set to "anyType" but then distribute the "genuine" WSDL to the clients - we've got a simple example of the kind working but I don't like the idea of "tricking" the system in this way.
    I'm working with WASD 5.1, which in theory conforms with JAX-RPC so any ideas offered here should also apply in that environment.
    Has ANYONE successfully created a service of this type?
    Any help with this issue would be very much appreciated and rewarded (with Duke Dollars of course).
    Chris.

    Chris,
    I too noticed that most vendors take the RPC centric approach. Its because most of the industry examples of how WSs were used were simple enough to implement using RPC and anything more (document literal) would add to the complexity of implementation. This is something that is feared by many developers, especialy the .Net crowd who seem to want everything done through a wizard menu interface and don't care about other WS implementations at all.
    This is sort of changing. J2EE 1.4 is WS-I compliant, so when you compile server side ties from WSDL you can specify a document literal option and WS-I compliance. This gives you access to the SOAPElement objects. There's still issues with going between W3C DOM and SOAP elements but that's just API inconvenience, not a show stopper. As the inudustry develops more complex WSs we will see the vendors change their tools to better support this...
    Anyway, some more help...
    I use the the following wscompile options to build from WSDL for document literal WSs.
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -import config.xml
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -gen:server config.xml
    My "wrapper" elements look like this...
    <xs:element name="AComplexXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element ref="myNS:MYComplexXMLType"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    If I do this:
    <xs:element name="ASimpleXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="AName" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    I still get the JAXRPC language bindings to a string, but in my case I don't really care. This may well be different for you.
    What I do to manage these elements is to split up the WSDL, WS wrapper element definitions and actual data XML schema definitions into separate documents. This means I have a WSDL which IMPORTS my message schema (this is where I define wrappers for in and out XML) which INCLUDES the actual DATA XML schema that I have.
    The WSDL import looks like this:
    <types>
         <xs:schema>
              <xs:import namespace="http://schemaURI" schemaLocation="./relativePath/WrapperElementSchema.xsd"/>
         </xs:schema>
    </types>
    The wrapper element schema has:
    <xs:include schemaLocation="./ActualDataSchema.xsd"/>
    This way I can easily replace the wrapper documents with just anyType references if something doesn want to play nice. The data schema file and the WSDL stay the same. This minimises the impact on what you have to change in your distribution. This is important as the WSDL is often generated on the fly by your WS environment and so can not be easily changed once you build your WSs, but the schema files it references are easily changed without affecting your code.
    Another reason for the wrapper elements was a JWSDP 1.2 issue (I don't know if this has been fixed in 1.3), where if you had the same method parameter signature in a web service (the parameters it took were the same XML types, for instance if you have an add and update methods for the same document input) JWSDP would get confused at runtime. It did not take account of the SOAP action that came along with the request to determine which operation to call. It just took the incoming XML, saw that it was of a certain type and it passed it to the first operation that took this element, which is VERY wrong. By using the wrapper elements, I could give all my input and output elements for each method different names (I used a naming stragegy that appended a 'request' or 'response' string to the method name to form a method parameter element name. This is a pain in the ass, but works and does wonders for interoperability with other WS vendors. Like I said before, I've got this working with JWSDP, BEA and .Net servers and clients.
    Hope this helps,
    If you think there is a real need for a public HOWTO on this, I could write one with a full step by step guideline that shows where I broke my legs getting this stuff to work. But this would eat into my sleep time :-/ TO JUDGE INTEREST I call on all people interested in a tutorial to respond to this thread (esp people involved with the JWSDP WS tutorial documentation). If I get 5 or more different people responding I will loose some sleep for the good of this community. Otherwise, I will just try to help you when I have time to read the forums.
    Kuba

  • Trouble Communicating with Document-Style Web Service

    I have a flash app that currently communicates with a
    RPC-style web service. I changed the web service to be
    document-style, and the flash app no longer sends valid requests. I
    was under the impression that one could simple swtich styles, and
    flash would play along. Apparently, this is not the case. Does
    anyone have an insight in this area?

    Clarified with Partick Calahan, who is maintaining this tool.
    Currently, doc style is not handled by this tool. I guess it will be
    supported in the future.
    Thanks.
    "Karthik V" <[email protected]> wrote in message
    news:[email protected]..
    I'm using WebLogic Webservice Explorer v.02 (WEX).
    I'm able to test rpc style web services without any problem.
    But whenever I try to open a document style web service WSDL, I get the
    following exception.
    I would appreciate if you have any suggestions for the to over come this
    issue.
    java.lang.IllegalArgumentException at
    weblogic.webservice.tools.wex.MessagePanel.<init>(MessagePanel.java:33)at
    >
    weblogic.webservice.tools.wex.ServicePanel.operationChanged(ServicePanel.jav
    a:153) at
    weblogic.webservice.tools.wex.ServicePanel.portChanged(ServicePanel.java:133
    ) at
    weblogic.webservice.tools.wex.ServicePanel.serviceChanged(ServicePanel.java:
    121) at
    weblogic.webservice.tools.wex.ServicePanel.<init>(ServicePanel.java:69)at
    >
    weblogic.webservice.tools.wex.tasks.FetchWsdlTask.perform(FetchWsdlTask.java
    :45) at
    weblogic.webservice.tools.wex.tasks.TaskQueue.run(TaskQueue.java:47) at
    java.lang.Thread.run(Unknown Source)

  • Problem testing JAXRPC based web services

    Hello,
    I have a JAXRPC based web service. The application was easily tested using earlier versions of sun java system application server.
    But when I am trying to test it using sun java Application Server 9 it is showing an error.
    Do I need to change some configurations?
    Hope to receive solutions.
    Shalmoli

    Hi Eoin,
    I had the exact problem. Struggled a lot and still couldn't figure out. I think its a problem in 8.1. Not sure. Might want to check with the support guys. If you are struck with 8.1 and still couldn't figure out, AXIS would be a option for you. Just an FYI. Thats what we are doing now.
    Luckily for us we are migrating to 9.1 and I just completed a POC for doc oriented webservices in 9.1. It works like a charm.
    Thanks and good luck
    - Aspert

  • Complex schemas using Document Literal Web Services

    I am trying to use document style web services and top down approach. I prepared a request, response and fault schema. In those schemas i have attributes defined. When i use WSCOMPILE, it does not generate proper classes, if the schema is too complex. It has worked only for simple schemas. Is there any other way of doing it?

    Hi!
    If you are using jwsdp 1.6 or earlier and I remember correctly this uses JAXB 1.0 for databinding, which doesnt support all schema constructs.. Even if I'm wrong on that, you could use the -f:nodatabinding option with wscompile and do your own databinding with for example xmlbeans, which supports all schema constructs and is far more flexible than jaxb 1.0 (= personal opinion ;-)
    good luck!
    /Ole

  • Another ESB issue in less than 24 hours!!!! (RPC based web service)

    Ok, now I'm a little upset :-(
    ESB does not support creating a SOAP service if the target service is RPC based and has its messages based on simple type.
    OK, but, BPEL DOES!!!!
    So, why ESB does not???
    Below my target WSDL, which works nicely on BPEL, but I'm not able to configure in ESB:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <!-- Created by TIBCO WSDL
    -->
    - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.example.com/1182368010880/customerInputImpl/RetrieveServices" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns0="http://xmlns.POC.com/unique/default/namespace/customerInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xmlns.example.com/1182368010880/customerInputImpl/RetrieveServices">
    - <wsdl:types>
    - <xs:schema xmlns="http://xmlns.POC.com/unique/default/namespace/customerInfo" targetNamespace="http://xmlns.POC.com/unique/default/namespace/customerInfo" elementFormDefault="qualified" attributeFormDefault="unqualified">
    - <xs:complexType name="customertype">
    - <xs:sequence>
    <xs:element name="SEQUENTIAL" type="xs:string" minOccurs="0" />
    <xs:element name="REFERENCE_TYPE" type="xs:string" minOccurs="0" />
    <xs:element name="ACTION" type="xs:string" minOccurs="0" />
    <xs:element name="COMPANY_CODE" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_STATUS" type="xs:string" minOccurs="0" />
    <xs:element name="STATUS_ADDRESS" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_TYPE" type="xs:string" minOccurs="0" />
    <xs:element name="LEGACY_CODE" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_NAME" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_NUMBER" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_NAME_PHONETIC" type="xs:string" minOccurs="0" />
    <xs:element name="BRANCH" type="xs:string" minOccurs="0" />
    <xs:element name="VERIFIER_DIGIT" type="xs:string" minOccurs="0" />
    <xs:element name="STATE_REGISTRATION" type="xs:string" minOccurs="0" />
    <xs:element name="MUNICIPAL_REGISTRATION" type="xs:string" minOccurs="0" />
    <xs:element name="INDICATOR_CONTRIB_ICMS" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_CATEGORY" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_CLASS" type="xs:string" minOccurs="0" />
    <xs:element name="ADDRESS_TYPE" type="xs:string" minOccurs="0" />
    <xs:element name="ADDRESS1" type="xs:string" minOccurs="0" />
    <xs:element name="DISTRICT" type="xs:string" minOccurs="0" />
    <xs:element name="CITY" type="xs:string" minOccurs="0" />
    <xs:element name="STATE" type="xs:string" minOccurs="0" />
    <xs:element name="ADDRESS3" type="xs:string" minOccurs="0" />
    <xs:element name="POSTAL_CODE" type="xs:string" minOccurs="0" />
    <xs:element name="PHONE_COUNTRY_CODE" type="xs:string" minOccurs="0" />
    <xs:element name="TELEPHONE_AREA_CODE" type="xs:string" minOccurs="0" />
    <xs:element name="TELEPHONE_NUMBER" type="xs:string" minOccurs="0" />
    <xs:element name="TELEPHONE_TYPE" type="xs:string" minOccurs="0" />
    <xs:element name="TELEPHONE" type="xs:string" minOccurs="0" />
    <xs:element name="TELEX" type="xs:string" minOccurs="0" />
    <xs:element name="FAX" type="xs:string" minOccurs="0" />
    <xs:element name="CONTACT_LAST_NAME" type="xs:string" minOccurs="0" />
    <xs:element name="JOB" type="xs:string" minOccurs="0" />
    <xs:element name="TELEPHONE_EXTENSION" type="xs:string" minOccurs="0" />
    <xs:element name="CREATION_DATE" type="xs:string" minOccurs="0" />
    <xs:element name="LAST_UPDATE_DATE" type="xs:string" minOccurs="0" />
    <xs:element name="ERROR_MESSAGE" type="xs:string" minOccurs="0" />
    <xs:element name="GL_ID_REC" type="xs:string" minOccurs="0" />
    <xs:element name="GL_ID_REV" type="xs:string" minOccurs="0" />
    <xs:element name="PAYMENT_METHOD_NAME" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_PROFILE_CLASS_NAME" type="xs:string" minOccurs="0" />
    <xs:element name="CUSTOMER_ATTRIBUTE" type="xs:string" minOccurs="0" />
    <xs:element name="ACCOUNT" type="xs:string" minOccurs="0" />
    <xs:element name="TAX_BUREAU_ADDRESS" type="xs:string" minOccurs="0" />
    <xs:element name="SALES_TERRITORY" type="xs:string" minOccurs="0" />
    <xs:element name="REGISTRATION_TYPE" type="xs:string" minOccurs="0" />
    <xs:element name="LAST_UPDATED_BY" type="xs:string" minOccurs="0" />
    <xs:element name="CREATED_BY" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    - <xs:element name="customer">
    - <xs:complexType>
    - <xs:sequence>
    - <xs:element ref="ns0:customerInfo" maxOccurs="unbounded">
    - <xs:annotation>
    <xs:documentation>Comment describing your root element</xs:documentation>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    - <xs:element name="customerInfo" type="ns0:customertype">
    - <xs:annotation>
    <xs:documentation>Comment describing your root element</xs:documentation>
    </xs:annotation>
    </xs:element>
    </xs:schema>
    </wsdl:types>
    - <wsdl:service name="customerInfo">
    - <wsdl:port name="SOAPEventSource" binding="tns:SOAPEventSourceBinding">
    <soap:address location="http://COMPANHI-F20AF2:8889/RetrieveServices/customerInfo" />
    </wsdl:port>
    </wsdl:service>
    - <wsdl:portType name="customerInterface">
    - <wsdl:operation name="customerInput">
    <wsdl:input message="tns:customerRequest" />
    <wsdl:output message="tns:customerResponse" />
    </wsdl:operation>
    </wsdl:portType>
    - <wsdl:binding name="SOAPEventSourceBinding" type="tns:customerInterface">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="customerInput">
    <soap:operation style="rpc" soapAction="/RetrieveServices/customerInfo" />
    - <wsdl:input>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://InputMessageNamespace" parts="customerRequestDATA" />
    </wsdl:input>
    - <wsdl:output>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://OutputMessageNamespace" parts="customerResponseDATA" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    - <wsdl:message name="customerRequest">
    <wsdl:part name="customerRequestDATA" type="ns0:customertype" />
    </wsdl:message>
    - <wsdl:message name="customerResponse">
    <wsdl:part name="customerResponseDATA" type="xs:string" />
    </wsdl:message>
    </wsdl:definitions>
    Now, I'm thinking about what to tell to the customer of my proof of concept :-(
    Denis

    I do agree that we need to go through Oracle SR process to get any resolution instead of just relying on public forums. That helps you, Oracle and others facing similar issue.
    Having said that I also can understand Heizard frustration because I felt the same way some times. Oracle needs to improve on their Support personnel skill set in SOA suite arena. The current support process makes you think twice/thrice...before you log a SR. In most of the cases you feel like training them with the tool set....:-(
    Let me give you a real situation. I created a simple test case with file in and file out bound adapter for one of my issues and uploaded to SR. Guess what the analyst came up with....can I do OWC with you to understand the scenario..or SR is missing which file to use to test etc..and the SR goes to @CUS status.....you loose a day or two on this....
    Once you were able to get through that first layer you will be impressed the kind of support you get. I am in same boat working aggressively on couple of critical SRs. Once those gets into development court I was able to resolve them in matter of weeks. It's only that getting there took me a while.
    So it all depends on what your timelines are and what kind of relationship you have with Oracle (read how deep you are with Oracle products)
    ESB is very lightweight and it does some trivial things very quickly. It also lot easier on developers who are new to whole web services world.
    So far I have been trying only Doc/Lit services because that's what our standard is and assumed RPC/Lit just works. Now this thread started to worry me as well. So better give it a spin and start Oracle Support fun.....:-)
    Regards,
    Rajesh

  • Future of Document/Literal Web Services in CF

    I would like some clarification on the future of web services
    in CF. Right now I use CF 7 RPC/encoded CFCs which communicates
    with a Java client product currently using the older JWSDP 1.6 for
    web services. However the new Java SOA with WS-Security has been
    out for a while but I cannot convert to it because it doesn't
    support the outdated RPC/encoded format and CF 7 does not handle
    Document/Literal properly. CF 7 does not properly handle cfproperty
    element arrays in publishing Document/Literal web services (well
    documented problem with CF and the current Axis engine).
    However JavaSE 6 is nearing a release and it too will not
    support RPC/encoded or xsd_AnyType, nor will it support the current
    Document/Literal produced by CF 7 which does not properly handle
    arrays for cfproperty elements. This may become a major problem for
    my application as all the Java environments are upgraded.
    Therefore is this issue being addressed in the upcoming CF 8
    release?
    Will CF 8 be upgraded to Axis2 and properly support
    Document/Literal arrays for cfproperty elements?
    When might we expect a release of CF 8?
    Is it possible for CF 7 to use Axis2?
    CF has been a great product but I do need to assess some
    options if CF can not handle Document/Literal arrays for cfproperty
    elements within the near future.
    Thanks,
    Jason Baumgartner
    Indiana University

    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?

  • URGENT: Error while invoking soap-based web service from BPEL process

    I am trying to invoke a soap-based web service deployed in a different OC4J container but on the same iAS middle tier install as the BPEL server. The deployment is successful. I am running 10.1.2 BPEL server.
    But invoking a process throws the following error.
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    <part name="summary">
    <summary>when invoking locally the endpoint 'http://stadd53.us.oracle.com:7779/idm/ProvService/cps', ; nested exception is: ORABPEL-02052 Cannot lookup BPEL domain. The BPEL domain "ProvService" cannot be found; the domain may not have initialized properly. Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.</summary>
    </part>
    <part name="detail">
    <detail>ORABPEL-02052 Cannot lookup BPEL domain. The BPEL domain "ProvService" cannot be found; the domain may not have initialized properly. Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.</detail>
    </part>
    </remoteFault>
    Any ideas on what the problem might be ?

    Sandor,
    Thanks. Your suggestion of turning off optSoapShortcut worked. So does that mean that by default remote web services cannot be invoked from BPEL process by SOAP - unless this configuration change is done ?

  • Document style web service receive and send org.w3c.Element

    All,
    I have created a simple Document-oriented web service and deployed to a standalone OC4J container using the following code:
    ********************* Interface ***********************
    import org.w3c.dom.*;
    interface PrimeNumberService
    //method to check the primality of the number passed in Element variable
    public Element isPrime(Element e) ;
    ******************** Implementation *******************
    @version 1.0
    Development Environment : Oracle9i JDeveloper
    Name of the File : PrimeNumberServiceImpl.java
    Creation/Modification History :
    13-Apr-2002 Created
    Overview:
    This class file defines methods to implement PrimeNumberWebService.
    The method isPrime() is exposed by the Web Service.
    import org.w3c.dom.*;
    import oracle.xml.parser.v2.*;
    import java.io.*;
    public class PrimeNumberServiceImpl implements PrimeNumberService
    public PrimeNumberServiceImpl()
    * This method is exposed by the Web Service to check if the number is
    * prime. It extracts the number for input element and checks if it is
    * prime or not and return the output in the XML Element.
    * The input element is of the form <number>23</number>
    public Element isPrime(Element e)
    // define an XML Element that will be returned to the client
    Element processedEl=null;
    try{
    // get the first clild of input element
    Node enode = e.getFirstChild();
    //get the value of input element and parse it
    String value= enode.getNodeValue();
    double number = Double.parseDouble(value);
    String answer=null;
    // check if the input number is prime
    answer = checkPrime(number);
    // create element from the answer
    processedEl =createElement(answer);
    }catch(Exception ex){
    ex.printStackTrace();
    return null;
    // return output to client
    return processedEl;
    * This method creates an XML element from the input string values and return it
    * The Element is of the form <answer>value</answer>
    private Element createElement(String value){
    // create a Document object
    Document xmldoc = new XMLDocument();
    // create an element with name "answer"
    Element e1 = xmldoc.createElement("answer");
    // append the element to document object
    xmldoc.appendChild(e1);
    // create a Text object from input values and append it to above element
    Text t = xmldoc.createTextNode(value);
    e1.appendChild(t);
    return (Element)xmldoc.getFirstChild();
    * This method check if the input number is prime or not
    private String checkPrime(double num){
    //For a prime number mod(power(2,number),number) is equal to 2
    if ( Math.IEEEremainder( Math.pow(2.0,num) ,num)==2){
    System.out.println ("the number is: " + num);
    return "The number " + num + " is prime";}
    else{
    System.out.println ("the number is: " + num);
    return "The number " + num + " is not prime";}
    ************************ Generated WSDL ***************
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="PrimeNumberService"
    targetNamespace="http://tempuri.org/PrimeNumberService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://tempuri.org/PrimeNumberService.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >
    <documentation>
    WSDL for Service: PrimeNumberService, generated by Oracle WSDL toolkit (version: 1.1)
    </documentation>
    <types>
    <schema targetNamespace="http://tempuri.org/PrimeNumberService.xsd" xmlns:tns="http://tempuri.org/PrimeNumberService.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
    </types>
    <message name="isPrimeOutput">
    <part name="return" element="xsd:any"/>
    </message>
    <message name="isPrimeInput">
    <part name="param0" element="xsd:any"/>
    </message>
    <portType name="PrimeNumberServicePortType">
    <operation name="isPrime">
    <input message="tns:isPrimeInput"/>
    <output message="tns:isPrimeOutput"/>
    </operation>
    </portType>
    <binding name="PrimeNumberServiceBinding" type="tns:PrimeNumberServicePortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <operation name="isPrime">
    <soap:operation soapAction="urn:PrimeNumberService/isPrime"/>
    <input>
    <soap:body use="literal" namespace="urn:PrimeNumberService"/>
    </input>
    <output>
    <soap:body use="literal" namespace="urn:PrimeNumberService"/>
    </output>
    </operation>
    </binding>
    <service name="PrimeNumberService">
    <port name="PrimeNumberServicePort" binding="tns:PrimeNumberServiceBinding">
    <soap:address location="http://hp-xeon-01:9799/primenumberws/primenumberService"/>
    </port>
    </service>
    </definitions>
    I get the following error when trying to deploy:
    Error:
    [Error ORABPEL-10902]: compilation failed
    [Description]: XML parsing failed because "undefined part element.
    In WSDL at "http://hp-xeon-01:9799/primenumberws/primenumberService?WSDL", message part element "{http://www.w3.org/2001/XMLSchema}any" is not defined in any of the schemas.
    Please make sure the spelling of the element QName is correct and the WSDL import is complete.
    [Potential fix]: n/a.
    Please let me know what I'm doing wrong.
    Regards,
    Jeff

    Here is the error code that I'm getting at the invoke:
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    <part name="code">
    <code>Client</code>
    </part>
    <part name="summary">
    <summary>parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /.</summary>
    </part>
    <part name="detail">
    <stackTrace xmlns="http://xml.apache.org/axis/">parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /. 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) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226) at org.collaxa.thirdparty.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.collaxa.thirdparty.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.collaxa.thirdparty.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.collaxa.thirdparty.apache.axis.client.AxisClient.invoke(AxisClient.java:173) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2725) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2708) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1738) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:1902) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1464) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1029) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:455) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:359) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:161) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:605) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3501) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1906) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:101) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:186) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5604) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1301) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:117) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:146) at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:483) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:489) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132) at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:82) at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:479) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65) at ngDoInitiate.jspService(_ngDoInitiate.java:220) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) at displayProcess.jspService(_displayProcess.java:303) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220) at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192) at java.lang.Thread.run(Thread.java:534)</stackTrace>
    </part>
    </remoteFault>

  • Document Literal Web Service Stub Error

    I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
    On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
    Any help would be much appreciated.

    I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
    On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
    Any help would be much appreciated.

  • Problem Generating Document/Literal Web Service

    Hi folks..
    I am currently using JDeveloper 10.1.3 (Preview Edition) and I am having trouble getting the Create Java Web Service wizard to work correctly when generating a document/literal web service. After going through the wizard selecting the appropriate settings to generate a document/literal web service from my implementation I get the following error during generation.
    oracle.j2ee.ws.common.tools.api.SeiValidationException
    oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:587)
    oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:455)
    oracle.j2ee.ws.common.processor.config.ModelInfo.buildModel(ModelInfo.java:160)
    oracle.j2ee.ws.common.processor.Processor.runModeler(Processor.java:76)
    oracle.j2ee.ws.common.tools.wscompile.CompileTool.run(CompileTool.java:510)
    oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.createWSDL(JavaToWsdlTool.java:234)
    oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:313)
    oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:205)
    oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:131)
    oracle.j2ee.ws.tools.wsa.Util.processAnnotations(Util.java:77)
    oracle.jdeveloper.webservices.model.java.JavaGenerator.generateWSDLFromAnnotations(JavaGenerator.java:1188)
    oracle.jdeveloper.webservices.model.java.JavaGenerator.doGeneration(JavaGenerator.java:362)
    oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:330)
    oracle.jdeveloper.webservices.model.Generator.access$1000071(Generator.java:100)
    oracle.jdeveloper.webservices.model.Generator$1$ReturningRunnable.run(Generator.java:250)
    oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:344)
    oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:526)
    java.lang.Thread.run(Thread.java:534)
    When I googled this error I actually get a hit for a thread here on this board, that looks VERY promising... but when I attempt to access it I get a message "Duscussion Forms Error" and I cant access it. (Very frustrating believe me.. :-)
    Any help that you can give would be appreciated...
    Thanks
    Dave

    Hi Dave,
    One reason to have the SeiValidationException is when you do not follow the java bean convention for getter/setter or some of the public methods you want to expose are not throwing the right execption.
    Using the command line utility genProxy [or the ant task] with the debug flag may give you some informations about the WSDL constructs WSA do not understand. Look at the following how-to to get started:
    http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-ws-bottomup/doc/how-to-ws-bottomup.html
    If this does not help, can you share your WSDL with us ?
    Thanks,
    Eric

Maybe you are looking for

  • How to handle accessing different types of files in e-tester

    I have a page which has 8 links: 1st link points to a zipper file, 2nd~7th link point to several word file and 8th link points to a GIF file. In this step, i will just randomly click one link and verify if the file can be successfully accessed. The p

  • Error Message: "Please install Apple Application Support" after QT7 Install

    Greetings: I attempted to update my Quicktime 6 application to QT7, but the install stopped partway through. I uninstalled Quicktime completely, and started over with a download and clean install of Quicktime 7.6.7. When I try to run my newly install

  • Restoring old photos using E9

    Is it posible to restore an old photo that has been partly sun bleeched using Elements 9? Any tips would be very welcome.

  • Multiple blogs with different sidebars

    We created a second blog on our site. I would like the two blogs to have different sidebars. I found the original sidebar in: Module Templates -> Blog Layouts -> Overall Blog Layout I would like to duplicate this file and modify the content and assig

  • Help needed, new to java programming

    hi, I have craeted a Frame with some check boxes and button called "button1". Can anyone tell me how can i count the number of CHECKED check boxes so that when i press the button1 in my code it should display the result as number of checked check box