cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: Cocoon Maven plugin - Merging deployer & rcl
Date Wed, 02 May 2007 12:15:40 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Reinhard Poetz wrote:
> Giacomo Pati wrote:

>> java.lang.IllegalStateException: BeanFactory not initialized or
>> already closed - call 'refresh'
>> before accessing beans via the ApplicationContext
>>         at
>> org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:120)
>>
>>         at
>> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:687)
>>
>>         at
>> org.acegisecurity.util.FilterChainProxy.obtainAllDefinedFilters(FilterChainProxy.java:220)
>>
>>         at
>> org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:135)
>>
>>         at
>> org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
>>
>>         at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
>>
>>         at
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:358)
>>         at
>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
>>         at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
>>         at
>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
>>         at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
>>
>> ...
>>
>> Now this seems to me that some changes with the RCL prevents third
>> party servlet filters to access
>> the ApplicationContext, or am I wrong?
> 
> no, that's my interpretation of the stacktrace too
> 
>> Any pointers?
> 
> The problem is that when the app context gets reloaded, there is a time
> frame, when the context is not available. At the moment I only have a
> vague idea how we can prevent e.g. the acegi filter from accessing a
> (temporarily) non-existing context.
> Maybe we can provide some kind of wrapper for the app context that locks
> the access to the app context in question for the time of
> reinitializiation.

Well, it happens on the first request. Does your scenario apply to the first request as well?

- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)

iD8DBQFGOIDrLNdJvZjjVZARAk8ZAJ0YvOihd3FlSfDE2HFInWMoAkfBEwCgoY4V
bY1BZfG35hzpZ9jrFPv249o=
=TwOy
-----END PGP SIGNATURE-----

Mime
View raw message