WSDL Client

Hello,
I made a WSDL client and now I've seen that java has a native client JAX-WS that I could of use.
My original client knows how to use PKCS11 and how to set HTTP header vars(including basic HTTP authentication).
I don't know how to translate PKCS11 and HTTP header vars in JAX-WS.
I should find a place where to specify a SSLSocketFactory in JAX-WS.
I started with the example from here: http://www.mkyong.com/webservices/jax-ws/jax-ws-hello-world-example/ and I tried to add these 2 functionalities.
But the problem line is at
{Service service = Service.create(url, qname);}
and I can't add here my new functionality.
What should I do?
This is the client:
package com.mkyong.client;
import java.net.URL;
import javax.xml.namespace.QName;
import javax.xml.ws.Service;
import com.mkyong.ws.HelloWorld;
public class HelloWorldClient{
    public static void main(String[] args) throws Exception {
    URL url = new URL("http://localhost:9999/ws/hello?wsdl");
        QName qname = new QName("http://ws.mkyong.com/", "HelloWorldImplService");
        Service service = Service.create(url, qname);
        HelloWorld hello = service.getPort(HelloWorld.class);
        System.out.println(hello.getHelloWorldAsString("mkyong"));
Thank you

This is what I tryed:
            URL url = new URL(protocol+"://"+host+":"+port+servicePath);
            QName portName = new QName(protocol+"://"+host+":"+port, servicePath);
            System.out.println("URL IS "+url.toString());
            Service service = Service.create(url, portName);
            OnlineSIUIDef portSIUI = service.getPort(OnlineSIUIDef.class);
            BindingProvider bindingProvider = (BindingProvider)portSIUI;
            Map requestContext = bindingProvider.getRequestContext();
            requestContext.put(BindingProvider.USERNAME_PROPERTY, SIUI_USERNAME);
            requestContext.put(BindingProvider.PASSWORD_PROPERTY, SIUI_PASSWORD);
            PKCS11 pk11 = new PKCS11();
            pk11.loadSecurityProviders();
            RetStruct statD = pk11.getKeyManagerFactory();
            if(statD.succes) {
                kKeyManagerFactory = (KeyManagerFactory)statD.returnParameters.get("KeyManagerFactory");
            } else {
                System.out.println("Eroare "+statD.errMessage);
            SSLContext context = SSLContext.getInstance("TLS");
            context.init(kKeyManagerFactory.getKeyManagers(), null, null);
            factory = context.getSocketFactory();
            Dispatch<SOAPMessage> dispatch = service.createDispatch(portName, SOAPMessage.class, Service.Mode.MESSAGE);
            dispatch.getRequestContext().put (JAXWSProperties.SSL_SOCKET_FACTORY, factory);
            dispatch.getRequestContext().put(BindingProvider.SOAPACTION_URI_PROPERTY, protocol+"://"+host+":"+port+servicePath);
            OnlineSIUIDef hello = service.getPort(OnlineSIUIDef.class);
            System.out.println(hello.getOnlineSIUIDefString("mkyong"));
The error is at line 4 - before setting the user, password and the SSL Context.
So the error is normal because the application never got to the line where the user, password and ssl context was set.
But how do I set these before line 4?
The error is
Exception in thread "main" javax.xml.ws.WebServiceException: Failed to access the WSDL at: https://www.siui.ro:443/svapntws/services/SiuiWS?wsdl. It failed with:
    Got Server returned HTTP response code: 401 for URL: https://www.siui.ro:443/svapntws/services/SiuiWS?wsdl while opening stream from https://www.siui.ro:443/svapntws/services/SiuiWS?wsdl.
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:173)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:155)
    at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:120)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:257)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:220)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:168)
    at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:96)

