beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil" <ekon...@gmail.com>
Subject Re: netui -- adding a required ServletContextListener
Date Tue, 04 Apr 2006 20:53:34 GMT
  Cool -- it also gives us the ability to initialize the NetUIConfig
object in a single place and put it in the ServletContext.  This will
free us from this ridiculous race condition caused by using a static
to store the bean in ConfigUtil.  Mea culpa.  ;)

  Thanks...

Eddie


On 4/4/06, Rich Feit <richfeit@gmail.com> wrote:
> Seems fine to me.  It doesn't buy us anything currently (since
> PageFlow{Jsp,Faces}Filter is required, so its init() always runs), but
> it does free us from depending on
> PageFlowActionServlet/PageFlow{Jsp,Faces}Filter in case we want to move
> away from them in the future.
>
> Rich
>
>
> Eddie O'Neil wrote:
> > All--
> >
> >   NetUI has a need for a common place to do setup and tear down tasks
> > for the framework, and as such, I'd like to make a
> > ServletContextListener a requirement as a place to do this work.
> >
> >   This provides a place to do NetUIConfig initialization as well as a
> > place to remove ServletContext attributes that NetUI (and Struts) put
> > there.  I've had some trouble with class reloading in Tomcat that
> > requires the latter problem be fixed in order for the framework(s) to
> > reinitialize correctly after classes are reloaded.
> >
> >   Thoughts on this?  Ideally, we'd make this an upgrade requirement
> > for moving from Beehive 1.0 to Beehive V.Next so that we can put the
> > initialization code in a single place.  Am open to suggestions on
> > that.
> >
> >   Ideally, this would be something called NetUIContextListener that
> > has interceptor chains for "initialize" and "destroy" phases with
> > implementations that plug-in to provide default behavior for each of
> > these phases.
> >
> >   Thoughts / ideas?
> >
> > Eddie
> >
> >
>
>

Mime
View raw message