[
http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12356362 ]
Chris Rudd commented on JBSEAM-715:
-----------------------------------
I also have a need for multiple pages.xml. These are done as a per-directory pages.xml.
Theoretically this is simple to implement, subclass the Pages component, override the
initialization method so that it find all your pages.xml files, and calls parse for each
one.
In practice its not that easy as most of the methods in the Pages component are private.
Because of this the only solution is to lift the entire class, and then add your
additional logic to the initialization method.
What would be helpful is if the parse routine was made protected or even better expose it
as a public so that one could write a helper component that used the Pages component to
register any additional pages.xml that were needed.
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL:
http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Currently it's possible to use one global pages.xml file or one file per page. I
believe that both options are not well-suited for large applications.
Consider an application like:
/catalog/foo.xhtml
/bar.xhtml
/...
/basket/foo.xhtml
/bar.xhtml
/...
/admin/foo.xhtml
/bar.xhtml
/...
In this case using a global file would be too convoluted, but at the same time one file
per page is too fine grained.
It would be great to allow one file per directory ("module"), either using a
similar naming convention to page.xml or by adding an "import" tag to pages.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira