[
http://jira.jboss.com/jira/browse/JBSEAM-1631?page=comments#action_12368450 ]
Hung Tang commented on JBSEAM-1631:
-----------------------------------
With a centralized XML file that Seam uses, you know all the page-actions will be stored
in one place and it'll be located under a particular view definition which is easily
navigated with basic editors using search. It's much easier to understand and to
maintain over the choice of annotations. I really don't know how users could find it
much more convenient to search for duplicated view-id configuration in different source
files. Yes, "XMLHell" is bad but equally bad is something we're moving
towards: AnnotationHell. Personally, I like it the way it is right now but I don't
believe it's perfect and I also agree with you that I don't like the proposed
syntax in his blog entry. I'm really a fan of "less is more" unless
there's a compelling reason to provide an alternative. But for users "buying
into the whole annotation thing" to me isn't really a compelling reason.
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