Issue when deploying web service

Hi,
I'm new to web services. Im currently using netbeans 6.0 beta 1 to create my web services. After creating and deploying it on the bundled tomcat 6 server, i get this error that says that requested resource not found. What could be the cause of it as it works in netbeans 5.5? Could it be that the error is caused by the difference in the JAX WS 2.0 and 2.1 libraries?
note: netbeans 5.5 uses JAX WS 2.0. netbeans 6.0 beta 1 uses JAX WS 2.1.
much help would be appreciated. Thank you...
coderDuck

here's the log
Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
**************************************WARNING***************************************
To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
before rt.jar. To do this you can use Java endorsed mechanism to override what is in
Java platform. The easiest way to do so is to copy all jars from the
C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:511)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1220)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1458)
at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:820)
at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:348)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
**************************************WARNING***************************************
To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
before rt.jar. To do this you can use Java endorsed mechanism to override what is in
Java platform. The easiest way to do so is to copy all jars from the
C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
... 36 more
Oct 29, 2007 11:15:59 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
**************************************WARNING***************************************
To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
before rt.jar. To do this you can use Java endorsed mechanism to override what is in
Java platform. The easiest way to do so is to copy all jars from the
C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:118)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1237)
at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:373)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
**************************************WARNING***************************************
To use JAX-WS 2.1 with JDK 6, newer versions of API jars need to be in bootclasspath
before rt.jar. To do this you can use Java endorsed mechanism to override what is in
Java platform. The easiest way to do so is to copy all jars from the
C:\Program Files\NetBeans 6.0 Beta 1\java1\modules\ext\jaxws21\api folder to
C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0\endorsed.
Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/WSDpractical/testWS/build/web/WEB-INF/lib/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:172)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:146)
at com.sun.xml.ws.model.AbstractSEIModelImpl$1.run(AbstractSEIModelImpl.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:144)
at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:83)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:260)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
... 22 more

Similar Messages

ServletException When Deploying Web Service Application to WL 10.3.1

I'm attempting to deploy a web service application to WebLogic 10.3.1 built using the ANT jwsc task. The majority of the build is being done by Maven to produce and EAR file which contains the web service application WAR file, but I'm using ANT for the jwsc task due to classpath issues in Maven. Here is my task definition from by ANT build script:
<jwsc srcdir="src" destdir="${basedir}/target"
classpathref="weblogic.jar.classpath" verbose="on" debug="on"
keepgenerated="yes">
<module contextpath="testapp" name="TestWSApp" explode="true">
<jws type="JAXWS" file="test/src/TestWSImpl.java"/>
<descriptor file="${basedir}/src/main/webapp/WEB-INF/web.xml"/>
<descriptor file="${basedir}/src/main/webapp/WEB-INF/weblogic.xml"/>
</module>
</jwsc>
When the process completes, within the WAR file is the web.xml, which has been modified by the jwsc process to contain a servlet definition and mapping:
<servlet>
<servlet-name>TestWSAppServlethttp</servlet-name>
<servlet-class>test.src.TestWSImpl</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>TestWSAppServlethttp</servlet-name>
<url-pattern>/TestWSAppServlethttp</url-pattern>
</servlet-mapping>
The problem comes when I try to deploy to WebLogic. The deployment fails and I get errors. The stack track is really long, but here is the main problem:
weblogic.application.ModuleException: [HTTP:101216]Servlet: "DataIntegrityServiceServlethttp" failed to preload on startup in Web application: "/testapp".
javax.servlet.ServletException: Servlet class: 'test.src.TestWSImpl' does not implement javax.servlet.Servlet
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:276)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
This error actaully makes sense if I was trying to deploy a servlet and not a web service class. If I manually remove the <load-on-startup>0</load-on-startup> element from the web.xml, then this deploys fine. I've tried to define the servlet in the web.xml permenantly, but jwsc throws an error saying the context is already in use.
So what I need to do is either have jwsc skip the modification of the web.xml or just not have it create the <load-on-startup>0</load-on-startup> element. Any ideas?

Nevermind, I figured it out.
I had to change the name of my JWS class (the one that implements the web service methods) and then it worked fine.
Thanks to all who responded.

Error when deploying web service do not have a property of the name return

