Deploying a JAX-WS web service in Weblogic 10

I created a web service starting from a WSDL, using the wsdlc and jwsc Ant tasks to build and package my web service, and the deploy Ant task for deployment. These steps used to work fine! However now I'm getting the following error during deployment:
deploy:
[wldeploy] weblogic.Deployer -noexit -name AESPServices -source C:\bea\user_projects\workspaces\stephanie\AESPTaskingSrv\stage\aespEar -targets Admin
Server -adminurl t3://localhost:7001 -user ******* -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -noexit -name AESPServices -source C:\bea\user_projects\workspaces\stephanie\AESPTaskingSrv\stage
\aespEar -targets AdminServer -adminurl t3://localhost:7001 -user ****** -deploy
[wldeploy] <Jun 25, 2009 9:01:22 AM CDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, AESPServices [archiv
e: C:\bea\user_projects\workspaces\stephanie\AESPTaskingSrv\stage\aespEar], to AdminServer .>
[wldeploy] Task 28 initiated: [Deployer:149026]deploy application AESPServices on AdminServer.
[wldeploy] Task 28 failed: [Deployer:149026]deploy application AESPServices on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy] java.lang.ClassNotFoundException: com.project.aesp.taskingserver.webservice.ActiveESP_ServiceImpl
[wldeploy]
[wldeploy]
BUILD FAILED
C:\bea\user_projects\workspaces\stephanie\AESPTaskingSrv\build.xml:78: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.Deploye
rException: Task 28 failed: [Deployer:149026]deploy application AESPServices on AdminServer.
Target state: deploy failed on Server AdminServer
java.lang.ClassNotFoundException: com.project.aesp.taskingserver.webservice.ActiveESP_ServiceImpl
The ActiveESP_ServiceImpl class file is clearly under WEB-INF/classes/com/project/aesp/taskingserver/webservice/ActiveESP_ServiceImpl.class. The only thing that has changed since my Ant tasks were working is the structure of our Weblogic libraries checked into SVN (thus the classpath used in my Ant script) - the tasks themselves have not changed. So it doesn't seem like this would be the problem.
Does anyone have an idea why the server can't locate the class file for my service implementation??
Thanks!
Stephanie

Appears to have been an issue with BEA Workspace Studio...I deleted all of my projects, recreated them from SVN, tried again and it worked.

Similar Messages

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

Deploy a JAX-WS web service to OC4J?

I have a JAX-WS Web Service that I need to deploy to OC4J. I've manged to set JDeveloper up to use ANT to build the server interfaces using jaxws and jaxb 2.0.
I've been able to deploy the web service to Sun's App Server, but I can't find any documentation that tells me how to deploy to OC4J. It doesn't matter if I have to deploy using ANT or thru JDeveloper, I just have to be able to deploy.
Any suggestions?

Here is a sample target to deploy on oc4j 10.1.3:
<project name="research" default="all" basedir="." xmlns:o="antlib:oracle">
<property file="../build.properties"/>
<property name="app.name" value="research"/>
<property name="web.name" value="${app.name}-web"/>
<property name="context.root" value="project-o/${app.name}"/>
<property name="oc4j.admin.user" value="oc4jadmin"/>
<property name="oc4j.binding.module" value="default-web-site"/>
<property name="oc4j.admin.port" value="23791"/>
<property name="oc4j.admin.password" value="welcome"/>
<property name="deployeruri" value="deployer:oc4j:${oc4j.host}:${oc4j.admin.port}" />
<target name="deploy" description="deploy application">
<echo>${deployeruri}</echo>
<o:deploy file="dist/${app.name}.ear"
deploymentname="${app.name}"
deployeruri="${deployeruri}"
userid="${oc4j.admin.user}" password="${oc4j.admin.password}"
logfile="deploy-ear.log"/>
<o:bindWebApp deploymentname="${app.name}"
deployeruri="${deployeruri}"
userid="${oc4j.admin.user}"
password="${oc4j.admin.password}" webmodule="${web.name}"
websitename="${oc4j.binding.module}"
contextroot="/${context.root}"/>
</target>
You may have to tweak a few properties to work in your environment.
Hope this helps,
Eric

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.

