[seam-issues] [JBoss JIRA] (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
Mon Oct 22 14:17:02 EDT 2012
[ https://issues.jboss.org/browse/SEAMFACES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Leathem updated SEAMFACES-33:
-----------------------------------
Description:
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://lists.jboss.org/pipermail/seam-dev/2010-February/002003.html
http://lists.jboss.org/pipermail/seam-dev/2010-March/002053.html
http://lists.jboss.org/pipermail/seam-dev/2010-July/002812.html
was:
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://lists.jboss.org/pipermail/seam-dev/2010-February/002003.html
http://lists.jboss.org/pipermail/seam-dev/2010-July/002812.html
> 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://lists.jboss.org/pipermail/seam-dev/2010-February/002003.html
> http://lists.jboss.org/pipermail/seam-dev/2010-March/002053.html
> http://lists.jboss.org/pipermail/seam-dev/2010-July/002812.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list