Spring Web service in Weblogic 10.0

Hi,
I have developed a spring webservice and it is running in tomcat 6.X but now I am trying to deploy that war file in weblogic 10.0 running on jdk5 and I end up with the error
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'payloadMapping' defined in ServletContext resource [WEB-INF/spring-ws-servlet.xml]: Cannot resolve reference to bean 'validatingInterceptor' while setting bean property 'interceptors' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validatingInterceptor' defined in ServletContext resource [WEB-INF/spring-ws-servlet.xml]: Error setting property values; nested exception is org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are:
PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'xsdSchema' threw exception; nested exception is org.springframework.xml.validation.XmlValidationException: Could not create Schema: SAX2 driver class weblogic.apache.xerces.parsers.SAXParser does not implement XMLReader; nested exception is java.lang.ClassCastException: weblogic.apache.xerces.parsers.SAXParser incompatible with org.xml.sax.XMLReader
So since some jars in weblogic is not supporting my application.
I added <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes> in weblogic.xml and I have all the jars in web-inf/lib folder.
Still It was not working, and according to a suggestion in Spring forum I added this argument in domain environment
JAVA_OPTIONS="-Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl"
But still I get the same error.
please help me to over come this issue.
thanks

Hi
To my surprise, When i asked my Server team to get me weblogic support, I got a response from them stating that weblogic will not support spring framework 2.5 and they sent me the link
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs100/100_over/overview.html#1131715
And asked me to downgrade my project to the supported version.
But I think it is not correct, I don't have information if really my local team contacted weblogic support, or they are just sending me this link based on the document they have.
But I don't understand why it is so hard to get this thing working. Is there many people facing this issue ?
Or every one using apache Axis2 or CFX for web service and spring webservice is not advised ?
Some time I don't know whom should be blamed.
Thanks

