Hi Peter,
are you leaning passively towards adding Fortress to Turbine (thinking
this is a good idea) or actively (adding Fortress to Turbine and lending
a hand for setting up the configuration files)?
Cheers,
Siegfried Goeschl
Peter Courcoux wrote:
Hi Leandro,
I am currently developing a component oriented pure java alternative
to Velocity and developing a small commercial application using it.
It's not ready for me to publish yet but seems to be coming along nicely.
The new service is plugged in using a replacement for the executepage
valve in the pipeline.
However, one problem is the private handleException(...) method in the
Turbine servlet. This is the bit I would like to make pluggable as
well and will require a change to Turbine.java.
I think that there has been some attempt to pull the Velocity Service
into fulcrum, but I don't think it was finished or if it was, then I
think that there is still some work to do in Turbine ( e.g the above )
to enable the fulcrum version to be used in place of the embedded
service.
I'm still using ECM as the container for the main services. In view of
the proposed new release of Excalibur-Fortress this month, I am
leaning towards making the effort to add a Fortress service to Turbine
shortly.
The new page framework is using the Context IOC pattern for the
components. There is no formal container as such although there are
some container-like features in the main page process.
I had a quick look a guara when you posted about it a few weeks back.
It looks good. I'm trying to keep the new page framework independant
of any particular web-app framework so maybe it will work in guara too.
Thanks,
Peter
Leandro Rodrigo Saad Cruz wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
