|
I am using MyFaces with Websphere 5.1.1.5. Obviously, this
is a pre 5.2 release and I believe that it uses the JSP 1.2 specification. Using the “normal” classloader mode which is
PARENT_FIRST (I’m not sure if the other app servers use this same
terminology, it indicates that the classloader precedence is application server
on down) everything works fine. I am including both jsp2.0.jar and commons-el.jar
in WEB-INF/lib of the web module. Unfortunately, the classloader mode of the production environment
which I must deploy into is PARENT_LAST Iindicating that the classloader
precedence begins with the web module). Under this classloader mode, all of the
non-faces jsp’s don’t work, I’m not absolutely certain as to
the cause but I think it is because they find the jsp2.0.jar before the
application server’s jsp 1.2 library. Does anyone have any suggestions or workaround? (other than
change the classloader mode ;-) Does MyFaces need the entire jsp2.0.jar or only
part of it? Questo
messaggio di posta elettronica contiene informazioni di carattere confidenziale
rivolte esclusivamente al destinatario sopra indicato. Confidentially
notice. This e-mail transmission may contain legally privileged and/or
confidential information. Please do not read it if you are not the intended recipient(S). |

