[
https://issues.apache.org/jira/browse/AXIS2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-1923:
------------------------------------
Assignee: Deepal Jayasinghe
> Define service impl. lifecycle.
> -------------------------------
>
> Key: AXIS2-1923
> URL: https://issues.apache.org/jira/browse/AXIS2-1923
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: adb, client-api, codegen, documentation, kernel
> Affects Versions: nightly
> Reporter: Ivan Latysh
> Assigned To: Deepal Jayasinghe
> Priority: Minor
> Attachments: LifeCycle.gif, LifecycleInterefaces.gif
>
>
> I noticed that AXIS2 does not have defined service impl. lifecycle. We can
> see bit's and pieces from it all over, but no concrete definition (I refer to
> init() method, ServiceLifeCycle interface, etc.)
> From mailing list I can see that many users are confused by absence of
> defined lifecycle.
> I belive that this can be solved easy with little (or none) code refactoring.
> For instance let's take Apache Avalon framework, and we don't even need an
> implementation, just interfaces (just 28k jar). Or if dev. team don't want to
> bring on board one more framework, just create AXIS2 own lifecycle interfaces.
>
> Now when service impl want to be aware of different events it should
> implement an interface.
> So init() method will be defined in Initializable interface,
> ConfigurationContext will be given when service implement Configurable
> interface, when service want to know about MessageContext it implement
> Contextualizable.
> Also the great asset is to serve impl. with binding events (not data binding)
> when impl. bound to the request, axis session or transport session.
> So the beauty of this approach that existing services with just a business
> method will be unaffected, but it will give an extra power to the AXIS2 since
> developers will benefit from defined lifecycle.
--
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]
