> > >> <SNIP/> >> >> What do you think ? > > > I love it :) > > This really seems to pick the best APIs for the job. > It's a good idea to use JNDI for configuration storing indeed, as it > allows enterprise scale deployments, and seems generally better suited > than JMX. > > Remy > > To the extent that JNDI and JMX do the jobs they were designed for, it makes perfect sense. JNDI is all about locating and retrieving data by name. JMX is mostly a runtime mechanism for component management.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
