Re: [Springframework-developer] JNDI mock move

[Rod J. <rod...@in...>]

> Another thought: Our "mock" JNDI isn't really about mocks, it's the
simplest JNDI SPI implementation that could possibly work (basically a
name/object map within the local VM). One could even build a J2EE web
container's JNDI environment on this (being not too serious though). It's
similar to our JDBC DataSources: They aren't really mocks - rather simple
but working implementations. That's why they aren't called "mock" anymore
and reside in "jdbc.datasource" now. Consequently, we could turn the "mock"
JNDI implementation into "simple JNDI": "SimpleInitialContextFactoryBuilder"
and "SimpleContext", residing in "jndi.support". On second thought, I
actually prefer such a solution!

OK, I hadn't thought about the valid usage scenarios you propose. I would
feel much happier if they were renamed Simple instead of Mock. Regarding
test coverage, clover.excludes would be fine. I think having a "Mock"
package in the source

Sorry for the premature move, but if you want to move them back and rename
them that's fine with me. I'll leave you to do this as you're using them and
may have better thoughts on comments etc.

Regards,
Rod