Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Sun, 22 May 2011 06:46:47 +0000 (UTC)
From: "Anjana Fernando (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: 
 <637143441.34142.1306046807532.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2035486689.27947.1305836087459.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AXIS2-5049) Axis2 Services / ServiceGroups Not
 Updating Properly When doing Hot-Update with Transport Session
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anjana Fernando commented on AXIS2-5049:
----------------------------------------

Hi Azeez,

Thank you for pointing that out. I guess, that was anyway a problem that was there in Axis2. And this patch just addresses a unique problem that comes with transport session scoped services. I guess we will later look into that problem more carefully and come with a solution to do that. Hope that's ok. 

Cheers,
Anjana,

> Axis2 Services / ServiceGroups Not Updating Properly When doing Hot-Update with Transport Session
> -------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5049
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5049
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.5.4
>            Reporter: Anjana Fernando
>             Fix For: nightly
>
>         Attachments: AXIS2-5049-Patch.txt
>
>
> The scenario is explained in the following points,
> * AxisService in Transport Session Scope.
> * Incoming request.
> * Create ServiceContext, ServiceGroupContext from AxisService and AxisServiceGroup and store it in SessionContext.
> * SessionContext contains fixed ServiceContext and ServiceGroupContext throughout Transport Session lifetime.
> * Changes to AxisConfiguratio wont be known by SessionContext, removing of services to service group, removing service group.
> * Removing Service Group, removing Service from service group must be communicated to SessionContext, so it can remove the necessory items from itself, and refresh the services / service groups in the next request.
> Because of the above problem, when doing hotupdate, a service which is in transport session will not be updated to the newly deployed service. Also, same for service groups, if a service group was removed and added again, the service group that is in the ServiceGroupContext will be the old service group. 
> Cheers,
> Anjana.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org