Using Jdeveloper 11.1.1.6 and Oracle 11g database.
I created entities classes from tables then created a Java Service Facade and then a web service from the facade.
When I delpoy (to Integrated WLS) or try to test the web service I get:
javax.xml.ws.WebServiceException: class src.jaxws.persistXXX do not have a property of the name return. (I put the XXX there because if I remove the class from the web service then another persist* class gives the same error.
I've checked the definitions and there's not a name 'return' anywhere other than return statements in the methods.
TIA,
Dave
Here's a stacktrace after the above error:
at com.sun.xml.ws.server.sei.EndpointResponseMessageBuilder$DocLit.(EndpointResponseMessageBuilder.java:206) at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.createResponseMessageBuilder(EndpointMethodHandlerImpl.java:213) at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.(EndpointMethodHandlerImpl.java:119) at com.sun.xml.ws.server.sei.EndpointMethodHandlerFactory.create(EndpointMethodHandlerFactory.java:15) at com.sun.xml.ws.server.sei.PayloadQNameBasedDispatcher.(PayloadQNameBasedDispatcher.java:118) at com.sun.xml.ws.server.sei.EndpointMethodDispatcherGetter.(EndpointMethodDispatcherGetter.java:83) at com.sun.xml.ws.server.sei.SEIInvokerTube.(SEIInvokerTube.java:82) at weblogic.wsee.jaxws.WLSContainer$WLSEndpointFactory$1.createServer(WLSContainer.java:800) at weblogic.wsee.jaxws.ServerLateInitTube.postCreateEndpoint(ServerLateInitTube.java:57) at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:46) at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:150) 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.(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: javax.xml.bind.JAXBException: return is not a valid property on class src.jaxws.PersistSubQuestionResponse at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:973) at com.sun.xml.ws.server.sei.EndpointResponseMessageBuilder$DocLit.(EndpointResponseMessageBuilder.java:203) ... 55 more

I found this in a google search:
OK, I've solved this myself. I was using -p with wsimport to name the package of the generated class. When I removed this from the generated class, everything works fine! I'm not really sure why but I think it's because the wsdl is using target namespace.
Does JDeveloper use this switch during deployment? If so, how do I remove it? Thanks, Dave

Java.lang.IncompatibleClassChangeError when deploying web service

Hi there,
I'm trying to deploy a jax-rpc web service and get a java.lang.IncompatibleClassChangeError error when I use org.apache.axis.client.AdminClient with the following deploy.wsdd file. The funny thing is the Web Service is deployed and listed in AXIS. Can anyone help me to resolve this.







<deployment
    xmlns="http://xml.apache.org/axis/wsdd/"
    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">

<service name="flightservice" provider="java:RPC" style="rpc" use="encoded">
      <parameter name="wsdlTargetNamespace" value="urn:flightservice"/>
      <parameter name="wsdlServiceElement" value="FlightInfoServiceIFService"/>
      <parameter name="wsdlServicePort" value="flightservice"/>
      <parameter name="className" value="flightCompany.rpcservice.FlightserviceSoapBindingImpl"/>
      <parameter name="wsdlPortType" value="FlightInfoServiceIF"/>
      <parameter name="typeMappingVersion" value="1.2"/>
      <operation name="getFlights" qname="operNS:getFlights" xmlns:operNS="urn:flightservice" returnQName="getFlightsReturn" returnType="rtns:string" xmlns:rtns="http://schemas.xmlsoap.org/soap/encoding/" soapAction="" >
        <parameter qname="in0" type="tns:string" xmlns:tns="http://schemas.xmlsoap.org/soap/encoding/"/>
      </operation>
      <parameter name="allowedMethods" value="getFlights"/>
      <parameter name="scope" value="Session"/>
</service>
</deployment>

I was getting this error running AdminClient from a ant task, but the got no error when I ran it from the commanr line. But I'm getting the same thing back from the actual service itself whrn I try and invoke it using stubs generated by the wsdl2java tool with the following code
    public String getFlightsFromWSService(String date) throws Exception {
     String REMOTE_ENDPOINT_URL = "http://localhost:7070/axis/services/flightservice";
     String namespace = "flightservice";
     String portName = "FlightInfoServiceIF";
     String servicename = "flightservice";
     //make a service
     FlightInfoServiceIFService service = new FlightInfoServiceIFServiceLocator();
     //get a stub to the service
     FlightInfoServiceIF flightSvc = service.getflightservice( new URL( REMOTE_ENDPOINT_URL ));
     //make a call
     return flightSvc.getFlights(date);
    }TCPMonitor gives me this pile of stuff
