Hi Guys,
The Service Interface defines the contract so would just have the methods that a client should see or know abt.
But the implementation might need several other methods to do its internal functions and also the implementation would implement the lifecycle interface methods.
So is it perfectly fine according to the Avalon design principles to have many other methods in the implementation besides the Service and lifecycle methods ?
Yes.
Typically you would break out the logic of a lifecycle or a service operation implementation into a set of methods - where (ideally) each method deals with a clear and well defined objective.
Or should the aim be to put the internal functionality of implementation into the lifecycle methods as much as possible ?
No.
This leads to overly complex method implementations.
Cheers, Steve.
Thanks
Vikas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
