You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gopalakrishnan (JIRA)" <ji...@apache.org> on 2005/07/05 09:45:11 UTC
[jira] Created: (AXIS2-63) Handling of "application" scope of the service instance is buggy in AbstractMessageReceiver.getTheImplementationObject()
Handling of "application" scope of the service instance is buggy in AbstractMessageReceiver.getTheImplementationObject()
------------------------------------------------------------------------------------------------------------------------
Key: AXIS2-63
URL: http://issues.apache.org/jira/browse/AXIS2-63
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: core
Versions: M2
Environment: All.
Reporter: Gopalakrishnan
The code that handles the "scope" of the service object (AbstractMessageReceiver.getTheImplementationObject()) is buggy in M2 release. I checked the latest code in the CVS today(1:00 PM IST on 5 july) and the code is improved but I think there is still one problem. Handling of the application scope is wrong :(
the current code is :
} else if (scopeParam != null && Constants.APPLICATION_SCOPE.equals(scopeParam.getValue())) {
SessionContext globalContext = msgContext.getSessionContext();
synchronized(globalContext){
...
Shouldn't it be
SessionContext globalContext = msgContext.getServiceContext();
or
SessionContext globalContext = msgContext.getSystemContext(); ?
I am not sure which one, but certainly not msgContext.getSessionContext(); right?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-63) Handling of "application" scope of the service instance is buggy in AbstractMessageReceiver.getTheImplementationObject()
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-63?page=all ]
Srinath Perera resolved AXIS2-63:
---------------------------------
Resolution: Fixed
Thanks Gopalakrishnan; that was a bad typo on my part. Fixed and commited
> Handling of "application" scope of the service instance is buggy in AbstractMessageReceiver.getTheImplementationObject()
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-63
> URL: http://issues.apache.org/jira/browse/AXIS2-63
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: M2
> Environment: All.
> Reporter: Gopalakrishnan
>
> The code that handles the "scope" of the service object (AbstractMessageReceiver.getTheImplementationObject()) is buggy in M2 release. I checked the latest code in the CVS today(1:00 PM IST on 5 july) and the code is improved but I think there is still one problem. Handling of the application scope is wrong :(
> the current code is :
> } else if (scopeParam != null && Constants.APPLICATION_SCOPE.equals(scopeParam.getValue())) {
> SessionContext globalContext = msgContext.getSessionContext();
> synchronized(globalContext){
> ...
> Shouldn't it be
> SessionContext globalContext = msgContext.getServiceContext();
> or
> SessionContext globalContext = msgContext.getSystemContext(); ?
> I am not sure which one, but certainly not msgContext.getSessionContext(); right?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira