[seam-issues] [JBoss JIRA] Commented: (SEAMFACES-33) Create a solution for consolidated page-flow, transactional control, security constraints and URL-rewriting configuration

[Dan Allen (JIRA)]

    [ https://issues.jboss.org/browse/SEAMFACES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588517#comment-12588517 ] 

Dan Allen commented on SEAMFACES-33:
------------------------------------

Not related to the previous comment, for the record, I want to suggest using a different name than ViewData for this feature. I think it's more like ViewInstructions or ViewConfigMetadata. I'm okay with the @ViewConfig annotation. I'm open to other suggestions. The problem with ViewData is that it's too easily confused with application data being stored in the view (component tree).

> 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