[jira] Commented: (AXIS2-4059) JAX-WS services and scope

["Davanum Srinivas (JIRA)" <ji...@apache.org>]

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

Davanum Srinivas commented on AXIS2-4059:
-----------------------------------------

Jarek,

Where/how do you change the scope? code inside Geronimo?

thanks,
dims

> JAX-WS services and scope
> -------------------------
>
>                 Key: AXIS2-4059
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4059
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>    Affects Versions: nightly
>            Reporter: Jarek Gawor
>
> By default the JAX-WS web services are deployed with "request" scope. If the scope was changed to "application" scope the following things break:
> 1) @Resource WebServiceContext injection is not performed. That's because the service class instance is created (and cached) in the DeploymentManager.java (which doesn't do injection) instead of EndpointLifecycleManagerImpl.java
> 2) Updating of WebServiceContextImpl.soapMessageContext is not thread safe. Since there would be one instance of WebServiceContextImpl associated with one instance of the service class which is shared for all requests, updating WebServiceContextImpl.soapMessageContext variable on each request is bad. That could cause, for example, WebServiceContext.getMessageContext() return the MessageContext for the last request instead of the current request. 
> The problem in 2) might also apply to the "session" scope.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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