URGENT **** Need help for JAX-RPC Web Service Proxy deploy to OC4J 10.1.3.5

Hi everyone!
I’m really new to web services.
I’m getting a *500 internal server error* while deploying my JAX-RPC web service Proxy to an Oracle AS, in an OC4J, v. 10.1.3.5.0.
Running my client from my development environment (*jdeveloper 10g, 10.1.3.5.0*) everything functions correctly: from jdeveloper I can contact and use the web service defined by the following endpoint: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
I created a "try_ws_client.jsp" file that runs correctly from my local development environment jdeveloper (that uses an embedded oc4j, v. 10.1.3.5.0) but fails when run from the test server (Oracle AS, in an OC4J, v. 10.1.3.5.0), getting, as I mentioned a 500 internal server error, a white page in IE but with FF the message says: The’s an error in the servlet .....
Here's how I created the ws proxy and how I’m using it to consume the ws I mentioned.
1. I used the jdeveloper “Create Web Service Proxy” wizard (File > New > Business Tier > Web Services > Web Service Prox) and in the WSDL document URL I put: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
2. The operation ended without adding nothing to the web.xml file and creating the proxy files. One of them is: FederaMLOLSoapClient.java that have the WS exposed methods (es: public boolean createUser(String) ) + a “main” method with the example how to use this client to consume the WS.
public static void main(String[] args) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
} catch (Exception ex) {
ex.printStackTrace();
3. In FederaMLOLSoapClient.java I’ve create the method "tyIt":
public String tryIt(String username) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
if(myPort.createUser(String username)) {
return “O.K”;
} else {
return “K.O”;
} catch (Exception ex) {
// logs error
4. I created my try_ws_client.jsp file that creates FederaMLOLSoapClient object and calls the tryIt method, printing the “OK” or “KO” message.
<%@ page import="it.reggiocity.provincia.biblioreggiane.*"%>
<%
String message = "";
FederaMLOLSoapClient obj= new FederaMLOLSoapClient( );
message = obj.tryIt(“AAAAAA70R10H226H”);
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1252"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
<title>prova</title>
</head>
<body><%=message%></body>
</html>
The situation is:
My try_ws_client.jsp runs correctly from my jdeveloper and the user is created while creating app.ear and deploying it to my Oracle AS/OC4J as mentioned above, I get a 500 Internal Server Error.
Any idea to find a solution to this problem?
Please help.
Take care.
John M.

Hi,
you want to build the Web Service, or you want to consume the Service as a client? If the latter, Web client (ADF?) or Java client?
Frank

Calling One Jax/rpc web service from another.

We have a number of services residing in the same Oracle 10.1.3 app server container. These are deployed as Jax RPC Web Services
I am trying to figure out what are the different options to have once web service invoke an operation on another (without directly linking to the Java code). The reason we want to keep separation as far as possible is that these services may later migrate to different app servers and in the spirit of SOA all we want to change when a service migrates is address and would like everything else to remain the same.
So for example, if Web Service A needs to invoke an operation X in web service B,
One way to do this seems to be to generate a proxy for web service B, include the proxy in Web Service A and then simply do B.X() from Web Service A.
Is this is the best way to do it ?
Are there other alternative approaches available ? Such as using the built in ESB features of Oracle App Server 10.1.3?
Any pointers will be greatly appreciated.
Thanks
RR

Hi all,
I've managed to get this working by using the following property settings:
System.getProperties().setProperty("http.proxyHost", "Proxy_Hostname");
System.getProperties().setProperty("http.proxyPort", "8080");
System.getProperties().setProperty("http.nonProxyHosts", "localhost,hostbox09");
And solving the authentication problem using this property setting on the java cmd line:
-Dweblogic.net.proxyAuthenticatorClassName=com.mycompany.MyProxyAuthenticator
This class is an impl class of weblogic.common.ProxyAuthenticator interface.
The other thing to note is that MyProxyAuthenticator needs to be in the server pre_classpath.
Then I just call JAX-RPC or JAX-WS web service client calls as normal.
Regards,
Paul

Calling One Jax RPC Web Service from another in Oracle AS 10.1.3

We have a number of services residing in the same Oracle 10.1.3 app server container. These are deployed as Jax RPC Web Services
I am trying to figure out what are the different options to have once web service invoke an operation on another (without directly linking to the Java code). The reason we want to keep separation as far as possible is that these services may later migrate to different app servers and in the spirit of SOA all we want to change when a service migrates is address and would like everything else to remain the same.
So for example, if Web Service A needs to invoke an operation X in web service B,
One way to do this seems to be to generate a proxy for web service B, include the proxy in Web Service A and then simply do B.X() from Web Service A.
Is this is the best way to do it ?
Are there other alternative approaches available ? Such as using the built in ESB features of Oracle App Server 10.1.3?
Any pointers will be greatly appreciated.
Thanks
RR

Found document of 10.1.3.1.0 how to Creating a Custom Identity Service Plug-in
Oracle® BPEL Process Manager Administrator's Guide
10g (10.1.3.1.0)
Part Number B28982-03
http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28982/plugin.htm
But may be no help.

Problems while deploying web services to WebLogic

Hi,
I am looking to deploy jax-ws web services developed in Myeclipse 7.0 to WebLogic 10.0 Server it is giving the following error, but when i deployed to tomcat it is working fine.
In this I am using the JDK 1.5
The error message is as follows...
<User defined listener weblogic.wsee.deploy.ServletDeployListener failed: weblogic.wsee.deploy.WSEEServletEndpointException: Failed to prepare wsse module: ex1.
weblogic.wsee.deploy.WSEEServletEndpointException: Failed to prepare wsse module: ex1
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:32)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run(EventsManager.java:480)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextPreparedEvent(EventsManager.java:149)
Truncated. see log file for complete stacktrace
weblogic.wsee.ws.WsException: Can't find wsdl WEB-INF/wsdl/wscoor.wsdl
at weblogic.wsee.deploy.WSEEWebModule.loadWsdlDefinitions(WSEEWebModule.java:131)
at weblogic.wsee.deploy.WSEEModule.loadWsdl(WSEEModule.java:291)
at weblogic.wsee.deploy.WSEEModule.verifyWsdd(WSEEModule.java:146)
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:104)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:29)
Truncated. see log file for complete stacktrace
>
<Dec 9, 2008 3:11:33 PM EST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application '_appsdir_ex1_dir' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:308)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
Truncated. see log file for complete stacktrace
weblogic.wsee.ws.WsException: Can't find wsdl WEB-INF/wsdl/wscoor.wsdl
at weblogic.wsee.deploy.WSEEWebModule.loadWsdlDefinitions(WSEEWebModule.java:131)
at weblogic.wsee.deploy.WSEEModule.loadWsdl(WSEEModule.java:291)
at weblogic.wsee.deploy.WSEEModule.verifyWsdd(WSEEModule.java:146)
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:104)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:29)
Truncated. see log file for complete stacktrace
Let us know if you are able to help us….
Thanks,
Koteswara Rao

Hi ,
I deployed it on my local machine,
the WSDL looks like as follows...
<?xml version="1.0" encoding="UTF-8"?>

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ex.tkr2.com/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="CalculatorService" targetNamespace="http://ex.tkr2.com/">
<types>
<xsd:schema>
<xsd:import namespace="http://ex.tkr2.com/" schemaLocation="CalculatorService_schema1.xsd"/>
</xsd:schema>
</types>
<message name="add">
<part element="tns:add" name="parameters"/>
</message>
<message name="addResponse">
<part element="tns:addResponse" name="parameters"/>
</message>
<message name="divide">
<part element="tns:divide" name="parameters"/>
</message>
<message name="divideResponse">
<part element="tns:divideResponse" name="parameters"/>
</message>
<message name="multiply">
<part element="tns:multiply" name="parameters"/>
</message>
<message name="multiplyResponse">
<part element="tns:multiplyResponse" name="parameters"/>
</message>
<message name="subtract">
<part element="tns:subtract" name="parameters"/>
</message>
<message name="subtractResponse">
<part element="tns:subtractResponse" name="parameters"/>
</message>
<portType name="CalculatorDelegate">
<operation name="add">
<input message="tns:add"/>
<output message="tns:addResponse"/>
</operation>
<operation name="divide">
<input message="tns:divide"/>
<output message="tns:divideResponse"/>
</operation>
<operation name="multiply">
<input message="tns:multiply"/>
<output message="tns:multiplyResponse"/>
</operation>
<operation name="subtract">
<input message="tns:subtract"/>
<output message="tns:subtractResponse"/>
</operation>
</portType>
<binding name="CalculatorPortBinding" type="tns:CalculatorDelegate">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="add">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="divide">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="multiply">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="subtract">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CalculatorService">
<port binding="tns:CalculatorPortBinding" name="CalculatorPort">
<soap:address location="http://localhost:8080/SampleWebServices/CalculatorPort"/>
</port>
</service>
</definitions>

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

