[
https://issues.jboss.org/browse/SEAMFACES-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588618#comment-12588618
]
Shane Bryzak commented on SEAMFACES-33:
---------------------------------------
I like @ViewConfig also, it's less ambiguous than @ViewData. The <f:metadata>
idea is great, I really like it. For now though, let's just go with the
enum-based configuration and proceed as you suggest Brian by creating a
separate JIRA feature request for alternative configuration options.
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
