Cannot acces usernametoken in web service handler

I am using wsse usernametoken security standard. I cannot access the usernametoken infomarion in the web services handler. The whole header is blank. Anyone have this situation ?

I am using wsse usernametoken security standard. I cannot access the usernametoken infomarion in the web services handler. The whole header is blank. Anyone have this situation ?

Similar Messages

  • Web service handler could not called in client web service

    Hi All,
    I have two web service ServiceA & ServiceB and both implemented in weblogic.
    The ServiceA is SSL enable and protocol is https which is not published by me.
    The ServieB is my web service(wls8.1) and act as client for ServiceA.
    My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
    My service file:
    import java.util.ArrayList;
    import java.util.HashMap;
    import java.util.Iterator;
    import java.util.List;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.HandlerRegistry;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import weblogic.webservice.client.SSLAdapterFactory;
    import weblogic.webservice.client.WLSSLAdapter;
    public class HelloService {
    String wsdl = "https://188.122.123.23/RemoetService?WSDL";
    static {
    SSLAdapterFactory factory = SSLAdapterFactory.getDefaultFactory();
    WLSSLAdapter adapter = (WLSSLAdapter) factory.getSSLAdapter();
    adapter.setTrustedCertificatesFile("D:\\lib\\certs
    cacerts");
    factory.setDefaultAdapter(adapter);
    System.setProperty("weblogic.xml.encryption.verbose","true");
    System.setProperty("weblogic.xml.signature.verbose","true");
    System.setProperty("weblogic.webservice.verbose","true");
    public String sayHello(String user) {
    RemoteService_Impl service = new RemoteService_Impl(wsdl);
    RemotePortType port = service.getRemoteServicePort1();
    String namespace = service.getServiceName()
    .getNamespaceURI();
    QName portName = new QName(namespace,
    "RemoteServicePortType");
    HandlerRegistry reg = service.getHandlerRegistry();
    List handlerList = new ArrayList();
    Map map = new HashMap();
    map.put("Username", "user1");
    map.put("Password", "pwd1");
    HandlerInfo info = new HandlerInfo();
    info.setHandlerClass(WSClientHandler .class);
    info.setHandlerConfig(map);
    handlerList.add(info);
    reg.setHandlerChain(portName,(List)handlerList);
    RemoteServiceResponse = port.callMe(name);
    My Handler file:
    package com.test;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.Handler;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.MessageContext;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import javax.xml.soap.Name;
    import javax.xml.soap.SOAPElement;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPException;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.soap.SOAPHeaderElement;
    public class WSClientHandler implements Handler {
    private HandlerInfo handlerInfo;
    public WSClientAuthenticateHandler(){}
    public void init(HandlerInfo hi) {
    System.out.println("Handler init");
    handlerInfo = hi;
    public void destroy() {
    System.out.println("Handler destroy method called");
    handlerInfo = null;
    public QName[] getHeaders() {
    System.out.println("Handler Header method called");
    try {
    Map map = handlerInfo.getHandlerConfig();
    QName[] headers = handlerInfo.getHeaders();
    System.out.println(" Config :"+map);
    for(int i=0;i<headers.length;i++) {
    System.out.println(headers.getLocalPart()+" "+
    headers.toString()+" "+headers.getNamespaceURI());
    }catch(Exception e) {
    e.printStackTrace();
    return handlerInfo.getHeaders();
    public boolean handleRequest(MessageContext mc) {
    SOAPMessageContext smc = (SOAPMessageContext) mc;
    System.out.println("Calling handler class.....................");
    try {
    SOAPEnvelope se = smc.getMessage().getSOAPPart().getEnvelope();
    System.out.println("Calling handler class.....................");
    SOAPHeader soapHeader = se.getHeader();
    Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
    SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
    SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
    element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
    element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
    System.out.println("Calling handler class.....................");
    System.out.println("** Request: \n "se.toString()"\n");
    }catch(SOAPException e) {
    e.printStackTrace();
    return true;
    /** * Specifies that the SOAP response message be logged to a
    * log file before the
    * * message is sent back to the client application
    * that invoked the Web service.
    public boolean handleResponse(MessageContext mc) {
    System.out.println("Handler Response method called");
    SOAPMessageContext messageContext = (SOAPMessageContext) mc;
    System.out.println("** Response: \n"messageContext.getMessage().toString()"\n");
    return true;
    /** * Specifies that a message be logged to the log file if a SOAP fault is
    * * thrown by the Handler instance.
    public boolean handleFault(MessageContext mc) {
    SOAPMessageContext messageContext = (SOAPMessageContext) mc;
    System.out.println("** Fault: \n"messageContext.getMessage().toString()"\n");
    return true;
    Please need help here.
    Thanks in Advance,
    pps

    I have tested static client calling using handler simple above service and found the issues.
    QName portName = new QName(namespace,
    "*RemoteServicePortType*");
    The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
    <?xml version="1.0"; encoding="UTF-8"?>
    <definitions name="HelloService"
    targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <message name="SayHelloRequest">
    <part name="firstName" type="xsd:string"/>
    </message>
    <message name="SayHelloResponse">
    <part name="greeting" type="xsd:string"/>
    </message>
    *<portType name="RemoteServicePortType">*
    <operation name="sayHello">
    <input message="tns:SayHelloRequest"/>
    <output message="tns:SayHelloResponse"/>
    </operation>
    </portType>
    <binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
    <soap:binding style="rpc"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="sayHello">
    <soap:operation soapAction="sayHello"/>
    <input>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </input>
    <output>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </output>
    </operation>
    </binding>
    <service name="Hello_Service">
    <port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">
    <soap:address
    location="http://host1:8080/soap/servlet/rpcrouter"/>
    </port>
    <port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">
    <soap:address
    location="http://host2:8080/soap/servlet/rpcrouter"/>
    </port>
    <port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">
    <soap:address
    location="http://host3:8080/soap/servlet/rpcrouter"/>
    </port>
    <port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">
    <soap:address
    location="http://host4:8080/soap/servlet/rpcrouter"/>
    </port>
    </service>
    </definitions>
    From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
    even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
    Please guide me here how i specify correct portname which can call Handler class also.
    Thanks in advance,
    pps

  • Web service handler could not registered/called in client web service

    Hi Expert,
    I have two web service ServiceA & ServiceB and both implemented in weblogic.
    The ServiceA is SSL enable and protocol is https which is not published by me.
    The ServieB is my web service(wls8.1) and act as client for ServiceA.
    My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
    My service file:
    import java.util.ArrayList;
    import java.util.HashMap;
    import java.util.Iterator;
    import java.util.List;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.HandlerRegistry;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import weblogic.webservice.client.SSLAdapterFactory;
    import weblogic.webservice.client.WLSSLAdapter;
    public class HelloService {
    String wsdl = "https://188.122.123.23/RemoetService?WSDL";
    static     {
              SSLAdapterFactory factory =                SSLAdapterFactory.getDefaultFactory();
              WLSSLAdapter adapter = (WLSSLAdapter)     factory.getSSLAdapter();
              adapter.setTrustedCertificatesFile("D:\\lib\\certs\\cacerts");
              factory.setDefaultAdapter(adapter);
              System.setProperty("weblogic.xml.encryption.verbose","true");
              System.setProperty("weblogic.xml.signature.verbose","true");
              System.setProperty("weblogic.webservice.verbose","true");
         public String sayHello(String user) {
              RemoteService_Impl service = new RemoteService_Impl(wsdl);
              RemotePortType port = service.getRemoteServicePort1();
              String namespace = service.getServiceName()
                        .getNamespaceURI();
              QName portName = new QName(namespace,
                        "RemoteServicePortType");
              HandlerRegistry reg = service.getHandlerRegistry();
              List handlerList = new ArrayList();
              Map map = new HashMap();
              map.put("Username", "user1");
              map.put("Password", "pwd1");
              HandlerInfo info = new HandlerInfo();
              info.setHandlerClass(WSClientHandler .class);
              info.setHandlerConfig(map);
              handlerList.add(info);
              reg.setHandlerChain(portName,(List)handlerList);
              RemoteServiceResponse = port.callMe(name);
    My Handler Class:
    package com.test;
    import java.util.Map;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.Handler;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.MessageContext;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    import javax.xml.soap.Name;
    import javax.xml.soap.SOAPElement;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPException;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.soap.SOAPHeaderElement;
    public class WSClientHandler implements Handler {
         private HandlerInfo handlerInfo;
         public WSClientAuthenticateHandler(){}
         public void init(HandlerInfo hi) {   
              System.out.println("Handler init");
              handlerInfo = hi;
         public void destroy() {
              System.out.println("Handler destroy method called");
              handlerInfo = null;
         public QName[] getHeaders() {
              System.out.println("Handler Header method called");
              try     {
                   Map map = handlerInfo.getHandlerConfig();
                   QName[] headers = handlerInfo.getHeaders();
                   System.out.println(" Config :"+map);
                   for(int i=0;i<headers.length;i++)     {
                        System.out.println(headers.getLocalPart()+" "+
                        headers[i].toString()+" "+headers[i].getNamespaceURI());
              }catch(Exception e)     {
                   e.printStackTrace();
              return handlerInfo.getHeaders();
         public boolean handleRequest(MessageContext mc) {   
              SOAPMessageContext smc = (SOAPMessageContext) mc;
              System.out.println("Calling handler class.....................");
              try     {
              SOAPEnvelope se =      smc.getMessage().getSOAPPart().getEnvelope();
              System.out.println("Calling handler class.....................");
         SOAPHeader soapHeader = se.getHeader();
         Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
         SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
         SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
         element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
         element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
         System.out.println("Calling handler class.....................");
                   System.out.println("** Request: \n "+se.toString()+"\n");
              }catch(SOAPException e)     {
                   e.printStackTrace();
              return true;
         /** * Specifies that the SOAP response message be logged to a
         * log file before the
         * * message is sent back to the client application
         * that invoked the Web service.
         public boolean handleResponse(MessageContext mc) {  
              System.out.println("Handler Response method called");
              SOAPMessageContext messageContext = (SOAPMessageContext) mc;
              System.out.println("** Response: \n"+messageContext.getMessage().toString()+"\n");
              return true;
         /** * Specifies that a message be logged to the log file if a SOAP fault is
         * * thrown by the Handler instance.
         public boolean handleFault(MessageContext mc) {   
              SOAPMessageContext messageContext = (SOAPMessageContext) mc;
              System.out.println("** Fault: \n"+messageContext.getMessage().toString()+"\n");
              return true;
    Please need help here.
    Thanks in Advance,
    pps

    I have tested static client calling using handler simple above service and found the issues.
    QName portName = new QName(namespace,
    *"RemoteServicePortType");*
    The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
    <?xml version="1.0"; encoding="UTF-8"?>
    <definitions name="HelloService"
    targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <message name="SayHelloRequest">
    <part name="firstName" type="xsd:string"/>
    </message>
    <message name="SayHelloResponse">
    <part name="greeting" type="xsd:string"/>
    </message>
    <portType name="*RemoteServicePortType*">
    <operation name="sayHello">
    <input message="tns:SayHelloRequest"/>
    <output message="tns:SayHelloResponse"/>
    </operation>
    </portType>
    <binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
    <soap:binding style="rpc"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="sayHello">
    <soap:operation soapAction="sayHello"/>
    <input>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </input>
    <output>
    <soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    namespace="urn:examples:helloservice"
    use="encoded"/>
    </output>
    </operation>
    </binding>
    <service name="Hello_Service">
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">+
    +<soap:address+
    location="http://host1:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">+
    +<soap:address+
    location="http://host2:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">+
    +<soap:address+
    location="http://host3:8080/soap/servlet/rpcrouter"/>
    +</port>+
    +<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">+
    +<soap:address+
    location="http://host4:8080/soap/servlet/rpcrouter"/>
    +</port>+
    </service>
    </definitions>
    From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
    even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
    Please guide me here how i specify correct portname which can call Handler class also.
    Thanks in advance,
    pps

  • How to write a Web service Handler without modifying the Web service code

    Hi,
    How can I write a SOAPHandler without modifying the Web service code. I want to add a generic handler which will take care of SOAPHeader for all the webmethods. To add a handler is it necessary to modify the web service code?

    You will find answer in [implementing_handlers_using_jaxws_2|http://blogs.sun.com/sdimilla/entry/implementing_handlers_using_jaxws_2]

  • Installing web service handler

    is there a way of programmatically deploying a handler onto a web
    service operation?
    i looked at jax-rpc HandlerRegistry but when i set a handler chain, it
    did not do anything. is this aupposed to set the handler chain on the
    server so all future calls will use the handler?
    i would like to do this instead of defining everything at deploy time in
    the web-services.xml file.

    I think you can use oracle web services manager for this. I can't speak from personal experience but from what I've heard I think this is the preferred approach for dealing with secured web services.

  • How my client can acces to my web Services??

    We want buy Oracle9iAS and we want know How our clients can access aour web services? They need some special software? or just need to send us a XML?
    Thanks

    As long as they can send standard XML based SOAP messages, Oracle can handle it. Interoperability based on standards is critical for the team building Web services into the Oracle environment.
    Backing that up, here is some pointers. Oracle belongs to both the Web Services Interoperability (WS-I) group (actually was a founding member along with IBM and Microsoft - http://www.ws-i.org) and SOAPBuilders (which is an ad-hoc consortium of several dozen vendors working on interoperability - http://ws-interop.oracle.com/soapbuilder/). One of our roles on the WS-I team is working on building a reference implementation of the WS-I Basic profile (specific versions of SOAP, WSDL and UDDI) which will be used to show interoperability amongst vendors in the WS-I.
    If you download the developer preview of Oracle9iAS Containers for J2EE (see: http://otn.oracle.com/tech/java/oc4j/content.html) you will see it includes the SOAPBuilders interoperability test showing this so you can test it out yourself.
    To see which standards groups Oracle belongs to, check out this page - in the Java space we participate in over 68 Java Specification Requests and more every day - but we also belong to W3C, OASIS and dozens of other standards groups and take that participation very seriously: http://otn.oracle.com/tech/xml/htdocs/standard.html
    Finally, to see how your partners can test in an Oracle Web services environment independent of any special software, check out the latest demo put up a few days ago showing the built in tester that comes with any Web service published on Oracle9iAS - you get a Web page which lets you pass in parameters and try the Web service out on the fly. This tutorial happens to be publishing PL/SQL as a Web service but the same applies if you publish an EJB, JMS queue, or Java class as a Web service (see step 24):
    http://otn.oracle.com/tech/webservices/htdocs/series/plsql/content.html
    Hope this is a start for you.
    Mike.

  • Cannot enable eprint through Web Services on my mfp m127fn

    Printer - MFP M127fn
    I have registered with HP Connect. Asks me to add my printer through Add Device. I need to enter Claim Code. I am able to connect to the URL displayed in my Configuration Page.
    I click on Web Services Tab to enable Eprint.
    It never connects to enable Eprint and to print out the Information Page that contains the Claim Code.
    OS - Windows 7 Professional
    Linksys Router.

    Hi @Mukhi,
    Welcome to the HP Support Forums.  I see that you are unable to setup the ePrint feature of your Laserjet M127fn printer.
    To better assist you, would you please provide some additional information?
    Is the printer connected to your router using an ethernet cable? This printer only supports a USB cable connection or an ethernet connection.  For ePrint to work the printer must be connected using an ethernet connection. 
    Are you getting any error messages at all?
    Are you able to post a screen shot of your configuration page? If you are unsure how to do this please reference the How to take and post a screenshot on HP Support Forum post by @Daniel_Potyrala
    Thank you.
    Regards,
    Happytohelp01
    Please click on the Thumbs Up on the right to say “Thanks” for helping!
    Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
    I work on behalf of HP

  • OBIEE web services: Handling saved filters

    I was trying to call obiee web services to get report data. And I used ReportParams to pass the prompt values. But this was not working in case of saved filters in the report.
    Plz advice .....

    searching.gif is referred through CSS files, thus replace the searching.gif (under res\sk_oracle10\b_mozilla_4) with another custom created blank gif and name it as searching.gif....rename the original searching.gif to searching_original.gif for reference.
    caveat: This will affect your enterprise wide display.
    mark answers promptly.
    J
    -bifacts
    http://www.obinotes.com

  • JSF tutorial cannot run on Java Web Services Developer Pack v1.1

    Hi,
    I downloaded JSF Tutorial dated March 17, 2003. According to it, I need WSDP 1.0_01. However, that version is not available on Sun's site. I downloaded v 1.1 instead.
    When I ran http://localhost:8080/helloDuke/faces/greeting.jsp, I got the following exception. Help?
    Thomas
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException: Unable to parse file:no protocol: event-attributes.xml
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:183)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2349)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:376)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:518)
    at java.lang.Thread.run(Thread.java:536)

    After digging through various sources, I found in
    http://java.sun.com/j2ee/javaserverfaces/docs/ReleaseNotes.html
    which stated that
    "Due to a bug in JSTL 1.0, you must have the jstl.jar and standard.jar in your WEB-INF/lib directory of each webapp. It is not sufficient to place these jars in your tomcat/common/lib directory.
    Even after I've done that, still got
    java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
         at com.sun.faces.context.FacesContextImpl.setLocale(FacesContextImpl.java:211)

  • Creating a Web Service to handle flow between BPEL process and XML Gateway

    I am new to Web Services. I have never created one, yet I have the task of designing the following for a project.
    Any help as to what steps I need to take would be very very helpful. There is a lot of information on XML, SOA and WSDL out there that it can get very confusing, and sometimes you just need someone to point the way
    What I need to do is create a Custom Send and a Custom Receive Program (both web services) handle the message flow between an Enterprise BPEL processes and a Deployed XML Gateway.
    BPEL compresses this XML business object document (for faster transmission), and sends remotely to this Custom Receive web service, which in turn calls a decompress java program and then send the document to the XML gateway inbound web service.
    The Custom Send web service does just the opposite. It needs to take the business object document from XML gateway, call the compress java program and then send to the Enterprise BPEL.
    In a nutshell...these Custom Send/Receive Web services handle the message flow between the Enterprise BPEL process and the Deployed XML Gateway.
    What I need help on...
    -Creating this in JDeveloper- where do I get started?
    -How does a web service receive a compressed file sent to me via BPEL? Does it just sit there waiting for it?
    -Is this a synchronous or asynchronous design?
    -Will this be 2 web services (Send and Receive) or do I make 1 with 2 functionalities
    -How do I call the java compress/decompress program within the web service? (this java function is already created and ready to be called)
    -Is this decompressed business object file an XML schema and an XML message? Or just a message?
    -I need to send this to the XML Gateway Web Service to load. How does that work?
    -I have a Generic XML Gateway WSDL file...I assume I need to take all the info I get and map it to this template? Is this true? How do I do that?
    Like I said, any help would be appreciated. Links answers to my many questions would be fabulous.
    -Jason

    If you are talking about simple XML transformation of the SOAP payload between the client calling your service and the final destination of the message you are routing, the ESB approach may be a better fit.
    If you have more complex transformation in mind, with major processing and rework of the message in the intermediary, you may be better of with using the POJO approach. Write your service and embed a callout to the other service in your implementation. If the two services share the same Java Model, you may even be able to re-use the same Java Bean.
    To get SOAP Element instead of Java bean, you just need to use the noDataBinding option with either genProxy and topDownAssemble (or assemble). See the WS-Guide [1] for details. Chapter 18 will give you all the details about the different WSA command line parameters.
    Hope this helps,
    -Eric
    [1] http://download-west.oracle.com/docs/cd/B31017_01/web.1013/b28974/toc.htm

  • Envy 7645 Cannot connect to web services

    I have a new Envy 7645 that cannot connect to the web services.
    Things I have tried:
    Verified Internet access. The printers "Web Access Test Results" report shows "No problems found"
    Verified wireless connectivity by connecting to the printers Embeded Web Server
    I statically set the DNS to 8.8.8.8 (primary) and 8.8.4.4 (secondary)
    The IPv4 address was assigned via DHCP so I changed it to static (manually) assigned
    Re-verified wireless connectivity by connecting to the printers Embeded Web Server with the static IP
    Lots of printer reboots to make sure the changes took effect. (Have you tried turning it off and on again? Ha!) 
    Logged into the https://www.hpconnected.com website 
         The printer is registered under my devices tab
         The printer status is "offline"  (I assume this would change if the web services were working)
    Any help would be appreciated.
    This question was solved.
    View Solution.

    Hello treadwayl,
    Welcome to the HP Support Forums!
    Thanks for putting the time in to a very informative post about the ENVY 7645 not being able to connect to Web Services. When you attempt, what is the exact error or message?
    I would like to you try the DNS of: Primary DNS Server = 209.244.0.3 & Secondary DNS Server = 209.244.0.4
    Re-boot printer and router, then try again to connect. 
    Let me know the out come, cheers.
    JERENDS
    I work on behalf of HP
    Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

  • Cannot connect to web services HP 7525 printer

    It used to work fine. Now I jsut get the message "unable to connect to web services......" I've chcked and the printer is connected to wifi. I tried the solution posted " put IP address in a browser etc...... but when I do that in Exploer all I get is jiberish, no web page with the network buttons.

    Hello @JACKUSHNER,
    Welcome to the HP Forums!
    I understand you're receiving a message stating "unable to connect to web services" using the Photosmart 7520. I will do my best to assist you! I would start off by following this entire HP document on A Network Connected Printer Cannot Access Print Apps, Web Services, or ePrint.
    Please post your results, as I will be looking forward to hearing from you. Have a great night!
    I worked on behalf of HP.

  • Cannot enable web services to get printer onto ePrint

    Got a new Photosmart 7520 and got it onto our wireless network alright. But I cannot enable on the printer the web services (always jumps to automatic software updates and fails to connect; and hence cannot enable ePrint or web services.
    Also typing in the IP Address into my browser gives me only a blank page...
    What to do and where? on the printer or Mac (OSX 10.9)?
    Thanks for the help
      Max 

    Hi Max4Print,
    Thank you for the update. 
    Yes you should be able to ping the printer.  That is the best way to check the communication.  I have included wikiHow’s article on How to Ping an IP Address.  It has a section on how to do this on a Mac. I’m wondering if you have a guest network and if the printer is connected to that.  Typically when you can’t access the embedded web server it would indicate that one of the devices is showing connected when it isn’t.
    If the ping fails, I would recommend rerunning the wireless setup wizard from the front panel.  The instructions on how to do this can be found on page 48 of your User Guide in the section titled “To connect the product with the Wireless Setup Wizard”.   Once you have run the wireless setup wizard chose the option to print the report.
    Regards,
    Happytohelp01
    Please click on the Thumbs Up on the right to say “Thanks” for helping!
    Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
    I work on behalf of HP

  • Adobe Interactive Form / Web Service - Connection question

    Hi
    We have CRM 2007 and want to use Adobe Interactive forms for our sales managers to upload customer information when they're out in the field. Before they leave all information about the customer will be downloaded to an Adobe Interactive Form. The client sees the customer and then enters the information required to e.g. create a sales order. He has an Internet connection but is not neccessarily logged into CRM 2007. He is a registered user in CRM 2007.
    My question is: if we create the web services to send and receive data to the CRM 2007 system, does the sales manager have to be online and signed into the CRM system to upload the Adobe Interactive Forms back to the server, or does the web service handle this?
    Kind regards
    Declan

    Hello Declan,
    You can send the information captured in an SAP Interactive Form by Adobe to your CRM system in two ways based on the way in which your form is designed -
    1] By making a direct web service call : A typical use case is that the user fills out all the necessary fields in the form and simply clicks a submit button; on clicking, the particular web service is called and the input data is transferred to SAP CRM. It should be noted that the web service authorizations should be in place to enable this kind of usage.
    2] By utilizing SAP CRM via Email scenario : A typical use case here would be that the user fills out all the necessary fields in the form and simply clicks a submit via email button; on clicking, an email is composed with all the form input infomration added as an attachment. The user can then send this email to the SAP CRM system. It should be noted that SAP CRM via Email application should be setup on the SAP CRM system and the particular SAP CRM via Email service & web service should have proper authorizations.
    An interesting point to note here is that while scenario 1] would require the user to have just internet access for this to work, scenario 2] could work in a fashion such that if the user isn't having internet access, he/she could still fill out the forms thereby creating emails which would then reside in the outbox of the user's email client. Once the user is having internet acces, the email client would send these emails automatically, thereby achieving a different flavour of "offline functionality".
    Hope this info helps!
    Best regards,
    Sandeep.

  • Deployment Aborted (EJB and Web Services)

    Hello All.
    In SAP Netweaber Developer Studio I created a Project with an Entity EJB and another Sesion EJB.
    The Sesion Bean uses the Entity Bean (persistence). After this, it generate a Web Services.
    After building the project ejb and project EAP. Within the Project EAP I took file Persistent_EAP.ear and to make respective deploy on the Server, in the Deploy out View I get the message 'Deploy Aborted'.
    The log of the message say,
    ++Sep 30, 2011 5:43:05 PM  Info: - Starting deployment -++
    ++Sep 30, 2011 5:43:05 PM  Info: Error handling strategy: OnErrorStop++
    ++Sep 30, 2011 5:43:05 PM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop++
    Sep 30, 2011 5:43:05 PM  Info: Update strategy: UpdateAllVersions
    Sep 30, 2011 5:43:05 PM  Info: Starting deployment prerequisites:
    Sep 30, 2011 5:43:10 PM  Info: Loading selected archives...
    Sep 30, 2011 5:43:10 PM  Info: Loading archive 'C:\usr\sap\J2E\JC01\SDM\program\temp\temp38292Persistencia_Mod_EAP.ear'
    Sep 30, 2011 5:43:16 PM  Info: Selected archives successfully loaded.
    Sep 30, 2011 5:43:16 PM  Info: Actions per selected component:
    Sep 30, 2011 5:43:16 PM  Info: Update: Selected development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'1' updates currently deployed development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'0'.
    Sep 30, 2011 5:43:16 PM  Info: Ending deployment prerequisites. All items are correct.
    Sep 30, 2011 5:43:16 PM  Info: Saved current Engine state.
    Sep 30, 2011 5:43:16 PM  Info: Starting: Update: Selected development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'1' updates currently deployed development component 'Persistencia_Mod_EAP'/'sap.com'/'localhost'/'2011.09.30.16.03.19'/'0'.
    Sep 30, 2011 5:43:16 PM  Info: SDA to be deployed: C:\usr\sap\J2E\JC01\SDM\root\origin\sap.com\Persistencia_Mod_EAP\localhost\1\2011.09.30.16.03.19\temp38292Persistencia_Mod_EAP.ear
    Sep 30, 2011 5:43:16 PM  Info: Software type of SDA: J2EE
    Sep 30, 2011 5:43:16 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 30, 2011 5:46:13 PM  Info: Begin of log messages of the target system:
    11/09/30 17:43:16 -  ***********************************************************
    11/09/30 17:43:21 -  Start updating EAR file...
    11/09/30 17:43:21 -  start-up mode is lazy
    11/09/30 17:43:22 -  EAR file updated successfully for 922ms.
    11/09/30 17:43:22 -  Start updating...
    11/09/30 17:43:25 -  EAR file uploaded to server for 1594ms.
    11/09/30 17:46:13 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/Persistencia_Mod_EAP..
                         Reason: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/Persistencia_Mod_EAP. . Additional info: none; nested exception is:
                         +     java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/Persistencia_Mod_EAP. . Additional info: none+
    I don't know what is wrong, when say: Error occurred, trying to update web services for application...
    Could someone please help me?
    Thanks in advanced,
    Esther

    Dear Esther,
    This exception usually happens when the application is not packaged properly.
    It seems that the J2EE engine web services deployment processor is looking for a descriptor which is absent in the jar file.
    This could happen for instance if you forget to save all the modified files before rebuilding.
    Unfortunately I cannot tell you which web service descriptor is missing, without looking at the packaged application.
    Try the following:
    1) Regenerate your virtual interfaces
    2) Save all modified files
    3) Rebuild the application
    4) Deploy the application again.
    Best Regards,
    Abhishek

Maybe you are looking for