Is there a best practice?
various longtime committers disagree after eons of discussion, so the general best practice seems to be "do what you think makes sense" ;)
It seems to me that (1) is the most commonly used, though I've used the ROLE method quite a bit myself. (3) doesn't look like a good idea, or is there a reasonable use case for it?
yes. There's good reasons for the lookup string to be a freeform string. I have been known to use custom URNs for lookup (which can be a nice way to extend the container-component contract in a custom container while maintaining component portability), as well as JNDI URIs (which can be rather handy when porting fron a JNDI to an avalon-based environment).
Also if I recall, there was a question about why we use Strings at all instead of Class objects.
the lookup contract is that you can use freeform strings. This means you're allowed to look up things which might not be able to use as Class objects. It also avoids classloader issues and lots of other things. There's lots of talks about this in the dev@ archives if you want more reasoning :D
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
