axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <>
Subject [jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
Date Tue, 25 Jan 2011 13:36:53 GMT


Deepal Jayasinghe commented on AXIS2-4881:

I would not consider this as a blocker.  In addition, it would be great if we can find a good
usecase for this feature, otherwise we do not need to fix this for 1.6 release. 

> Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
> ----------------------------------------------------------------
>                 Key: AXIS2-4881
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>            Reporter: Rich Scheuerle
>            Priority: Blocker
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> Background:
> The AbstractHandler class exposes an invoke() method that Handlers override to provide
the specific invoke code.
> Problem:
> Many Handlers actually have 2 stages of logic.  The first stage simply does some quick
processing to determine if the handler should be called.  The second stage does the actual
> Because there is only one invoke method, these separate stages of processing get lumped
> Solution:
> Provide an alternative (optional) invoke semantic.
> A Handler can choose to override the new invoke_stage1 and invoke_stage2 methods.
> All current Handlers will continue to work.  The existing invoke() method is retained.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message