Weblogic 12c (12.1.2.1) JAX-WS Web Service :: Admin Console

When in my development environment (eclipse, weblogic server) and working on a JAX-WS web service; From the administrative console, under deployments, when I expand the EAR, i can see the EAR, a module for the web service project, and under Web Services, the context name of the service.
When i export the EAR and load this on my integration server, i do not see the Web Service listed, when expanding the depolyed EAR.
Anyone know what i am missing to have the service displayed?
Thanks,

Hi,
This community is to discuss Oracle Application Server specific issues, you can post this query in Oracle Weblogic for better response :-
WebLogic Server - Management / Console / WLST / Configuration
Regards,
Prakash.

Cannot attach a WS-Policy to Jax-RPC Web Service

I am having trouble trying to associate a WS-Security Policy with a BEA Jax-RPC Web Service?
I am following the following procedure to try to associate a the policy:
http://edocs.bea.com/wls/docs100/ConsoleHelp/taskhelp/webservices/ConfigureWSPolicyFile.html
The problem is that when I navigate on the Administration Console to
Deployments
=> AdapterAdminService (this is the name of my application)
=> com.gateway.admin.wsdl.v10.AdminImpl (this is the name of my Web Service)
=> Configuration
=> WS-Policy
The Web console displays a stacktrace mentioning an "IndexOutOfBoundsException" :
Error opening /jsp/webservice/WebServiceConfigurationWebServicePoliciesForm.jsp.
The source of this error is java.lang.IllegalArgumentException: The property you provided 'contents' of form 'deploymentPlanForm' must not be set to null. at com.bea.console.taglib.html.TableTag.registerDataSet(TableTag.java:1588) at com.bea.console.taglib.html.TreeTableTag.doRegisterDataSet(TreeTableTag.java:49) at com.bea.console.taglib.html.TableTag.doStartTag(TableTag.java:1360) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag9(__webserviceconfigurationwebservicepoliciesform.java:498) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag8(__webserviceconfigurationwebservicepoliciesform.java:459) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag7(__webserviceconfigurationwebservicepoliciesform.java:416) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jspService(__webserviceconfigurationwebservicepoliciesform.java:265) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) 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.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551) at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306) at com.bea.netuix.nf.UIControl.render(UIControl.java:578) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) 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.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at
I have this issue with both IE7 and Firefox 2. My domain is a WLS 10.0MP1 domain and is deployed on my Windows XP laptop.
I am generating the WS from WSDL with the following ant command:
          <wsdlc srcWsdl="${wsdl.location.path}/AdapterAdministration.wsdl"
               destJwsDir="${gen.compiled.wsdl.dir}"
               packagename="com.gateway.admin.wsdl.v10.server"
               destImplDir="server_impl_example" />
then
               <jwsc     srcdir="${src.dir}" destdir="${dist.dir}" classpathref="project.class.path" debug="true">
                         <jws file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                              compiledWsdl="${gen.compiled.wsdl.dir}/AdapterAdministration_wsdl.jar" />
                    </jwsc>
