Developing Web Services: Three Easy Steps tutorial error

I'm following the tutorial Developing Web Services: Three Easy Steps, the first lab. I created the GetDates POJO, no problems. Then I went on to step 4 and am creating the WS for the java class. I get to step 5 where I've gone through the wizard for the web service and at step 5 in the wizard the tutorial says to click finish. When I click finish I get a popup saying
Validation Error
Files at the following URLs cannot be modified:
file:/C:/jdevhome/jdev/.....GetDates/public_html/WEB-INF/webservices.xml
and the same path but oracle-webservices.xml
Anyone else experience this when going through the tutorial? I'm not sure where the tutorial is on OTN or if it's on OTN yet. It's a tutorial I did in a session at OpenWorld and now i'm going through it locally now that we have the latest SOA suite installed.
Any thoughts?
Thanks, Rob

Just checked and it's not running. It's preventing the web service from being created, none of the directories are getting created since it's erroring.
I tried closing out and opening JDev up again and it's my C drive so I don't have anything set to read only.
JDev Studio Edition Version 10.1.3.1.0.3914
Rob

Similar Messages

  • Which is best web service framework for developing web services in Java?

    Hi Friends,
    I want to develop web services using Java 1.5.
    But I am in confusion with different frameworks provides to develop WS.
    Like
    1) Apache axis
    2) Java Web Service dev. Pack
    3) JSON-RPC-Java
    4) Web Ser. Invocation Pack
    5) XFire
    Can some one guide which framework should I use?
    OR where will i get useful comparison between this frameworks?

    Hi,
    Personally I have used:
    1. XFire
    2. Apache Axis
    3. Java Web Service Pack
    My personal opinion / .02 cents?
    1. XFire is awesome and very easy to set up and get running. They also have a great community / mailing lists. We use it in some production systems and it runs great.
    2. Apache AXIS 1/2 made me want to dive out the window and go splat just short of the double yellow line on the road. Pain in the butt to set up and get running. Way too complex. Really bad docs / tutorials / support.
    3. Java Web Service Pack - I really prefer NetBeans 5.5 and the JWSP. Easy to build services, cohesive enviroment. You can get the job done.
    That's my two cents.
    M Goodell

  • How to develop web service using Intellij Idea 6.0

    How to develop web services using Intellij Idea 6.x. A sample web service and service client is needed with full procedure. Thanx in advance.

    Web service is technology not a tools that bundle with IDE.
    For example you can't say how can I develope object orented program with Eclipse.
    1- You should get some general info about SOAP, WSDL and Web sevice usage
    2- Start to implmenet a simple Hello world web service and deploy it on application(web service) server
    3- Write Client code and test it.
    for step 2,3 Apache Axis(2) could be a good solution for developement or you can use JAX-WS for sun

  • Weblogic app server wsdl web service call with SSL Validation error = 16

    Weblogic app server wsdl web service call with SSL Validation error = 16
    I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
    Cannot complete the certificate chain: No trusted cert found
    Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
    Validation error = 16
    From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
    Here is how I load trustStore and keyStore in my java program:
         System.setProperty("javax.net.ssl.trustStore",”cacerts”);
         System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
         System.setProperty("javax.net.ssl.trustStoreType","JKS");
    System.setProperty("javax.net.ssl.keyStoreType","JKS");
    System.setProperty("javax.net.ssl.keyStore", keyStoreName);
         System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd);      System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
    Here is how I create cacerts using verisign hierarchy certs (in this order)
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
    1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
    Because my program is a weblogic app server, when I start the program, I have java command line options set as:
    -Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
    -Dweblogic.security.SSL.ignoreHostnameVerification=true
    -Dweblogic.security.SSL.enforceConstraints=strong
    That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
    In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
    I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
    1.     Do I create “cacerts” the correct order with right keeltool options?
    2.     Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
    3.     Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
    4.     Do I need to put the “cacerts” to some specific weblogic directory?
    ---------------------------------wsdl file
    <wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
         <wsp:Policy wsu:Id="TokenServices_policy">
              <wsp:ExactlyOne>
                   <wsp:All>
                        <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
                             <wsp:Policy>
                                  <sp:TransportToken>
                                       <wsp:Policy>
                                            <sp:HttpsToken RequireClientCertificate="true"/>
                                       </wsp:Policy>
                                  </sp:TransportToken>
                                  <sp:AlgorithmSuite>
                                       <wsp:Policy>
                                            <sp:Basic256/>
                                       </wsp:Policy>
                                  </sp:AlgorithmSuite>
                                  <sp:Layout>
                                       <wsp:Policy>
                                            <sp:Strict/>
                                       </wsp:Policy>
                                  </sp:Layout>
                             </wsp:Policy>
                        </sp:TransportBinding>
                        <wsaw:UsingAddressing/>
                   </wsp:All>
              </wsp:ExactlyOne>
         </wsp:Policy>
         <wsdl:types>
              <xsd:schema targetNamespace="http://tempuri.org/Imports">
                   <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
                   <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
              <wsdl:part name="parameters" element="tns:GetUserToken"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
              <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
              <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
         </wsdl:message>
         <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
              <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
         </wsdl:message>
         <wsdl:portType name="ITokenServices">
              <wsdl:operation name="GetUserToken">
                   <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
                   <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
              </wsdl:operation>
              <wsdl:operation name="GetSSOUserToken">
                   <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
                   <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="TokenServices" type="tns:ITokenServices">
              <wsp:PolicyReference URI="#TokenServices_policy"/>
              <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="GetUserToken">
                   <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
                   <wsdl:input>
                        <soap12:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap12:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
              <wsdl:operation name="GetSSOUserToken">
                   <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
                   <wsdl:input>
                        <soap12:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap12:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="TokenServices">
              <wsdl:port name="TokenServices" binding="tns:TokenServices">
                   <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
                   <wsa10:EndpointReference>
                        <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
                   </wsa10:EndpointReference>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    ----------------------------------application log
    adding as trusted cert:
    Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
    Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
    adding as trusted cert:
    Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
    Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
    adding as trusted cert:
    Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
    Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
    Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
    Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
    <Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
    <Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
         at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at com.certicom.tls.record.WriteHandler.write(Unknown Source)
         at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
         at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
         at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
         at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
         at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
         at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
         at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
         at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
         at javax.xml.ws.Service.<init>(Service.java:56)
         at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
         at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
         at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
         at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
    Not Valid Before:Tue Dec 18 19:00:00 EST 2012
    Not Valid After:Wed Jan 07 18:59:59 EST 2015
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
    Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
    Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
    Not Valid Before:Sun Feb 07 19:00:00 EST 2010
    Not Valid After:Fri Feb 07 18:59:59 EST 2020
    Signature Algorithm:SHA1withRSA
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
    <Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
         at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
         at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
         at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
         at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at com.certicom.tls.record.WriteHandler.write(Unknown Source)
         at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
         at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
         at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
         at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
         at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
         at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
         at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
         at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
         at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
         at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
         at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
         at javax.xml.ws.Service.<init>(Service.java:56)
         at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
         at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
         at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
         at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

    I received a workaround by an internal message.
    The how to guide is :
    -Download the wsdl file (with bindings, not the one from ESR)
    -Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
    -Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
    -Create a new logicial destination that point to the wsdl file modified
    -Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
    Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

  • The Best Java Web Services Technology for Developing Web Services

    Hi,
    I am new to Web services world.
    I read the java web services page . there are more than 6 technologies.
    JAX-WS,
    JAX-RPC,
    JAXB,
    SAAJ,
    JAXP,
    WSIT,
    XWS-Security
    I went through several documents on web services.
    I could not get a clear idea of which technolgy to use.
    Which Java web service technology will be the best to develop web services independant of language, platform.
    or is there any 3rd party implemetations available ? for rapid development of web services.
    Could anyone help me !.
    Thanks in advance.
    Message was edited by:
    Siva.Prakash

    Which Java web service technology will be the best
    to develop web services independant of language,
    platform.
    Java by nature is a cross-platform language, so if your focus is on the need for portability, the choisce of WS should not be a problem. However, each WS is best suited for paricular uses.
    SAAJ, a low-level level API, offers much simplicity, but is not the first choice for programmers, as SOAP (Simple Object Access Protocol)messages need to be constructed piece by piece, making it a quite arduous code to program.
    If you are not familiar with XML, your best bet would be to use JAX-RPC (Java API for XML-Remote Procedure Calls), as it hides the underlying detail from the programmer, in terms of SOAP and XML. The shortcoming with RPC-based WS is that it is "restricted to the local programming experience". Another failing is that assumes there is a network path- a reliability concern.
    If your program will be contacting other services during downtimes, unlike JAX-RPC, JAXM is quite useful. However, your listing did not mention it, so I wont cover it.
    JAXR is a client-side only API that acts as an interface between registries (not referring to JAXP)
    I am not famiiar with JAXB, JAXP, WSIT or XWS-Security..
    or is there any 3rd party implemetations available ?It depends on what platform you are used to. Assuming you are familiarized with the J2EE platform (now changed to Java EE SDK), the NetBeans IDE (either 5.5, 5.5.1 or the latest editiion) is quite useful. I am using 5.5.1, but have found that it is quite buggy, especially when adding WS operations, a core requirement of a WS. if you will be using to devlop a service for an immediate need, you may find the learning curve to be a bit high, in terms of getting to grips with how to use it. (Download link:
    http://www.netbeans.info/downloads/index.php)
    The IBM Autonomic IDE (or AIDE), based on the WSDM standard, includes 3 sub-tools, icluding the IBM Manageability Endpoint Builder which, according to their website, allows individuals to build endpoints to allow manageability interface exposure; Manageable Resource Browser and the IBM Manageability Endpoint Simulator. However, I'm not familiar with this IDE. (Download link: http://www.alphaworks.ibm.com/tech/aide/download)
    The .NET Framework uses the Visual Studio IDE. For an unbiased comparison of J2EE and the .NET Framework in terms of WS, see http://www.webservicesarchitect.com/content/articles/hanson01.asp.
    Apache Axis2, Geronimo and JiBX allows fast development of WS, or so the creators profess.
    The PHP environment- you could try NuSPHERE PHPed. According to one website, with it you can develop a web service in under an hour.
    I hope this was useful to you.
    [Based partly on Topley, K. (2003) [i]Java TM Web Services in a Nutshell: A desktop Quick Reference. 1st ed. California: O�Reilly & Associates, Inc]

  • What is the best practice for developing web service?

    Hi All,
    I'm a newbee to web services...
    I was wondering what would be the best approach in developing a web service,
    using tools or programmatic approach?
    If I use WebLogic Workshop, am I tied to a vendor?
    Is it possible for me to develop web services using workshop and deploy in
    another app server..?
    I would appreciate if somebody could give me a pointer to start.
    I have already referred BEA's docs.
    I'm still confused on a good starting point on the best approach to develop
    protable web services.
    Thanks in advance for any inputs.
    K K

    K K-
    You have a very valid point on the simplify or complicate matters. If you are
    going for clean and not-so-time-centric code, then there are several different
    programs and packages out there you can choose from.
    Since you are specialized in J2EE, than the Sun package may be what you are looking
    for. BEA's classes simplify much of the work you will be doing, but you could
    emulate their classes or extend yours above the functions provided in theirs.
    It all boils down to how much work are you willing to do.
    If you are asking for more detailed, coding 'Design Patterns' to utilize, I would
    wait for a few more posts from other folks as my work often requires me to utilize
    the tools provided.
    Sincerely,
    Eric Ballou
    "K K" <[email protected]> wrote:
    Eric,
    Thanks for the response.
    I was also looking at Sun's WSDP 1.1, which is more programmatic approach.
    Some how, I feel being a J2EE developer, I should go on the direction
    of the
    programmatic approach.
    Using the tools could simplify or complicate things. Also, the Workshop
    samples import all weblogic specific packages.
    My code looks so dirty with many vendor specific packages being imported.
    Could you give me your suggestions for a clean and neat approach?
    I would personally prefer to avoid the quick and dirty approach.
    Thanks again.
    "Eric Ballou" <[email protected]> wrote in message
    news:[email protected]...
    K K-
    The best approach in developing portable web services is knowing whatyou
    are
    planning on using them for as well as how much is willing to be spent,etc.
    BEA's Workshop is portable to other frameworks, but the ease ofintegrating a
    developed client or a developed server can very greatly. Even moreof an
    issue
    is migration from one framework to another. If you choose to developin
    Workshop
    and your company later deploys .Net solutions, some of your work mayhave
    to be
    redone unless the company is willing to keep portions of the 'old'system
    around
    until new versions of the service are available. However, Workshophas
    several
    ant tools available that would assist you in deploying to other appservers or
    even a stand-alone application should you need cross framework abilities.
    If you are just starting out in web services, http://www.webservices.org
    is a
    good place to start checking out vendors in the space.
    Sincerely,
    Eric Ballou
    "K K" <[email protected]> wrote:
    Hi All,
    I'm a newbee to web services...
    I was wondering what would be the best approach in developing a web
    service,
    using tools or programmatic approach?
    If I use WebLogic Workshop, am I tied to a vendor?
    Is it possible for me to develop web services using workshop and deploy
    in
    another app server..?
    I would appreciate if somebody could give me a pointer to start.
    I have already referred BEA's docs.
    I'm still confused on a good starting point on the best approach todevelop
    protable web services.
    Thanks in advance for any inputs.
    K K

  • What is needed to develop web services with DI Server using C #?

    Hi,
    What is needed to develop web service using DI Service ad C#?
    Does anyone have any examples?
    thanks,
    Willian

    Login C# sample
    u2018 Create Service WebReference
    LoginWebRef.LoginService loginService = new LoginWebRef.LoginService();
    // service command login call
    string sessionID = login.Login(
    "localhost",
    "COM_OBS_AUT_TEST",
    LoginWebRef.LoginDatabaseType.dst_MSSQL2005, true,
    "sa", "xx",
    "manager", "manager",
    LoginWebRef.LoginLanguage.ln_English, true,
    "localhost:30000");
    Business Partners add C# sample.
    // Create Service WebReference
    BPWebRef.BusinessPartnersService bpsService = new
    BPWebRef.BusinessPartnersService();
    // MsgHeader class
    BPWebRef.MsgHeader msgheader = new BPWebRef.MsgHeader();
    msgheader.SessionID = DIServerSessionID;
    msgheader.ServiceName = MsgHeaderServiceName.BusinessPartnersService;
    msgheader.ServiceNameSpecified = true;
    bpsService.MsgHeaderValue = msgHeader;
    // fill business partner class
    BPWebRef.BusinessPartner bp = new BPWebRef.BusinessPartner();
    bp.CardCode = "MyBPCardCode";
    u2026
    // service command call
    BPWebRef.BusinessPartnerParams bpParams = bpsService.Add(bp);

  • Developing web services for interoperability

    Hello,
    I often read that the correct way in terms of interoperability to develop web services is to start from the wsdl towards java classes, not the other way round. I find this puzzling since I was sure that jaxrp compliant toolkists were able to only generate ws-i basic profile compliant web services. So, is it really an interoperability issue or is there some other problem with the java to wsdl approach ?
    Thanks

    If you want to develope intoperable web services you should probably use JAX-WS to start with. You can read about JAX-WS at http://jax-ws.dev.java.net and you can download it with JWSDP 2.0 (http://java.sun.com/webservices/downloads/webservicespack.html).
    JAX-RPC's databinding is somewhat limited and its interop is also limited.
    During the development of JAX-WS we have been working with Microsoft to make sure that JAX-WS will interop with WCF (Indigo).

  • Please give me your opinion... about tools for develop web service

    If you would like to choose the tool for develop web service.
    what is the most important feature that you will consider,
    Please help me to order these topic from the most to the least
    a. creating web service
    b. creating web service client
    c. searching web service to UDDI registry
    d. publish web service to UDDI registry
    e. connecting to database management systems.
    f. license fee
    g.system requirements
    h. Installation procedures
    thank you very much for your opinion. I will keep your information for my research....
    :)

    Hi Fangnaka,
    You can use JWDSP2.0 + Tomcat 5.X +Jdk1.5 to develop and deploy webservice.
    Better IDEA are Intellij or Eclipse for webservice code development.
    Cheers
    Rajesh R

  • Need help developing web services on Jdeveloper

    Hi,
    I'm having some problems developing a particular web service using jdeveloper 10.1.2.1.0 (build 1913).
    The web service is located on a remote computer (windows server 2003 SP1), deployed on a jboss3.2.5.
    I got the following error:
    java.lang.ClassCastException: oracle.xml.parser.v2.XMLText
    at oracle.jdeveloper.webservices.runtime.WrappedDocLiteralStub.fromElement(WrappedDocLiteralStub.java:614)
    at mypackage1.PdfGenStub.getConfigurationXML(PdfGenStub.java:189)
    at mypackage1.PdfGenStub.convertDocumentToPdf(PdfGenStub.java:241)
    at mypackage1.PdfGenStub.main(PdfGenStub.java:42)
    The web service is from a product that we have that converts documents to pdf.
    Any ideas ??
    However, I will try to intall the product on another machine that has connection outside the company network to put the WSDL link here for anyone who wants to test it .
    thanks

    Hi,
    Would really help if you could provide the wsdl and also steps to reproduce this exception, for us to try it out locally.
    You could also try to install the latest JDev 10.1.3.1 available on OTN, to see if it works on it.
    Regards,
    Sunil..

  • Doubts developing web services on JDev 10.1.3.0.4

    Hi,
    I was trying to follow this guide
    http://www.oracle.com/technology/oramag/webcolumns/2003/techarticles/balusamy.html
    in order to develop this web service on Jdev 10.1.3.0.4.
    But the menus are different from the version used on the tutorial. I´m having some difficulties with the selections that i have to make in the menus. Also, after trying several options, the files generated are different from the ones that appear on this tutorial.
    Does anyone know how to reproduce this tutorial on this version of jdev ?
    Thanks.

    Hi,
    The guide you were refering was pointing to 10.1.2 wizards.
    For the latest 10.1.3 tutorial, please follow the below tutorial link :
    http://www.oracle.com/technology/products/jdev/101/tutorials/WS/WSandAScontrol.htm
    Hope this helps,
    Sunil..

  • Consuming a web service in ABAP exception and error

    Hi experts,
    I have succesfully implemented this example web service http://www.webservicex.net/airport.asmx?WSDL from http://www.webservicex.net/airport.asmx and everything works perfect so I know it is possible.
    But my requirement is to implement the following web service: http://ws1.webservices.nl/business/soap_doclit?wsdl it is a document/literal soap web service and WS-I Basic Profile 1.0 compliant. When I try to create a proxy object I get the following errors:
    - Exception occurred in library handler
    - Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/wsdl
    I already found that library handler exception might have something to do with http bindings, I found note 1403271 but as my system is running on release 702 level 0008 this note is obsolete.
    Now 2nd error, incorrect value I don't really understand.. I also think the web service is SOAP 1.1 and not 1.2 because that should also give problems according to this topic: Proxy object to consume web service - can anyone verify to be sure? I'm not that familiar with WSDL files but does anyone know what I can test and what I can remove from the web service?
    The web service documentation is found here: https://webview.webservices.nl/documentation/files/interfaces/soap/soap-txt.html#SOAP_Interface.Differences_between_SOAP_interfaces
    There are also other versions such as RPC/Encoded and one without a header but ALL versions give the exact same error.
    Thx!

    check the beginning of your WSDL file
    just after the first line <xml> you should have
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    followed by the namespaces related to your web service if required.
    SAP does all the job (generate the web service client) but any very little error in the file (or element not recognized) leads to this message "exception occurred in library handler" and it is not easy to know exactly what is the error...

  • UTL_DBWS accessing  web service gives 'not contain port' error

    Hello
    I am trying to call a web service from https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl
    In the WSDL xml, i get the targetNamespace (http://PlanonWebServices.ws),
    the service name (PlanonSession),
    the wsdl URL (https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl),
    the portType name (PlanonSessionHttpEndpoint),
    the operation name (login).
    When i call the web service, i get an error about the port :
    -29532 - ORA-29532: Java call terminated by uncaught Java exception: service:
    {http://PlanonWebServices.ws}PlanonSession does not contain port:
    {http://PlanonWebServices.ws}PlanonSessionHttpEndpoint
    The code is :
    CREATE OR REPLACE PROCEDURE planon_Login AS
    planon_username     VARCHAR2(50):= 'XXXXXX'; --- removed for security
    planon_passwd     VARCHAR2(50):= 'XXXXX'; --- removed for security
    service_ sys.utl_dbws.SERVICE;
    call_ sys.utl_dbws.CALL;
    service_qname sys.utl_dbws.QNAME;
    port_qname sys.utl_dbws.QNAME;
    operation_qname sys.utl_dbws.QNAME;
    string_type_qname sys.utl_dbws.QNAME;
    username     sys.utl_dbws.QNAME;
    password      sys.utl_dbws.QNAME;
    --retx               ANYDATA;
    retx_string VARCHAR2(1000);
    l_namespace     VARCHAR2(1000);
    l_wsdl_url VARCHAR2(1000);
    l_input_params      sys.utl_dbws.ANYDATA_LIST;
    outputs      sys.utl_dbws.ANYDATA_LIST;
    output_retx VARCHAR2(1000);
    xml_string sys.xmltype;
    retx sys.xmltype;
    qname_list_     sys.utl_dbws.QNAME_LIST;
    qname_list_string sys.utl_dbws.QNAME_LIST;
    BEGIN
    dbms_output.put_line('Step 1');
    dbms_output.put_line('Step 1 : Set l_wsdl_url');
    l_wsdl_url := 'https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl';
    dbms_output.put_line('Step 1 : Set l_namespace');
    l_namespace := 'http://PlanonWebServices.ws';
    dbms_output.put_line('Step 1 : Set service_');
    service_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSession');
    service_ := sys.utl_dbws.create_service (URIFACTORY.getURI(l_wsdl_url), service_qname);
    dbms_output.put_line('Step 1 : Set port_qname_');
    port_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSessionHttpEndpoint');
    dbms_output.put_line('Step 1 : Set operation_qname');
    operation_qname := sys.utl_dbws.to_qname(l_namespace, 'login');
    dbms_output.put_line('Step 1 : Set call_');
    call_ := sys.utl_dbws.create_call(service_,port_qname,operation_qname);
    dbms_output.put_line('Step 2');
    sys.utl_dbws.set_property(call_,'USERNAME', planon_username);
    sys.utl_dbws.set_property(call_,'PASSWORD', planon_passwd);
    sys.utl_dbws.set_property(call_,'SOAPACTION_USE','TRUE');
    sys.utl_dbws.set_property(call_,'SOAPACTION_URI','https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession');
    sys.utl_dbws.set_property(call_,'ENCODINGSTYLE_URI', 'https://schemas.xmlsoap.org/soap/encoding/');
    sys.utl_dbws.set_property(call_,'OPERATION_STYLE','document');
    dbms_output.put_line('Step 3');
    string_type_qname := sys.utl_dbws.to_qname('https://www.w3.org/2001/XMLSchema', 'string');
    /* first return parameter in the WSDL should not be specified in the parameter list or errors occur
    sys.utl_dbws.add_parameter(call_, 'loginResponse', string_type_qname, 'ParameterMode.OUT');
    sys.utl_dbws.set_return_type(call_,string_type_qname);
    xml_string := xmltype('<PlanonSession xmlns="https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services">'
    || '</PlanonSession>');
    retx := sys.utl_dbws.invoke(call_,xml_string);
    dbms_output.put_line('Step 6');
    dbms_output.put_line('Step 7');
    dbms_output.put_line('Call Web Service:services:PlanonSession: ' || retx.getStringVal());
    dbms_output.put_line('Step 10');
    sys.utl_dbws.release_call(call_);
    sys.utl_dbws.release_service(service_);
    dbms_output.put_line('Step 11');
    EXCEPTION
    when others then
    dbms_output.put_line(SQLCODE || ' - ' || SQLERRM);
    END;
    The WSDL document is :
    ?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:ns="http://PlanonWebServices.ws" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://PlanonWebServices.ws">
    <wsdl:documentation>PlanonSession</wsdl:documentation>
    <wsdl:types>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://PlanonWebServices.ws">
    <xs:complexType name="Exception">
    <xs:sequence>
    <xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
    </xs:sequence>
    </xs:complexType>
    <xs:element name="logout">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="logoutResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="return" type="xs:boolean"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setReferenceDate">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
    <xs:element minOccurs="0" name="param1" nillable="true" type="xs:dateTime"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setReferenceDateResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="return" type="xs:boolean"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setSessionDataSection">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
    <xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setSessionDataSectionResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="return" type="xs:boolean"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="login">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
    <xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="loginResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    </wsdl:types>
    <wsdl:message name="logoutRequest">
    <wsdl:part name="parameters" element="ns:logout"/>
    </wsdl:message>
    <wsdl:message name="logoutResponse">
    <wsdl:part name="parameters" element="ns:logoutResponse"/>
    </wsdl:message>
    <wsdl:message name="loginRequest">
    <wsdl:part name="parameters" element="ns:login"/>
    </wsdl:message>
    <wsdl:message name="loginResponse">
    <wsdl:part name="parameters" element="ns:loginResponse"/>
    </wsdl:message>
    <wsdl:message name="setSessionDataSectionRequest">
    <wsdl:part name="parameters" element="ns:setSessionDataSection"/>
    </wsdl:message>
    <wsdl:message name="setSessionDataSectionResponse">
    <wsdl:part name="parameters" element="ns:setSessionDataSectionResponse"/>
    </wsdl:message>
    <wsdl:message name="setReferenceDateRequest">
    <wsdl:part name="parameters" element="ns:setReferenceDate"/>
    </wsdl:message>
    <wsdl:message name="setReferenceDateResponse">
    <wsdl:part name="parameters" element="ns:setReferenceDateResponse"/>
    </wsdl:message>
    <wsdl:portType name="PlanonSessionPortType">
    <wsdl:operation name="logout">
    <wsdl:input message="ns:logoutRequest" wsaw:Action="urn:logout"/>
    <wsdl:output message="ns:logoutResponse" wsaw:Action="urn:logoutResponse"/>
    </wsdl:operation>
    <wsdl:operation name="login">
    <wsdl:input message="ns:loginRequest" wsaw:Action="urn:login"/>
    <wsdl:output message="ns:loginResponse" wsaw:Action="urn:loginResponse"/>
    </wsdl:operation>
    <wsdl:operation name="setSessionDataSection">
    <wsdl:input message="ns:setSessionDataSectionRequest" wsaw:Action="urn:setSessionDataSection"/>
    <wsdl:output message="ns:setSessionDataSectionResponse" wsaw:Action="urn:setSessionDataSectionResponse"/>
    </wsdl:operation>
    <wsdl:operation name="setReferenceDate">
    <wsdl:input message="ns:setReferenceDateRequest" wsaw:Action="urn:setReferenceDate"/>
    <wsdl:output message="ns:setReferenceDateResponse" wsaw:Action="urn:setReferenceDateResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="PlanonSessionSoap11Binding" type="ns:PlanonSessionPortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <wsdl:operation name="logout">
    <soap:operation soapAction="urn:logout" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="login">
    <soap:operation soapAction="urn:login" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setSessionDataSection">
    <soap:operation soapAction="urn:setSessionDataSection" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setReferenceDate">
    <soap:operation soapAction="urn:setReferenceDate" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="PlanonSessionSoap12Binding" type="ns:PlanonSessionPortType">
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <wsdl:operation name="logout">
    <soap12:operation soapAction="urn:logout" style="document"/>
    <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="login">
    <soap12:operation soapAction="urn:login" style="document"/>
    <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setSessionDataSection">
    <soap12:operation soapAction="urn:setSessionDataSection" style="document"/>
    <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setReferenceDate">
    <soap12:operation soapAction="urn:setReferenceDate" style="document"/>
    <wsdl:input>
    <soap12:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="PlanonSessionHttpBinding" type="ns:PlanonSessionPortType">
    <http:binding verb="POST"/>
    <wsdl:operation name="logout">
    <http:operation location="PlanonSession/logout"/>
    <wsdl:input>
    <mime:content type="text/xml" part="logout"/>
    </wsdl:input>
    <wsdl:output>
    <mime:content type="text/xml" part="logout"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="login">
    <http:operation location="PlanonSession/login"/>
    <wsdl:input>
    <mime:content type="text/xml" part="login"/>
    </wsdl:input>
    <wsdl:output>
    <mime:content type="text/xml" part="login"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setSessionDataSection">
    <http:operation location="PlanonSession/setSessionDataSection"/>
    <wsdl:input>
    <mime:content type="text/xml" part="setSessionDataSection"/>
    </wsdl:input>
    <wsdl:output>
    <mime:content type="text/xml" part="setSessionDataSection"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setReferenceDate">
    <http:operation location="PlanonSession/setReferenceDate"/>
    <wsdl:input>
    <mime:content type="text/xml" part="setReferenceDate"/>
    </wsdl:input>
    <wsdl:output>
    <mime:content type="text/xml" part="setReferenceDate"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="PlanonSession">
    <wsdl:port name="PlanonSessionHttpSoap11Endpoint" binding="ns:PlanonSessionSoap11Binding">
    <soap:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap11Endpoint/"/>
    </wsdl:port>
    <wsdl:port name="PlanonSessionHttpSoap12Endpoint" binding="ns:PlanonSessionSoap12Binding">
    <soap12:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap12Endpoint/"/>
    </wsdl:port>
    <wsdl:port name="PlanonSessionHttpEndpoint" binding="ns:PlanonSessionHttpBinding">
    <http:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpEndpoint/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Any help is greatly appreciated.
    Thanks in advance

    I got the same error... did you find a solution?
    tks
    M&aacute;rio Cardia

  • How to develop web services using a existing WSDL

    I wrote a test web service program using a existing .NET HelloWorld WSDL.
    After wsdeploying step, new WSDL was generated that was different from original one. There was a mismatch in messge part name between two WSDL.
    When i ran a client program, it generated a following error;
    java.rmi.ServerException: Internal Server Error (deserialization error : unexpected XML reader state. expected: END but found: START: input)
    How can I get wsdeploy to use existing WSDL when it generates server artifacts internally?

    I created a web service client from the original WSDL using wscompile -gen:client.
    original WSDL is:
    <?xml version="1.0"?>
    <wsdl:definitions name="HelloWorld" targetNamespace="http://soap/WebService/HelloWorld" xmlns:typens="http://soap/WebService/HelloWorld" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" >
         <wsdl:types/>
         <message name="SayHelloRequest">
              <part name="input" type="xsd:string"/>
         </message>
         <message name="SayHelloResponse">
              <part name="return" type="xsd:string"/>
         </message>
         <portType name="HelloWorldPort">
              <operation name="sayHello">
                   <input message="typens:SayHelloRequest"/>
                   <output message="typens:SayHelloResponse"/>
              </operation>
         </portType>
         <binding name="HelloWorldBinding" type="typens:HelloWorldPort">
              <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="sayHello">
                   <soap:operation soapAction=""/>
                   <input>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://soap/WebService/HelloWorld"/>
                   </input>
                   <output>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://soap/WebService/HelloWorld"/>
                   </output>
              </operation>
         </binding>
         <service name="HelloWorldService">
              <port name="HelloWorldPort" binding="typens:HelloWorldBinding">
                   <soap:address location="http://localhost/ws/helloworld"/>
              </port>
         </service>
    </wsdl:definitions>

  • Developing Web Services with TeleAtlas + custom data.

    A client has some TeleAltas data + own data and would like to develop some Web Services. Initially some WMS and WFS, then Geocoding + Inverse and maybe some routing. I see 2 options:
    1. Try and get the data into the format required by the Oracle OpenLS GeoCoding + Routing Functions.
    2. Design a custom data model and develop all the functions from scratch.
    I'm inclined towards the second option.
    Any feedback will be gratefully received.

    In my experience, the Oracle Spatial Geocoder is very well done, and support for it is excellent.
    I do not know how easy/difficult it will be to convert TA data into a format consumable by the Oracle geocoder.
    I do know that NAVTEQ (the company I work for) ships data out-of-the-box for the Oracle Geocoder and Router (as well as mapping and analysis).
    Dan Abugov

Maybe you are looking for