[seam-issues] [JBoss JIRA] Commented: (SEAMFACES-33) Create a solution for consolidated page-flow, transactional control, security constraints and URL-rewriting configuration
Brian Leathem (JIRA)
jira-events at lists.jboss.org
Sun Mar 20 19:43:45 EDT 2011
[ https://issues.jboss.org/browse/SEAMFACES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589179#comment-12589179 ]
Brian Leathem commented on SEAMFACES-33:
----------------------------------------
Updates for those following along
1) Class Renames. I renamed @ViewData to @ViewPattern, and everything else is named @ViewConfig[Something], all in the "org.jboss.seam.faces.view.config" package. This naming convention is a strawman proposal - I'd like to get the API working, and put it out there for community feedback.
2) The @ViewConfig annotation enums wan't being picked up by Weld 1.1, so I switched to using an interface, with @ViewPattern annotations on methods. Slightly more cumbersome - but it works!
3) Some ideas for refinements on Security options
1) timing for security enforcement is (depending on request type):
initial | postback = AFTER_RESTORE | BEFORE_INVOKE | BEFORE_RENDER
default timing is
initial = BEFORE_RENDER, postback = AFTER_RESTORE
2) view to redirect to on authentication failure:
1) if not logged in, redirect to a login page
2) if logged in, and auth fails, redirect to an error page by default, with option of providing an "auth failed view" via anotation or parameter
> Create a solution for consolidated page-flow, transactional control, security constraints and URL-rewriting configuration
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SEAMFACES-33
> URL: https://issues.jboss.org/browse/SEAMFACES-33
> Project: Seam Faces
> Issue Type: Feature Request
> Components: Configuration API
> Reporter: Lincoln Baxter III
> Assignee: Brian Leathem
> Priority: Blocker
> Fix For: 3.0.0.Final
>
>
> We need a solution to address consolidated page-flow, transactional control, security constraints, and perhaps URL-rewriting -- all in one place.
> It has been previously discussed that a type-safe API be possible for this - which is definitely preferred over XML configuration:
> http://old.nabble.com/Replacing-pages.xml-td27649799.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list