| Author |
New JSF project getting javax.faces.context.FacesContextFactory
|
J Miller
Ranch Hand
Joined: Oct 21, 2010
Posts: 62
|
|
Hi, I’m having a problem where my JSF isn’t getting parsed correctly. I’m using IBM RAD, and a WebSphere 7 server. I created this page:
If I try to go to the web page using .xhtml in the URL, I get a blank page, and you can see the tags in the source. If I try to use .faces, I get the exception at the bottom.
Here’s what I’ve done:
- Created a new project using the new > Dynamic web project.
- Right-click the project > Properties > Project Facets, I have the following checked:
Dynamic Web ModuleJavaJavascriptJavaServer Faces (version 1.2)JSTLWebSphere Web (Co-existence)WebSphere Web (Extended)
I went under the build path, and added the following jars to my project:
commons-beanutils-1.7.0.jarcommons-collections-3.2.1.jarcommons-digester-1.8.jarcommons-lang-2.1.jarcommons-logging.jarjsf-api.jarjsf-facelets.jarjsf-impl.jarjstl.jar
Here's my web.xml:
And my faces-config.xml:
Exception:
I've done some searching around and I've tried removing the load-on-startup, and made sure I've got all the correct jar files. Anybody know what I'm doing wrong?
|
 |
J Miller
Ranch Hand
Joined: Oct 21, 2010
Posts: 62
|
|
So just in case anybody else runs into this, I found what I did wrong. When I added my jars for jsf, I went to the build path and put them in there. I went back and took them out of there, and instead just put them in my "lib" folder. Works like a champ.
It's always something simple...
|
 |
Tim Holloway
Saloon Keeper
Joined: Jun 25, 2001
Posts: 14491
|
|
|
Be careful when doing that. WAS has JSF implementation jars built into WebSphere itself and you can get classpath conflicts. Check IBM's documentation for the proper way to build a JSF webapp for WAS.
|
Customer surveys are for companies who didn't pay proper attention to begin with.
|
 |
 |
|
|
subject: New JSF project getting javax.faces.context.FacesContextFactory
|
|
|