[
https://issues.apache.org/jira/browse/AXIS2-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505257
]
Glen Daniels commented on AXIS2-1304:
-------------------------------------
NOTE - a big part of fixing this isssue is correctly dispatching (at runtime)
down to the AxisMessage level. This should include fault dispatching. At the
least this means changing the Action->operation mapping we currently have into
an Action->message mapping (you can easily get the operation from the message).
> Enabling engage/disengage modules to AxisMessage
> ------------------------------------------------
>
> Key: AXIS2-1304
> URL: https://issues.apache.org/jira/browse/AXIS2-1304
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: kernel
> Environment: Linux version 2.6.17-gentoo ([EMAIL PROTECTED]) (gcc
> version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1,
> pie-8.7.7.1))
> java version "1.4.2_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
> Reporter: Sanka Samaranayake
> Assignee: Deepal Jayasinghe
> Priority: Blocker
>
> In order to support policies that are attached at message levels, it is
> necessary to enabling module engagement/ disengagement on AxisMessage
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
