[
http://jira.jboss.com/jira/browse/JBSEAM-1631?page=comments#action_12368432 ]
Hung Tang commented on JBSEAM-1631:
-----------------------------------
Hmmm.. So Seam needs to be basically support something like this
@PageActions {
@PageAction(view="/view1.xhtml" if="#{foo1.true}")
@PageAction(view="/view2.xhtml" if="#{foo2.true}")
@PageAction(view="/view3.xhtml" if="#{foo3.true}")
}
The only problem I have with this is that it becomes much more disorganized when trying to
locate all the page actions for a particular view. I need to scan my entire source tree
for /view1.xhtml, for example, to find all the page actions.
add @PageAction annotation to method
------------------------------------
Key: JBSEAM-1631
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1631
Project: JBoss Seam
Issue Type: Feature Request
Components: Tools
Affects Versions: 2.0.0.BETA1
Reporter: Dan Allen
Original Estimate: 2 days
Remaining Estimate: 2 days
I cannot help but to conclude that a page action ought to be able to be declared as an
annotation on a method. Why not? It is very similar to a @WebRemote method in a sense. It
would also eliminate the need for the XML file if you prefer to return view ids directly
in the action handler methods. Think about the love Seam would get by removing the
dependency on the XML for this feature. No XMLHell, remember?
The way it would work is that when Seam spots the annotation during initialization time,
it just registers that method with the Page framework just as if it had found it in the
XML file.
I wouldn't be broken-hearted if this is rejected, but it seems consistent with the
goals of Seam.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira