[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tuscany-dev
Subject:    [jira] [Resolved] (TUSCANY-3822) PolicyHandler.afterInvoke should
From:       "Simon Nash (JIRA)" <dev () tuscany ! apache ! org>
Date:       2011-03-30 8:26:05
Message-ID: 502932437.20937.1301473565732.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/TUSCANY-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Simon Nash resolved TUSCANY-3822.
---------------------------------

       Resolution: Fixed
    Fix Version/s: Java-SCA-1.x

Thanks for the patch. I've applied this to the 1.x trunk under revision r1086734, \
with additional code to ensure that afterInvoke() is called for in-only invocations \
as well as in-out invocations. 

> PolicyHandler.afterInvoke should be called with outbound MessageContext.
> ------------------------------------------------------------------------
> 
> Key: TUSCANY-3822
> URL: https://issues.apache.org/jira/browse/TUSCANY-3822
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Policy
> Affects Versions: Java-SCA-1.6, Java-SCA-1.6.1
> Environment: Tuscany 1.6.1 on Windows platform (2003 and XP).
> Reporter: Gang Yang
> Assignee: Simon Nash
> Fix For: Java-SCA-1.x
> 
> Attachments: Axis2ServiceInOutSyncMessageReceiver.java, Axis2ServiceProvider.java
> 
> 
> Tuscany runtime calls the policy extension method PolicyHandler.afterInvoke() with \
> the inbound MessageContext, but the outbound MessageContext should've been used to \
> process the outbound message.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]