On 11/6/06, Andrew C. Oliver <[EMAIL PROTECTED]> wrote:
>> Local namepaces are generally used for configuration settings ala (which >> I don't particularly like JNDI for, preferring >> to inject into individual setters), portability and instance separation. > > I'm not mad on the idea of using JNDI for config either, but its > always going to be available to vendors and developers via > context.bind unless we lock it down, which I'm not crazy about either, > so I guess we can only sneer about it and attempt to cover the bases > with a well designed API. > > That said the indirection provided by mapping global to local is a > good thing, its just that the means of doing it isn't easy to trace or > debug (debug errors in the mappings I mean, not the things which are > bound and mapped). I'm 99% sure we're a long way from needing to make > a decision about deployment descriptors, I'm happy to let this remain > undecided until we actually do need an answer, none of the PoC stuff > would be invalid in either case. yes. Once other have had time to sound of on this particular issue we should start specing it out on the wiki as well. I prefer your code-first method but think some level of specification is also required. Mainly because I'm way to lazy to search mail archives when it comes time to implement.
I prefer dependency injection to service lookups, so much of what you guys are discussing seems moot to me. Since you (one or both of you) have expressed preference for dependency injection as well, I'm struggling to picture the use cases for when JNDI lookup is necessary. Can you guys give some examples to help me understand this requirement? -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