and finally, I deploy it with:
          <wldeploy action="deploy"
               name="AdapterAdminService"
               source="${dist.dir}/AdminImpl.war"
               user="${wls.domain.user}"
               password="${wls.domain.pwd}"
               verbose="true"
               stage="no"
               upload="true"
               adminurl="t3://${wls.domain.host}:${wls.domain.port}"
               targets="${wls.domain.servername}" />
Do you have any idea what might be wrong here?
Thanks in advance,
Svend

Hi all,
Some more information: I have created another very simple Jax-RPC Web Service, now using the @Policy annotation. The policy I specify is then correctly taken into account, but I still have the same symptom when I navigate to the Configuration => WS-Policy page on the Web Console (i.e., I cannot associate a WS-Policy to my WS with the Web Console)
Beginning of the JWS file:
@WebService(...)
@WLHttpTransport(serviceUri = "", portName = "AdapterAdmin")
@Binding(Binding.Type.SOAP12)
@Policy(uri="Wssp1.2-Http-UsernameToken-Digest.xml")
public class AdminImpl implements Admin {
Ant task I use to build and deploy the service:
<target name="build-service" depends="prepare">
          <mkdir dir="package"/>
          <mkdir dir="package/WEB-INF"/>
          <mkdir dir="package/WEB-INF/lib"/>
          <jwsc
               srcdir="${src.dir}"
               destdir="package"
               classpathref="project.class.path"
               debug="true">
               <jws
                    file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                    contextpath="/AdminImpl2"
                    explode="true"
               />
          </jwsc>
          <move todir="package/WEB-INF">
               <fileset dir="package/com/gateway/admin/wsdl/v10/AdminImpl/WEB-INF"></fileset>
          </move>
          <move todir="package/META-INF">
               <fileset dir="package/xsize/gateway/admin/wsdl/v10/AdminImpl/META-INF"></fileset>
          </move>
          <copy todir="package/WEB-INF/lib">
               <fileset dir="${lib.dir}"
                              includes="client-1.0.jar,
                                   tools.jar />
          </copy>
          <delete dir="package/com" />
          <jar destfile="${dist.dir}/simpleWS2.war" >
               <fileset dir="package" />
          </jar>
          <wldeploy action="deploy"
               name="AdminService-withPolicyAnnotation"
               source="${dist.dir}/simpleWS2.war"
               user="weblogic"
               password="weblogic"
               verbose="true"
               stage="no"
               upload="true"
               adminurl="t3://localhost:9001"
               targets="AdminServer" />
     </target>
"

JAXB unmarshaller error in JAX-WS web service

Hi,
We have a JAX-WS web service deployed to WLS 10.3.3.0 as an EAR file. The EAR file deploys without any problems, but the first time we attempt to call an operation we get a classloading problem when we run the following code snippet (I've put a comment after the failed line of code):
          Object jaxbObject = null;
          Unmarshaller unmarshaller = null;
          try {
               unmarshaller = JAXB_CTX.createUnmarshaller(); // JAXB_CTX is an instance of JAXBContext
               jaxbObject = unmarshaller.unmarshal(new ByteArrayInputStream(xmlString.getBytes())); // this line fails
          } catch (JAXBException e) {
If we update the EAR file or delete and re-install the EAR file in the WLS console then the problem doesn't go away, but if we restart the WL server that hosts the EAR file then the problem is resolved. The problem is consistently repeatable.
The stacktrace for the error is:
java.lang.ClassCastException: org.apache.xerces.parsers.XML11Configuration
     at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
     at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
     at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
     at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
     at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.createDocument(SAX2DOM.java:326)
     at com.sun.org.apache.xalan.internal.xsltc.trax.SAX2DOM.<init>(SAX2DOM.java:85)
     at com.sun.org.apache.xalan.internal.xsltc.runtime.output.TransletOutputHandlerFactory.getSerializationHandler(TransletOutputHandlerFactory.java:187)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getOutputHandler(TransformerImpl.java:392)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerHandlerImpl.setResult(TransformerHandlerImpl.java:137)
     at com.sun.xml.bind.v2.runtime.unmarshaller.DomLoader$State.<init>(DomLoader.java:74)
     at com.sun.xml.bind.v2.runtime.unmarshaller.DomLoader.startElement(DomLoader.java:113)
     at com.sun.xml.bind.v2.runtime.unmarshaller.ProxyLoader.startElement(ProxyLoader.java:56)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:456)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:433)
     at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:138)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:184)
     at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
     at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:184)
     at com.northernrock.applicationdataservice.interaction.util.ServiceSoapPortUtil.generateJAXBObjectFromXML(ServiceSoapPortUtil.java:184)
     at com.northernrock.applicationdataservice.interaction.util.DataMapper.mapFullApplication(DataMapper.java:130)
     at com.northernrock.applicationdataservice.interaction.ServiceSoapPort.retrieveFullApplicationData(ServiceSoapPort.java:148)
     at com.northernrock.applicationdataservice.interaction.ServiceSoapPortImpl.retrieveFullApplicationData(ServiceSoapPortImpl.java:69)
     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 weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
     at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
     at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:265)
     at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:373)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:524)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:255)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:141)
     at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:210)
     at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:311)
     at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:223)
     at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:124)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
