Home/ Questions/Q 6997037
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T20:13:59+00:00

I have recently moved the masterLayout template for a web application into an external

  • 0

I have recently moved the masterLayout template for a web application into an external jar as mentioned in the answer here
Java EE6> Packaging JSF facelets (xhtml) and ManagedBeans as JAR

Since I am not using any managed beans. I haven’t included faces-config.xml in the jar.

I have a local template that extends this masterLayout. The application is running fine. But I noticed that when I open the Debug Output window. The Component Tree does not expand but Scoped Variables does expand nicely. (Before this transition it worked well)

Local Template

ui:composition xmlns=”http://www.w3.org/1999/xhtml”
xmlns:h=”http://java.sun.com/jsf/html”
xmlns:f=”http://java.sun.com/jsf/core”
xmlns:ui=”http://java.sun.com/jsf/facelets”
xmlns:p=”http://primefaces.prime.com.tr/ui”
template=”/templates/masterLayout.xhtml”

index.xhtml

ui:composition xmlns=”http://www.w3.org/1999/xhtml”
xmlns:h=”http://java.sun.com/jsf/html”
xmlns:f=”http://java.sun.com/jsf/core”
xmlns:ui=”http://java.sun.com/jsf/facelets”
xmlns:p=”http://primefaces.prime.com.tr/ui”
template=”/templates/localTemplate.xhtml”

Initially I thought it could be this bug
http://java.net/jira/browse/FACELETS-292
But that was fixed way back in 2008

I am using JSF 2.0.6.FCS, Primefaces 2.2.1. Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I figured out that ..the external project where I was having this masterLayout already was being used for JSF 1.2 project. I just added a JSF 2.0 resource resolver along side with it. So the build script was pulling facelets-1.1.14.jar from that project so JSF2.0 facelets was never being used. So I excluded that jar file from my ivy dependency which solved the problem.

    • 0