axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS2-4059) JAX-WS services and scope
Date Wed, 01 Oct 2008 18:17:46 GMT


Davanum Srinivas commented on AXIS2-4059:


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


> JAX-WS services and scope
> -------------------------
>                 Key: AXIS2-4059
>                 URL:
>             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 (which doesn't do injection)
instead of
> 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:
For additional commands, e-mail:

View raw message