]
Gavin King commented on JBSEAM-374:
-----------------------------------
This stuff no longer seems so useful. Especially (1) looks nondoable now.
Normalize the event model
-------------------------
Key: JBSEAM-374
URL:
http://jira.jboss.com/jira/browse/JBSEAM-374
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Currently some events can be handled by either an @Observer method, or a method binding
in events.xml. Ideally we would like this to be true for ALL events, but for now our
integration with JSF and jBPM is not quite that deep. Nevertheless, there are some things
we could do to allow a more consistent model where everything can be handled by either a
method binding or an annotated method:
(1) Rebuild the page actions functionality on top of the Seam event bus - defining
standard org.jboss.seam.page.<viewId> events that can be handled via
@Observer("org.jboss.seam.page./myViewId.xhtml")
(2) Introduce "outcome observers" for JSF: if I have <h:commandButton
action="myOutcome"/>, allow us to handle it using
@Observer("org.jboss.seam.outcome.myOutcome")
(3) Ditto for jBPM: if I have <transition name="myTransition" ... />,
allow us to handle it using @Observer("org.jboss.seam.transition.myTransition")
(4) Finally, introduce annotations layered over @Observer:
@RenderPage("/myViewId.xhtml"), @Outcome("myOutcome"),
@Transition("myTransition")
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: