Hello, I'm diving in the first time deeper into Avalon when developing my first not only cocoon-based, but also avalon-based application. Now I have a bit of knowledge already due to my work on Cocoon and heard already of ServiceManager and ServiceSelector.
I read a bit more on ServiceSelector on the Avalon homepage and there I found that ServiceSelector is probably only required for badly designed applications. I searched the avalon lists archives for a thread and found Peter's mail [1], where he states that the ServiceSelector might be to general - and that's where I stumble. What's the problem of a generic interface? Isn't it an issue of the implementation to be more specific? And how should it be done instead? The use case in my application is the selection of business actions based on some criteria. As I'm still in design phase I'm open for suggestions. Or is the selector still the way to go through lack of alternatives (see the end of Peter's mail). I would appreciate any comments. Joerg [1] http://marc.theaimsgroup.com/?l=avalon-users&m=104657563531041&w=2 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
