I'm having issues with the migration of applications from WAS 7.0.0.37 to WAS 8.5.5.9. Getting the following error: WSVR0212W: Library, com.ibm.ws.jsf.RI1_2, defined in deployment.xml does not exist.
is defined in deployment.xml for WAS 8.5.5. JSF implementation is set Sun Reference Implementation 1.2 .
FYI, reference to com.ibm.ws.jsf.RI1_2 is not in WAS 7 deployment.xml.
Hello @SJD_SA;
Can you check the application's deployment.xml file on tWAS v7? deployment.xml location:
EAR_PROJECT>\META-INF\ibmconfig\cells\defaultCell\applications\
defaultApp\deployments\defaultApp
deployment.xml location and informations
Application may require the sun ri 1.2.
Best Regards.
Answer by SJD_SA (1) | Jul 30, 2016 at 01:04 PM
As I mentioned, the WAS 7 deployment.xml does not contain the reference to com.ibm.ws.jsf.RI1_2.
Hello @SJD_SA;
That technote can be useful. Can you check it? It is mentioned about tWAS 7 to tWAS 8.5 deployment operation.
The EAR is an embedded EAR (EAR with deployment.xml). During
deployment the code assumes that the resource adapter (RA)
definition should have a <propertySet> element in the
deployment.xml and tried to read the properties in it. This
assumption caused the NullPointerException.
In WebSphere Application Server (WAS) v7 the embedded
deployment.xml is handled differently, hence there were no
issues in deploying the sample EAR in WAS v7.
A workaround to proceed with the deployment can be achieved by
applying one of the following modifications:
1) add a <propertySet> element and set of properties, if any,
to the RA definition in the deployment.xml in the EAR
-or-
2) if the deployment.xml can be ignored
a) remove the deployment.xml from the EAR, or
b) uncheck the processEmbeddedConfig option during
deployment, which will make the deployment logic
ignore the deployment.xml
Best Regards.
Answer by Cindy High (111) | Aug 01, 2016 at 08:41 AM
In WAS V8, the default JSF engine changed from JSF SunRI to MyFaces 2.0. In v8.5.5, you can configure the server to continue to use the SunRI engine (in v9 it is removed). Some of the application artifacts that can indicate use of the SunRI include:
If a web.xml file contains a listener-class with the value com.sun.faces.config.ConfigureListener
If a web.xml file contains a servlet-class with any of these values: javax.faces.webapp.FacesServlet com.sun.faces.ConfigureListener org.apache.myfaces.StartupConfigureListener com.ibm.faces.webapp.JSResourceServlet
If the file is an XML file, and its root element is faces-config and has no DTD information
If the file is an XML file, and its root element is faces-config and has DTD information with a system ID set to: http://java.sun.com/dtd/web-facesconfig_1_0.dtd or http://java.sun.com/dtd/web-facesconfig_1_1.dtd
If Java code has references to the com.sun.faces package
Cindy
Answer by SJD_SA (1) | Aug 04, 2016 at 05:25 AM
I have resolved issue by modifying deployment.xml and it now mirrors WAS 7.0 deployment.xml. The migration process is not perfect. There were a few things I needed to fix with the app server and application configuration. With these changes the applications are functioning normally.
Thank you for all responses.
Steve