There seems to be something strange going on with the classloading, such that re-deploying the application causes the wrong Xerces parser classes to be loaded until the WL server is restarted. Once the restart is done then there is no problem until the next re-deployment.
Does anyone know a fix for this issue?
Any help is appreciated.
Thanks,
Jason

Hi Jason,
Below is the sample.....You can use this..
JAXBElement<Task> root = null;
          try {
               ByteArrayInputStream input = new ByteArrayInputStream(
                         xmlStr.getBytes());
               JAXBContext jc = JAXBContext.newInstance(Task.class);
               Unmarshaller u = jc.createUnmarshaller();
               StreamSource sc = new StreamSource(new StringReader(
                         xmlStr.toString()));
               root = u.unmarshal(new StreamSource(input), Task.class);
          } catch (Exception e) {
               e.printStackTrace();
          }

How to create JAX-WS web services using providers?

I am looking at WebLogic web services, because we are investigating the possibility of migrating our web services from Apache CXF to WegLogic web services. Our web services are implemented using JAX-WS providers. However, I browsed through the Oracle Fusion Middleware document library, but I couldn't find any documents for implementing JAX-WS web services using providers.
Is there any document, tutorial, or examples of that?
Thanks in advance!
Tao

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

Jax-ws web service client

Hi, I am confused by the web service document http://docs.oracle.com/cd/E17904_01/web.1111/e13758/use_cases.htm#i244846 section 2.4. The Note states:
You can invoke a Web service from any Java SE or Java EE application running on WebLogic Server (with access to the WebLogic Server classpath). Invoking a Web service from stand-alone Java applications that are running in an environment where WebLogic Server libraries are not available is not supported in this release for JAX-WS Web services.If I understand it correctly, it says jax-ws only can be consumed by the clients that have access to wls libraries. My web service client will be 3rd party business parnter. Not sure if they are on wls or not. Does it mean I can't use jax-ws?

When you just use the JAX-WS standard you do not need any WebLogic related classes to create a client for your web service.
When the web service is deployed the WSDL can be accessed. By using this WSDL you can create your client by using tools
such as wsimport (which comes with a JDK distribution and is located in the JDK_HOME/bin directory)
wsimport -keep -d C:\YOUR_PROJECT\src http://hostname:port/context/SomeWebService?wsdlthe 'keep' option make sure the generated .java files are not thrown away.

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE? I am asking this because I need to pass xmlbeans generated objects as arguments in the web method. For JAX-WS there has to be a no argument constructor for it to be able to pass in theweb method. The workshop 10.3 was able to pass the xmlbeans generated object as the web service was implemented as a JAX-RPC web service....

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

Deploying a JAX-WS web service in Weblogic 10

Similar Messages

Maybe you are looking for