[
https://issues.apache.org/jira/browse/AXIS2-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986452#action_12986452
]
Ruwan Linton commented on AXIS2-4881:
-------------------------------------
Deepal, this API is wired and this is a commonly used extension point in axis2,
any module will get affected, if we do not properly do the API, so we need to
fix the API before the 1.6 without that fix we cannot do the 1.6 release, so it
is a blocker.
> 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
> 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 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-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
