[
https://issues.apache.org/jira/browse/AXIS2-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040555#comment-13040555
]
Hiranya Jayathilaka commented on AXIS2-5049:
--------------------------------------------
This patch breaks some of the existing stuff. Most significantly the following
change is very dangerous:
public ArrayList<AxisObserver> getObserversList() {
- return observersList;
+ return new ArrayList<AxisObserver>(observers);
}
There are many classes that use the getObserversList method to remove an
already existing observer. With the above change it cannot be used to
unregister observers anymore. There is a definite regression in base transport
and there could be others elsewhere.
> 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-2.txt, 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-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
