Re: [Springframework-developer] JNDI mock move

[Luke T. <ne...@fr...>]

Hi,

Is the code in flux at the moment? I'm getting compilation errors from a 
fresh checkout:

StaticListableBeanFactory.java:79: cannot resolve symbol
symbol  : constructor NoSuchBeanDefinitionException (java.lang.String)
location: com.interface21.beans.factory.NoSuchBeanDefinitionException
    throw new NoSuchBeanDefinitionException(name);
              ^
Luke.

Rod Johnson wrote:

> I've moved the JNDI mock package from /src to /test. The reason I've done
> this is that it's artificially lowering test coverage (this _is_ really test
> code), and that I don't think we should encourage people to go down this
> route for JNDI testing.  I think the proper way to use Spring is to use it
> to help you avoid doing JNDI lookups in your own code. If you do this, you
> don't need JNDI mocking: you can just expose bean properties for the
> resources that Spring will pull from JNDI.
> 
> I'm keen to remove all non-essential code for 1.0 RC1, so I'm using Clover
> to help me sniff it out.
> 
> I'm also starting a "play" source tree, in which I'm moving some non-core
> stuff from /src. I think we should be very focused on what we release in
> 1.0. And of course paring back to essentials also helps with test coverage.
> (Suggestions for a better name than "play" welcome.)
> 
> The Visitor stuff from com.interface21.core is on its way to the play tree,
> unless there are any objections.
> 


-- 
  Luke Taylor.                      Monkey Machine Ltd.
  PGP Key ID: 0x57E9523C            http://www.monkeymachine.ltd.uk