[
https://issues.apache.org/jira/browse/AXIS2-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Afkham Azeez reassigned AXIS2-4080:
-----------------------------------
Assignee: Afkham Azeez
> AxisService's scope inside ServiceLifeCycle startUp() is always "request"
> scope regardless of actual
> ----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4080
> URL: https://issues.apache.org/jira/browse/AXIS2-4080
> Project: Axis2
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.4.1, 1.4
> Reporter: Manny Lim
> Assignee: Afkham Azeez
> Priority: Minor
>
> By default, the AxisService constructor sets the scope to be "request". The
> org.apache.axis.deployment.ServiceBuilder is responsible for setting this
> value to be the actual value specified in the services.xml file. However, the
> populateService() method which handles this, processes the service life cycle
> attribute before it processes the service scope attribute. As a result, the
> AxisService object which is passed to the ServiceLifeCycle.startUp() method
> is always the default scope regardless of what the user has specified in
> their services.xml.
> I believe that by simply rearranging the order in which these attributes are
> processed (in ServiceBuilder.populateService()) we can avoid confusion in
> situations where users are performing scope specific actions in their
> ServiceLifeCycle implementations. It may be beneficial to leave off
> processing of the service life cycle attribute for as long as possible, so
> that when the startUp() method is finally invoked, users are given the most
> accurate representation of their service.
> Thanks,
> Manny Lim
--
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: [email protected]
For additional commands, e-mail: [email protected]
