cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject RE: Why does Action extend ThreadSafe ?
Date Mon, 20 Aug 2001 10:42:00 GMT
> > > > > There are two distinct problems here that I'd like to discuss
> > > > > separately: XSP as actions and the Action interface.
> > > >
> > > > +0 on xsps as actions. sure, it might be nice to leverage existing
> > > > logicsheets in xsp actions, but writing a standalone action class is quite
> > > > easy anyway.
> > >
> > > ...as long as they are quite static. If you start to try to configure
> > > them via XML descriptor you wish Cocoon would give you a helping hand.
> > 
> > Avalon is giving you the helping hand (DefaultConfigurationBuilder) if
> > you need to read a XML configuration from a file.
> 
> Besides that is what the akwardly named
> AbstractComplimentoryConfigurableAction
> is for.  It abstracts away the method to load a run-time configuration
> file
> specified by a parameter.  Check out the FormValidator Actions and the
> Database
> Actions for examples on how to use it.  You would be surprised at what
> is possible.
> 
> I even have it cache the Configuration tree for you so you minimize the
> traffic
> on the filesystem.

Well, I know about this nice thing but as soon as the config will not
be plain XML anymore (e.g. esql?) you are doomed. Being able to use
the cocoon: protocol might be an option but unfortunately we don't have
the environment in the action. So cocoon: will not work.
--
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message