[
https://jira.jboss.org/jira/browse/JBSEAM-1896?page=com.atlassian.jira.pl...
]
Ian Darwin commented on JBSEAM-1896:
------------------------------------
Dan: Could you please document the interactions of having multiple <page> elements
where one is a wildcard and the other(s) not, for things like login-required? E.g.,
I'd LIKE to be able to do:
<page view-id="*" login-required="true">
<page view-id="/registration/register.xhtml"
login-required="false">
<page view-id="/registration/forgotten-password.xhtml"
login-required="false">
That is, I'd like to provide an "industry-standard" :-) secure-by-default
security stance with clearly defined exceptions... If this is NOT possible at present
please document that fact (and I'll open a Feature Request). If it IS possible please
give an example.
Thanks!!
Documentation for pages.xml
---------------------------
Key: JBSEAM-1896
URL:
https://jira.jboss.org/jira/browse/JBSEAM-1896
Project: Seam
Issue Type: Task
Components: Documentation Issues
Reporter: Pete Muir
Assignee: Dan Allen
Priority: Blocker
Fix For: 2.1.2.CR1
Documentation for pages.xml is missing in places (e.g no mention of begin-conversation
element).
Also, it's still (including navigation!) under the heading Events -> Page Actions
which is odd.
--
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