JAX-RPC wscompile modeler error

I run wscompile with the following arguments:
-verbose -keep -features:documentliteral -gen:both -d generated -nd other -s source -model model.txt config.xmlI am getting an error message running JAX-RPCs wscompile tool against my WSDL. The error message is:
error: modeler error: model error: undeclared namespace prefix: ""
Unfortunately, this message doesn't give me enough information to begin locating the problem.
Has anyone else run into this problem?
I am running JWSSDK 1.2 on Windows XP w/JDK 1.4.1.
Thanks,
Chris

i think you should use the encoding and the use
specified bythe wsdl and try to override it. Also
i would encourage you to do this in 2 steps.
As you are starting from a wsdl :
wscompile -import -verbose -keep -d generated -nd other -s source -model model.gz config.xml
then have a config.xml for the client which would
allow you to do
wscompile -gen:client -verbose -keep -d generated -nd other -s source config-client.xml
Also please check the validity of the wsdl or post it back on.

Similar Messages

  • Wscompile modeler error

    I'm trying to use wscompile with a WSDL file and XSDs and it keeps failing with the following error. The error is "[exec] error: modeler error: model error: invalid entity name: "EntityIdType" (in namespace: "http://ns.hr-xml.org/2004-08-02")" The type EntityIdType is defined in one of the included XSDs. The XSDs that I'm trying to use is for the HR-XML spec, so I don't really have any control over the XSDs themselves, but I tend to assume that the XSDs should be valid. I've got the WSDL file and XSDs available at http://quasistatic.com/webservices if anyone would be able to check them out for me. As a side note, I am able to use WSDL2Java from Axis on these files and it works fine. The command that I'm executing is "wscompile.bat -gen:server -f:documentliteral -mapping ${basedir}/generated/jaxrpc-mapping.xml -d ${basedir}/generated -s ${basedir}/generated/src -verbose -keep ${basedir}/wscompile-config.xml" and the wscompile-config.xml file contains:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration
    xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
         <wsdl location="etc/AssessmentResult.wsdl" packageName="com.lominger.survey.assessment"/>
    </configuration>
    Thanks for any help you can provide!

    Vivek,
    Thanks for responding to my post. I am using wscompile version:
    C:\jwsdp-1.5\jaxrpc\bin>wscompile.bat -version
    JAX-RPC Standard Implementation (1.1.2_01, build R40)
    My WSDL and other files are up at http://quasistatic.com/webservices as well, but here's just the WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://assessment.survey.lominger.com/"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://assessment.survey.lominger.com/"
    xmlns:intf="http://assessment.survey.lominger.com/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:hrxml="http://ns.hr-xml.org/2004-08-02"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
    <schema elementFormDefault="qualified"
    targetNamespace="http://assessment.survey.lominger.com/"
    xmlns="http://www.w3.org/2001/XMLSchema">
    <xsd:import namespace="http://ns.hr-xml.org/2004-08-02"
         schemaLocation="hrxml/Assessment/AssessmentResult.xsd" />
    <xsd:element name="AssessmentResultResponse" type="xsd:string">
    <xsd:annotation>
    <xsd:documentation>Root element for AssessmentResultResponse, which is designed to hold data necessary to convey information on the results of the assessment addition</xsd:documentation>
    </xsd:annotation>
    </xsd:element>
    </schema>
    </wsdl:types>
    <wsdl:message name="AddAssessmentResultRequest">
    <wsdl:part element="hrxml:AssessmentResult" name="parameters" />
    </wsdl:message>
    <wsdl:message name="AddAssessmentResultResponse">
    <wsdl:part element="impl:AssessmentResultResponse" name="response" />
    </wsdl:message>
    <wsdl:portType name="Assessment">
    <wsdl:operation name="addAssessmentResult">
    <wsdl:input message="impl:AddAssessmentResultRequest" name="AddAssessmentResultRequest" />
    <wsdl:output message="impl:AddAssessmentResultResponse" name="AddAssessmentResultResponse" />
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="AssessmentSoapBinding" type="impl:Assessment">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="addAssessmentResult">
    <wsdlsoap:operation soapAction="" />
    <wsdl:input name="AddAssessmentResultRequest">
    <wsdlsoap:body use="literal" />
    </wsdl:input>
    <wsdl:output name="AddAssessmentResultResponse">
    <wsdlsoap:body use="literal" />
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="AssessmentService">
    <wsdl:port binding="impl:AssessmentSoapBinding" name="AssessmentPort">
    <wsdlsoap:address location="http://localhost:8180/axis/services/AssessmentResult" />
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Any help you can provide me is MUCH appreciated.
    -Jesse

  • JWSDP 1.4, JAX-RPC, wscompile, http proxies

    I have a JAX-RPC client that works properly. However, I'm trying to modify the client so that RPC calls can go through an http proxy prior to reaching the web service.
    Here are some of the problems I'm experiencing:
    There are posts on this site, and elsewhere on the net, stating that the wscompile -httpproxy:host:port option can be used to provide this solution. However, wscompile generates the same exact code - whether the httpproxy option is used or not. Is this a problem in JWSDP 1.4?
    There are also posts that state to use properties, such as http.proxyHost or proxyHost. I've used several versions of this solution (while using a sniffer to verify network activity), but all that happens is that the code continues to call directly to the web service - not the http proxy. Makes me think these properties are only useful when using http directly. Many of the posts I've seen regarding this are two years old, and I've seen at least three different opinions on how the property strings should be named. Anybody know the real solution?

    For me these system properties do work:
    proxyHost, proxyPort (maybe also http.proxyHost, http.proxyPort) for Http
    https.proxyHost, https.proxyPort for Https
    The nice thing is that from a WebStart application or the plug-in these properties are set automatically from the browser configuration if not reconfigured manually.

  • JAX-RPC + Bean = deserialization error: java.lang.NullPointerException

    I�m trying to use a bean as return type from a web service method, but I get an error:
    deserialization error: java.lang.NullPointerException
    this is the class consuming the web service
    package local.jws;
    import local.jws.remote.TestBeanIF;
    import local.jws.remote.TestBean;
    import java.io.*;
    import java.net.URL;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceException;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.namespace.QName;
    public class Client implements java.io.Serializable
         private TestBean tb;
         private String somestring;
         public Client()
              try
                   String wsURL = "http://localhost:8080/webservice/testbean?WSDL";
                   String nameSpaceURI = "http://local.jws/wsdl/MyTestBean";
                   String portName = "TestBeanIFPort";
                   String serviceName = "MyTestBean";
                   URL serviceURL = new URL( wsURL );
                   ServiceFactory serviceFactory = ServiceFactory.newInstance();
                   QName qServiceName = new QName( nameSpaceURI, serviceName );
                   Service ws = serviceFactory.createService( serviceURL, qServiceName );
                   QName qPortName = new QName( nameSpaceURI, portName );
                   TestBeanIF myTestBeanIF = (TestBeanIF)ws.getPort( qPortName, local.jws.remote.TestBeanIF.class );
                   somestring = myTestBeanIF.getString();
                   tb = myTestBeanIF.getTestBean( "hello bean" );
              catch( Exception ex )
         public TestBean getTb()
              return this.tb;
         public void setTb( TestBean tb )
              this.tb = tb;
         public String getSomestring()
              return this.somestring;
         public void setSomestring( String value )
              this.somestring = value;
    this is the bean:
    package local.jws.beans;
    public class TestBean implements java.io.Serializable
         private String test;
         public TestBean(){ }
         public String getTest()
              return test;
         public void setTest( String value )
              this.test = value;
    this is the interface implementation:
    package local.jws;
    import local.jws.beans.TestBean;
    public class TestBeanImpl implements TestBeanIF
         public TestBean getTestBean( String value )
              TestBean tb = new TestBean();
              tb.setTest( value );
              return tb;
         public String getString()
              return "some string";
    using the getString() method works fine but getTestBean() doesn�t;
    any clue on this?
    thanks

    Hi,
    I'm experiencing exactly the same problem as you ...
    The only fix I found is to use static invocation ... with static invocation, WSCompile generates a deserializer and everything works fine, no mure NullPointer exception ...
    With dynamic invocation as you are trying to manage here, I didn't find any way to tell the client to use the deserializer generated with wscompile ...
    Does anyone know how to do it ?
    Thanks,
    Olivier

  • Problems with jax-rpc HelloWorld sample

    Hi
    Running on Linux Red Hat 9.0
    Jwsdp 1.3
    I'm following the jwsdp tutorial trying to build the jax-rpc HelloWorld sample. I do what the tutorial says:
    "ant build" in the sample directory but it "Fails" with this message:
    init:
    [echo] -------- HelloWorld Sample --------
    prepare:
    generate-server:
    edit-config:
    [wscompile] modeler error: failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorl
    d/etc/HelloWorldService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/Hell
    oWorld/etc/HelloWorldService.wsdl (No such file or directory)
    [wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:179)
    [wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
    [wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
    [wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
    [wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
    [wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
    [wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
    [wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
    [wscompile] CAUSE:
    [wscompile] failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorl
    dService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/Hell
    oWorldService.wsdl (No such file or directory)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImport(WSDLParser.java:252)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLParser.java:170)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:162)
    [wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:126)
    [wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
    [wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
    [wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
    [wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
    [wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
    [wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
    [wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
    [wscompile] CAUSE:
    [wscompile] java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWor
    ldService.wsdl (No such file or directory)
    [wscompile] at java.io.FileInputStream.open(Native Method)
    [wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:106)
    [wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:66)
    [wscompile] at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
    [wscompile] at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
    [wscompile] at java.net.URL.openStream(URL.java:913)
    [wscompile] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:947)
    [wscompile] at org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:893)
    [wscompile] at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(XMLEntityManager.java:846)
    [wscompile] at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(XMLDocumentScannerImpl.java:264)
    [wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:513)
    [wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
    [wscompile] at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
    [wscompile] at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:253)
    [wscompile] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:206)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImport(WSDLParser.java:248)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLParser.java:170)
    [wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:162)
    [wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:126)
    [wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
    [wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
    [wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
    [wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
    [wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
    [wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
    [wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
    [wscompile] error: modeler error: failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/He
    lloWorld/etc/HelloWorldService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/sampl
    es/HelloWorld/etc/HelloWorldService.wsdl (No such file or directory)
    [wscompile] Command invoked: wscompile -d /home/medimg/pablo/jwsdp-1.3/jaxrpc/build/samples/HelloWorld/classes/server -import -keep -model /home/medimg/pablo/jwsdp-
    1.3/jaxrpc/build/samples/HelloWorld/model-wsdl-rpcenc.xml.gz -Xprintstacktrace /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/config.xml -classpath /hom
    e/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/mail.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/activation.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/jaxp-api.jar:/
    home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/dom.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/sax.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/xalan.ja
    r:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/xercesImpl.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrpc-api.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrp
    c-spi.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrpc-impl.jar:/home/medimg/pablo/jwsdp-1.3/saaj/lib/saaj-api.jar:/home/medimg/pablo/jwsdp-1.3/saaj/lib/saaj-impl
    .jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/relaxngDatatype.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/xsdlib.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-s
    hared/lib/jax-qname.jar:/home/medimg/pablo/jwsdp-1.3/apache-ant/lib/ant.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/${compile.classpath}
    BUILD FAILED
    file:/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/build.xml:98: wscompile failed
    I took a look into the etc/config.xml file and the path location of HelloWorldService.wsdl is fine as follows
    "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorldService.wsdl"
    BUT.. after "ant build", the path in th config.xml file automatically change for:
    "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorldService.wsdl"
    Anybody knows how to solve this problem
    HELP !!!
    J.Pablo

    Hi,
    I guess you need some changes in your build script.
    One solution would be to specify correct value for location attribute in your config.xml and then
    uncomment the call to "edit-config" target as show below in your build.xml file:
    <target name="generate-server" depends="prepare">
    <!--antcall target="edit-config">
    <param name="config.rpcenc.file" value="${config.rpcenc.file}"/>
    </antcall-->
    -Amol

  • Jax-rpc endpoint interface

    in richard mansion-haffel book, endpint interface (which extends java.rmi.Remote ) is mentioned .
    but when i try to build a sample application in weblogic or axis , endpoint interface is not yet all used.
    the implementation class is used directly.
    can any one please tell me abt endpoint interface..

    I had found a solution on this. By changing the SessionBean extends EJBObject to Remote, then problem solved.
    But here I had a newer challenge, this is the error log:
    2006-05-15 15:37:00,296 ERROR gov.mohr.ems.core.entity.logic.PersistenceWebServicesTest - javax.xml.rpc.ServiceException: modeler error: expected root element "definitions" (in namespace "http://schemas.xmlsoap.org/wsdl/"), found element "html" (in namespace "http://www.w3.org/1999/xhtml")

  • XML Parser Error while creating Web service Client using JAX RPC

    hello evryone,
    Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
    wscompile -gen:client -d build -classpath build config-wsdl.xml
    here im getting Error:
    error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
    Please help me out.
    Many thanks in advance,
    Kacee

    Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

  • Cannot import WSDL to JAVA JAX-RPC (using WSCOMPILE)

    I exported a WSDL-file (i.e. for RFC_PING) via the BSP WebServiceBrowser (WAS 6.20). For generating the interface i have to start the wscompile-tool of JAX-RPC (right ?). But wscompile answers with an error:
    unerwartetes Element "definitions" in Konfigur
    ationsdatei (Zeile 1)
    Are the WSDL-files not compatible ? How I have to work with the WSDL ?

    Oops, i used a wrong configfile for the wscompile tool. It's all right now.

  • JAX-RPC documentliteral with -model option problems in JWSDP 2.0

    Hello,
    I am trying to deploy a service generated with JAX-RPC. Howeverr when I write URL (http://localhost:8080/webservicedeployable/webservice001) in a browser I am getting message: 404 Not Found: Invalid request. Appending ?WSDL shows propers wsdl code, so endpoint URL is allright.. There is my config file delow:
    <?xml version="1.0" encoding="utf-8"?>
    <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
      <service name="webservice001"
               targetNamespace="http://scdjws/webservices/wsdl"
               typeNamespace="http://scdjws/webservices/types"
               packageName="com.service001">
        <interface name="service.MyServicePort" servantName="service.MyServiceImpl"/>     
      </service> 
    </configuration>I am using command:
    wscompile -gen:server -f:documentliteral -s "C:\Documents and Settings\Michal\jbproject\mojservice\src\" -classpath WEB-INF/classes -d build -model webservice001.xml.gz config.xml -keepmy jaxrpc-ri.xml is:
    <?xml version="1.0" encoding="utf-8"?>
    <webServices xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
                 version="1.0"
                 targetNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/wsdl"
                 typeNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/types"
                 urlPatternBase="/ws">
      <endpoint name="service001"
                displayName="Service 001"
                description="This is service001"
                interface="service.MyServicePort"
                implementation="service.MyServiceImpl"
                model="/webservice001.xml.gz"/>
      <endpointMapping endpointName="service001"
                       urlPattern="/webservice001"/>
    </webServices>I am using Tomcat 5.5.16 and JWSDP 2.0.
    Making a call to the service throws exception:
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/webservicedeployable/webservice001
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:791)
    Thank you in advance for all suggestion.
    Michal

    Hi,
    I reselved the problem by just copying the FastInfoset to the jaxrpc\lib directory (I am sure this should work in a different way).
    Well, the next problem I am getting is that the "XMLStreamWriter" class cannot be found. This class is contained in jsr173_api.jar.
    I guess my main question is the following:
    Which projects are necessary to get this simple helloWorld example to work?
    I did set the JWSDP_HOME varible. Is there another setting I have to make to have all necessary jar-files available and to be able to run the samples?
    Could anybody point me to a tutorial that does not only show a few lines of code (as the HelloWorld sample in the JWSDP-Tutorial) but that would instead lead me through a step-by-step sample application that I write by myself and actually runs at the end? The example in the JWSDP-Tutorial uses all kinds of existing config files which are not explained.
    Thanks for your help.

  • Weblogic 8, no jax-rpc context info available error

    i've developed some web services using the jwsdp 1.3. they deploy and run fine in jwsdp 1.3 and also in jboss 3.2. i deployed the same web services in weblogic 8.1 with no problems. when i access the web service and the wsdl, i get the following error:
    Web Services
    No JAX-RPC context information available.
    my jaxrpc-ri.xml is:
    <?xml version="1.0" encoding="UTF-8"?>
    <webServices
        xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
        version="1.0"
        targetNamespaceBase="urn:Foo"
        typeNamespaceBase="urn:Foo"
        urlPatternBase="/ws">
        <endpoint
            name="JobService"
            displayName="WorkPoint Job Service"
            description="WorkPoint Job Service for API calls"
            interface="com.workpoint.webservices.JobServiceIF"
            wsdl="/WEB-INF/JobService.wsdl"
            model="/WEB-INF/JobService.xml.gz"
            implementation="com.workpoint.webservices.JobServiceImpl"/>
        <endpoint
            name="ServerConfigService"
            displayName="WorkPoint ServerConfig Service"
            description="WorkPoint ServerConfig Service for API calls"
            interface="com.workpoint.webservices.ServerConfigServiceIF"
            wsdl="/WEB-INF/ServerConfigService.wsdl"
            model="/WEB-INF/ServerConfigService.xml.gz"
            implementation="com.workpoint.webservices.ServerConfigServiceImpl"/>
        <endpoint
            name="WorkItemService"
            displayName="WorkPoint Job Service"
            description="WorkPoint Job Service for API calls"
            interface="com.workpoint.webservices.WorkItemServiceIF"
            wsdl="/WEB-INF/WorkItemService.wsdl"
            model="/WEB-INF/WorkItemService.xml.gz"
            implementation="com.workpoint.webservices.WorkItemServiceImpl"/>
        <endpointMapping
            endpointName="JobService"
            urlPattern="/JobService"/>
        <endpointMapping
            endpointName="ServerConfigService"
            urlPattern="/ServerConfigService"/>
        <endpointMapping
            endpointName="WorkItemService"
            urlPattern="/WorkItemService"/>
    </webServices>any ideas on what is going on? also, what is the urlPatternBase used for?

    I had this problem when I created custom web services : some classes where not generated in the right folder (ie package name).
    Check the content of the generated war to see if all the necessary classes and files are in it and in the right place.

  • JAX-RPC deserialization error: unexpected XML reader state

    Guys,
    Trying to write a Jax-Rpc client that consumes a web service hosted on WebLogic 7.1 talking soap 1.1. I can bind to that service using Apache SOAP - so I don't think that service is returning invalid XML.
    Is there something in my client's classpath that's old or not compatible ?
    Getting the following exception
    java.rmi.RemoteException: Runtime exception; nested exception is:
    deserialization error: unexpected XML reader state. expected: END but found: START: stockSymb
    ol
    deserialization error: unexpected XML reader state. expected: END but found: START: stockSymbol
    at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:209)
    at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerIm
    pl.java:115)
    at trader.TraderServicePort_buy_ResponseStruct_SOAPSerializer.doDeserialize(TraderServicePort
    buyResponseStruct_SOAPSerializer.java:37)
    at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:165)
    at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerIm
    pl.java:115)
    at trader.TraderServicePort_Stub._deserialize_buy(TraderServicePort_Stub.java:180)
    at trader.TraderServicePort_Stub._readFirstBodyElement(TraderServicePort_Stub.java:153)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:168)
    at trader.TraderServicePort_Stub.buy(TraderServicePort_Stub.java:115)
    at portal.jsp._portal._test.__TestJaxrpc._jspService(__TestJaxrpc.java:83)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:2
    69)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
    CAUSE:
    unexpected XML reader state. expected: END but found: START: stockSymbol
    at com.sun.xml.rpc.streaming.XMLReaderUtil.verifyReaderState(XMLReaderUtil.java:49)
    at trader.TradeResult_SOAPSerializer.doDeserialize(TradeResult_SOAPSerializer.java:66)
    at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:165)
    at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerIm
    pl.java:115)
    at trader.TraderServicePort_buy_ResponseStruct_SOAPSerializer.doDeserialize(TraderServicePort
    buyResponseStruct_SOAPSerializer.java:37)
    at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:165)
    at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerIm
    pl.java:115)
    at trader.TraderServicePort_Stub._deserialize_buy(TraderServicePort_Stub.java:180)
    at trader.TraderServicePort_Stub._readFirstBodyElement(TraderServicePort_Stub.java:153)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:168)
    at trader.TraderServicePort_Stub.buy(TraderServicePort_Stub.java:115)
    at portal.jsp._portal._test.__TestJaxrpc._jspService(__TestJaxrpc.java:83)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:945)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:909)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:2
    69)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:392)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:274)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
    Thanks
    Atish

    Using WSDP 1.1 this can be fixed IF you're using a static stub to access the service by running wscompile with the -f:searchschema option when generating the client stubs. It will then search the schema aggressively for subtypes when generating the stubs and your client will function correctly. The downside is that this ties your client down to using implementation specific functionality that is not part of the standard, which IMHO is very bad but if you're happy to live with this then it will work.
    Therefore I want to use a dynamic proxy client. For this you don't need to use the wscompile tool to generate client stubs and therefore the above fix doesn't work. I have searched the API documentation for some method that would have the same effect but thus far to no avail. Does anybody have any ideas?
    On a side note I have to say I'm fairly unhappy that in the entire 900 page web services tutorial no mention is made of how to utilise inheritance for parameter and return types without running into problems, neither is any mention made of support for / lack of support for polymorphism which also seems to cause problems. Forgive my sarcasm and lack of grace but, "What, is it 1975 already?" In this day and age I DO expect to be able to use these things without having to specify obscure compiler options, or indeed worry about them in any way whatsoever.

  • Error deploying JAX-RPC war in JBoss

    I am using the JBoss 3.0.3 with Tomcat 4.1.12. After creating a JAX-RPC application I have tried deploying the completed war to JBoss, but get an error saying that Jboss cannot find the:
    com.sun.xml.rpc.server.JAXRPCContextListener. java.lang.ClassNotFoundException
    This class lives in the jaxrpc-ri.jar file, from the jwsdp-1_0_01 distribution (Java Web Services Developer Pack). I've tried copying this jar file to the Jboss lib directory, but it still doesn't get past the error.
    How can install this jar (and/or other JAX-RPC jars) for Jboss to use? See server errors below:
    9:56:31,071 INFO [Engine] WebappLoader[VehicleInfoService]: Deploy class files /WEB-INF/classes/space/jboss/jboss-3.0.3_tomcat-4.1.12/tomcat-4.1.x/work/MainEngine/localhost/VehicleInfoService/WEB-INF/classes
    19:56:31,671 INFO [Engine] ContextConfig[VehicleInfoService]: Added certificates -> request attribute Valve
    19:56:31,852 INFO [EmbeddedCatalinaService41] Using Java2 parent classloader delegation: true
    19:56:31,853 INFO [Engine] StandardManager[VehicleInfoService]: Seeding random number generator class java.security.SecureRandom
    19:56:31,856 INFO [Engine] StandardManager[VehicleInfoService]: Seeding of random number generator has been completed
    19:56:32,141 ERROR [Engine] StandardContext[VehicleInfoService]: Error configuring application listener of class com.sun.xml.rpc.server.http.JAXRPCContextListener
    java.lang.ClassNotFoundException:
    com.sun.xml.rpc.server.http.JAXRPCContextListener
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1428)
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1274)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3217)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3524)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:821)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579)
    at org.jboss.web.catalina.EmbeddedCatalinaService41.createWebContext(EmbeddedCatalinaService41.java:427)
    at org.jboss.web.catalina.EmbeddedCatalinaService41.performDeploy(EmbeddedCatalinaService41.java:302)
    at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
    at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
    at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
    at $Proxy4.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:427)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:648)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:499)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
    at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:397)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
    at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)

    Deploy the jax-rpc implementation along with your application.
    The library is found in the Webservices Developers Kit at
    jaxrpc-1.0.3/lib/jaxrpc-ri.jar

  • 503 error code when trying to access a weblogic jax-rpc webservice

    I'm going crazy on a webservice issue with Weblogic server 10.2.
    I have a DocumentRepository webservice deployed and I generated a JAX-RPC library based on its WSDL.
    Now I'm trying to access this webservice from Spring in a desktop application with the following bean declaration:
    <bean id="documentRepository" class="eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl">
         <constructor-arg value="http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL" />
    </bean>
    But when the Spring application context initializes, after a few minutes, I get the following exception:
    javax.xml.rpc.ServiceException: Failed to parse WSDL http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
    +     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)+
    +     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)+
    +     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)+
    +     at eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl.<init>(Unknown Source)+
    +     at eu.europa.ec.rdg.efp.services.document.v1_00.DocumentRepository_Impl.<init>(Unknown Source)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
    +     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
    +     at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)+
    +     ... 35 more+
    Caused by: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
    +     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)+
    +     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)+
    +     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)+
    +     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)+
    +     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)+
    +     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:476)+
    +     ... 43 more+
    Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
    +     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1305)+
    +     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)+
    +     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)+
    +     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)+
    +     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)+
    +     ... 48 more+
    Yet, I can see the WSDL in my browser when I go to http://myserver.mycompany.com:7021/efpServices/DocumentRepository?WSDL
    Now it looks a lot like a proxy issue, which is possible because I'm behind a proxy, and I had to set the following command-line parameters in order to access remote HTTP resources before the spring application context is initialized:
    -DproxySet=true -DproxyHost=<my proxy IP> -DproxyPort=8012
    And I authenticate to my proxy using the following code, once again before the Spring application context is initialized:
    Authenticator.setDefault(new Authenticator() {
                                       protected PasswordAuthentication getPasswordAuthentication() {
                                            return new PasswordAuthentication(<my login>, <my password>);
    Yet, those settings seem to have absolutely no effect on how the webservice client is loading the WSDL.
    So my question is the following: is it possible to specify a proxy to be used by the webservice client class to load the WSDL? If yes, how?
    On the other hand, if it was a proxy issue, then I guess the webservice client couldn't reach the server and I would get a connection timeout or something. But here I get a response, even though it's a 503 error. Any other idea where my exception comes from?
    I'm really desperate here. I've tried to ask our corporate weblogic support but they couldn't reproduce my issue. I've been fighting with this for weeks. Please help!

    Please, take a look at https://blogs.oracle.com/proactivesupportWCC/entry/clustering_and_high_availability_for (and contact the support group as advised)

  • Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
    We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
    However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
    java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
    We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
    What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

    Hi,
    I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
    Regards,
    Sylvain

  • Very basic questions on JAX-RPC and wscompile

    Hello,
    well, I have this tool that generates java packages. The thing is that this tool needs now to generate JAX-RPC compliant java packages. To verify its compilance, I am using wscompile 1.1.3 build R1 and Sun AS Edition 8.2.
    My questions are:
    - In the generated packages, there might some classes with no attributes at all :P(remember that I am handling automatically generated classes). When running wscompile to generate the corresponding WSDL, I am getting "invalid type for JAX-RPC structure", even if it has a default empty constructor. I know it looks stupid, but I could not find anywhere in the JAX-RPC specification saying that for a class to be jaxrpc compliant, it must have at least one attribute. Any idea?
    - It might be the case that I have same class name in different packages:
    mypackage.structures.messages.A
    mypackage.structures.segments.AWhen generating the server stub, I am getting:
    Duplicate type name "{urn:mynamespace}A" for java type "mypackage.structures.segments.A" found.
    Is there a way to tell wscompile to keep the class package name for every class when generating the wsdl? Or is it always building all the classes together in the package specified in the service/packageName within the configuration xml file?
    Thanks a lot in advance for any help.

    1. Does predictive text only work in the SMS app, or does it work in the apps for email, writing notes, etc?
    It works with Safari, the Mail client, the Notes app, and with the SMS app.
    2. Can you turn the predictive text off? (I find it wildly irritating, because I know far better what words I want to write than a pesky phone does!)
    Yes.
    3. Having email sent to a mobile is a whole new world for me! Do I need to subscribe to MobileMe at £££ per month, or is there another way of having email from my three accounts forwarded to my mobile?
    You can access any IMAP or POP account with the iPhone's Mail client, and access multiple email accounts. I currently access to email accounts with the iPhone's mail client - my MobileMe account, and a business POP account. You can access all 3 of your email accounts with the iPhone's Mail client.

Maybe you are looking for