Web service client type

Hi,
I am new to web services. I need to write a web service client that invokes a web service method. The method takes complex types as parameter and returns a complex type.what kind of client(static stub, dynamic proxy or DII) should I use to invoke such kind of method from a standalone java application?
Thanks in advance.

yes, you are right. stubs must be regenerated when the service definition changes. But is it possible to write a standalone client using dynamic proxy to invoke a web service method that uses complex types as parameters?.

Similar Messages

  • How to prevent downloading wsdl in weblogic web service client

    Hi,
    I get a problem regarding weblogic web service client. My working environment:
    weblogic server 8.1
    Windows XP SP2
    JDK 1.4
    I use the weblogic tool to generate the client jar file from the wsdl file.
         <target name="generate-client">
              <clientgen wsdl="ACCESS.wsdl"
                   packageName="xxxxxx.client"
                   clientJar="${client}/${AccessClient_jar_file}"
                   keepGenerated="true"
                   saveWSDL="true"
              />
              <javac srcdir="${source}"
              destdir="${client}"
              includes="**/AccessClient.java">
              <classpath>
              <pathelement path="${client}/${AccessClient_jar_file}"/>
              </classpath>
              </javac>
         </target>
    After that, I create a client java file to invoke the service deploy in the server.
    public static void main(String[] argv)
    throws Exception
         int transactionId = 100;
         int id = 1000;
    // Setup the global JAXM message factory
    System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
    // Setup the global JAX-RPC service factory
    System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    AccessServicePorts ws = new AccessServicePorts_Impl(argv[0]);
    AccessService port = ws.getAccessService();
    // Resource - create
    Resource resource = new Resource();
    resource.setRES_CD("Create ResCo");
    resource.setCODE_CODE("code_cod");
    resource.setRES_TYPE("Resource typ");
    resource.setCOMMON_FIELD(common);
    AccessDefaultResult resultItems = port.createResource(resource);
    System.out.println("createResource : " + resultItems);
    I find that this web service client always issue 2 http requests to invoke an web service method deployed in server.
    1st http reqeust:
    GET /AccessEpol/EpolServiceSoap?WSDL HTTP/1.1
    User-Agent: Java/1.4.2_08
    Host: 127.0.0.1:8001
    Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
    Connection: keep-alive
    the return result is the wsdl downloaded from the server.
    2nd http request is the real web service request.
    The question is how could I eliminate the 1st http request because it's really unnecessary. I use other web service client like Axis 1.x, Axis client never has the http request to download the wsdl from the server.
    I read through weblogic web service document. It do mentions that put saveWSDL="true" in the clientgen ant task. the default value for saveWSDL is true already. I did try saveWSDL="false" also. None of them can eliminate the 1st http request.
    appreciate for any answer my question?

    Hi David,
    thanks for the reply.
    More or less I agree some points you mentioned above.
    I did use Axis 1.x to test the inter-operability. The web service was developed in Weblogic 8.1 and is a part of an existing web application. It will be merged to existing application deployed in weblogic 8.1.
    I also program the web service client to test the web service.
    The implementation of the server and client will be handed over the project team and training for supporting or continuous development have to be conducted by me. So I don't like to use two types of technologies which will make thing complex.
    I found this issue when I tried to protected the web service endpoint, eg http://localhost:7001/epol/service, using the web application Basic mechanism. The wsdl URL http://localhost:7001/epol/service?WSDL is also protected in this case. Unfortunately the username/password pair is not sent to the server when the weblogic client download the WSDL from the server. In this case, the client failed and throw exception.

  • Problems - WLS 10.0 web service client

    I'm having a few issues with WLS 10.0 web service client.
              I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
              1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
              2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
              3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
              Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
              Thanks,
              [email protected]

    Thank you for the reply..
    But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
    ---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
    LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
    return lagerServiceServant;
    Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
    Or could there be some different fundemental thingy I have forgotten ??
    thanks
    Aqoi

  • OC4J web service client and Spring

    Hello!
    I'm trying to use the Web Service client mechanism of Spring 1.2.6 in conjunction with OC4J by subclassing org.springframework.remoting.jaxrpc.JaxRpcPortProxyFactoryBean and using generated classes from soap-ui.
    Problem is that I keep getting errors like this when starting the (embedded) OC4J:
    org.springframework.beans.FatalBeanException: Could not instantiate class [at.sozvers.bva.shared.util.CommaSeparatedClassPathContext]; constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'zpvPartnerAdresseWebService' defined in class path resource [onlineContext.xml]: Initialization of bean failed; nested exception is oracle.j2ee.ws.client.ServiceExceptionImpl: service: {http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/}PartnerAdresse does not contain port: {http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/}PartnerAdresse
    The WSDL:
    <?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://service.zpv.esb.bva.sozvers.at" xmlns:ns2="http://error.shared.bva.sozvers.at" xmlns:ns3="http://dto.zpv.esb.bva.sozvers.at" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://service.zpv.esb.bva.sozvers.at/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://service.zpv.esb.bva.sozvers.at/">
    <wsdl:types>
    <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.zpv.esb.bva.sozvers.at/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="lesen">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="ns1:PartnerAdresseServiceRequest"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="lesenResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="ns3:ZPVPartnerAdresseDTO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="schreiben">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string"/>
    <xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="ns1:PartnerAdresseServiceRequest"/>
    <xsd:element maxOccurs="1" minOccurs="1" name="in2" nillable="true" type="ns3:ArrayOfZPVAdresseDTO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="schreibenResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="ns3:ZPVResponseDTO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://service.zpv.esb.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:complexType name="PartnerAdresseServiceRequest">
    <xsd:sequence>
    <xsd:element minOccurs="0" name="bisDat" type="xsd:dateTime"/>
    <xsd:element minOccurs="0" name="bkFachschluessel" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="bkInput" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="vonDat" type="xsd:dateTime"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://dto.zpv.esb.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:complexType name="ZPVPartnerAdresseDTO">
    <xsd:sequence>
    <xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
    <xsd:element minOccurs="0" name="responseDto" nillable="true" type="ns3:ZPVResponseDTO"/>
    <xsd:element minOccurs="0" name="zpvAdresseDTOs" nillable="true" type="ns3:ArrayOfZPVAdresseDTO"/>
    <xsd:element minOccurs="0" name="zpvPartnerStammdatenDTO" nillable="true" type="ns3:ZPVPartnerStammdatenDTO"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="ZPVResponseDTO">
    <xsd:sequence>
    <xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
    <xsd:element minOccurs="0" name="fehlerJN" nillable="true" type="xsd:boolean"/>
    <xsd:element minOccurs="0" name="zpvFehlerId" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="zpvMeldungstext" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="ArrayOfZPVAdresseDTO">
    <xsd:sequence>
    <xsd:element maxOccurs="unbounded" minOccurs="0" name="ZPVAdresseDTO" nillable="true" type="ns3:ZPVAdresseDTO"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="ZPVAdresseDTO">
    <xsd:sequence>
    <xsd:element minOccurs="0" name="abgabestelle" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="adresstyp" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="anschriftzusatz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="beginn" type="xsd:dateTime"/>
    <xsd:element minOccurs="0" name="beharrungsadresse" nillable="true" type="xsd:boolean"/>
    <xsd:element minOccurs="0" name="bundeslandKennzeichen" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="ende" type="xsd:dateTime"/>
    <xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
    <xsd:element minOccurs="0" name="gebrauchKurz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="hausnummer" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="ort" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="plz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="postfach" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="staatkennzeichen" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="staatname" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="stocktuernummer" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="strasse" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="updatecount" nillable="true" type="xsd:int"/>
    <xsd:element minOccurs="0" name="verwendungsartKurz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="zpvAevnummer" nillable="true" type="xsd:long"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="ZPVPartnerStammdatenDTO">
    <xsd:sequence>
    <xsd:element minOccurs="0" name="angehoeriger" type="xsd:boolean"/>
    <xsd:element minOccurs="0" name="bkFachschluesselAngabe" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="exceptionDTO" nillable="true" type="ns2:ExceptionDTO"/>
    <xsd:element minOccurs="0" name="familienname" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="familiennameDiakritisch" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="geburtsDAT" type="xsd:dateTime"/>
    <xsd:element minOccurs="0" name="geschlechtKZ" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="isoa3Staatsbuergerschaft" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="landesstellenKennzeichen" nillable="true" type="xsd:int"/>
    <xsd:element minOccurs="0" name="namensergaenzung" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="namenskorrektur" type="xsd:boolean"/>
    <xsd:element minOccurs="0" name="staatsbuergerschaftSonderformKZ" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="stornoJN" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="titelHintenKurz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="titelVorneKurz" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="todesDAT" type="xsd:dateTime"/>
    <xsd:element minOccurs="0" name="updatecount" nillable="true" type="xsd:int"/>
    <xsd:element minOccurs="0" name="versicherter" type="xsd:boolean"/>
    <xsd:element minOccurs="0" name="vorname" nillable="true" type="xsd:string"/>
    <xsd:element minOccurs="0" name="vornameDiakritisch" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://error.shared.bva.sozvers.at" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:complexType name="ExceptionDTO"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="schreibenResponse">
    <wsdl:part element="tns:schreibenResponse" name="parameters">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="lesenRequest">
    <wsdl:part element="tns:lesen" name="parameters">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="lesenResponse">
    <wsdl:part element="tns:lesenResponse" name="parameters">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="schreibenRequest">
    <wsdl:part element="tns:schreiben" name="parameters">
    </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="PartnerAdresseServicePortType">
    <wsdl:operation name="lesen">
    <wsdl:input message="tns:lesenRequest" name="lesenRequest">
    </wsdl:input>
    <wsdl:output message="tns:lesenResponse" name="lesenResponse">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="schreiben">
    <wsdl:input message="tns:schreibenRequest" name="schreibenRequest">
    </wsdl:input>
    <wsdl:output message="tns:schreibenResponse" name="schreibenResponse">
    </wsdl:output>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="zpvPartnerAdresseBinding" type="tns:PartnerAdresseServicePortType">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="lesen">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="lesenRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="lesenResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="schreiben">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="schreibenRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="schreibenResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="PartnerAdresse">
    <wsdl:port binding="tns:zpvPartnerAdresseBinding" name="zpvPartnerAdresse">
    <wsdlsoap:address location="http://0.0.0.0:8192/zpvPartnerAdresse/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    The Spring configuration of the WS- bean:
    <bean id="zpvPartnerAdresseWebService" class="at.sozvers.bva.panda.m02.service.PartnerAdresseProxyFactoryBean">
    <property name="serviceInterface">
    <value>at.sozvers.bva.panda.m02.service.RemotePartnerAdresseBean</value>
    </property>
    <property name="wsdlDocumentUrl">
    <value>http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/main.wsdl</value>
    </property>
    <property name="namespaceUri">
    <value>http://oasdev1.bva.sozvers.at:8192/zpvPartnerAdresse/</value>
    </property>
    <property name="serviceName">
    <value>PartnerAdresse</value>
    </property>
    <property name="portName">
    <value>PartnerAdresse</value>
    </property>
    </bean>
    Does anyone have ideas or experience using Spring 1.2.6 for web service clients with oc4j 10.1.3 ?
    Thank you in advance
    Stefan

    I also tried to use "zpvPartnerAdresse" as portName, but this didn't change anything.
    Stefan

  • Web service client in Workshop 10.1

    Anybody have any advice on the best way to create a Web service CLIENT in Workshop 10.1 ?
    I've been looking around for a couple of days. I understand how to run clientgen from the command line. That works fine.
    I have looked at the tutorial for using 'Web service controls' also. As far as I can tell, though, in Workshop 10.1 I can only generate such a control nside another Web service, as in the tutorial. In other types of classes, the Insert option is not available on the menu I pull up by right-clicking in the source. I hope I am missing something obvious.
    My goal is to call Web services from other applications inside Workshop. The other applications may be Web applications or they may not. Most of the time they will not be other Web services.
    Thanks in advance for any help !!

    Thanks Vimala.
    I am able to create the JAR using clientgen, and I can call the Web service after that from the command line. All of that depends upon various environment variables being set with setDomainEnv.cmd and it works fine.
    I would like to create a Java project in Workshop 10.1 and use that JAR created with clientgen, but that does not work - I get an Exception wqhen I try to run, although it all compiles :
    Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/descriptor/BasicDescriptorManager
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClass(Unknown Source)
         at java.security.SecureClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.access$100(Unknown Source)
         at java.net.URLClassLoader$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
         at com.kohls.example.client.SimpleClient.main(SimpleClient.java:29)
    The classes are al lthere, or it would not compile, so I assume I am missing some of the scaffolding around calling the Web service. I just created a normal Java project - maybe that's wrong ?
    Edited by ethan_kohls at 01/18/2008 12:44 PM
    Edited by ethan_kohls at 01/18/2008 12:44 PM

  • Standalone Web Service clients in NetBeans with WSIT security

    I'm having a problem create a secure app with NetBeans, any help would be appreciated, here's what I did:
    Following the WSIT tutorial (http://java.sun.com/webservices/reference/tutorials/wsit/doc/index.html) I was able to create a Web Service with (for example) Username Authentication with Symmetric Key. I select the keystore as being the either the default development settings (I installed V3 certificates previously) or what I imagine are the same as them: keystore from domain1, alias xws-server and a username and password that I've created in the glassfish admin console. All good so far.
    I then create a new web app servlet client, configuring the Web Service client with the corresponding cacerts keystore, alias xws-security-server from domain1 and the correct username and password. Deploy that and bingo, it works.
    Try that again with a standalone Java client configuring the client reference in exactly the same way and using:
            try { // Call Web Service Operation
                uk.ac.ox.sddag.glassfish.server.SecureWSService service = new uk.ac.ox.sddag.glassfish.server.SecureWSService();
                uk.ac.ox.sddag.glassfish.server.SecureWS port = service.getSecureWSPort();
                int x = 1200;
                int y = 36;
                int result = port.add(x, y);
                System.out.println("Result = "+result);
            } catch (Exception ex) {
                System.out.println("Exception:");
                ex.printStackTrace();
            }but this time, it doesn't work:
    Exception:
    javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
            at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
            at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
            at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
            at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
            at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
            at $Proxy29.add(Unknown Source)
            at securestandaloneclient.Main.main(Main.java:26)
    Caused by: javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
            at com.sun.xml.ws.security.opt.impl.util.SOAPUtil.getSOAPFaultException(SOAPUtil.java:171)
            at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:277)
            at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:179)
            at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:168)
            at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
            at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
            at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
            at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
            at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
            at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
            at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
            at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
            at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
            at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
            at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:176)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
            at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
            at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
            at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
            at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
            at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
            at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
            at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
            at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
            at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
            at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
            at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
            at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
            at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
            at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
            at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)I'm assuming that it's something to do with the WSDL being used to create the request, here's what the source view for the web service reference says:
    <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService">
    <ns1:Policy xmlns:ns1="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBindingPolicy">
    <ns1:ExactlyOne>
    <ns1:All>
    <ns4:SignedSupportingTokens xmlns:ns4="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns4:UsernameToken ns4:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns4:WssUsernameToken10></ns4:WssUsernameToken10>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns4:UsernameToken>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns4:SignedSupportingTokens>
    <ns5:SymmetricBinding xmlns:ns5="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns5:AlgorithmSuite>
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns5:Basic128></ns5:Basic128>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns5:AlgorithmSuite>
    <ns5:IncludeTimestamp></ns5:IncludeTimestamp>
    <ns5:Layout>
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns5:Strict></ns5:Strict>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns5:Layout>
    <ns5:OnlySignEntireHeadersAndBody></ns5:OnlySignEntireHeadersAndBody>
    <ns5:ProtectionToken>
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns5:X509Token ns5:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns5:RequireIssuerSerialReference></ns5:RequireIssuerSerialReference>
    <ns5:WssX509V3Token10></ns5:WssX509V3Token10>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns5:X509Token>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns5:ProtectionToken>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns5:SymmetricBinding>
    <ns6:Wss11 xmlns:ns6="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns1:Policy>
    <ns1:ExactlyOne>
    <ns1:All>
    <ns6:MustSupportRefEncryptedKey></ns6:MustSupportRefEncryptedKey>
    <ns6:MustSupportRefIssuerSerial></ns6:MustSupportRefIssuerSerial>
    <ns6:MustSupportRefThumbprint></ns6:MustSupportRefThumbprint>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    </ns6:Wss11>
    <ns7:UsingAddressing xmlns:ns7="http://www.w3.org/2006/05/addressing/wsdl" ns1:Optional="true"></ns7:UsingAddressing>
    </ns1:All>
    </ns1:ExactlyOne>
    </ns1:Policy>
    <ns8:Policy xmlns:ns8="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Input_Policy">
    <ns8:ExactlyOne>
    <ns8:All>
    <ns9:EncryptedParts xmlns:ns9="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns9:Body></ns9:Body>
    </ns9:EncryptedParts>
    <ns10:SignedParts xmlns:ns10="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns10:Body></ns10:Body>
    <ns10:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns10:Header>
    <ns10:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
    <ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns10:Header>
    <ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns10:Header>
    <ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns10:Header>
    <ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns10:Header>
    </ns10:SignedParts>
    </ns8:All>
    </ns8:ExactlyOne>
    </ns8:Policy>
    <ns11:Policy xmlns:ns11="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Output_Policy">
    <ns11:ExactlyOne>
    <ns11:All>
    <ns12:EncryptedParts xmlns:ns12="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns12:Body></ns12:Body>
    </ns12:EncryptedParts>
    <ns13:SignedParts xmlns:ns13="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
    <ns13:Body></ns13:Body>
    <ns13:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns13:Header>
    <ns13:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
    <ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns13:Header>
    <ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns13:Header>
    <ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns13:Header>
    <ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns13:Header>
    </ns13:SignedParts>
    </ns11:All>
    </ns11:ExactlyOne>
    </ns11:Policy>
    <types>
    <xsd:schema>
    <xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
    </xsd:schema>
    </types>
    <message name="add">
    <part name="parameters" element="tns:add"></part>
    </message>
    <message name="addResponse">
    <part name="parameters" element="tns:addResponse"></part>
    </message>
    <portType name="SecureWS">
    <operation name="add">
    <input message="tns:add"></input>
    <output message="tns:addResponse"></output>
    </operation>
    </portType>
    <binding name="SecureWSPortBinding" type="tns:SecureWS">
    <ns14:PolicyReference xmlns:ns14="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBindingPolicy"></ns14:PolicyReference>
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
    <operation name="add">
    <soap:operation soapAction="add"></soap:operation>
    <input>
    <ns15:PolicyReference xmlns:ns15="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Input_Policy"></ns15:PolicyReference>
    <soap:body use="literal"></soap:body>
    </input>
    <output>
    <ns16:PolicyReference xmlns:ns16="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Output_Policy"></ns16:PolicyReference>
    <soap:body use="literal"></soap:body>
    </output>
    </operation>
    </binding>
    <service name="SecureWSService">
    <port name="SecureWSPort" binding="tns:SecureWSPortBinding">
    <soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
    </port>
    </service>
    </definitions>The contents of META-INF (The WSDL):
    <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:sc="http://schemas.sun.com/2006/03/wss/client" xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy">
    <types>
    <xsd:schema>
    <xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
    </xsd:schema>
    </types>
    <message name="add">
    <part name="parameters" element="tns:add"></part>
    </message>
    <message name="addResponse">
    <part name="parameters" element="tns:addResponse"></part>
    </message>
    <portType name="SecureWS">
    <operation name="add">
    <input message="tns:add"></input>
    <output message="tns:addResponse"></output>
    </operation>
    </portType>
    <binding name="SecureWSPortBinding" type="tns:SecureWS">
        <wsp:PolicyReference URI="#SecureWSPortBindingPolicy"/>
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
    <operation name="add">
    <soap:operation soapAction="add"></soap:operation>
    <input>
    <soap:body use="literal"></soap:body>
    </input>
    <output>
    <soap:body use="literal"></soap:body>
    </output>
    </operation>
    </binding>
    <service name="SecureWSService">
    <port name="SecureWSPort" binding="tns:SecureWSPortBinding">
    <soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
    </port>
    </service>
        <wsp:Policy wsu:Id="SecureWSPortBindingPolicy">
            <wsp:ExactlyOne>
                <wsp:All>
                    <sc:CallbackHandlerConfiguration wspp:visibility="private">
                        <sc:CallbackHandler default="example1" name="usernameHandler"/>
                        <sc:CallbackHandler default="password1" name="passwordHandler"/>
                    </sc:CallbackHandlerConfiguration>
                    <sc:TrustStore wspp:visibility="private" type="JKS" storepass="changeit" location="/Applications/NetBeans/glassfish-v2ur2/domains/domain1/config/cacerts.jks" peeralias="xws-security-server"/>
                </wsp:All>
            </wsp:ExactlyOne>
        </wsp:Policy>
    </definitions>The wsit-client:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="mainclientconfig"
    >
        <import location="SecureWSService.xml" namespace="http://server.glassfish.sddag.ox.ac.uk/"/>
    </definitions>

    This bug still isn't fixed.
    Thank you, adding Glassfish's webservices-rt.jar does fix it.

  • Web service client compilation error

    With the help of wscompile on JWSDP 1.6 I created all the files required for a web service client in SabreServerBridge.client.stub package. Now when I am trying to compile these files, I am getting the following stack trace. The stacktrace also includes the compile command:
    C:\JWSE\Pool\SabreServerClient>compile *.java
    C:\JWSE\Pool\SabreServerClient>javac -cp .;C:\Tomcat5\common\lib\servlet-api.jar
    ;C:\Tomcat5\common\lib\mssqlserver.jar;C:\Tomcat5\common\lib\msbase.jar;C:\Tomca
    t5\common\lib\msutil.jar;C:\Tomcat5\common\lib\xercesImpl.jar;C:\Tomcat5\common\
    lib\jaxp-api.jar;C:\Tomcat5\common\lib\sax.jar;C:\Tomcat5\common\lib\poolit.jar;
    C:\Tomcat5\common\lib\databahn.jar;C:\Tomcat5\webapps\Book\WEB-INF\classes\DBSer
    ver;C:\Tomcat5\webapps\Book\WEB-INF\classes\SabreServer\;C:\Tomcat5\commaon\lib\
    jb2refscan-2.62.jar;C:\sun\jwsdp-1.6\jaxws\lib\jsr181-api.jar;C:\sun\jwsdp-1.6\j
    axws\lib\jsr250-api.jar;C:\sun\jwsdp-1.6\jaxws\lib\jaxws-tools.jar;C:\sun\jwsdp-
    1.6\jaxws\lib\jaxws-rt.jar;C:\sun\jwsdp-1.6\jaxws\lib\jaxws-api.jar;C:\sun\jwsdp
    -1.6\jaxrpc\lib\jaxrpc-impl.jar;;;C:\sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-api.jar;C:\
    sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-spi.jar;C:\sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-impl.
    jar;C:\sun\jwsdp-1.6\jwsdp-shared\lib\jax-qname.jar;C:\sun\jwsdp-1.6\jwsdp-share
    d\lib\activation.jar;C:\sun\jwsdp-1.6\jwsdp-shared\lib\mail.jar;C:\sun\jwsdp-1.6
    \saaj\lib\saaj-impl.jar;C:\sun\jwsdp-1.6\saaj\lib\saaj-api.jar;C:\sun\jwsdp-1.6\
    jaxp\lib\endorsed\xercesImpl.jar;C:\sun\jwsdp-1.6\jaxp\lib\endorsed\dom.jar;C:\J
    WSE\Pool\SabreServerClient\gen; -d gen src\SabreServerBridge\client\stub\*.java
    src\SabreServerBridge\client\stub\SabreServerBridge.java:11: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    public SabreServerBridge.client.stub.SSBridge getSSBridgePort() throws Servi
    ceException;
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:55: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    public SabreServerBridge.client.stub.SSBridge getSSBridgePort() {
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPBuilder.java:12
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_get_RequestStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPBuilder.java:1
    2: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_get_ResponseStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPBuilder
    .java:12: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct _in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPBuilder.java:12
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_put_RequestStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    implements SabreServerBridge.client.stub.SSBridge {
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:33: interface expected here
    implements SabreServerBridge.client.stub.SSBridge {
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:22: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private static final Class SSBridge_PortClass = SabreServerBridge.client.stu
    b.SSBridge.class;
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:28: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SabreServerBridge_SerializerRegist
    ry().getRegistry());
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:59: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_Stub stub = new SabreServerBridge
    .client.stub.SSBridge_Stub(handlerChain);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:59: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_Stub stub = new SabreServerBridge
    .client.stub.SSBridge_Stub(handlerChain);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:31:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_getVersion_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:34:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    tVersion_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:38:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_getVersion_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:41:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    tVersion_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:45:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_get_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:48:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    t_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:52:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_put_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:55:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_pu
    t_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:59:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_put_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:62:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_pu
    t_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:66:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_get_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:69:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    t_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPBuilder.java:57
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeget_RequestStruct)in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct_SOAPBuilder bui
    lder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPBuilder.java:5
    7: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeget_ResponseStruct)i
    nstance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct_SOAPBuilder bu
    ilder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    ResponseStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPBuilder
    .java:57: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgegetVersion_ResponseS
    truct)instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = new SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = new SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct_SOAPBui
    lder builder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    Version_ResponseStruct_SOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPBuilder.java:68
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeput_RequestStruct)in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :38: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :38: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct_SOAPBuilder bui
    lder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :54: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_put
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :68: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_put
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :87: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :87: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :92: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :92: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:58: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct _mySSBridge
    getRequestStruct =
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:59: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:72: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct _mySSBridg
    e_get_ResponseStruct = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:76: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    (SabreServerBridge.client.stub.SSBridge_get_ResponseStruct)(
    (SOAPDeserializationState)_responseObj).getInstance();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:79: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    (SabreServerBridge.client.stub.SSBridge_get_ResponseStruct)_
    responseObj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:109: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct _myS
    SBridge_getVersion_RequestStruct =
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:110: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStr
    uct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:122: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct _my
    SSBridge_getVersion_ResponseStruct = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:126: cannot find symbol
    symbol : class client
    locat

    With the help of wscompile on JWSDP 1.6 I created all the files required for a web service client in SabreServerBridge.client.stub package. Now when I am trying to compile these files, I am getting the following stack trace. The stacktrace also includes the compile command:
    C:\JWSE\Pool\SabreServerClient>compile *.java
    C:\JWSE\Pool\SabreServerClient>javac -cp .;C:\Tomcat5\common\lib\servlet-api.jar
    ;C:\Tomcat5\common\lib\mssqlserver.jar;C:\Tomcat5\common\lib\msbase.jar;C:\Tomca
    t5\common\lib\msutil.jar;C:\Tomcat5\common\lib\xercesImpl.jar;C:\Tomcat5\common\
    lib\jaxp-api.jar;C:\Tomcat5\common\lib\sax.jar;C:\Tomcat5\common\lib\poolit.jar;
    C:\Tomcat5\common\lib\databahn.jar;C:\Tomcat5\webapps\Book\WEB-INF\classes\DBSer
    ver;C:\Tomcat5\webapps\Book\WEB-INF\classes\SabreServer\;C:\Tomcat5\commaon\lib\
    jb2refscan-2.62.jar;C:\sun\jwsdp-1.6\jaxws\lib\jsr181-api.jar;C:\sun\jwsdp-1.6\j
    axws\lib\jsr250-api.jar;C:\sun\jwsdp-1.6\jaxws\lib\jaxws-tools.jar;C:\sun\jwsdp-
    1.6\jaxws\lib\jaxws-rt.jar;C:\sun\jwsdp-1.6\jaxws\lib\jaxws-api.jar;C:\sun\jwsdp
    -1.6\jaxrpc\lib\jaxrpc-impl.jar;;;C:\sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-api.jar;C:\
    sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-spi.jar;C:\sun\jwsdp-1.6\jaxrpc\lib\jaxrpc-impl.
    jar;C:\sun\jwsdp-1.6\jwsdp-shared\lib\jax-qname.jar;C:\sun\jwsdp-1.6\jwsdp-share
    d\lib\activation.jar;C:\sun\jwsdp-1.6\jwsdp-shared\lib\mail.jar;C:\sun\jwsdp-1.6
    \saaj\lib\saaj-impl.jar;C:\sun\jwsdp-1.6\saaj\lib\saaj-api.jar;C:\sun\jwsdp-1.6\
    jaxp\lib\endorsed\xercesImpl.jar;C:\sun\jwsdp-1.6\jaxp\lib\endorsed\dom.jar;C:\J
    WSE\Pool\SabreServerClient\gen; -d gen src\SabreServerBridge\client\stub\*.java
    src\SabreServerBridge\client\stub\SabreServerBridge.java:11: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    public SabreServerBridge.client.stub.SSBridge getSSBridgePort() throws Servi
    ceException;
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:55: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    public SabreServerBridge.client.stub.SSBridge getSSBridgePort() {
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPBuilder.java:12
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_get_RequestStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPBuilder.java:1
    2: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_get_ResponseStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPBuilder
    .java:12: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct _in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPBuilder.java:12
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private SabreServerBridge.client.stub.SSBridge_put_RequestStruct _instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    implements SabreServerBridge.client.stub.SSBridge {
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:33: interface expected here
    implements SabreServerBridge.client.stub.SSBridge {
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:22: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    private static final Class SSBridge_PortClass = SabreServerBridge.client.stu
    b.SSBridge.class;
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:28: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SabreServerBridge_SerializerRegist
    ry().getRegistry());
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:59: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_Stub stub = new SabreServerBridge
    .client.stub.SSBridge_Stub(handlerChain);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_Impl.java:59: cannot find sy
    mbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_Stub stub = new SabreServerBridge
    .client.stub.SSBridge_Stub(handlerChain);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:31:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_getVersion_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:34:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    tVersion_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:38:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_getVersion_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:41:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    tVersion_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:45:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_get_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:48:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    t_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:52:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_put_RequestStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:55:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_pu
    t_RequestStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:59:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_put_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:62:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_pu
    t_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:66:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    CombinedSerializer serializer = new SabreServerBridge.client.stub.SS
    Bridge_get_ResponseStruct_SOAPSerializer(type,
    ^
    src\SabreServerBridge\client\stub\SabreServerBridge_SerializerRegistry.java:69:
    cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    registerSerializer(mapping,SabreServerBridge.client.stub.SSBridge_ge
    t_ResponseStruct.class, type, serializer);
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPBuilder.java:57
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeget_RequestStruct)in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct_SOAPBuilder bui
    lder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_RequestStruct_SOAPSerializer.java
    :69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_get_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPBuilder.java:5
    7: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeget_ResponseStruct)i
    nstance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct_SOAPBuilder bu
    ilder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    ResponseStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_get_ResponseStruct_SOAPSerializer.jav
    a:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_get_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_RequestStruct_SOAPSerializ
    er.java:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct instance
    = (SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPBuilder
    .java:57: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgegetVersion_ResponseS
    truct)instance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = new SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:33: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = new SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:34: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct_SOAPBui
    lder builder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:46: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_get
    Version_ResponseStruct_SOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:64: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_getVersion_ResponseStruct_SOAPSeriali
    zer.java:69: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct instanc
    e = (SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPBuilder.java:68
    : cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    instance = (SabreServerBridge.client.stub.SSBridgeput_RequestStruct)in
    stance;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :38: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :38: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct_SOAPBuilder bui
    lder = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :54: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_put
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :68: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    builder = new SabreServerBridge.client.stub.SSBridge_put
    RequestStructSOAPBuilder();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :87: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :87: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :92: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_RequestStruct_SOAPSerializer.java
    :92: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_RequestStruct instance = (Sab
    reServerBridge.client.stub.SSBridge_put_RequestStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:28: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = new
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:39: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_put_ResponseStruct_SOAPSerializer.jav
    a:44: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_put_ResponseStruct instance = (Sa
    breServerBridge.client.stub.SSBridge_put_ResponseStruct)obj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:58: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_RequestStruct _mySSBridge
    getRequestStruct =
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:59: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SSBridge_get_RequestStruct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:72: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_get_ResponseStruct _mySSBridg
    e_get_ResponseStruct = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:76: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    (SabreServerBridge.client.stub.SSBridge_get_ResponseStruct)(
    (SOAPDeserializationState)_responseObj).getInstance();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:79: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    (SabreServerBridge.client.stub.SSBridge_get_ResponseStruct)_
    responseObj;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:109: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_RequestStruct _myS
    SBridge_getVersion_RequestStruct =
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:110: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    new SabreServerBridge.client.stub.SSBridge_getVersion_RequestStr
    uct();
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:122: cannot find symbol
    symbol : class client
    location: interface SabreServerBridge.client.stub.SabreServerBridge
    SabreServerBridge.client.stub.SSBridge_getVersion_ResponseStruct _my
    SSBridge_getVersion_ResponseStruct = null;
    ^
    src\SabreServerBridge\client\stub\SSBridge_Stub.java:126: cannot find symbol
    symbol : class client
    locat

  • Web service client invoke problem

    Hi all,I want to in sap studio to develop web service client to invoke a .net webservice,this webservice  need authen ,so I develop a standandalone proxy to write a consle to invoke my code.
    The follwoing is my invoke  code
    public class WebServiceTest {
         public static void main(String[] args) throws Exception {
              GetScaVersion parameter = new GetScaVersion();
              ManagementSoap port = new ManagementImpl().getLogicalPort(); 
                        port._setProperty(port.USERNAME_PROPERTY,"administrator");
                        port._setProperty(port.PASSWORD_PROPERTY,"administrator");
              GetUserList list=new GetUserList();
              GetScaVersionResponse response= port.getScaVersion(parameter);
              System.out.println(response.getGetScaVersionResult());
              System.out.println(response.getAErrorMsg());          
    But final I got the following errors,
    Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
    Error Message is :com/sap/guid/GUIDGeneratorFactory
    null
    Invalid UserName and Password
    so I just want to ask ,if the webservice is need to authen,does the following tow senteces works for authenciation ?
      port._setProperty(port.USERNAME_PROPERTY,"administrator");
      port._setProperty(port.PASSWORD_PROPERTY,"administrator");

    Hi,
    You need to set the credentials of the .net user.
    Also, which type of proxy have you created? Are you able to open the wsdl in the browser?.
    Thanks,
    Vasu

  • Processing ABAP Idocs in SAP Java AS CE 7.1 web service client applicatin

    I am trying to build a Java web service client which would call a web service in a non-SAP system.  I am trying to send  Idocs from the back-end CRM system to my Java web service client using a Jco RFC Provider.  I have already created the RFC Destination on the ABAP side to send my Idocs to my Jco RFC Provider program on the Java side.  The connections between the ABAP and Java are working fine.  My question is how in my Java web service client do I pick up the IDoc sent from ABAP to the Jco RFC Provider? 
    Please let me know if more clearification is needed

    I do receive the IDoc with the SAP Java AS "RFC Jco Provider" component I created, and in my Java application I created a class for "IDOC_INBOUND_ASYNCHRONOUSBean" which has a method "processFunction(Function function)" and in that method I can do function.write("filename.xml") and it writes out an xml document of the Idoc sent from the ABAP server.  I can further process the Idoc by pulling field values from the xml structure.  However, my problem is I am now trying to write a second Java application to do the same thing but with a different Idoc type.  I created a a second RFC Jco provider(listener) on the server but the Idocs still flow through the first Java application, which is an undesirable affect.  I got this idea from this document originally "http://nwadave.com/NwadExplorer/data/SAPDoc/ProcessingIDocsWithTheSAPJavaConnector.doc", and it works fine until now when I'm trying to add a second application to do similar work.  This is makeing me wonder if I should have even done the first one this way?  Bottomline is what tell the RFC Jco provider(listener) on the Java server which application to send the Idocs too?

  • Problem using WSDL from SAP in IBM's RAD for generating web service client

    When importing a WSDL from the ABAP stack on a SAP 6.40 system into IBM's RAD tool for generating a web service client there are errors with the soap fault classes that get generated.  The WSDL declares the types for the faults with WebServiceName.RfcException and these have elements of name, text, and message.  When the tools see this in the WSDL they generate classes that extend the Java exeception class and this causes an error because the "message" name conflicts with the standard java exception message.  Has anyone else ran into this problem?  It seems like a basic problem many java tools for generating web service client proxies would have because the soap faults get turned into java exceptions.  This name conflict of the java exception with the WSDL fault definition means that code always needs to be adjusted and cannot simply use the classes that are generated from the WSDL.  Anyone run across this or a similar problem in the java environment using the SAP WSDL?
    Aaron

    Hi,
    Hello again .
    Have you tried your service using soapui ?
    You can use your WSDL as input .
    In order to eliminate eclipse problem try this service:(I just did)
    http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
    Regards.
    package main;
    import java.io.FileInputStream;
    import java.rmi.RemoteException;
    import java.util.Properties;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
    import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
    import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
    public class Main {
    public static void main(String[] args) {
      try {
       final Properties properties = new Properties();
       properties.load(new FileInputStream("properties.ini"));
       System.getProperties().putAll(properties);
      } catch (final Exception exception) {
       exception.printStackTrace();
      new Main();
    public Main() {
      try {
       final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
       final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
       for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
        System.out.println(tCountryCodeAndName.getSName());
      } catch (final RemoteException exception) {
       exception.printStackTrace();

  • Creating web service client with WSDL in NetBeans

    NetBeans: 5.5
    Java: 1.6
    WSDL: http://jira.atlassian.com/rpc/soap/jirasoapservice-v2?wsdl
    Using netbeans, I can't seem to successfully generate the stubs for a client based on the WSDL file above.
    SoapUI ( www.soapui.org ) has no problems receiving and creating the client stubs using the same WSDL file.
    The error I'm getting in the dialog is "Illegal attempt to exit early".
    Further details from the output window reads as follows:
    -=-
    warning: src-resolve: Cannot resolve the name 'impl:ArrayOf_tns2_RemoteEntity' to a(n) 'type definition' component.
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema2
    warning: src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type definition' component.
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
    error: undefined simple or complex type 'soapenc:Array'
    line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
    -=-
    And on and on...
    What is going on? Why can't I generate my web service client? Any help is greatly appreciated!

    There is a bug in the processLauncher for deploytool. The workaround is to edit the processLauncher.xml located under <AS_INSTALL>/lib/processLauncher.xml and add
    add xalan.jar and mail.jar to the classpath includes of the s1as-deploytool process:
    includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar, mail.jar"
    The web service wizard should now work.

  • Web Service Client Generation.

    <b>Hi
    I have deployed an EJB as a web service, now am trying to create a client using the web service client wizard in NWDS to test the web service. I pass the wsdl url to the wizard for the service definition, move the slider for Test client and change the web service runtime to SAP Netweaver and say Next. Then the wizard asks for the Output Folder and i use the default folder and say Next. Now at this point an error comes which says,</b>
    Publishing failed
      Error during deployment:
          com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
    Nested exception -
          com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
          at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
          Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_SummitOrder_140207ClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
          at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
          at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
          at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
          at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
          at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
          at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
          at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_SummitOrder_140207ClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          . Cannot deploy it.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
          at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
          ... 16 more
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\DevStudio\eclipse\workspace\SummitOrder_140207ClientEAR\SummitOrder_140207ClientEAR.ear.
          Reason: Exception while validating application sap.com/SummitOrder_140207ClientEAR.
          No one of the [app_libraries_container, connector] containers, which processed it, returned deployed component names.
          The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
          Possible reasons :
          1.An AS Java service, which is providing a container, is stopped or not deployed.
          2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:302)
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
          ... 18 more
    <b>Now what can be the reason for this failure, is there any configuration issues with the server which i have to take care of.
    Also is there any other way of testing a web service in NWDS. I tried using soap sonar as was specified in one article on SDN, but either you have to but that product or use a trial version, which expires after some days.
    Please help me on this.
    Thanks & Regards
    Bhupesh...</b>

    I tried with the project <i>type</i> as 'SAP Application Client Project', then this error comes,
    Publishing failed
      Error during deployment:
          com.sap.ide.eclipse.sdm.deploy.DeploymentException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:145)
    Nested exception -
          com.sap.engine.services.dc.api.deploy.DeployException: DeploymentException.
          Reason: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:734)
          at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:220)
          at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:111)
          at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:119)
          Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while deploying the deployment item 'sap.com_DummyClientEAR'.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:186)
          at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:47)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:177)
          at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
          at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:76)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:624)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:483)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:206)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:153)
          at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:807)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:253)
          at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
          at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
          at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
          at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
          at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
          at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:168)
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: sap.com_DummyClientEAR
          sdu file path: C:\SAP\DevStudio\eclipse\workspace\DummyClientEAR\DummyClientEAR.ear
          version status: NEW
          deployment status: Admitted
          description:
          1. Error:
          Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:162)
          at com.sap.engine.services.dc.gd.impl.GenericDeliveryImpl.deploy(GenericDeliveryImpl.java:54)
          at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:157)
          ... 16 more
          Caused by: java.rmi.RemoteException:  class com.sap.engine.services.deploy.server.utils.DSRemoteException: Cannot deploy application sap.com/DummyClientEAR. Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved...
          Reason: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.; nested exception is:
          java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:299)
          at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.performDeployment(ApplicationDeployer.java:150)
          ... 18 more
          Caused by: java.rmi.RemoteException:  com.sap.engine.services.library_container.deploy.LCDeploymentException: Class-path entry jaxb-impl.jar specified in C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\deploy\work\deploying\DummyClientEAR.ear1171514810109\jaxb-xjc.jar/META-INF/MANIFEST.MF file cannot be resolved.
          at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElement(LibraryContainer.java:328)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.addLibsFromClassPathElements(LibraryContainer.java:290)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.getDeployableFiles(LibraryContainer.java:220)
          at com.sap.engine.services.library_container.deploy.LibraryContainer.deploy(LibraryContainer.java:148)
          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:506)
          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:248)
          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:215)
          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:371)
          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2298)
          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:286)
          ... 19 more
    <b>What can be the reason for this?</b>

  • Creating web service client/server

    Try to ask a question in regarding to creating web service client/server:
    First, please see the attachment for a simplized WSDL file:
    Based on which, I can create a web service client. Now, can I create a web service provider (server) by using the same wsdl file? If not, what change do I need to make?
    Thanks
    Scott
    ----WSDL-------
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://www.example3.org/testWSDL2/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    name="testWSDL2"
    targetNamespace="http://www.example3.org/testWSDL2/">
    <wsdl:types>
    <xsd:schema targetNamespace="http://www.example3.org/testWSDL2/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="NewOperation">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="in" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="NewOperationResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="out" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="NewOperationRequest">
    <wsdl:part element="tns:NewOperation" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="NewOperationResponse">
    <wsdl:part element="tns:NewOperationResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="testWSDL2">
    <wsdl:operation name="NewOperation">
    <wsdl:input message="tns:NewOperationRequest"/>
    <wsdl:output message="tns:NewOperationResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="testWSDL2SOAP" type="tns:testWSDL2">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="NewOperation">
    <soap:operation soapAction="http://www.example3.org/testWSDL2/NewOperation"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="testWSDL2">
    <wsdl:port binding="tns:testWSDL2SOAP" name="testWSDL2SOAP">
    <soap:address location="http://abc.example.net/test"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

    the web service is the specification for whatever functionality you wish to provide
    there are a few artifacts you can auto-generate using the WSDL, but you still need to create a client and server application
    the web service is simply exposing the application remotely and the WSDL is the contract
    http://java.sun.com/webservices/docs/1.6/tutorial/doc/index.html

  • What is the steps to create the web service client

    I'm quite new to web service and currently need to work on a web application that will call web service by passing the request data. Then will handle the response data. Following are questions that I would like to get your advice.
    First, should I manually develop a schema? The request data will be passed as some element type (I thought a class should be generated and put in the class path), which will be some class with set/get(). Then I will use the schema to get a jar that contains the class file by using the xmlbean? Any example or suggestion on this?
    Secondly, how does the java code in web application send/get the request/response data to/from the web service. Your example will greatly help.
    I read article about WSDL and Schema and Soap. Get very confused on what really should be to follow step by step. Thanks in advance for your help!

    I propose that you start with some introductory tutorials. At seekda you will find two tutorials for newbies:
    1) [Finding and Testing Web Services|http://seekda.com/blog/write-your-first-web-services-client-%e2%80%93-part-1-finding-and-testing-services/]
    2) [Using Web Services|http://seekda.com/blog/write-your-first-web-services-client-part-2-using-services/]
    The second tutorial actually addresses most of your questions.
    Greetings,
    Michal

  • Unable to create web service client

    I am using NetBeans to build the the first-cup example but I have failed in all my attempts to create the web service client for first-cup web module.
    The reported error is: "
    init:
    wsimport-init:
    wsimport-client-check-DukesAgeService:
    wsimport-client-DukesAgeService:
    error: Connection timed out: connect
    unknown location
    error: java.net.ConnectException: Connection timed out: connect
    I have tried to start the sun server application but that doesn't solve the problem.
    I have strictly followed the following instructions taken from the first-cup tutorial, found at http://java.sun.com/javaee/5/docs/firstcup/doc/p8.html.
    Creating a Web Service Client for the firstcup-war Web Module
    The firstcup-war web module must consume the firstcup-dukes-age web service in order to get Duke's current age. For this to happen, you need to create a web service client for the firstcup-war web module.
    Creating a Web Service Client for the firstcup-war Web Module
    Select firstcup-war from the Project pane.
    Select File -> New File.
    Select Web Services from the Categories pane.
    Select Web Service client from the File Types pane.
    Click Next.
    Select WSDL URL.
    Into the WSDL URL field, enter the following location of the WSDL file of the web service that the web service client will consume.
    http://localhost:8080/DukesAgeService/DukesAgeService?WSDL
    Into the Package field, enter the following package where the client files will be generated.
    com.sun.firstcup.webservice
    Click Finish.
    Thank you and look forward to hearing from you all.

    Hi there.
    I don't know what the problem is with NetBeans, but if you see the local copy of the WSDL in the firstcup-war project, you will find that the name of your computer should be there as part of the URL. Change it to 'localhost' or to '127.0.0.1' and it should work.
    Example:
    <xsd:schema>
          <xsd:import namespace="http://webservice.firstcup.sun.com/" schemaLocation="http://localhost:8080/DukesAgeService/DukesAgeService/__container$publishing$subctx/WEB-INF/wsdl/DukesAgeService_schema1.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </xsd:schema>And...
    <port name="DukesAgePort" binding="tns:DukesAgePortBinding">
          <soap:address location="http://localhost:8080/DukesAgeService/DukesAgeService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </port>

Maybe you are looking for

  • RAM doesn't fit in the Memmory Slot on PowerBook G4 17"

    I recently purchased a 512 MB RAM from apple.com for my powerbook G4 17" 1.67 that I bought a year ago. I currently have a 512 MB RAM on my powerbook, trying to upgrade it to 1 G by adding one more RAM to it. The problem is the new RAM can't fit in o

  • Clob vs. Blob XML Storage

    Hi, we're currently using Oracle 8i to store XMl and are wondering which to use for large XML pieces CLOB or BLOB. Although I saw an earlier post differentiating CLOBS from BLOBS. Which is better for XML storage. I noted that Oracle always seems to f

  • DB02:Space management/Segments/Most allocated extents in any segment

    Hi , in My SAP server: DB02 > Oracle Database Administration > Alerts > Alert monitor, there are few red alerts. 1. Space management > Segments >Most allocated extents in any segment  263  > 200   - 263 > 200: number of extents > threshold 03.03.2009

  • Exporting FLA/SWF to FLV

    How can I turn my Flash 8 animation into an FLV file? The only solution I've found is exporting it as a .MOV file. But to do this I have to use Flash 5, which destroys my animation since there's no movieclip filters. There has to be a way to do this,

  • Error conecting oracle

    Enviroment: client Windows nt 4.0 Oracle EE 8.0.6 in hp-ux Oracle odbc driver 8.0.6.3 ASP we want to display a list of names...but it doesn't display an error message and the list is empty. Why? Thanks. code: ...<% dim conn dim rs Set con=Server.Crea