Similar Messages

  • Building WSDL client for OIM SPML webservice

    Has any one created WSDL client for OIM SPML webservice,
    Any help is appreciated.
    Thanks,
    Pandu
    old thread -->
    add udfs to spml prov. request to oim
    ==========================
    Hi,
    I am provisioning users in OIM from by sending spml requests
    I used the sample client that comes in xellerate directory.
    How can I update spml requests to include UDFs to create user in him with udf s.
    Thanks
    Pandu
    Edited by: pandu345 on Aug 5, 2009 3:27 PM

    Hello there,
    There is a .NET web service client which is successfully able to access the weblogic application server wsdl from oim 9101 and it can see the complete user profile as a response from the same.
    1.) Now, there is a situation where oim needs to send some attribute values to that .NET web service client, after the data from their side comes to OIM and updates a single attribute values for e.g. PIN. How can we do that ?
    2.) and I want to add some UDFs into the existing SPML provisioning user profile. How can I do that ?
    3.) Also, how will OIM know that it was able to successfully send the attribute values to the web service client.
    http://download.oracle.com/docs/cd/E10391_01/doc.910/e10360/creategtc.htm#Toc153968032
    I have gone through this. I didnt found this in OIM 9101.
    Any ideas/references/clues/hints appreciated in this concern.
    Thanks in advance,
    - oidm.

  • Error in consuming a WSDl client through a servlet

    Hi Guys,
    I have generated a client by consumig an enterprise service wsdl.
    I have made a servlet to call the client but i get the error as shown below..
    Request your help ASAP.
    "Application error occurred during the request procession."
    Details:     <b>Exception:</b>
    javax.servlet.ServletException: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at test.TestServlet.doGet(TestServlet.java:66)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         ... 30 more
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more
    <BR><BR><b>Root cause:</b>
    javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more
    javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more

    Hi Guys,
    I have generated a client by consumig an enterprise service wsdl.
    I have made a servlet to call the client but i get the error as shown below..
    Request your help ASAP.
    "Application error occurred during the request procession."
    Details:     <b>Exception:</b>
    javax.servlet.ServletException: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at test.TestServlet.doGet(TestServlet.java:66)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         ... 30 more
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more
    <BR><BR><b>Root cause:</b>
    javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more
    javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
         at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
         at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
         at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
         at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
         at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
         at test.TestServlet.doGet(TestServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:137)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
    Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
         at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
         ... 38 more
    Caused by: java.net.ConnectException: Connection timed out: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
         at sun.net.www.http.HttpClient.New(HttpClient.java:304)
         at sun.net.www.http.HttpClient.New(HttpClient.java:316)
         at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
         at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
         at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
         ... 39 more

  • Process as a Web Service WSDL client

    Hi,
    I am using the Process as a Web Service Option inside of BPM . I launch the deployed webservices webapps and I get the WSDL out of it.. The WSDL works fine with SOAP UI..But when I try to create a web service client out of that WSDL it gives me the following error:-
    com.bea.albpm.TestProject.SampleProject.OperationException cannot be resolved as type and the web service client does not work..
    how do I resolve this error.. Is there a jar file that I need to import?

    Did you use PAPI code inside your web service or did u just use PAPI Web Services ( like did u just pressed the button Launch PAPI Web Services ) and it created the WSDL for you and u used it to create the client?
    I am using the latest version of OBPM..
    Oracle 10.3.10
    Can you let me know what do u mean by PAPI interface.. Is it the PAPI code of is the PAPI Web Service which is built by BPM automatically and could be used?
    Edited by: user8707382 on Sep 10, 2009 9:00 AM

  • Dynamic WSDL Client troubles

    First I would love a dynamic client example that actualy used the wsdl type generated by Workshop. BEA's example is using the "URN:" format not using their own format.
    I havent been able to get the example dynamic client to work yet against their generated wsdl for my simple method
    which has no inputs or outputs.
    I am getting the following error and need help, Im not sure where to go from here.
    Any pointers would be very welcome.
    ERROR{
    javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAP
    Elementweblogic.xml.schema.binding.SerializationException: mapping lookup failur
    e. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{sc
    hemaType=['http://www.openuri.org/']:test}
    at weblogic.webservice.core.DefaultPart.invokeSerializer(Ljavax/xml/soap
    /SOAPElement;Ljava/lang/Object;Lweblogic/xml/stream/XMLOutputStream;Lweblogic/xm
    l/schema/binding/SerializationContext;)V(DefaultPart.java:332)
    at weblogic.webservice.core.DefaultPart.toXML(Ljavax/xml/soap/SOAPElemen
    t;Ljava/lang/Object;Lweblogic/xml/schema/binding/SerializationContext;ZLjavax/xm
    l/rpc/encoding/TypeMapping;)V(DefaultPart.java:297)
    target service{
    package testset;
    * @editor-info:link autogen-style="stateless" source="TestImpl.jcs" autogen="true"
    public class TestTest implements com.bea.jws.WebService
    static final long serialVersionUID = 1L;
    /** @common:control */
    public testset.Test test;
    /** @common:operation
    public void test()
    { test.test(); }
    Client {
    public void run(String wsdl_url,String service_url,String namespace,String jws_name,String conn_port,String operation,String[] args) throws Exception {
    // Setup the global SAAJ 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");
    // create service factory
    ServiceFactory factory = ServiceFactory.newInstance();
    if (service_url.length() == 0){
    service_url = "http://www.themindelectric.com/wsdl/";
    if (namespace.length() == 0){
    namespace = "net.xmethods.services.stockquote.StockQuote";
    if (wsdl_url.length() == 0){
    wsdl_url = "http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl";
    if (operation.length() == 0){
    operation = "getQuote";
    if (jws_name.length() == 0){
    jws_name = namespace+"Service";
    if (conn_port.length() == 0){
    conn_port = namespace+"Port";
    // define qnames
    String targetNamespace = service_url+namespace+"/";
    QName serviceName =
    new QName(targetNamespace,
    jws_name);
    QName portName =
    new QName(targetNamespace,
    conn_port);
    QName operationName = new QName(targetNamespace,
    operation);
    URL wsdlLocation =
    new URL(wsdl_url);
    //new URL("http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
    // create service
    Service service = factory.createService(wsdlLocation, serviceName);
    // create call
    Call call = service.createCall(portName, operationName);
    // invoke the remote web service
    Float result = (Float) call.invoke(args);
    System.out.println("\n");
    System.out.println("This example shows how to create a dynamic client"+
    "application that invokes a non-WebLogic Web Service.");
    System.out.println("The webservice used was:"+
    "http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
    System.out.println("The quote for BEAS is: ");
    System.out.println(result);
    }

    Hi,
    When I add a valueChangeListener for the App selection, the method is called before the ExecuteWithParams action is run. This means that I cannot get the new value for the Table selection list. And since I never know both the value of App and the value of Table, I cannot force the dynamic table to refresh.
    did you try to execute the query within the managed bean and then access the iterator to obtain the value ?
    Frank

  • Directory API - WSDL client

    Hi All,
    I am trying to create a simple program to edit and activate some channels in ID. The environment is PI 7.11 SP 6.
    I tried to import the WSDL directly from WSNavigator and tried to create a Java proxy client. The wizard would not complete and it throwed me an error saying
    IWAB0399E Error in generating Java from WSDL:  WSDLException (at /definitions/import/wsdl:definitions/wsdl:import/wsdl:definitions/wsdl:portType/PolicyReference): faultCode=INVALID_WSDL: Encountered unexpected element 'PolicyReference'.:
    I then tried to export the service interface WSDL and then tried to create the Client Java proxy components. This time the wizard completed but the packages imported are reporting eror mainly in LONG_Description.java (com.sap.xi.BASIS.Global package).Also the imported WSDL which was fine until I tried to generate the client now started complaining with error
    Element type "xsd:element" must be followed by either attribute specifications, ">" or "/>"
    The error points to this particular tag
    <xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="p3:Text"/>
    Any pointers to over come this would be highly appreciated.
    Thanks
    Jai

    One step forward. When I create the client proxy, the packages created are
    com.sap.xi.BASIS and com.sap.xi.BASIS.Global
    The packages
    types.api.server.ib.aii.sap.com and types.api.server.ibdir.aii.sap.com are not getting created.
    Is this correct? This is not in accordance with the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11653. [original link is broken] [original link is broken] [original link is broken]
    Thanks
    Jai

  • WSDL/client-stub generation without EJBs ?

    My WL7 application invokes methods on external subscriber
    web-apps. I need to provide WSDLs for these external apps, since
    they'll be implemented by our customers.
    Currently, I create 'dummy' EJBs, then create .ears out of it,
    run 'servicegen' to create a dummy webservice, then run
    'clientgen' to create the WSDLs and the client stub classes
    that I'll finally use. I'd like to avoid some of the above
    steps. Ideally, I'd just create the appropriate Java interface
    classes, then use some tool to create the WSDL and the
    client-stub classes. Is this possible ?
    -john

    Hi John,
    Have you considered using a WSDL generation GUI, such as
    http://www.omniopera.com/omniopera.html
    Bruce
    BTW, you do realize that when a webservice is deployed on WLS v7, the
    WSDL is available to anyone using
    http://<host>:<port>/<context_url>/<webservice>?WSDL
    john wrote:
    Bruce, I'm not sure how I would use those other tasks to obtain
    what I want. AFAIK, the only way to generate a WSDL for a service
    is to use the 'clientgen' task. And the clientgen task requires
    the actual webservice implementation in the form of a .ear
    file.
    In my case, I need to create WSDLs which I then pass on to
    my customers, for them to implement and host. Currently, to do
    this I have to myself implement the desired dummy webservice
    and then use clientgen to obtain the WSDL (along with the
    stubs etc ..)
    thanx
    -john
    Bruce Stephens <[email protected]> wrote:
    Hi John,
    In addition to the servicegen and clientgen ant tasks there are now
    several other narrowly focused ant tasks such as autotype, and
    source2wsdd. Check out the documentation:
    http://edocs.bea.com/wls/docs70/webserv/assemble.html#1011066
    Hope this helps,
    Bruce
    john wrote:
    My WL7 application invokes methods on external subscriber
    web-apps. I need to provide WSDLs for these external apps, since
    they'll be implemented by our customers.
    Currently, I create 'dummy' EJBs, then create .ears out of it,
    run 'servicegen' to create a dummy webservice, then run
    'clientgen' to create the WSDLs and the client stub classes
    that I'll finally use. I'd like to avoid some of the above
    steps. Ideally, I'd just create the appropriate Java interface
    classes, then use some tool to create the WSDL and the
    client-stub classes. Is this possible ?
    -john

  • J2ME Wsdl Client Help!! Please!!!!!!!!!!

    Hey guys, i was wondering could any one help me..
    i've basically used c# to create a wsdl that is deployed on iis.
    my question is how exactly do i use java (j2me) to access and use the wsdl?
    the wsdl retreives info from an oracle database..
    can anyone point me in the right direction!

    any one help?!! please i'm really stuck!

  • WSDL Eclispe VS WebSphere Client Generation

    Hi All,
    I am facing issues while generating WSDL Clients on WebSphere plateform.
    After generating the clients I am not able to execute the UCM services.
    While when i generate the WSDL Client from Eclispe, I can successfully execute UCM Services.
    Any pointers, as to how can this be avoided.
    regards,
    sapan
    Edited by: sapan on Mar 9, 2009 7:27 AM
    Solved it on my own, problem in selection of jars, dont forget to add obectpoolimpl.jar in your class path.

    Hi Sapan,
    I am able to generate sample client using IBM WID 6.2.
    I am generating it using axis and with Websphere libraries.
    What kind of error do you get ? make sure that you do not include any axis libraries.
    I hope this will help you

  • SAXException while generating stubs from WSDL

    Hi Friends
    i am stuck in a problem for which i need your help.
    i am using the Axis wsdl2java tool to generate the client side stub classes.
    the wsdl which i was using was referring to the port http://localhost/hth/services/Client?wsdl
    i was running the wsdl2java tool on this wsdl to generate stubs. it was working fine.
    Now i have removed the client.wsdl from the default localhost port and
    want to keep it in some location like D:\wsdl\Client.wsdl so that i don't need to depend on the Application server everytime for the wsdl to be up all the time.
    when i run the wsdl2java command on this location i get the following error.
    org.xml.sax.SAXException: Fatal Error: URI=file:///D:/wsdl/Client.wsdl Line=1: The processing instruction target matching "[xX][mM][lL]" is not allowed.
         at org.apache.axis.utils.XMLUtils$ParserErrorHandler.fatalError(XMLUtils.java:723)
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:218)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
         at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
         at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPIData(XMLScanner.java:689)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanPIData(XMLDocumentFragmentScannerImpl.java:750)
         at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanPI(XMLScanner.java:664)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:845)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
         at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
         at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
         at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)
         at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:420)
         at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:482)
         at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         at java.lang.Thread.run(Thread.java:595)
    Please let me know what is the problem here and how can i resolve this issue.
    here is bit of the sample client.wsdl
    <?xml version="1.0" encoding="UTF-8" ?>
    - <wsdl:definitions targetNamespace="D:\wsdl\Client.wsdl" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="D:\wsdl\Client.wsdl" xmlns:intf="D:\wsdl\Client.wsdl" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="D:\wsdl\Client.wsdl" xmlns:tns2="http://client.hth.march.com" xmlns:tns3="http://exception.hth.march.com" xmlns:tns4="http://equipment.hth.march.com" xmlns:tns5="http://equipment.ws.hth.march.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <!--
    WSDL created by Apache Axis version: 1.3
    Built on Oct 05, 2005 (05:23:37 EDT)
    -->
    - <wsdl:types>
    - <schema targetNamespace="D:\wsdl\Client.wsdl" xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://equipment.ws.hth.march.com" />
    <import namespace="http://xml.apache.org/xml-soap" />
    <import namespace="http://exception.hth.march.com" />
    <import namespace="http://client.hth.march.com" />
    <import namespace="http://equipment.hth.march.com" />
    <import namespace="http://localhost/hth/services/Client" />
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
    - <complexType name="HTHBaseDTO">
    - <sequence>
    <element name="md5Sum" nillable="true" type="xsd:string" />
    <element name="primaryKey" nillable="true" type="xsd:integer" />
    </sequence>
    </complexType>
    - <complexType name="VitalThresholdEnum">
    - <sequence>
    <element name="labelKey" nillable="true" type="xsd:string" />
    <element name="pk" nillable="true" type="xsd:short" />
    </sequence>
    </complexType>
    - <complexType name="VitalThresholdDTO">
    - <complexContent>
    - <extension base="tns1:HTHBaseDTO">
    - <sequence>
    <element name="categoryPk" nillable="true" type="xsd:short" />
    <element name="clientCarePlanPk" nillable="true" type="xsd:long" />
    <element name="clientPk" nillable="true" type="xsd:integer" />
    <element name="clientVitalPrescriptionPk" nillable="true" type="xsd:integer" />
    <element name="statusPk" nillable="true" type="xsd:short" />
    <element name="syncStatusPk" nillable="true" type="xsd:short" />
    <element name="thresholdType" nillable="true" type="tns1:VitalThresholdEnum" />
    <element name="thresholdValue" nillable="true" type="xsd:double" />
    <element name="unitTy
    hoping for positive replies from your side.
    Thanks & regards
    Vikram K

    So what was the problem? I am getting:
    error: invalid element "{http://java.sun.com/jax-rpc-ri/xrpcc-config}configuration" in configuration file (line 3)
    and I copied my config.xml from an example on xrpcc site!

  • Web Services - PHP client

    Hi,
    I'm trying to connect a php script using NuSOAP to a web service implemented with Netbeans 5.5 and runnig on Tomcat 5.5.20
    The web-service provider:
    package server;
    import javax.jws.WebMethod;
    import javax.jws.WebParam;
    import javax.jws.WebService;
    @WebService()
    public class NewWebService {
    @WebMethod
    public String getUserName(@WebParam(name = "id") String id) {
    return "Hi Number "+id+"!";
    the php client:
    require_once('nusoap.php');
    $wsdl="http://192.168.0.1:8080/Server/NewWebService?wsdl";
    $client=new soapclient($wsdl, 'wsdl');
    $param = array('id' => $_POST['id']);
    print_r($client->call('getUserName', $param));
    Netbeans generates this WSDL:
    <?xml version="1.0" encoding="UTF-8"?><definitions xmlns:tns="http://server/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server/" name="NewWebServiceService">
    <types>
    <xsd:schema>
    <xsd:import namespace="http://server/" schemaLocation="http://server/Server/NewWebService?xsd=1"></xsd:import>
    </xsd:schema>
    </types>
    <message name="getUserName">
    <part element="tns:getUserName" name="parameters"></part>
    </message>
    <message name="getUserNameResponse">
    <part element="tns:getUserNameResponse" name="parameters"></part>
    </message>
    <portType name="NewWebService">
    <operation name="getUserName">
    <input message="tns:getUserName"></input>
    <output message="tns:getUserNameResponse"></output>
    </operation>
    </portType>
    <binding type="tns:NewWebService" name="NewWebServicePortBinding">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"></soap:binding>
    <operation name="getUserName">
    <soap:operation soapAction=""></soap:operation>
    <input>
    <soap:body use="literal"></soap:body>
    </input>
    <output>
    <soap:body use="literal"></soap:body>
    </output>
    </operation>
    </binding>
    <service name="NewWebServiceService">
    <port binding="tns:NewWebServicePortBinding" name="NewWebServicePort">
    <soap:address location="http://192.168.0.1:8080/Server/NewWebService"></soap:address>
    </port>
    </service>
    </definitions>
    PHP returns an array that, when printed, looks like this:
    Array ( [faultcode] => soapenv:Client [faultstring] => Cannot find the dispatch method )
    Can anyone help me?

    Try saving the wsdl to a file and then remove all schemaLocation=xxx. I have not tried nusoap, but that works for the stand SoapClient.
    $ini = ini_set("soap.wsdl_cache_enabled","0");
    $url = 'test.wsdl'; # in same directory as script
    try {
    $client = new SoapClient($url,
    array(
    "trace" => 1,
    "exceptions" => 1));
    # print_r($client->__getFunctions());
    } catch (SoapFault $e) {
    print("SOAP Fault: faultcode: ".$e->faultcode." faultstring: ".$e->faultstring);
    print "<BR><BR>Error: SOAP failure\n";
    return;
    $result = $client->getMyFunction('xyz');
    print_r($result);

  • How to get OSB to stop appending port # in the endpoint of a published WSDL

    This is the closest thread I could find to my issue, but still is not quite what I am looking for: How to get ip number in WSDL instead of host name? I have an OSB server behind a VIP, and I am publishing a proxy service for an external client to call. The VIP only accepts connections over SSL/https. OSB only hosts services on http/port 80, and the VIP handles the connectivity and security between them.
    I wrote a wsdl by hand, set my endpoint to the VIP address (https), created the proxy service, and deployed to OSB. I can test the service all day in SoapUI by calling the VIP, so far so good. However, when the client calls https://VIP/myService/?wsdl, he sees the wsdl's endpoint populated as http://VIP/myService:80.
    How do I stop OSB from appending :80 to the endpoint in the wsdl? This makes it unusable for any client caller to generate code by calling ?wsdl, so it forces us to export the wsdl and all schema files and provide to clients by hand. What configuration setting can we change that will fix this behavior?

    vladodias wrote:
    OSB only hosts services on http/port 80...You can change OSB to host on any port you want and can also configure security...
    http://docs.oracle.com/cd/E28280_01/dev.1111/e15866/model.htm
    http://docs.oracle.com/cd/E28280_01/web.1111/e13707/ssl.htm#i1200848
    appending :80 to the endpoint in the wsdl ... makes it unusable for any client caller to generate code by calling ?wsdl
    I should have mentioned that :80 was an external constraint, so it was not an option to change this portion of the OSB configuration...
    Most wsdl clients should be able to call a wsdl from any port as well... The presence of :80 shouldn't make any difference... So, I can't quite understand that either...The point is to be able to provide a framework to clients that needs as few settings overridden as possible, so we'd like the published endpoint to actually match the true endpoint that we would expect a client to call.

  • Portal Service from wsdl testing problem

    Hi all,I use Developer Studio to generate sap portal wsdl client,when I finished generating,I want to do test.But it throws the Exception like that
    java.lang.IllegalStateException: Not able to initialize Web Service configuration for service TPOStatusService#
    com.sapportals.portal.prt.service.soap.mapping.SpecializedRegistry.initSerializersXML(SpecializedRegistry.java:601)
    com.sapportals.portal.prt.service.soap.mapping.SpecializedRegistry.initXMLBased(SpecializedRegistry.java:477)
    com.sapportals.portal.prt.service.soap.SOAPServiceManager.getSpecializedRegistry(SOAPServiceManager.java:321)
    com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:181)
    com.ilog.pct.tpo.proxy.TPOService.getProblemInfo(TPOService.java:168     at com.ilog.pct.tpo.pages.KpiPage$KpiPageDynPage.doProcessAfterInput(KpiPage.java:48)
    I don't know what's the problem.Can anyone help me to solve this problem?
    The followings is my wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://ws.tpo.ilog.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://ws.tpo.ilog.com" xmlns:intf="http://ws.tpo.ilog.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--WSDL created by Apache Axis version: 1.3
    Built on Oct 05, 2005 (05:23:37 EDT)-->
    <wsdl:types>
      <schema elementFormDefault="qualified" targetNamespace="http://ws.tpo.ilog.com" xmlns="http://www.w3.org/2001/XMLSchema">
       <element name="getProblemInfo">
        <complexType>
         <sequence>
          <element name="name" type="xsd:string"/>
         </sequence>
        </complexType>
       </element>
       <element name="getProblemInfoResponse">
        <complexType>
         <sequence>
          <element name="getProblemInfoReturn" type="impl:ProblemInfo"/>
         </sequence>
        </complexType>
       </element>
       <simpleType name="ProcessStatus">
        <restriction base="xsd:string">
         <enumeration value="1"/>
         <enumeration value="2"/>
         <enumeration value="3"/>
        </restriction>
       </simpleType>
       <complexType name="Vehicle">
        <sequence>
         <element name="cost" type="xsd:double"/>
         <element name="count" type="xsd:int"/>
         <element name="fixcost" type="xsd:double"/>
         <element name="name" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <complexType name="ArrayOfVehicle">
        <sequence>
         <element maxOccurs="unbounded" minOccurs="0" name="item" type="impl:Vehicle"/>
        </sequence>
       </complexType>
       <complexType name="ProblemInfo">
        <sequence>
         <element name="numbervehicles" type="xsd:int"/>
         <element name="numbervisit" type="xsd:int"/>
         <element name="processStatus" nillable="true" type="impl:ProcessStatus"/>
         <element name="shipvisit" type="xsd:int"/>
         <element name="total" type="xsd:double"/>
         <element name="vehicle" nillable="true" type="impl:ArrayOfVehicle"/>
        </sequence>
       </complexType>
       <complexType name="SvcException">
        <sequence>
         <element name="errorMsg" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <element name="fault" type="impl:SvcException"/>
      </schema>
    </wsdl:types>
       <wsdl:message name="getProblemInfoResponse">
          <wsdl:part element="impl:getProblemInfoResponse" name="parameters"/>
       </wsdl:message>
       <wsdl:message name="getProblemInfoRequest">
          <wsdl:part element="impl:getProblemInfo" name="parameters"/>
       </wsdl:message>
       <wsdl:message name="SvcException">
          <wsdl:part element="impl:fault" name="fault"/>
       </wsdl:message>
       <wsdl:portType name="TPOProcessSvc">
          <wsdl:operation name="getProblemInfo">
             <wsdl:input message="impl:getProblemInfoRequest" name="getProblemInfoRequest"/>
             <wsdl:output message="impl:getProblemInfoResponse" name="getProblemInfoResponse"/>
             <wsdl:fault message="impl:SvcException" name="SvcException"/>
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:binding name="TPOProcessSvcSoapBinding" type="impl:TPOProcessSvc">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getProblemInfo">
             <wsdlsoap:operation soapAction=""/>
             <wsdl:input name="getProblemInfoRequest">
                <wsdlsoap:body use="literal"/>
             </wsdl:input>
             <wsdl:output name="getProblemInfoResponse">
                <wsdlsoap:body use="literal"/>
             </wsdl:output>
             <wsdl:fault name="SvcException">
                <wsdlsoap:fault name="SvcException" use="literal"/>
             </wsdl:fault>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:service name="TPOProcessSvcService">
          <wsdl:port binding="impl:TPOProcessSvcSoapBinding" name="TPOProcessSvc">
             <wsdlsoap:address location="http://localhost:8080/tpo-web/services/TPOProcessSvc"/>
          </wsdl:port>
       </wsdl:service>
    </wsdl:definitions>

    Your installation for SAP JCO is not correct. Download the SAP JCO from service.sap.com and install it on your computer as the installation guide says.
       The above error is due to missing file librfc32.dll. If you are using windows operating system. Put the dll files in windows/system32 directory. thank you.
    Read the following thread. this should definitely solve your problem.
    https://forums.sdn.sap.com/profile.jspa?userID=608260
    PS: reward points if this hepls. thank you
    Message was edited by: Prakash  Singh

  • How to invoke a proxy service from a java client

    Hi all,
    how could I invoke a proxy service from a java client ?
    The proxy service type is 'any xml service' with http protocol.
    For a proxy with web service type I can export the related WSDL and generate the java client source.
    With 'any xml service' there is no associated wsdl and I'm wondering how to do that.
    Thanks
    ferp

    Hi Ferp,
    I used ClientGEN to generate client files from WSDL deployed in ALSB. You can also use Axis for client file generation.
    You need to know the WSDL URL. Generate Client files from WSDL URL.
    Sample ANT Script
    <project name="simple-web" default="mytask" basedir=".">
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" classpath="C:\bea92\weblogic92\server\lib\weblogic.jar"/>
    <target name="mytask" description="Generate web service client">
              <clientgen wsdl="http://<hostname>:<port>/URL?WSDL"
         destDir="src"
         packageName="com.client.mytask"
         classpath="${java.class.path}" />
         </target>
    </project>
    Use the following JAVA Code,
    try {
         ActivationService service = new ActivationService_Impl("http://<hostname>:<port>/url?WSDL");
    client = service.getActivationServicePort();
    } catch (Exception ex) {
    // Handle Exception
    client.activateNumber();
    Let me know if you need any more information.
    Thanks,
    Suman.

  • Netbeans and WSDL file location

    Hello,
    I'm new to web services and the Netbeans Web Services client wizard. I'm creating a simple web app that calls a 3rd party web service. I'm able to use Netbean's client wizard to create a ws client (stub code) from a local WSDL file. When I deploy the web app on my production server I get a javax.xml.ws.WebServiceException: java.io.FileNotFoundException when I create a new instance of the web service. This is not surprising since the production system does not have a local copy of the WSDL file at the exact path as on my dev system. I noticed the wizard seemed to have copied the WSDL file to WEB-INF\wsdl\client\ so I figured that's the file that would be used, but when I looked at the stub code it seems to have the path to my local WSDL hard coded in it. What's the correct way for deploying a web service client that is generated from a local WSDL file? I know there is a version of the Service constructor that allows you to specify a URL (and QName), but I'd rather not take this route unless it's what's supposed to be used.
    TIA

    We are running into the same problem. Has anyone found any information on deploying Web Service clients generated from a local WSDL?

Maybe you are looking for

  • File adapter not activating

    Hi. I have a frustrating problem. I set up a sender file adapter.However even after activating the adapter it does not show up in the adapter monitor.I can see a entry for file but no lights(Green or Red).The XI file adapter service is activated in t

  • Journal Detail Report in XL Reporter

    Hi I am trying to get journal details into a xl report. on the SBODemoUS it is working 100% but on any database with segmentised gl-accounts it doesn't return anything. I have even tested with the sample report from SAP "GL Accounts Posting Details.i

  • Cost Element with Cost center in column in one report

    Hello experts, Kindly, can you help me to create a report where I can see for each cost center all the cost element balance related. B. R F Tay

  • Mail user authentication failure

    My site has been suffering from a problem with access from Macs running Mail to POP3 mailboxes hosted on Snow Leopard server mail from at least 10.6.3 upwards (including the latest build of 10.6.5). It manifests itself as the notorious failed connect

  • Master data Load from Oracle table

    Hi, My master data comes from an Oracle table. The table has both attributes and texts combined. How do I load the Master data into the text and attribute info objects thru Direct Upload of Master Data? Is it necessary to go in for Flexible Upload in