[
https://issues.apache.org/jira/browse/AXIS2-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504676
]
Glen Daniels commented on AXIS2-1304:
-------------------------------------
IMO we have to fix this at some point, message-level policies are going to be a
reality in the not-too-distant future. As for whether it's a show-stopper for
1.3... I'm not so sure about that. There is too much to do (both cleanup/fixes
and new features) for us to get everything into 1.3, so I think it would be OK
if we managed to do it in 1.3, and also OK if we got it done for 1.4. We
should investigate it though, if we need any kind of major overhaul we should
scope the work soon.
> 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]
