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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2006/03/03 10:03:48 UTC
[jira] Resolved: (AXIS2-386) scope parameter for service
implementation class is not interpreted
[ http://issues.apache.org/jira/browse/AXIS2-386?page=all ]
Deepal Jayasinghe resolved AXIS2-386:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
now you can add services scope in the services.xml as follows
<service scope="application">
....
</services>
> scope parameter for service implementation class is not interpreted
> -------------------------------------------------------------------
>
> Key: AXIS2-386
> URL: http://issues.apache.org/jira/browse/AXIS2-386
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 0.94
> Reporter: Andreas Bobek
> Fix For: 0.95
>
> in Axis2 0.93 follow configuration in a services.xml was possible:
> <parameter name="ServiceClass" locked="false">com.MyService</parameter>
> <parameter name="scope">application</parameter>
> The AbstractMessageReceiver class in Axis2 0.94 takes no care about the scope parameter anymore.
> It is not possible to force Axis to create only one instance of a service implementation class for the whole runtime any longer.
> related entry in mailing list is
> http://marc.theaimsgroup.com/?l=axis-user&m=113711865827709&w=2
--
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