On Thu, 2005-08-18 at 00:08 +0100, Peter Courcoux wrote: > Hi all, > > I have in mind to make the exception reporting in Turbine.java pluggable > so that I can use an alternative 'executepage' mechanism which does not > use the Velocity service.
Great. Are you planning to change the Turbine servlet or just point the execute at another pipeline on error? > I would hope to make the Velocity service a > separate pluggable fulcrum service in due course. At the moment the > error reporting is hard coded to try the Velocity service first and if > that fails sends the raw exception to the servlet output stream. Turbine should abstract the Template service (not sure if it's not as is today). This is what was done on guara. > > I would suggest an Avalon style component for this. Does anyone have any > comments, suggestions or objections? For me, Avalon is the best IOC framework around. Go for it! Which container are you planning to use? We have a tinny container called Pulga. It relies on the fact that all components are thread safe. > > Clearly the default would be to continue to use a Velocity page for > error reporting but make it possible to replace Velocity with something > else if needed using settings in a configuration file. > > Thanks, > > Peter -- Leandro Rodrigo Saad Cruz CTO - InterBusiness Technologies OJB - db.apache.org/ojb XINGU - xingu.sf.net GUARA - guara-framework.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
