Had to read [1],[2],[3],[4],[5] and your email twice ;). Its pretty clear. On 8/13/07, David Blevins <[EMAIL PROTECTED]> wrote: > > So one of the remaining issues for the 3.0 release is the JNDI name > strategy we're going to use. I had totally thought this was all > straightened out when I added the TemplatedStrategy (documented here: > http://openejb.apache.org/jndi-names.html), but it turns out we are > still using the LegacyAddedSuffixStrategy by default so the > documentation in that page also isn't right by default :) > > I recall not switching us over by default as we have the huge itest > which all use the LegacyAddedSuffixStrategy. Really, it should be > fine as each app should be able to use the strategy they want (maybe > even put a strategy implementation class in their jar). > > So we need to get the default switched over to the new > TemplatedStrategy as it's the most powerful by far. As well we > should probably provide a way provide a way for individual apps to > specify which strategy they'd like via the openejb-jar.xml file or > something. > > Going to try and plumb something in. Thinking the first steps maybe > to eliminate the JndiNameStrategy.Interface enum and use the top- > level o.a.o.InterfaceType enum. Also thinking we would be better off > if the TempalatedStrategy could support the > LegacyAddedSuffixStrategy, which it can't at the moment. > > Once we get the default working as documented with the > TemplatedStrategy, we should probably switch over our examples to use > the new names. > > -David > >
-- Karan Singh Malhi
