axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Scheuerle (JIRA)" <>
Subject [jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
Date Wed, 26 Jan 2011 15:45:43 GMT


Rich Scheuerle commented on AXIS2-4881:

Hi folks,


I believe the concept is a good one, which is why I opened the defect.    Please feel empowered
to take ownership of this work and change/improve the implementation.   

My involvement in Axis2 will decrease over the next few months due to my involvement in other


> 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