Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

any jsf element is not rendering/parsing while migrating to JSF 2.0 from JSF1.2 with myfaces  RSS feed

 
shashank kothari
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hii Friends,


I m trying to migrate JSF 1.2 project with myfaces to JSF 2.0 with myfaces 2.0 jars on weblogic10.3 server.

Found some problem related build and publishing after resolving them when i hitting my application all JSF html tags are coming in browser as it is they are parsed to html tags. all h: tages are coming as it is on my browser they are not converted to html tags for browser display.

problemhas been attached as image.

using myfaces-api-2.0.3.jar
myfaces-impl-2.0.2.jar
tomahawk-1.1.8.jar


Please Help...
error.jpg
[Thumbnail for error.jpg]
 
Tim Holloway
Bartender
Posts: 18705
71
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Shashank!

When a JSF page renders with the all original JSF tags unchanged (instead of as an HTML page), that means that the JSF FacesServlet did not process the page. Meaning that you attempted to submit a URL that didn't have a matching URL-pattern in WEB-INF/web.xml that aimed the URL at the FacesServlet. For example, you'd typically have a pattern like this:


Which would route URLs ending in ".jsf" to the FacesServlet.

If you are migrating from JSF v1, chances are that your page templates were originally ".jsp" files. JSP templates are not supported in JSF2, which uses Facelets (.xhtml) templates. So for a URL such as "http://www.javaranch.com/webapp/accounts/new.jsf", the corresponding resource would be "/accounts/new.xhtml" within the WAR.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!