8:20 a.m.
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
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
8:40 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Peter Muir reassigned JBSEAM-715:
---------------------------------
Assignee: Gavin King
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
9:08 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12353935 ]
Gavin King commented on JBSEAM-715:
-----------------------------------
What we would support here is searching for a file called pages.xml in all directories in
the path to the view id.
We wont add any "import" tag (yew).
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
9:12 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12353937 ]
Stephan Bublava commented on JBSEAM-715:
----------------------------------------
Another idea would be to add a "pageFiles" property (similar to
"ruleFiles" in "RuleBase") so that one can set multiple files in
components.xml:
<core:pages page-files="/WEB-INF/pages.xml,/WEB-INF/more-pages.xml,..."
/>
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
2:04 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ 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
1:13 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12354744 ]
Adam Brod commented on JBSEAM-715:
----------------------------------
We have a need for multiple pages.xml and components.xml in our application. Sometimes in
different directories, sometimes in the same directory with a different name. So I logged
this related defect. http://jira.jboss.com/jira/browse/JBSEAM-968
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
9:48 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ 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
4:36 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Stephan Bublava updated JBSEAM-715:
-----------------------------------
Attachment: multiple-pages-files-patch.txt
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
Attachments: multiple-pages-files-patch.txt
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
4:40 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Stephan Bublava updated JBSEAM-715:
-----------------------------------
Issue Type: Patch (was: Feature Request)
This patch allows multiple pages.xml files to be specified in components.xml, e.g.:
<core:pages page-files="/WEB-INF/pages.xml,/WEB-INF/more-pages.xml" />
If you do not agree with this change, please consider changing the visibility of
Pages.parse(InputStream) to protected, so that I can add the functionality in a subclass.
Thanks,
Stephan
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Attachments: multiple-pages-files-patch.txt
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
1:18 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12363339 ]
Stephan Bublava commented on JBSEAM-715:
----------------------------------------
Would it be possible to include this in Seam 1.3?
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Attachments: multiple-pages-files-patch.txt
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
7:30 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12363366 ]
Adam Brod commented on JBSEAM-715:
----------------------------------
+1 This would really help us out too. We build our application as separate wars (for
different teams) and then include them together at build time. Having multiple pages.xml
would really help us keep our application modular.
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Attachments: multiple-pages-files-patch.txt
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
10:20 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Gavin King updated JBSEAM-715:
------------------------------
Fix Version/s: 1.3.0.ALPHA
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch.txt
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
12:55 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12363662 ]
Hiroyuki Wada commented on JBSEAM-715:
--------------------------------------
I want this feature too.
Moreover, I consider that it's very useful if it can just specify a directory which
include some *-pages.xml, e.g.
<core:pages page-dir="/WEB-INF/pagesdir" />
Core component scan all files under the /WEB-INF/pagesdir and regist *-pages.xml to
Pages component.
This is good for more large applications.
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch.txt
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
2:03 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Hiroyuki Wada updated JBSEAM-715:
---------------------------------
Attachment: multiple-pages-files-patch-2.txt
extension of Stephan Bublava's patch.
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch-2.txt, multiple-pages-files-patch.txt
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
2:11 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12363999 ]
Hiroyuki Wada commented on JBSEAM-715:
--------------------------------------
I extended Stephan Bublava's patch and attached.
This patch allows multiple pages.xml files in directory to be searched automatically.
<core:pages page-files="/WEB-INF/pages.xml,/WEB-INF/pages/" />
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch-2.txt, multiple-pages-files-patch.txt
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
9 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=all ]
Gavin King closed JBSEAM-715.
-----------------------------
Resolution: Done
I applied the first patch, not the second.
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: JBoss Seam
Issue Type: Patch
Components: JSF
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch-2.txt, multiple-pages-files-patch.txt
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
12:12 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-715) Allow multiple pages.xml files
[ http://jira.jboss.com/jira/browse/JBSEAM-715?page=comments#action_12413249 ]
Martin Sznapka commented on JBSEAM-715:
---------------------------------------
in seam 2 it works this way:
<navigation:pages
resources="/WEB-INF/pages.xml,/WEB-INF/more-pages.xml"/>
Allow multiple pages.xml files
------------------------------
Key: JBSEAM-715
URL: http://jira.jboss.com/jira/browse/JBSEAM-715
Project: Seam
Issue Type: Patch
Components: JSF Integration
Affects Versions: 1.1.1.GA
Reporter: Stephan Bublava
Assigned To: Gavin King
Fix For: 1.3.0.ALPHA
Attachments: multiple-pages-files-patch-2.txt, multiple-pages-files-patch.txt
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
5889
days inactive
6364
days old
16 comments
9 participants
participants (9)
-
Adam Brod (JIRA) -
Chris Rudd (JIRA)
-
Fernando Monta?ño (JIRA)
-
Gavin King (JIRA)
-
Hiroyuki Wada (JIRA)
-
Martin Sznapka (JIRA)
-
Peter Muir (JIRA)
-
Stephan Bublava (JIRA)
-
Stephan Bublava (JIRA)