Deploy to Standalone WLS 10.3.5 java.lang.ClassNotFoundException:

Question

Hi there, I am having a problem with my upgraded application and upgraded WLS server.
I am really hoping that someone can help me out here.... I simply can't get it to deploy.
Basically I had no deployment issues ever, with 11.1.1.4 and WLS 10.3.4 with deployments. I have since upgraded my JDEV application to 11.1.2 and also our standalone WLS server to 10.3.5. I believe that all post patches (upgrade ADF and the Sherman patch) have been applied. I can see the JSF 2.0 library under deployments and these are correctly targeted.
When I attempt to deploy now, the following error message is recieved:
[08:30:46 AM] [Deployer:149191]Operation 'deploy' on application 'HROpenView_application1' is initializing on 'wls_adf1'
[08:31:02 AM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'CEL'
[08:31:02 AM] Caused by: java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.TrinidadConverterELTag
[08:31:02 AM] See server logs or server console for more details.
[08:31:02 AM] weblogic.application.ModuleException: Failed to load webapp: 'CEL'
[08:31:02 AM] Deployment cancelled.
[08:31:02 AM] ---- Deployment incomplete ----.
[08:31:02 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I have read the following note:
when deplying ear file in weblogic  getting this error
However this seems to be relevant to someone trying to deploye on weblogic 10.3.4. Is there something specific here that I can be looking at? It works fine on the integrated server.
I have checked my project libraries, and ADF Faces runtime 11 and Trinidad Faces Runtime 11 are both included and ticked. Is there something on the server that I need to be looking for? Does anyone know what the deployment library name is?
Cheers,
Simon
Edited by: Simo on Oct 20, 2011 2:11 PM

Answer 1

Simon,
your test application should be simple but not blank. If you're using BC in your other application, you should add a table (EO) and a VO. A minimal UI e. g. the vo as table on a jsf page should be enough.
If this works on the stand alone wls know that the server is running OK.
The em or enterprise manager is an application to manage one or more wls serves our cluster of serves. This em is part of the installation. When You instal the adf runtime in a server, our extend an on, you should see a check box to install the em in the server. This its am option, you don't need to do this, but my experience is that if em runs OK, the adf runtime installation is OK.
If the em its installed, you should see an application named em on the server. If this app is in running state OK you can it with the same url you use to start the admin console, only you write em instead of condole at three end of the url.
Timo