[
https://jira.jboss.org/jira/browse/JBSEAM-3412?page=com.atlassian.jira.pl...
]
Jakub Janczak commented on JBSEAM-3412:
---------------------------------------
the problem with this task is that, the pages.xml are not processed within the web
application context. The solution might be either moving Pages initialization to somewhere
near SeamListener (where the ServletContext is accessible), or parsing all the
web.xml's from the resources and finding whether there is a context-param called
javax.faces.DEFAULT_SUFFIX.
.page.xml are only loaded for pages with .xhtml extesnion.
----------------------------------------------------------
Key: JBSEAM-3412
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3412
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.BETA1
Environment: JBoss
Reporter: Prashant Kadam
Priority: Minor
Fix For: The future
I have a facelete pages with '.jspx' extension. It seems that pages with only
.xhtml extensions are mapped for page orchestration. Here's the code from
org.jboss.seam.navigation.Pages.java file :
private void parsePages(Set<String> ...fileNames)
{
Set<String> mergedFileNames = new HashSet<String>();
for (Set<String> f : fileNames)
{
mergedFileNames.addAll(f);
}
for (String fileName: mergedFileNames)
{
String viewId = "/" +
fileName.substring(0,fileName.length()-".page.xml".length()) +
".xhtml"; // needs more here
InputStream stream = ResourceLoader.instance().getResourceAsStream(fileName);
if (stream==null)
{
log.info("no pages.xml file found: " + fileName);
}
else
{
log.debug("reading pages.xml file: " + fileName);
parse(stream,viewId);
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira