Search:

We are talking nearly about the same thing ;-)

I am just saying that the SingletonBeanFactoryLocator is not as perfect as on the first look, since you have to create a new instance of the...

As far as I understand you, it won't work.

For Example. Quartz can store jobs in the database. The Job is stored only with its full qualified class name. When it starts a new Job, it propably...

I disagree (but still not sure). Of course, if you use SingletonBeanFactoryLocator, it would use only one ApplicationContext, but the instance of ApplicationContext this Locator is using must be a...

OK, thanks, but do I see it correctly that solution 1) would create a second ApplicationContext as well?

Summarize because a bit confusing:

Solutions

1) http://forum.springframework.org/showthread.php?t=27884

But I guess, it would create 2 ApplicationContexts

2)...

Why Do I create a new ApplicationContext? I thought, that an ApplicationContextAware bean is getting the current ApplicationContext, and not a new one....

in the othe case, I can't see, why spring...

For the quartz problem, there would be this solution:

http://forum.springframework.org/archive/index.php/t-22499.html

In case of the hibernate validation, I only see the BeaFactorySolution ....

The thing is, the class is not spring configured. :) It is just a class, which will be instantiated by a 3rd party tool, but still needs to access a DAO.

But still, the ApplicationContextAware is...

We have several 3rd party tools, which just remember the class and instantiate these by themself.

eg.:

* Hibernate Validator

We need to write an validator, which access the database to...

Hi,

my question can be nearly summarized by this thread: http://forum.springframework.org/showthread.php?t=27884

What we need to do is to get a bean which cannot be injected since the class is...