HTTP/1.1 500 Internal Server Error
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-IE
Date: Tue, 31 May 2005 22:43:12 GMT
Server: Apache-Coyote/1.1
Connection: close
<html>
   <head>
      <title>Apache Tomcat/4.1.31 - Error report</title>
      <STYLE>
         </STYLE>
      </head>
      <body>
         <h1>HTTP Status 500 - </h1>
         <HR size="1" noshade="noshade">
            <p>
               <b>type</b> Exception report
            </p>
            <p>
               <b>message</b>
               <u></u>
            </p>
            <p>
               <b>description</b>
               <u>The server encountered an internal error () that prevented it from
fulfilling this request.</u>
            </p>
            <p>
               <b>exception</b>
               <pre>javax.servlet.ServletException: Servlet execution threw an exception
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:222)     at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:146)     at ...........lots more exceptions.........
            </p>
            <p>
               <b>root cause</b>
               <pre>java.lang.IncompatibleClassChangeError     at
org.apache.axis.message.MessageElement.addTextNode
(MessageElement.java:1387)
     at org.apache.axis.message.SOAPHandler.endElement
(SOAPHandler.java:118)
     at org.apache.axis.encoding.DeserializationContext.endElement
(DeserializationContext.java:1083)     at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement
(Unknown Source)     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
     at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument
(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:595)
</pre>
            </p>
            <HR size="1" noshade="noshade">
               <h3>Apache Tomcat/4.1.31</h3>
            </body>
         </html>

Sys.UTL_DBWS issue when calling web service .......

Hi,
Background Details :
Linux : 2.6.18-164.10.1.0.1.el5 #1 SMP Fri Jan 8 02:34:10 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
Web Server : Apache Tomcat 6.0.20
Database : Oracle 10.2.0.4
Utility that we use to consume the Web Service from PL/SQL : JPublisher 10g Release 2 (10.2)
Load Balancer : Citrix Netscaler
We are using the Oracle built in package called UTL_DBWS to invoke the Java web service. The web service is been called through a Load Balancer called Citrix Netscaler.
Load balancer has been configured to use the Source IP mechanism to route the request to the appropriate web service.
Problem :
When invoking the web service from Pl/SQL (with the below piece of code) there are multiple times the web servers are been called which is supposed to be only once. The number of times the call varies is about to 2 or 3.
Query :
Hence we need to understand in general how the UTL_DBWS works ? Are there any issues when the call being made through the LoadBalancer ?
The default time out value while connecting ? If we want to override the default timeout how we can do that ?
Code for reference :
BEGIN
l_service := sys.UTL_DBWS.create_service (
wsdl_document_location => sys.URIFACTORY.getURI(l_wsdl_url),
service_name => l_service_qname);
l_call := sys.UTL_DBWS.create_call (
service_handle => l_service,
port_name => l_port_qname,
operation_name => l_operation_qname);
l_input_params(0) := sys.ANYDATA.ConvertVarchar2(p_dayend_date);
l_result := sys.UTL_DBWS.invoke (
call_handle => l_call,
input_params => l_input_params);
sys.UTL_DBWS.release_call (call_handle => l_call);
sys.UTL_DBWS.release_service (service_handle => l_service);
EXCEPTION WHEN OTHERS THEN
PKG_IRIS_SH.PRC_ins_spm('WEB','9999', 'Web Service', TO_DATE(p_dayend_date ,'DD/MM/YYYY HH24:MI:SS') ,'Error Description:' ||SQLERRM , '0');
End ;
Can any body advise on this issue.
thanks,
Ram

Cross posted to APEX support forum, PLEASE CLOSE THIS THREAD..
Thank you,
Tony Miller
Webster, TX
Never Surrender Dreams!
JMS
If this question is answered, please mark the thread as closed and assign points where earned..

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

Issue when importing web service into CTI Aspect ECS server

