Yeah, this is something I'm interested in.
I know you can have a per-page xml file, but one problem is that there is still some shared stuff that must go in pages.xml like the elements that define the conversation ids using business ids. These cannot go in xyz.page.xml files, and chances are that they are shared across multiple pages anyway.
I don't know so much about a pages component, but being able to specify one or more pages.xml files would be nice since then you can split out the conversation definitions, the login/logout and exception logic, and maybe even combine the pages.xml info for a set of similarly grouped pages into a single file i.e. :
<navigation:pages> <navigation:resources> <value>/WEB-INF/conversations.pages.xml</value> <value>/WEB-INF/common.pages.xml</value> <value>/WEB-INF/inventory.pages.xml</value> <value>/WEB-INF/contacts.pages.xml</value> <value>/WEB-INF/admin.pages.xml</value> </navigation:resources> </navigation:pages>
<navigation:pages> <navigation:resources> <value>...</value> <value>...</value> </navigation:resources> </navigation:pages>
I think there is a similar setting in 1.2.1.
That's just perfect, thanks :)
Wonderful, as usual, I stand corrected!