[jira] Commented: (AXIS2-4881) Added invoke_stage1 and invoke_stage2 methods to AbstractHandler

["Glen Daniels (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932109#action_12932109 ] 

Glen Daniels commented on AXIS2-4881:
-------------------------------------

Why is it so challenging to simply return from invoke() if you decide you don't need to do anything?  I guess I really don't see the need for this.

> Added invoke_stage1 and invoke_stage2 methods to AbstractHandler
> ----------------------------------------------------------------
>
>                 Key: AXIS2-4881
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4881
>             Project: Axis2
>          Issue Type: Bug
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   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 work.
> Because there is only one invoke method, these separate stages of processing get lumped together.
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org