Deploy a Corba POA in WLS 9.1 - how ?

Hi,
http://edocs.bea.com/wls/docs92/rmi/appa.html
states that the Portable Object Adapter (POA) is supported.
How do you deploy and start a servant in WLS 9.2 ? As startup-class? If yes, is the POA integrated in the WLS thread management?
Is the IDL type fixed implemented?
Are there plans to support Portable Interceptors in future releases?
I could not find these topics in the docs.
Thanks,
Juergen Weber

Jurgen Weber <> writes:
http://edocs.bea.com/wls/docs92/rmi/appa.html
states that the Portable Object Adapter (POA) is supported.
How do you deploy and start a servant in WLS 9.2 ? As startup-class? Yes, or init method of a servlet.
If yes, is the POA integrated in the WLS thread management?Yes
Is the IDL type fixed implemented?No. It is not supported by the JDK so we do not support it either.
Are there plans to support Portable Interceptors in future releases?I would say its unlikely at this juncture
I could not find these topics in the docs.andy

Similar Messages

Problem while deploying ADF application to standalone WLS server

Hi,
I am facing a problem while deploying ADF application to standalone WLS Server.
Following is the error message that I am getting.
[07:24:03 PM] ---- Deployment started. ----
[07:24:03 PM] Target platform is (Weblogic 10.3).
[07:24:07 PM] Retrieving existing application information
[07:24:08 PM] Running dependency analysis...
[07:24:08 PM] Building...
[07:24:13 PM] Deploying 2 profiles...
[07:24:14 PM] Wrote Web Application Module to D:\WorkSpace3\DashboardUi\deploy\Dashboard.war
[07:24:14 PM] Wrote Enterprise Application Module to D:\WorkSpace3\deploy\Dashboard.ear
[07:24:14 PM] Deploying Application...
[07:24:22 PM] [Deployer:149191]Operation 'deploy' on application 'Dashboard' is initializing on 'msDevServer1'
[07:24:27 PM] [Deployer:149193]Operation 'deploy' on application 'Dashboard' has failed on 'msDevServer1'
[07:24:27 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Dashboard on msDevServer1.: .
[07:24:27 PM] Weblogic Server Exception: weblogic.application.ModuleException:
[07:24:27 PM] Caused by: weblogic.common.ResourceException: DataSource DashboardDb already exists
[07:24:27 PM] See server logs or server console for more details.
[07:24:27 PM] weblogic.application.ModuleException:
[07:24:27 PM] #### Deployment incomplete. ####
[07:24:27 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)Any suggestion how to fix this.
Thanks
Ajay

I logged into console and browsed to 'Home >Summary of JDBC Data Sources' but not able to locate DashboardDb. Please let me know where to find DashboardDB on wls console.
Also, please let me know how to configure the app to not to auto-deploy JDBC data sources

I have deploy an EJB in weblogic 6.1,but how to use jsp to invoke the EJB's method?

i have deploy an EJB in weblogic 6.1,but how to use jsp to invoke the EJB's method?
thanks!

You'd do something like:
<%
//vvv this part can potentially be done in initialization
Context ctx = getInitialContext();
BeanHome home =
(BeanHome)PortableRemoteObject.narrow(ctx.lookup("the.jndi.name"),
BeanHome.class);
Bean b = home.create();
//^^^
Result r = b.invokeMethod();
%>
"toxin" <[email protected]> wrote in message
news:3d2e95e5$[email protected]..
>
i have deploy an EJB in weblogic 6.1,but how to use jsp to invoke theEJB's method?
thanks!

Help!! - Unable to use the Application Module Deployed as Corba Object in Oracle 8i

I have been able to successfully deploy an Application Module in Oracle 8i but i am un able to get a reference to the Application Module from the database the code used by me is -
package client;
import javax.naming.Context;
import javax.naming.InitialContext;
import java.util.Hashtable;
import oracle.jbo.*;
import org.omg.CORBA.*;
public class Corba8IClient{
Hashtable env = new Hashtable();
ApplicationModule appMod = null;
String theAMDefName = "test/jd/freshJBO.FreshJBOModule";
public Corba8IClient() {
System.out.println("Started...");
// Load the Application Module
try{
// Component deployed to Oracle8i CORBA Server.
// Set up the 8i environment
System.out.println("Setting up initial Context...");
env.put(Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_ORACLE8I);
env.put(Context.SECURITY_PRINCIPAL, "jd");
env.put(Context.SECURITY_CREDENTIALS, "jd");
env.put(JboContext.HOST_NAME, "Dev51");
env.put(JboContext.CONNECTION_PORT, "2481");
env.put(JboContext.ORACLE_SID, "ORA8I");
// env.put(JboContext.APPLICATION_PATH, "test/jd/");
System.out.println("Getting initial Context.");
Context ic = new InitialContext(env);
System.out.println("Doing Lookup...");
ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(theAMDefName);
System.out.println("Calling create...");
// home
System.out.println("Home Class Name : "+home.getClass().getName());
oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome am = (oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome)home;
System.out.println("DefName "+am.getDefName());
appMod = home.create();
System.out.println("Setting up connetion from AppMod to database...");
appMod.getTransaction().connect("jdbc:oracle:thin:jd/jd@dev51:1521:ORA8I");
}catch(Exception e) {
e.printStackTrace();
System.out.println("AppMod full Name "+ appMod.getFullName());
public ApplicationModule getAppMod(){
return appMod;
public static void main(String args[]){
Corba8IClient c8c = new Corba8IClient();
after running the output is -
Started...
Setting up initial Context...
Getting initial Context.
Doing Lookup...
Diagnostics: Silencing all diagnostic output (use -Djbo.debugoutput=console to see it)
Calling create...
Home Class Name : oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome
DefName null
oracle.jbo.ApplicationModuleCreateException: JBO-25222: Unable to create application module.
at oracle.jbo.client.remote.corba.CORBAApplicationModuleHomeImpl.create(CORBAApplicationModuleHomeImpl.java:63)
at client.Corba8IClient.<init>(Corba8IClient.java:39)
at client.Corba8IClient.main(Corba8IClient.java:53)
java.lang.NullPointerException
at client.Corba8IClient.<init>(Corba8IClient.java:45)
at client.Corba8IClient.main(Corba8IClient.java:53)
Corba Object is deployed as -
ObjectName = /test/jd/freshJBOModule
Server Class = freshJBO.server.o8.FreshJBOModuleServerO8
Helper Class = oracle.jbo.common.remote.corba.RemoteApplicationModuleHomeHelper
The Application Module conatians an entity object and a view object for Dept Table in schema jd(Username -jd, Password -jd).

Moneesh,
I believe there is a problem with the way you set the variable theAMDefName. It should be:
String theAMDefName = freshJBO.FreshJBOModule";
Then you need to reinstate the line you commented out, to set the application path (but remove the trailing / from the path, as shown):
env.put(JboContext.APPLICATION_PATH, "test/jd");
If that doesn't work, and for future reference, I suggest testing your deployed application module from the Business Component Browser (aka the tester) before trying your hand-coded client. Start the tester, select Oracle8i as the middle tier server type, make sure the other information in the connect window is correct, then click Connect.
Good luck
Blaise

Deploying simple HTML page to WLS 10.3.6 fails with HTTP response code: 502

- I created a simple HTML page and want to test deployment to WLS 10.3.6 on Linux. I created WAR file and when using JDev 11.1.1.4.0 to deploy to WebLogic Server, it fails to deploy. Full errors/messages are:
[04:40:56 PM] ---- Deployment started. ----
[04:40:56 PM] Target platform is (Weblogic 10.3).
[04:40:59 PM] Retrieving existing application information
[04:40:59 PM] Running dependency analysis...
[04:40:59 PM] Building...
[04:40:59 PM] Deploying profile...
[04:40:59 PM] Wrote Web Application Module to C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war
[04:41:01 PM] Deploying Application...
[04:41:01 PM] Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\DOCUME~1\NGOLDR~1.LAT\LOCALS~1\Temp\SimpleHTML.war' for the application 'SimpleHTML' could not be loaded to the server 'http://dupe:7031/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 502 for URL: http://dupe:7031/bea_wls_deployment_internal/DeploymentService
[04:41:01 PM] See server logs or server console for more details.
[04:41:01 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war' to 't3://dupe:7031'
[04:41:01 PM] #### Deployment incomplete. ####
[04:41:01 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
- The Application Server connection is accessible within JDev. 'dupe' is my server name and it's running RH 5.4
- Any help or suggestions appreciated, although I've already asked Mr. Google without success.
Thanks in advance,
Neville

HTTP response code 502 means temporarily overloaded.
I would say that we have to check the deployment error on the weblogic server logs located at <Domain_Home>\servers\dupe\logs\dupe.log
Check for any errors like OutOfMemory etc OR any deployment failures.
If possible, try accessing the console at http://dupe:7031/console
Check if you are able to successfully deploy your application using the console.
From the error it looks like the "dupe" server might not be healthy. So, the log file would really help here to get clues into the root cause.
Arun

'weblogic.application.ModuleException:'while deploying the EAR file to WLS

Hi
i am trying to deploy the ADf11g app on to external WLS 10.3 server.
My WLS is having the shared libraries .so i didn't include the liibraries in WAR.
while deploying i am facing errors.
My domain log:
Nov 12, 2008 2:40:30 PM EST     J2EE     Warning     BEA-160195     The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dep2EARapplication1 is not versioned.
     Nov 12, 2008 2:40:30 PM EST     HTTP     Error     BEA-101371     There was a failure when processing annotations for application F:\oracleWls\user_projects\domains\sailu1base_domain\servers\AdminServer\tmp\_WL_user\Dep2EARapplication1\6e738n\Dep2webapp1.war. Please make sure that the annotations are valid. The error is org.apache.myfaces.trinidad.webapp.ResourceServlet
     Nov 12, 2008 2:40:30 PM EST     Deployer     Error     BEA-149265     Failure occurred in the execution of deployment request with ID '1226518830484' for task '4'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root'' weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
     Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149004     Failures were detected while initiating deploy task for application 'Dep2EARapplication1'.
     Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149078     Stack trace for message 149004 weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
     Nov 12, 2008 2:40:30 PM EST     Console     Error     BEA-240003     init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
     Nov 12, 2008 2:41:04 PM EST     netuix     Warning     BEA-423420     Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29.
Can anyone plz tell me why i am getting errors.
what is the 'weblogic.application.ModuleException:' error.
and the HTTP error.

Hi,
My EAR file size is about 25 MB.this size is becoz of libraries.so i decided to make a jar file of all libraries.and i installed that jar as library on wls10.3. so that my ear apps later refer this jar.by this no need to include the libraries in every EAR and also size of ear is reduced.
In my weblogic-application.xml file i refer this jar using the <library-ref> tag.when i am trying to install ear file i am facing this weblogic.application.ModuleException: error as posted above .
Can you tell me where i went wrong.
Is the way i am doing is right or not.

Deploy same EAR twice in WLS

Hi,
I have an application developed under Jdev 11g.
I prepared my ear file.
I need to deploy the ear file twice on the same WLS.
I deployed the first time.
The second time i was told that the context "CGB" is already user.
I created a deployment plan where i changed the context root to "DEMO" and updated the deployment to take into consideration the deployment plan "PLAN.XML"
Still when i start the deployment, i always get the its is is use.
Kindly advice the nature of the problem.
A document or link to this case is highly appreciated.
Thank you in advance
Emile BITAR
Edited by: ebitar on May 22, 2009 2:11 AM

I think I would first only deploy the EAR with the modified context root from the deployment plan. Verify that the deployment plan actually worked by verifying the application is only available from the modified context root (and not the old one). Assuming that shows no issues, now deploy the original EAR and see what happens.

Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices 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://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" 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://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
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/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi again,
I got it - i've forgot the namespace prefix for the wsdl-port.
Now it works.
Thanks!
"Ben" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices 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://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" 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://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
>
>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
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/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Corba - differences between WLS 7.02 / WLS 8.1

In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an exception
on the last line (see the log below). Would someone have a clue why it’s not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM : exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)

"Alain Pigeon" <[email protected]> wrote:
>
In WLS 7.02 the following piece of code works, but in WLS 8.1 I get an
exception
on the last line (see the log below). Would someone have a clue why it’s
not working
with WLS 8.1
Note: if you want to send me an email, remove the NOSPAM
TIA !
public OimSessionInstance openSession() throws EomSessionException {
Properties props = new Properties();
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");
EomSessionException: class EomSession, method corbaConnection to OIM
: exception
: org.omg.CORBA.MARSHAL: Exception waiting for response; nested exception
is:
java.io.EOFException: GIOP protocol error vmcid: 0x0 minor
code: 0
completed: No
at EomDefaultConnection.openSession(EomDefaultConnection.java:114)
at EomSession.<init>(EomSession.java:78)Found a solution:
In WLS7.0 the code automatically returned the SUN ORB found in the rt.jar. But
in WLS8.1 you have to force it to the SUN ORB by specifying it in the properties
file used to instantiate the ORB.
Example:
public OimSessionInstance openSession() throws EomSessionException {
String ORBClassName = "com.sun.corba.se.internal.iiop.ORB";
String ORBSingletonClassName = "com.sun.corba.se.internal.corba.ORBSingleton";
Properties props = new Properties();
props.put("org.omg.CORBA.ORBClass" , ORBClassName);
props.put("org.omg.CORBA.ORBSingletonClass" , ORBSingletonClassName);
props.put("org.omg.CORBA.ORBInitialPort", (new Short(corbaPortNumber)).toString());
props.put("org.omg.CORBA.ORBInitialHost", serverHost);
try {
orb = ORB.init((String[]) null, props);
String[] services = orb.list_initial_services();
// setting up the CORBA stuff
org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService");

List deployed webservices / webapps in one WLS domain

Is there a way to list all of the deployed webservices through JMX in one WLS domain,
or list all of the deployed web applications which contains a web service. Thanks,
M.

Yes, look for WebServiceComponentMBeans.
-- Rob
Mat wrote:
Is there a way to list all of the deployed webservices through JMX in one WLS domain,
or list all of the deployed web applications which contains a web service. Thanks,
M.

Read the version of deployed EAR modules via JMX (WLS 10.0)

Hello
We are deploying some EAR components into a WLS 10.0. Now we want to monitor the version number of the deployed EARs via a JMX client. The version number is provided in the manifest of the EAR (Implementation-Version).
I read through some JMX related documents by BEA and searched the web, but I could not find any information on how to read the version.
Does anybody know how to do that or where to look in order to get the version numbers of the deployed components via JMX? Do I have to write my own MBean offering this version attribute?
Every hint is welcomed!
Thanks
Toni
Edited by: user10451156 on Oct 21, 2008 10:53 AM

Hi, Toni.
The input must be a externally provided version number, if you have no access to write manifest entries, or to the deployment process.
If this version number is already set in the ear file, you can use this process inside your custom mbean (an elaboration of Benoit's suggestion)
1 look up the application component from JMX
* http://edocs.bea.com/wls/docs100/wlsmbeanref/mbeans/AppDeploymentMBean.html
2 obtain the path of the ear file
3 open a JarURLConnection to this ear
* http://java.sun.com/javase/6/docs/api/java/net/JarURLConnection.html
4 read the implementation version, which was already provided.
* http://java.sun.com/javase/6/docs/api/java/util/jar/Attributes.Name.html#IMPLEMENTATION_VERSION
Sadly, this won't pop-up on the WLS console, you'd have to write or use a custom extension to do that.
* https://wls-console-extensions.projects.dev2dev.bea.com/
I hope this helps.
-Adrian

Failure deploying FOD app to standalone WLS

I consistently get the following message when trying to run the Fusion Order Demo application on a standalone WLS
<BEA-101371> <There was a failure when processing annotations for application C:\JDev_projects\FOD_11\StoreFrontModule\StorefrontUI\deploy\StoreFrontWebApp.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet>
I performed a "clean all" then used the delivered deployment descriptor to build the war.
From the standalone WLS I accessed the Admin Console and tried to install the war.
I saw an earlier post about this, but not sure it was resolved for this reason (Re: Problem in running the Fusion Store Front demo..)
Has anyone else encountered this and have a solution?

Hi Lynn,
I rebuilt all projects under the StoreFronModule workspace.
I can run the app just fine when deployed to the integrated WLS, but still not when I generate an EAR and deploy on and stand-alone.
The connection.xml looks good. Here it is with some of the urls x'ed out.
<?xml version = '1.0' encoding = 'UTF-8'?>
<References xmlns="http://xmlns.oracle.com/adf/jndi">
<Reference name="FOD" className="oracle.jdeveloper.db.adapter.DatabaseProvider" credentialStoreKey="FOD" xmlns="">
<Factory className="oracle.jdeveloper.db.adapter.DatabaseProviderFactory"/>
<RefAddresses>
<StringRefAddr addrType="subtype">
<Contents>oraJDBC</Contents>
</StringRefAddr>
<StringRefAddr addrType="user">
<Contents>FUSIONOD</Contents>
</StringRefAddr>
<StringRefAddr addrType="hostname">
<Contents>xxxx.xx.xxxx.xxxx.edu</Contents>
</StringRefAddr>
<StringRefAddr addrType="port">
<Contents>1711</Contents>
</StringRefAddr>
<SecureRefAddr addrType="password"/>
<StringRefAddr addrType="serviceName">
<Contents>xxxx.xxxx.xxxx.edu</Contents>
</StringRefAddr>
<StringRefAddr addrType="DeployPassword">
<Contents>true</Contents>
</StringRefAddr>
<StringRefAddr addrType="oraDriverType">
<Contents>thin</Contents>
</StringRefAddr>
</RefAddresses>
</Reference>
</References>
Here is the full listing of entries in the AdminServer-diagnostic.log for the intial startup of the app:
[2008-11-07T09:15:35.796-06:00] [AdminServer] [NOTIFICATION] [J2EE JMX-46010] [oracle.as.jmx.framework.PortableMBeanFactory] [tid: 11] [APP: FODDS] [arg: class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl] JMX Portable Framework initialized with platform SPI "class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl"
[2008-11-07T09:16:08.187-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 11] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:18:31.880-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 12] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:19:07.459-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 15] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:20:33.571-06:00] [AdminServer] [WARNING] [ADFC-54008] [oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl] [tid: 12] [APP: StoreFrontModule] [arg: oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder] ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
[2008-11-07T09:20:34.118-06:00] [AdminServer] [NOTIFICATION] [ADFC-60001] [oracle.adfinternal.controller.util.model.AdfmInterface] [tid: 12] [APP: StoreFrontModule] ADFc: BindingContext is not present, not using ADFm APIs for DataControlFrames.
[2008-11-07T09:20:34.337-06:00] [AdminServer] [NOTIFICATION] [ADFC-50009] [oracle.adfinternal.controller.metadata.provider.MdsMetadataResourceProvider] [tid: 12] [APP: StoreFrontModule] ADFc: Controller caching of MDS metadata resources ENABLED.
[2008-11-07T09:20:34.696-06:00] [AdminServer] [NOTIFICATION] [ADFC-52039] [oracle.adf.controller.internal.metadata.MetadataService] [tid: 12] [APP: StoreFrontModule] [arg: /WEB-INF/adfc-config.xml] ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
[2008-11-07T09:20:53.962-06:00] [AdminServer] [NOTIFICATION] [ADFC-52039] [oracle.adf.controller.internal.metadata.MetadataService] [tid: 11] [APP: StoreFrontModule] [arg: /WEB-INF/adfc-config.xml] ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
[2008-11-07T09:20:54.806-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.security] [tid: 11] [APP: StoreFrontModule] Unable to locate the credential for key FOD in C:\weblogic\user_projects\domains\base_domain\config\oracle.
[2008-11-07T09:20:54.806-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.jndi.ReferenceStoreHelper] [tid: 11] [APP: StoreFrontModule] Incomplete connection information
[2008-11-07T09:21:05.713-06:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.renderkit.rich.NavigationPaneRenderer] [tid: 11] [APP: StoreFrontModule] Warning: There are no items to render for this level
I hope this gives you more info to diagnose the deployment problem. Thank you.

How to create and deploy a war file on wls using the console

          my question is how to deploy the simpleSession.jsp example in the weblogic/samples/examples/jsp/
          dir examples as a war file on wls cluster what are the steps to do so.. thanks
          in advance


[att1.html]

Can not Deploy struts web app on WLS 8

Hi
We are trying to migrate the struts web app from WLS 6 into WLS 8, but keep getting
exception: org.apache.commons.digester.Digester startElement
When I use blank struts-config.xml, the web app can be deployed without exception.
but when I use the struts-config.xml we are supposed to use ( had been deployed
on WLS6 and WLS7 for production), I get the exception.
Please can anybody help? Thanks
Chun
Nov 3, 2003 10:00:35 AM org.apache.commons.digester.Digester startElement
SEVERE: Begin event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.beanutils.PropertyUtils.setSimpleProperty(Property
Utils.java:1789)
at org.apache.commons.beanutils.PropertyUtils.setNestedProperty(Property
Utils.java:1684)
at org.apache.commons.beanutils.PropertyUtils.setProperty(PropertyUtils.
java:1713)
at org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:101
9)
at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:808)
at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule
.java:259)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at weblogic.apache.xerces.parsers.AbstractSAXParser.startElement(Abstrac
tSAXParser.java:459)
at weblogic.apache.xerces.impl.xs.XMLSchemaValidator.startElement(XMLSch
emaValidator.java:591)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XML
NamespaceBinder.java:877)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamesp
aceBinder.java:569)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDVa
lidator.java:727)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartE
lement(XMLDocumentFragmentScannerImpl.java:759)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
ntentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
nt(XMLDocumentFragmentScannerImpl.java:329)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
n.java:525)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
n.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXPar
ser.java:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionSe
rvlet.java:1006)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet
.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(Servl

Here is the struts-config.xml. I only add
<form-bean name="batchQueryForm"
type="web.struts.batch.forms.BatchQueryForm"/>
into the blank struts-config.xml, then I get the exception
org.apache.commons.digester.Digester startElement
SEVERE: Begin event threw exception
Here is the struts-config.xml:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE struts-config PUBLIC
"-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
<struts-config>
<form-beans>

<form-bean name="batchQueryForm"
type="web.struts.batch.forms.BatchQueryForm"/>

</form-beans>
<global-forwards>
<forward
name="welcome"
path="/Welcome.do"/>
</global-forwards>
<action-mappings>
<action
path="/Welcome"
type="org.apache.struts.actions.ForwardAction"
parameter="/pages/Welcome.jsp"/>
</action-mappings>
<controller
processorClass="org.apache.struts.tiles.TilesRequestProcessor"/>
<message-resources parameter="resources.application"/>

<plug-in className="org.apache.struts.tiles.TilesPlugin" >
<set-property property="definitions-config"
value="/WEB-INF/tiles-defs.xml" />
<set-property property="moduleAware" value="true" />
<set-property property="definitions-parser-validate" value="true" />
</plug-in>

<plug-in className="org.apache.struts.validator.ValidatorPlugIn">
<set-property
property="pathnames"
value="/WEB-INF/validator-rules.xml,/WEB-INF/validation.xml"/>
</plug-in>
</struts-config>
"Deepak Vohra" <[email protected]> wrote:
>
Could you post your struts-config.xml file.
thanks,
Deepak
"Chun" <[email protected]> wrote:
Hi
We are trying to migrate the struts web app from WLS 6 into WLS 8, but
keep getting
exception: org.apache.commons.digester.Digester startElement
When I use blank struts-config.xml, the web app can be deployed without
exception.
but when I use the struts-config.xml we are supposed to use ( had been
deployed
on WLS6 and WLS7 for production), I get the exception.
Please can anybody help? Thanks
Chun
Nov 3, 2003 10:00:35 AM org.apache.commons.digester.Digester startElement
SEVERE: Begin event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.beanutils.PropertyUtils.setSimpleProperty(Property
Utils.java:1789)
at org.apache.commons.beanutils.PropertyUtils.setNestedProperty(Property
Utils.java:1684)
at org.apache.commons.beanutils.PropertyUtils.setProperty(PropertyUtils.
java:1713)
at org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:101
9)
at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:808)
at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule
.java:259)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at weblogic.apache.xerces.parsers.AbstractSAXParser.startElement(Abstrac
tSAXParser.java:459)
at weblogic.apache.xerces.impl.xs.XMLSchemaValidator.startElement(XMLSch
emaValidator.java:591)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XML
NamespaceBinder.java:877)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamesp
aceBinder.java:569)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDVa
lidator.java:727)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartE
lement(XMLDocumentFragmentScannerImpl.java:759)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
ntentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
nt(XMLDocumentFragmentScannerImpl.java:329)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
n.java:525)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
n.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXPar
ser.java:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at org.apache.commons.digester.Digester.parse(Digester.java:1548)
at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionSe
rvlet.java:1006)
at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet
.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(Servl

Unable to deploy oracle portal app on wls 10.3

I was deploying an Oracle Portal 10.3 app (a very simple one) exported in EAR file onto WLS 10.3 through WLS admin console. When I went through Deployments -> Install -> Locate deployment -> Install this deployment as an application -> Select deployment targets -> Finish and tried to "activate chagnes", it said "Object Deleted - The object that you were viewing has been deleted, either by you or another user. Please make another selection.", therefore no deployment was successful. Can anyone explain why and how to fix it?

Since you deployed the application 'successfully', but are unable to activate the deployment, there could be several things reasons which you can find out only after looking at the Server log file.
Look at <domain_folder>/servers/AdminServer/logs/AdminServer.log
It is unlikely that you have a missing shared library on your WLP installation - because errors like that are caught before you reach the stage of 'activation'.
Regards
Prashanth

Deploy a Corba POA in WLS 9.1 - how ?

Similar Messages

Maybe you are looking for