[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files

[Fernando Monta?ño (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12353980 ] 
            
Fernando Monta?ño commented on JBSEAM-715:
------------------------------------------

I saw this issue JBSEAM-849 was closed as duplicated, which is good for pages.xml.

But what about components.xml? 
There sould be a similar way (as pages.xml reported in this issue) to configure the components.xml

Regarding Gavin comment:
"What we would support here is searching for a file called pages.xml in all directories in the path to the view id. "

I think there should be an alternative to this. I think is better to have separated to configuration files and the view pages. As you suggest, we will mix the view and configuration in the view part (directory path). But it could be better to have separated configuration an view. I thought.





> 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