In my case i was getting a blank page but when i viewed the source i can't find any source generated and no exception thrown. I use a tiles template to load all the required jsp pages with (*.faces extension) In the trace i can see the request getting processed and the appropriate jsp pages with .faces mapping getting compiled but when the response was directed nothing comes up (i felt like some kind of JSP processor issue) but again my workaround works fine for me so i didn't bother to dig deep into it. But in your case clearly looks the myfaces tags are not recognized by the JSP processor. Like simon mentioned please check the Faces Servlet's servlet mapping in your web.xml and make sure it is correct and also when the application starts make sure from the logs that FacesServlet is getting initialized.
thanks, mchandir Simon Kitching-4 wrote: > > > On Sat, 2008-02-09 at 13:37 -0800, Richard Yee wrote: >> Have you viewed the source to your blank page? Do you see the MyFaces >> tags? I am having this problem on the Oracle OC4J external server that >> comes with JDeveloper. The application starts up fine w/o any error >> messages and the requests are getting processed but the tags are not >> getting processed so they appear in the source view of the page. >> > > Are you using JSP pages, but with a ".faces" suffix on urls? > If so, then it looks like you don't have the FacesServlet mapped to > handle ".faces" suffixes, so the container is just serving them as text. > > If .jsp pages are being processed at all, then the jsp engine will try > to execute them as tags and fail if the tag-class cannot be found. As > that is not happening, it looks like you have some wrong config that > means the container is not even recognising them as jsp tags. > > If you are using facelets, then again it looks like you haven't got the > facelets servlet set up. Alternatively, maybe facelets passes tags > through unaltered if it doesn't recognise them; I don't know much about > configuring Facelets correctly. > > In neither case does this appear to be a MyFaces issue. > > Regards, > Simon > > > -- View this message in context: http://www.nabble.com/MyFaces-1.1-not-working-on-Websphere-5.1.1.15-with-Classloader-set-to-PARENT_LAST-tp15192182p15412037.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
