Description
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.