[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)]

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

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

Agreed, the "data" part sounds too much like application data.  I think the only way to get away from that is to drop the data word altogether - "meta" alone seems sufficient.

I propose we keep the annotation as @ViewConfig, and rename the data structures:
ViewDataStore => ViewMetaStore 
ViewDataConfiguration => ViewMetaConfiguration

These ViewMeta* classes aren't going to be visible in your run-of-the mill applications anyway.  They'll simply have an enum with the @ViewConfig annotation.

> 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