Similar Messages

  • Spring web-service application in weblogic 9.1

    Hi,
    Iam trying to port the sample application given with Spring Web Services download(It works great with tomcat) to Weblogic 9.1. There were some issues doing it. You can see the discussion here. [url http://forum.springframework.org/showthread.php?t=26205]
    I did that accordingly and Iam getting a [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:451)
            at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
            at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
            Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
            at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:759)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:724)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:387)
            Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
            at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.<init>(AxiomSoapMessageFactory.java:97)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            Truncated. see log file for complete stacktrace error.
    Look at this page for the settings i have done. [url http://forum.springframework.org/showthread.php?t=40051]
    Please help me resolve this issue.
    Thanks
    Vignesh

    Well, in the web.xml for the app we have it set up as BASIC authentication, and list the roles that are allowed at that particular site. In order to sign in, another app would have to set the authorization property in the URLConnection.
    The problem is, using AXIS to connect, I have no way to set this property in the connection, since it is wrapped up by axis. (Call)
    I have reached a potential solution of constructing the soap message with the client using means other than the AXIS API, which I am implementing now and praying it will work!
    Everything I have read suggests using SSL to connect to the web service, but I can't figure out how to set up SSL so that my host/axisweb directory needs HTTPS but host/ doesn't...
    Does this make sense? Any suggestions?

  • Invoking web service using Weblogic Workshop (JCX)

    Invoking web service using Weblogic Workshop
    Posted: 5 Jan 2005 23:31 PM Reply
    Hi,
    I have WSDL from which I have generated a web service control (.jcx) using Weblogic Workshop.
    I need to write a client which will invoke the web service using the control.
    Can someone help me on how to go about this ?
    BTW .. I also tried the clientgen route and tried to generated the proxy jar from the WSDL but wasn't successful because of a existing clientgen bug.
    Refer bug

    Hi,
    if the consumer of the webservice is a control-aware consumer ( pageflow, control, process ) simply drag the control to this consumer and the control variable is ready for use.
    if the consumer is not control-aware, try to generate a proxy using eg. the axis tool, or handcode your proxy class.
    links :
    how to use webservice control
    http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/conGettingStartedWithJavaControls.html
    axis
    http://ws.apache.org/axis/
    - Anders M.
    - Anders M.

  • Deploying a web service to WebLogic 7 - error with RemoteDispatcherBean

    Hi there,
    I have just created a web service through WebLogic Workshop. The web service can be tested through the workshop and it works fine
    I am trying now to deploy it to a development server, and I am having the following error:
    preparing application <appName> on mope
    Exception caught for task Activate application <appName> on mope: Prepare failed. Task Id = 1
    Module, AP_NotificationEJB.jar, reported error: Exception preparing module: EJBModule(AP_NotificationEJB.jar,status=NEW)
    Unable to deploy EJB: C:\bea\<deploymentPath>\.wlnotdelete\<appName>\AP_NotificationEJB.jar from AP_NotificationEJB.jar:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: weblogic.knex.bean.RemoteDispatcherBean
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:440)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfo(EJBDeployer.java:965)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1276)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:235)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1742)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:745)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:559)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1116)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:784)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
    Looking inside the EAR I generated (using jwsCompile), I can find several classes RemoteDispatchBean_bu6zup_....class but no RemoteDispatchBean.class file anywhere
    Am I doing anything wrong to generate the EAR file? Anything fancy I need to include to my jws file or any descriptor?
    Any idea or suggestion would be much appreciated
    Thank you,
    Miguel

    We have found a work around for that specific problem.
    We have included the whole knex library within our libs folder. Now we can deploy the Web services as a web application to the webLogic, The deployment returns successful, but any time we initiate the server, there is another ClassNotFoundException. This time the missing class is weblogic.knex.bean.DeploymentListener.
    The strange thing is that that specific class is part of the knex.jar library we have included within our libs folder ...
    It seems that the folder is not read from the server when starting, but it is read when executing the application.
    Any suggestion to this nonsense?
    Thanks,
    Miguel

  • Deployment of JSR-109 Web Services on Weblogic 11g (OAS migration)

    Hi.
    I'm being part of an ongoing migration effort from Oracle Application Server 10.1.3.5 to WebLogic 11g (10.3.6). Some of the OAS applications use old JSR-109 Web Services, where each service has the following components:
    - A SEI interface that extends java.rmi.Remote and declares the service methods, which throw java.rmi.RemoteException (e.g. ServiceSEI)
    - A service implementation POJO that implements the SEI interface (e.g. ServiceImpl)
    - A [Service]-config.xml file that declares the service and relates name, namespaces, packages, interface and implementation (e.g. Service-config.xml)
    - A declaration of the service implementation POJO as a servlet (with mapping) in web.xml (docs says it doesn't have to be technically a servlet)
    - A webservices.xml file that defines the service and references the mapping file.
    - A [Service]-mapping.xml file that defines the WS-Java mappings.
    All the artifacts look right according the old documentation:
    - Programming Web Services for WebLogic Server, Creating a J2EE Web Service Manually: http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html
    - Web Services for J2EE 1.0 Final Release Spec: http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    The Web Services work OK in OAS. When I try to deploy any of the application that contain one of that services to WebLogic, I get the following Exception:
    <BEA-101216> <Servlet: "WSServlet_Procesos" failed to preload on startup in Web application: "/webapp".
    java.lang.IllegalStateException: ClassNotFound co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:601)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:273)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:171)
    at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
    at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:705)
    at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201)
    at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54)
    at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:91)
    at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:372)
    at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:83)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    I obviously though the EAR package given to me was incomplete, lacking the ClassNotFound related class, but the package was OK, and is exactly the same that deploys without problems in OAS.
    The ClassNotFound related class is referenced in the <java-xml-type-mapping> element of the [Service]-mapping.xml file, e.g.:
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperationResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>result</java-variable-name>
    <xml-element-name>result</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I searched the OAs installation deployment dirs looking for the missing class and found it was present in a Jar called deployment-cache.jar. According OC4J related documentation, this Jar es auto-generated at deployment time.
    Weblogic 11g documentation says that kind of Web Services will continue to run, without any changes, on version 10.3.x of WebLogic Server because the associated Web services run time is still supported in this release, although it is deprecated and will be removed from the product in future releases (http://docs.oracle.com/cd/E21764_01/web.1111/e13760/upgrade.htm). I know the right estrategy is migrate the Web Services, but right now my client needs to deploy and use them as they are. I think WL recognizes my service since internally is calling a "Deploytime109MappingHelper" class.
    ¿Is there any way I can deploy that kind of services to Weblogic 11g? ¿I'm I missing some required step?
    As a workaround, I included the OAS generated deployment-cache.jar into the EAR to deploy in Weblogic 11g and the app deploys without errors, but I see this is not a nice solution.
    Any help would be much appreciated.
    Thanks,
    Esteban
    Edited by: salzo on Oct 30, 2012 9:54 AM
    Edited by: salzo on Oct 30, 2012 9:56 AM

    Hi. The [Service]-mapping.xml file is a standard "JAX-RPC mapping file" according the JSR-109 spec and WebLogic 9.2 doc ([1],[2]). That's the file that references the class. Here's a fragment:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Service/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Services/wsdl</namespaceURI>
    </package-mapping>
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperation</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>String_1</java-variable-name>
    <xml-element-name>String_1</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I'll take a look at the ant task.
    Thank you very much.
    [1]http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    [2]http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html

  • Not able to consume Spring web services form Apex.

    Hi all,
    I have written web services using Spring web services and i have tested them using SoapUi- web services testing tool. But when i try to consume the same using Apex, Apex fails to parse the Wsdl properly and invalid request and response elements are created.
    The request and response elements are in an different xsd and i have imported it in the wsdl.
    Problem: when Apex parses the wsdl, it fails to download the referenced xsd and hence fails to create the request and response elements properly.
    Questions: Can apex download an xsd through http? if yes, how do we enable apex to do it.
    What are the other options available.?
    I have pasted a extract from the wsdl below:
    <?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:schema="http://com/webservice" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://com/webservice">
    <wsdl:types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:import namespace="http://com/webservice" schemaLocation="../model/WebServiceModel.xsd"/></xsd:schema>
    </wsdl:types>
    Regards
    Anish

    Anish:
    Application Express will attempt to download external XSD references (version 3.0 or later), but I believe the problem with this particular reference is that the reference is relative:
    ../model/WebServiceModel.xsd
    Another option is to use the Manual Web references feature. You can use a tool like SOAPUI to get a properly formatted SOAP Envelope for the operation of the particular service you wish to interact with.
    http://download.oracle.com/docs/cd/E10513_01/doc/appdev.310/e10499/advnc.htm#BABCBBHJ (Creating a Web Service Manually)
    http://download.oracle.com/docs/cd/E10513_01/doc/appdev.310/e10497/web_serv.htm#CHDEFEGH
    Regards,
    Jason

  • How to Migrate OC4J EJB Web service to Weblogic

    Hello,
    We have a J2EE app developed under OC4J that needs to be migrated to weblogic 10.x. It uses web services mapped to EJB's with the oracle.j2ee.ws.SessionBeanWebService class, example setup:
    <servlet>
    <servlet-name>CreditCardManager</servlet-name>
    <servlet-class>oracle.j2ee.ws.SessionBeanWebService</servlet-class>
    <init-param>
    <param-name>jndi-name</param-name>
    <param-value>CreditCardManagerBean</param-value>
    </init-param>
    </servlet>
    Can someone point me to any docs on how to create the equivalent objects in Weblogic?
    Thanks,
    Leor

    Microsoft webservices uses HTTP sessions to maintain state. That means that the webservice sends a token to the client to be passed back on subsequent calls.
    Unfortunately, the webservice control in 8.1 doesn't know how to send the session token back to the MS webservice. The webservice control knows how to talk SOAP only. It doesn't know about session tokens. The reason for this is the different protocols available to transmit SOAP. Most of them are not HTTP session aware.
    Workshop webservices uses conversation ID's that are contained within the SOAP header to maintain state. That way, we don't have the dependency on the session state for maintaining state.
    The way to handle Microsoft's stateful webservice implementation is to create a custom webservice control that uses an HTTP client. Query the HTTP client for the session cookie. Store the session token and send it with subsequent calls to the MS webservice.
    Thanks,
    David Gorton
    Workshop Customer Centric Engineering

  • How to use call back and user session id based conversation with web service in weblogic 6.1 sp2 ?????????

    Hi, every one:
    Here's my question of my day - >>>
    I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K, and
    I got a web service up and running called Price Update web service through
    which user can pick up a price and push a deal to another web service
    called: deal service, the deal service will take the user deal and book the
    deal ( sending a JMS message to a Queue, a MD will pick up and do the work,
    then send the confirmation to another JMS Queue ), then the confirmation
    will be picked up and sent to another web service , called: User Deal
    Confirmation Service, here's the question:
    1. Since the client application is only allowed to see its own confirmed
    deals, how I can make the confirmed deal encrypted based on a server
    generated key or the session id that client application provides
    2. Now, I have 3 webservices: update, deal and confirm, each of them has a
    client.jar file available - from the client application point of view, do I
    need all these 3 client.jar, or I just need one of them ?????
    3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
    beta, you can do this easily in the workshop, in the second question above,
    I think I need some how relate the confirmation to the client conversation
    id ??
    thanks a lot for the input, have a nice day.
    regards,
    mark.

    Any comments ?
    mark
    "markhu" <[email protected]> wrote in message
    news:[email protected]..
    Hi, every one:
    Here's my question of my day - >>>
    I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K,and
    I got a web service up and running called Price Update web service through
    which user can pick up a price and push a deal to another web service
    called: deal service, the deal service will take the user deal and bookthe
    deal ( sending a JMS message to a Queue, a MD will pick up and do thework,
    then send the confirmation to another JMS Queue ), then the confirmation
    will be picked up and sent to another web service , called: User Deal
    Confirmation Service, here's the question:
    1. Since the client application is only allowed to see its own confirmed
    deals, how I can make the confirmed deal encrypted based on a server
    generated key or the session id that client application provides
    2. Now, I have 3 webservices: update, deal and confirm, each of them has a
    client.jar file available - from the client application point of view, doI
    need all these 3 client.jar, or I just need one of them ?????
    3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
    beta, you can do this easily in the workshop, in the second questionabove,
    I think I need some how relate the confirmation to the client conversation
    id ??
    thanks a lot for the input, have a nice day.
    regards,
    mark.

  • How to run a Spring Web service?

    Hi,
    I have to deploy a WAR with OAS 10.1.3.3. That WAR contains a Web service build on the Spring Fwk 2.0.6. It runs on Tomcat and Jetty without problems.
    I get an error when I try to call a Web service operation:
    Caused by: oracle.j2ee.ws.saaj.soap.SOAPVersionMismatchRuntimeException:
    Envelope namespace must be: http://schemas.xmlsoap.org/soap/envelope/ is http://trivadis.com/amexcoCard/schemas
         at oracle.j2ee.ws.saaj.soap.SOAPDoc.createRootElement(SOAPDoc.java:98)
         at oracle.j2ee.ws.saaj.soap.SOAPDoc.createNodeFromType(SOAPDoc.java:44)
         at oracle.j2ee.ws.saaj.soap.SOAPPartImpl$SOAPPartDocument.createNodeFromType(SOAPPartImpl.java:593)
         at oracle.xml.parser.v2.XMLDocument.createElement(XMLDocument.java:2122)
         at oracle.xml.parser.v2.DocumentBuilder.startElement(DocumentBuilder.java:262)
         at oracle.xml.xslt.XSLEventHandler.reportStartElement(XSLEventHandler.java:267)
         at oracle.xml.xslt.XSLEventHandler.startElement(XSLEventHandler.java:389)
         at oracle.xml.xslt.XSLTContext.reportNode(XSLTContext.java:345)
         at oracle.xml.xslt.XSLTContext.reportNode(XSLTContext.java:368)
         at oracle.xml.xslt.XSLTContext.reportNode(XSLTContext.java:1303)
         at oracle.xml.xslt.XSLCopyOf.processAction(XSLCopyOf.java:141)
         at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
         at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
         at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
         at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
         at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
         at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
         at oracle.xml.xslt.XSLStylesheet.execute(XSLStylesheet.java:581)
         at oracle.xml.xslt.XSLStylesheet.execute(XSLStylesheet.java:548)
         at oracle.xml.xslt.XSLProcessor.processXSL(XSLProcessor.java:333)
         at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:437)
         ... 25 moreDuring deloyment I have changed the class loading. here is my orion-application.xml
    <orion-application ...>
    ...      <imported-shared-libraries>
                <import-shared-library name="Apache Commons Collection"/>
                <import-shared-library name="Backport java.util.concurrent"/>
                <import-shared-library name="JAXB"/>
                <remove-inherited name="soap"/>
          </imported-shared-libraries>
    </orion-application> I have tried many different configuration and excluded oracle.xml, WS related libs and so on, but I never managed to run a request on the Spring WS
    What else can I do?
    Any hints are welcome,
    Thanks, Markus

    Hi Jacco,
    What is the proper version of oracle.xml? I'm not sure that the Oracle XML Parser stuff is the root of my problems.
    Just another fact: When I removed all inherited libs during deployment, OAS can't deploy and start my Web service because of a NullPointerException:
    Operation failed with error:
    Unexpected exception parsing XML document from class path resource [context/applicationContext.xml];
    nested exception is javax.xml.parsers.FactoryConfigurationError:
    Provider oracle.xml.jaxp.JXDocumentBuilderFactory could not be instantiated:
    java.lang.NullPointerException Why does OAS still needs oracle.xml.jaxp.JXDocumentBuilderFactory??

  • Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

    Hi!
    We need to implement authentication using our own methods, and the authentication
    information is provided to the web service implementation in a basic authentication
    header. The problem is, that the servlet
    weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
    in
    wls 7.0.sp2, always attempts to perform authentication, if the header is present.
    Is there any way to circumvent this, because we want to implement authentication
    on our own?
    I already know two workarounds:
    The best would of course be to implement a custom security realm for our own
    authentication system. This is not an option, implementing an own security
    realm is overkill for this specific web service.
    The other way would be to route the requests by way of a custom servlet, which
    would
    remove the basic authentication header, and put the authentication info in custom
    headers, such as x-auth: <user:password>, or smthng similar, and after successful
    authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
    But still, I'd like to know if there is any way to tell bea's servlet to ignore
    the basic
    authentication header?
    Oh yeah, by the way, this is URGENT, as always. (really!! ;)
    Toni Nykanen

    Currently there is no option to turn off security check.
    I think you can use a servlet filter mapped to the URL
    of your service, instead of a proxy servlet?
    Regards,
    -manoj
    http://manojc.com
    "Toni Nykanen" <[email protected]> wrote in message
    news:3ef1577b$[email protected]..
    >
    Hi!
    We need to implement authentication using our own methods, and theauthentication
    information is provided to the web service implementation in a basicauthentication
    header. The problem is, that the servlet
    weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
    in
    wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
    Is there any way to circumvent this, because we want to implementauthentication
    on our own?
    I already know two workarounds:
    The best would of course be to implement a custom security realm for ourown
    authentication system. This is not an option, implementing an own security
    realm is overkill for this specific web service.
    The other way would be to route the requests by way of a custom servlet,which
    would
    remove the basic authentication header, and put the authentication info incustom
    headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
    authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
    >
    But still, I'd like to know if there is any way to tell bea's servlet toignore
    the basic
    authentication header?
    Oh yeah, by the way, this is URGENT, as always. (really!! ;)
    Toni Nykanen

  • Error in execution of  Web Services on WebLogic --ArrayIndexOutOfBoundsExc

    Hi,
    I Have an error with web services hosted on weblogic server and it is throwing the following exception stack trace.
    <MS1> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329818512003> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@f048e943 -appName 'newMyApp', name: '/newmyapp', context-path: '/newmyapp'] Root cause of ServletException.
    javax.servlet.ServletException
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:39)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    java.lang.ArrayIndexOutOfBoundsException: -1
         at com.sun.xml.bind.v2.util.CollisionCheckStack.findDuplicate(CollisionCheckStack.java:112)
         at com.sun.xml.bind.v2.util.CollisionCheckStack.push(CollisionCheckStack.java:53)
         at com.sun.xml.bind.v2.runtime.XMLSerializer.pushObject(XMLSerializer.java:471)
         at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:574)
         at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:241)
         at com.sun.xml.bind.v2.runtime.BridgeImpl.marshal(BridgeImpl.java:54)
         at com.sun.xml.bind.api.Bridge.marshal(Bridge.java:71)
         at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:281)
         at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:124)
         at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:91)
         at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:170)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:186)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
         at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Edited by: 915901 on Feb 21, 2012 3:10 AM

    Hi Gabriel,
    Thank you for your response.
    I have checked this note and checked all my configuration. They all are in place.
    Any other input?
    Thank You,
    Mugdha Kulkarni

  • Deploying JAX-WS web service to weblogic server 9.2

    Hi,
    I want to deploy webservice created with JAX-WS 2.1 RI to BEA Weeblogic Server 9.2. After some research on forums and groups I have:
    sun-jaxws.xml
    <endpoints xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime" version="2.0">
    <endpoint name="TSOrganization"
    implementation="service.TsOrganizationImpl"
    url-pattern="/SOA/tsorganization"/>
    </endpoints>
    web.xml
    <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <listener>
    <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
    </listener>
    <servlet>
    <servlet-name>TsOrganization</servlet-name>
    <servlet-class>sun.com.xml.ws.transport.http.servlet.WSServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>TsOrganization</servlet-name>
    <url-pattern>/SOA/tsorganization</url-pattern>
    </servlet-mapping>
    <session-config>
    <session-timeout>
    30
    </session-timeout>
    </session-config>
    <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
    </web-app>
    weblogic.xml
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <context-root>/SOA/tsorganization</context-root>
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    </weblogic-web-app>
    weblogic-application.xml
    <weblogic-application xmlns="http://www.bea.com/ns/weblogic/90">
    <application-param>
    <param-name>webapp.encoding.default</param-name>
    <param-value>UTF-8</param-value>
    </application-param>
    <prefer-application-packages>
    <package-name>javax.jws.*</package-name>
    </prefer-application-packages>
    </weblogic-application >
    application.xml
    <application version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    <display-name>TSOrganization</display-name>
    <module>
    <web>
    <web-uri>TsOrganizationWS.war</web-uri>
    <context-root>/SOA/tsorganization</context-root>
    </web>
    </module>
    </application>
    I've included all the libraries from JAX-WS 2.1.3 into WEB-INF/lib in war file, packed it into ear and deployed. When I try to start deployed application I get following error:
    javax.servlet.ServletException: [HTTP:101249][weblogic.servlet.internal.WebAppServletContext@aed2df - appName: 'TSOrganization', name: '/SOA/tsorganization', context-path: '/SOA/tsorganization']: Servlet class sun.com.xml.ws.transport.http.servlet.WSServlet for servlet TsOrganization could not be loaded because the requested class was not found in the classpath . java.lang.ClassNotFoundException: sun.com.xml.ws.transport.http.servlet.WSServlet.
    although the missing class is in jaxws-rt.jar included in WEB-INF/lib folder.
    Any ideas what to try next?

    Ok.. with some help I found the error...
    servlet class is com.sun... and not sun.com :-S
    but everything else is right.. so it can be like reference for deploying jaxws service on weblogic 9.2.

  • Problems when deploying web service onto Weblogic 12c

    Hello everybody:
    Created a web service with MyEclipse 8.5; when deploying onto Weblogic I'm facing this next problem:
    Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
    INFO: WSSERVLET15: JAX-WS servlet destroyed
    Nov 3, 2012 7:44:40 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
    INFO: WSSERVLET13: JAX-WS context listener destroyed
    <Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1351950260963' for task '0'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    Truncated. see log file for complete stacktrace
    Caused By: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    Truncated. see log file for complete stacktrace
    >
    <Nov 3, 2012 7:44:40 AM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
    <Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WSConsultaTrabajadorCurp_dir'.>
    <Nov 3, 2012 7:44:40 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "com.sun.xml.ws.tx.webservice.member.at.CompletionCoordinatorPortTypeImpl" failed to preload on startup in Web application: "WSConsultaTrabajadorCurp".
    javax.xml.ws.WebServiceException: [failed to localize] WSP_1018_POLICY_EXCEPTION_WHILE_FINISHING_PARSING_WSDL()
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1052)
    at com.sun.xml.ws.wsdl.parser.DelegatingParserExtension.finished(DelegatingParserExtension.java:183)
    at com.sun.xml.ws.wsdl.parser.WSDLParserExtensionFacade.finished(WSDLParserExtensionFacade.java:328)
    at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:242)
    at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:550)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:135)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.sun.xml.ws.policy.PolicyException: [failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getPolicyMap(PolicyMapBuilder.java:85)
    at com.sun.xml.ws.policy.jaxws.PolicyWSDLParserExtension.finished(PolicyWSDLParserExtension.java:1048)
    ... 54 more
    :com.sun.xml.ws.policy.PolicyException:[failed to localize] WSP_1014_POLICY_REFERENCE_DOES_NOT_EXIST(zip:C:/oracle/middleware/user_projects/domains/d_wsacceder/servers/AdminServer/tmp/_WL_user/_appsdir_WSConsultaTrabajadorCurp_dir/1f06hn/war/WEB-INF/lib/webservices-rt.jar!/WEB-INF/wsdl/wsat.wsdl#Addressing_policy)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicies(BuilderHandler.java:93)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.getPolicySubjects(BuilderHandler.java:103)
    at com.sun.xml.ws.policy.jaxws.BuilderHandlerEndpointScope.doPopulate(BuilderHandlerEndpointScope.java:67)
    at com.sun.xml.ws.policy.jaxws.BuilderHandler.populate(BuilderHandler.java:75)
    at com.sun.xml.ws.policy.jaxws.PolicyMapBuilder.getNewPolicyMap(PolicyMapBuilder.java:103)
    Truncated. see log file for complete stacktrace
    It seems it is looking for the file; it is in the specified path so I cannot figure out what's wrong. No reference about the problem found over internet. Same web service deploys without problem on Tomcat, but by requirement, needed to deploy onto Weblogic 10g or above. Any help?
    Thanks in advance.

    how did you configured this ws-policy file?
    are you using any @Policy annotations?
    Regards,
    Sunil P

  • Consume conversational web services from WebLogic

    hi all,
    any one tried to consume conversational async webservices from weblogic 7 ? or tried to create conversational async webserices on sunONE ?
    I am looking for standards to create interoperable async webservices which will use callbacks on the client side for notifications. Please advise...

    Hi Raja,
    Following patterns will likely give you a good idea of the type of problems you will have to address in real-world apps involving interactions with async Web services. I would encourage you to make the leap to studying BPEL4WS (and possibly WS-Transaction as well if you have true transactional requirements).
    App servers are at the core synchronous engines while BPEL4WS calls for asynchrony top to bottom. Saying that, it is possible to create an orchestration engine (as a J2EE container) on top of an app server to deliver orchestration infrastructure that deals with asynchrony, exception handling, long-running transactions, to enable developers to focus on the orchestration logic (i.e. BPEL) rather than re-invent the infrastructure wheel for each application built.
    Take a look at the Q&A content here, hope it helps.
    http://searchwebservices.techtarget.com/ateAnswers/0,289620,sid26_cid492833_tax292928,00.html
    Doron\

  • How to implement the security in web service with Weblogic 9.2

    I've generated web service by Web Logic 9.2 using existing WSDL (as per client requirement) and want to add security policy for authentications.
    I have used following annotation in service class.
    @Policies({
    @Policy(uri="policy:Auth.xml" , direction=Policy.Direction.inbound)
    But it gives compilation time error with following message.
    The Policy and Policies annotations are not allowed on jws file when compiledWsdl option is specified
    I've also tried to modify the WSDL to accommodate policy configuration and again generate the web service but problem is being as it is.
    If anybody has solution of this issue then please let me know ASAP.

    Did you get an answer to your question? I have the same problem with WebLogic 10.0.

Maybe you are looking for

  • Error while executing the standard API in HRMS

    Hi Amigos, Currently i am working on the api "hr_personal_pay_method_api.create_us_personal_pay_method" while i try to run a procedure with hard coding some values passing to this api, i am getting the following error. ORA-20001: The legislation for

  • Formatting a string

    Hello All Is there a way I can use format specifiers with variables? OK so I need to format a string to be a certain length equal to the longest string I am using. So what I would like to use is something like: %xs where x is the number of the length

  • My socket gets tired!

    Do "lazy sockets" exist? :-p I've got a problem with one... In a client-server application, the client connects to the server, the server accepts, and sends a very long string to the client (about 900k characters). the server does like this: PrintWri

  • Vista Circuit Design Suite - DEP

    I'm running Windows Vista Home Premium, last reformat was 2 months ago, no issues until after installing Circuit Design Suite 10.0.144. After installing, Windows began throwing me Data Execution Prevention (DEP) errors during startup. The error reads

  • Displaing BINARY_DOUBLEs in a SQL Report

    I am trying to display BINARY_DOUBLEs in a SQL report and the vales display with scientific notation: 1.0495999999999999E+002 I would like to display them like this: 1.04