At 12:07 PM 6/13/2002 +0200, you wrote:
LET ME MAKE THIS REAL CLEAR,
>I WANT TO KNOW WHY "org.apache.Thing/key" is any different to "something"
>in the context of a component lookup key value.
Because everyone but you follow the first convention. Thats the main
reason. You can choose to follow our conventions or not - depends on how
widely used you want your components to be ;)
In 99% of cases you don't need they "/key" postfix. And thus reasons being;
* automagically maintained. ie if you change the package of service
interface you don't have to worry that you forgot to update the ROLE string.
* You can reuse the ROLE string in interface across multiple consumers
without worrying about name clashes.
* don't need to worry about maintaining <role> in dependency for component
as it is auto maintained for you
etc.
Anyways most containers require or at least show a preference for the
pattern and it has been a fairly established pattern. Why not save yourself
the extra work and follow suite? Maintaining role strings in 4 difference
places and remembering to change them when you move the interface is
something you can do if you want. Don't expect anyone else to feel sympathy
for you though ;)
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
