RE: [Springframework-developer] Summary of pending points

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

>Is anybody working on other concrete issues? I'd like to 
finally release 0.9.1 early next week. As far as I'm 
concerned, all urgent issues are resolved, and the AOP 
support has already been updated. 

So long as I haven't broken anything in my fairly extensive 
AOP-oriented commits last night, I'm not working on anything 
else critical. 
**** Can anyone working with Spring AOP please check that 
their code works with the necessary changes before 0.9.1? ****

I'm planning to revise the EJB support classes by pushing up 
some of the stuff I've been doing at work. This means that 
there will again be a BeanFactory associated with an EJB 
instance (someone posted in the forum about this). I'm 
planning to introduce a BeanFactoryLoader interface so that 
an EJB could choose where the BeanFactory comes from. The 
default will be to look for an environment variable 
specifying the classpath of an XML BeanFactory 
(like /com/foo/bar/myfile.xml). I think this is nicer than 
the old JNDI way, which I've demoted to the sandbox.

Unfortunately enterprise bean and resource manager access 
isn't permitted in setSessionContext() so I've had to do it 
in ejbCreate() and introduce a protected abstract onEjbCreate
() method. Sound reasonable?

However, this is fairly low priority, and won't break 
anything else. So I'm not too bothered about getting it in 
0.9.1. I can probably safely commit it over the weekend.

In other recent checked in changes, I've introduced a static 
emptyActivatedContextBuilder() method on 
SimpleNamingContextBuilder. This allows multiple test cases 
to populate a JNDI context without ordering becoming an issue.

Regards,
Rod