Hi Experts,
We have an SOAP to ABAP Proxy interface in our production XI system.
this interface connects CTI ASPECT ECS system to SAP CRM system
(via XI or PI system).
CTI ASpect system consumes the web service exposed by XI system.
recently we edited the web service in XI system. when we try to import
the web service (WSDL file) into CTI ASPECT system , it generates an
XML parser error.
has any one anyone faced this issue earlier.please let me know how this issue can be resolved.
-Kaushik

Hi Experts,
We have an SOAP to ABAP Proxy interface in our production XI system.
this interface connects CTI ASPECT ECS system to SAP CRM system
(via XI or PI system).
CTI ASpect system consumes the web service exposed by XI system.
recently we edited the web service in XI system. when we try to import
the web service (WSDL file) into CTI ASPECT system , it generates an
XML parser error.
has any one anyone faced this issue earlier.please let me know how this issue can be resolved.
-Kaushik

DDBeanCreateException when deploying web service EAR

Hi All,
I would very much appreciate any help on the following problem.
I used WorkSpace 1.1 to develop my app and tested in on WLS 10.0 within it. In WorkSpace the server runs on port 7021 and it has ALSB as well on the same port.
I created EARs and tryed deploying them to another WLS 10.0 that was used by ALSB, outside of Work Space. All module deployed fine.
Then I created a standalone WLS 10.0 server and tried deploying my modules on it. The server by default is on port 7001. Deployment failed with this error:
javax.enterprise.deploy.model.exceptions.DDBeanCreateException: [J2EE Deployment SPI:260142]The descriptor at 'META-INF/annotation-manifest.xml' in module 'XXX.war' is not recognized, and could not be parsed.
I found this article in Chris Hogue's blog (http://dev2dev.bea.com/blog/hogue/archive/2006/09/changing_annota.html_)
He recommends adding weblogic J2EE weblogic-controls-1.0 library to the EAR. I already have weblogic-controls-10.0 library attached. The only thing that jumps at me is the difference in ports. I manually changed references in annotation.xml from port 7021 to port 7001, but it did not help.
Thoughts?? Thanks in advance!
Edited by svitlana.dukhovna at 05/09/2008 3:05 PM

Hi Dipesh,
well, if you are using J2EE Engine 6.20 you cannot deploy directly from the NetWeaver Developer Studio (as far as I know, this feature is available only after 6.30/6.40 versions).
Also, web services are only partially implemented on J2EE Engine 6.20! So it is possible that the web service you've developed with the Developer studio depends on features that are not available on J2EE Engine 6.20. My recommendation is to give a try to the J2EE Engine 6.40, if possible for you at all.
Finally, there is an alternative to Deploy Tool for deployment on the J2EE Engine 6.20. This is the DEPLOY shell command that you can execute in the server console. For more info about that, refer to the Shell Commands Reference section in the Administration Manual for J2EE Engine 6.20 located here: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/administration manual for sap j2ee engine 6.20.pdf
Hope that helps!

Connection error when deploying Web Services example

C:\java\sample\how-to-web-services\ejb>ant deploy-usingadmin.jar
Buildfile: build.xml
common:
[echo] BuildName: EJB Stateless Web Service
[echo] BuildHome: C:\java\sample\how-to-web-services\ejb
[echo] BuildFile: C:\java\sample\how-to-web-services\ejb\build.xml
[echo] BuildJVM: 1.3
init:
deploy-ear:
[java] Error: javax.naming.NamingException: Lookup error: java.net.ConnectE
xception: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect
bind-web-app: [java] Java Result: 1
[java] Error: javax.naming.NamingException: Lookup error: java.net.ConnectE
xception: Connection refused: connect; nested exception is:
[java] java.net.ConnectException: Connection refused: connect
deploy-usingadmin.jar:
BUILD SUCCESSFUL
Total time: 7 seconds
Thanks,

You have to start OC4J and make changes in the common.xml/buld.xml to have connection information for your OC4J instance.
Otherwise you can take this EAR file and deploy in your OC4J instance.
regards
Debu

Disable launch of front panel when starting web services

Hello all,
This may be a naive question as it may have a simple answer that I am missing, but is there a way to not have all VIs associated with a web service launch (i.e. show their front panel) when you start a web service? I find this to be very irritating as I have a lot of VIs associated with the web service that I am running and don't want my windows cluttered up with VI front panels that I am not interested in viewing.
Thanks, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC

