On Sep 25, 2007, at 1:44 PM, Eric Dalquist wrote:
The problem is in some places that the
PortalApplicationContextFacade is
used to access the BeanFactory there is no access to a ServletContext
which the WebApplicationContextUtils needs to access the replacement
WebApplicationContext.
The
Will we still run certain tools outside the web context? If so, will
this approach handle that scenario too? For example importing and
exporting objects, initializing the database.
Susan
Eric Dalquist wrote:
I ended up following the static locater pattern which is similar to
Spring's
Thats a good approach too, I might look into creating a utility bean to
do that injection that also inject a null when the context is shutting
down. Making sure the solution works nicely with spring context and
servlet context reloads which cause problems right now. I'm thinking the
injecting
I ended up following the static locater pattern which is similar to
Spring's WebApplicationContextUtils class but does not require a
ServletContext to get at the WebApplicationContext. These changes are in
SVN so now there is a single loaded WebApplicationContext that follows
the
Drew Wills wrote:
++ BeansML:
bean id=personDirectoryService factory-method=setPersonAttributeDao
constructor-arg
ref bean=personAttributeDao/
constructor-arg
/bean
Sorry, should be more like:
bean id=personDirectoryService
class=org.jasig.portal.services.PersonDirectory
