Hi,
Currently the interface org.apache.avalon.phoenix.Service should be the base
interface of any service interfaces. However there is nothing in the kernel
that mandates this or raises an error when Services don't extend this
interface.
The question is - should they?
The original motivation behind requiring services extend the Service
interface was to enable easy identification for GUI assembler to be written.
However we can get around this through other methods, the most obvious of
which would be placing attributes in manifest (perhaps Avalon-Service: true)
or something.
So my question is should we require that services extend service. I can make
it required or maybe just sternly warn when Service interfaces are
non-compliant or we can deprecate the interface altogether.
Thoughts?
--
Cheers,
Pete
*---------------------------------------------------------*
| Contrary to popular belief, UNIX is user-friendly. It |
| just happens to be selective on who it makes friendship |
| with. |
| - Richard Cook |
*---------------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