Thanks for the reply, tst. I was hoping that I would be able to reproduce this on the client side, but unfortunately I can't generate a simple example . My web service is large and contains a lot of resources to access different variables and it seems to reproduce this, you would have to deploy this onto an RT target.
Some further insight into the issue - starting a web service on my current target is similar to when you select Deploy All on a virtual folder in a project - all of the front panels become visible.
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC

To launch Oracle BPM deployed Web Services [In BPM Enterprise]

Hi all,
I have expose my Process Instance into Web Services in Studio.
It is working well. In Studio, I start the Engine (Run -> Start Engine),
Then, I Start the Web Services (Run -> Launch deployed Web Services webapps).
It would show me my local webservice links.
http://localhost:9000/albpmServices/<ProjectName>/ws
But, I unable to launch this Web Service Webapps, when i deploy the project into Oracle BPM Enterprise with Weblogic Server.
May know what is the link for BPM Enterprise?
Regards,
Chris

My URL is:-
http://localhost:9000/albpmServices/TestProject/ws/TestProcessServiceListener?wsdl=true
and it does not seem to open the WSDL when I start the enterprise server engine..
I have the process exposed as a web-service with two methods..
One for Process Creation and another for Notification Wait Activity...
I have also checked the box to start PAPI WS Services on my standalone server
Is there some other config that I need to make inside my standalone server to get this WSDL?
I understand that standalone works on Tomcat...

ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
when browsed through some of the messages they point to setting Oracle Wallet Manager.
I am trying to connect
Any idea on how to resolve this issue ?
your input is appreciated.
Thanks
Ravi

Duplicate post ... please ignore.

Errors when processing web service call

Hello Experts,
Based on a requirement, I got a URL based on WSDL, using which I created a Consumer Proxy in SAP.
I created a Logical Port in SOA Manager with type selected as 'WSDL'.
When I'm trying to execute the proxy class to call the webservice using the logical port through SE80 it is throwing an error log as stated below.
1) SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
2)Error when processing Web service call
3)Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Kindly help me out.
Thanks,
Vamshi

Hi,
Check Anton's reply in this thread: External WS Consumption Issue
Also refer the below doc which may help you: Consume an External Web Service in a Nutshell with Good Old ABAP
Calling WebServices from ABAP via HTTPS
Regards,
Kiran

Parameter names change when generating web service from WSDL

Hi,
I have a problem with BEAs web services that I'm hoping someone can help me with.
I have a
WSDL file, and from that I want to generate a web service implementation and a
web service
client. In the WSDL file, I have a message defined like this:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="data"/>
</message>
I generate the server using the server using the wsdl2service Ant task, I implement
the necessary classes, and I deploy it. When I access the deployed web service,
the parameter name has changed, from "data" to "bytes". If I access the WSDL file
of the deployed web service, it says:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="bytes"/>
</message>
This happens for all parameters, string parameters are renamed to "string", base64Binary
parameters are renamed to "bytes", etc...
This poses a problem to me, because if I generate a web service client from the
original WSDL file, it will not be able to talk to my web service. Is there any
way of forcing a web service generated from a WSDL file to keep the parameter
names of the original WSDL file?
Any help in this is greatly appreciated.
Regards,
Petter

From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
Here are sample of bare-style :
<xsd:element name="getPupilAddressResponse" type="xsd:string"/>
<xsd:element name="getPupilAddressRequest" type="xsd:int"/>
Wrapped will looks like that:
<xsd:element name="getSENLevelResponse">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
<xsd:element name="RecordCount" type="xsd:int">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Hope this helps,
Eric

How to deploy web service in EP

Hi Gurus!!!
I am trying to connect GRC to EP. GRC system is trying to reach EP via a web service but it is giving connection failed. But it is not giving any error.
I have a feeling that web service is not published. Somehow I published web service in EP in VA tool. But still issue is not resolved. Can any one guide me with steps to deploy web service in EP so that external systems can reach EP via web service.
Thanks in advance,
Sandeep

Sandeep check if your web service requires any authentication...
then you would need to set the same in Visual administrator...........
refer below article....
it is not the exact scenario as of yours....but still you might get some hint............
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0cf9e42-ccb0-2c10-d0a4-f5aa8a79e19a?QuickLink=index&overridelayout=true

Issue when deploying web service

Similar Messages

Maybe you are looking for