I think it depends where the call originates. But most of the method invocation is in Component (that is where all bijection (@In, @Out, DataBinder, Logger etc.) occurs AFAICS).
It looks like AbstractSeamPhaseListener.callPageActions() deals with page actions as defined in pages.xml.
pete> yeah tahts what i thought.
And i realize the component stores all the attributes surrounding.
But just trying to figure out the sequence flow .... andi think i am missing a disconnect where the SeamPhaseListner calls and the POJO/EJB is called ... which i realise the SeamListener is responsible for the storing of the context objects in the EJB.
Just cant seam to find where it would actually mkae hte call that hey .. call the component.
The SeamInvocationContext seems just for EJBs
- SeamInterceptor deals with injection into objects (delegates to Component)
- SeamPhaseListener does init for JSF requests
- SeamVariableResolver resolves (and loads?) the component for JSF
I for one would be interested to see a more complete list