On 6/9/06, Mert Çalışkan <
[EMAIL PROTECTED]> wrote:
You can find detailed info here..
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/crun_classload.html
and for the error...
everything is ok in web.xml file for FacesServlet, definition & mapping?
Regards,
Mert
On 6/9/06, Gregg Bolinger <[EMAIL PROTECTED] > wrote:I think I am getting somewhere. I am now getting the following error message when trying to access my application.
Error 404: SRVE0201E: Servlet [javax.faces.webapp.FacesServlet]: not a servlet class
Any ideas?
Thanks.On 6/9/06, Gregg Bolinger < [EMAIL PROTECTED]> wrote:Ok, I have done as you described. I set the war to module and set it as PARENT_LAST. And I am having the same issues. I am going to bounce and server and see if it solves the problem....On 6/9/06, Gregg Bolinger <[EMAIL PROTECTED]> wrote:At the moment? I have none. HA. This is my first experience with a full fledged bonafied app server. I typically only have to deal with containers like Tomcat. If you had a link with information on how to adjust the classloader in the EAR application file, that would be helpful. Until then, I'll be pinging google for it.
Thanks. Much appreciated.On 6/8/06, Mert Çalışkan < [EMAIL PROTECTED]> wrote:If you can determine deployment properties, if you have the rights,
you can specify classloader policy for ear to application and war to module with parent last modes.
when you put all the jars under the web-inf lib of your war, the problem shouldn't arise.
Whats your classloader adjustments at the moment...
Regards,
Mert
On 6/9/06, Gregg Bolinger <[EMAIL PROTECTED] > wrote:Um, can you elaborate?
Thanks.On 6/8/06, Mert Çalışkan < [EMAIL PROTECTED]> wrote:even over the classloader mode and policy?
if you can adjust them for the ear & war you can solve the problem.
Regards,
MertOn 6/9/06, Gregg Bolinger < [EMAIL PROTECTED]> wrote:I know all the issues surrounding running MyFaces in Websphere 6. I searched this mailing list and found plenty of useful tips. However, I am having problems getting any of them to work. If I remove jsf-api.jar and ws-jsf.jar then not only does my app not work, but the server console app stops working.
What I really would like is a solution that doesn't involve doing anything with the websphere install, if possible. I know, unlikely. The thing is that our app will be installed on a Websphere server we have no control over. Is this something that is possible?
Thanks.