[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
Thu Mar 17 01:31:45 EDT 2011


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

Brian Leathem commented on SEAMFACES-33:
----------------------------------------

At first glance, the @ViewConfig enum and view data store solution seems like a great fit.

I would like to see support for configuring the ViewData via tags in the facelet metadata.  Brainstorming with Stuart, it seems reasonable to have a phase listener that parses the component tree of a view, and dynamically builds the ViewData on first visit.

We would then be able to support ViewData configuration via the @ViewConfig enum, as well as <f:metadata> tag overrides for transactional control, security constraints and URL-rewriting.  This would be ideal in my opinion.

However, pursuing the metadata tag configuration should be treated with a separate issue (possibly post 3.0.0.Final), and we should focus on creating the annotations and phase listeners to support security constraints and URL-rewriting.  (Stuart has already created the annotations, and a phase listener for transactional control.)

> 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