[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1432) Rework Lifecycle.beginCall/endCall so that the default InterceptionType works.

[Chris Rudd (JIRA)]

Rework Lifecycle.beginCall/endCall so that the default InterceptionType works.
------------------------------------------------------------------------------

                 Key: JBSEAM-1432
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1432
             Project: JBoss Seam
          Issue Type: Feature Request
          Components: Core
    Affects Versions: 1.2.1.GA, 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1, 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA
            Reporter: Chris Rudd


Currently when invoking components inside a Lifecylce.beginCall / endCall pair, the default InterceptionType results in no-interception.

Consider reworking the beginCall/endCall to allow interception for components using the default interception type  (AFTER_RESTORE_VIEW).

This could be accomlished by either 
a) beginCall manually setting the Lifecyle.setPhaseId( PhaseId.APPLY_REQUEST_VALUES)
b) altering InterceptionType.isActive to treat a null PhaseId as valid for InvocationTypes AFTER_RESTORE_VIEW,AFTER_UPDATE_MODELS and INVOKE_APPLICATION.

Currently the only work around is to either 
a) manually set thte phase if after each call to Lifecycle.beginCall
b) set the @Intercept to ALWAYS on any component that may be used outside a standard faces request.

Both of these approaches are cumbersom when you are working with components that need to be utilized by both foreground (UI request) and background (JMS, scheduled events etc) processes.

-- 
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