David Sean Taylor <[EMAIL PROTECTED]> writes:
>> Yes. If you're using the tools, you simply change the class names for
>> the
>> tools in TR.props and then you're set.
>>
>And for the DynamicURI class?
The whole URI code has been reworked (newly written) and has now a
unified API. It resides in the org.apache.turbine.util.uri package and
contains of BaseURI which contains common methods, derived DataURI
used for non-turbine references (old ContentURI), TurbineURI (for
non-template based URIs that are processed by the Turbine Servlet) and
TemplateURI which has a few special methods for the template related
URI stuff.
The tools have been separated out into org.apache.turbine.services.pull.tools
[...]
>>> Is there anything left in Turbine?
>>
>> I don't understand this sentence.
>>
>Is there any code remaining in the Turbine project?
>I was trying to make a little joke based on the observation that
>everything is either being deprecated, moved out to commons or fulcrum.
Well, Turbine still has > 400 classes and builds to a ~ 750k jar
archive. IMHO this is still too big for the core of a web
framework. Fulcrum is dead, there is some work now to revive it as an
Avalon Component repository but for all the Jetspeed stuff, that runs
on Turbine-2, you can consider it dead and gone. Same goes to the
Turbine-3 effort.
It's right, we moved lots of generic code to commons, mainly because
there is no reason to drag things around that can be used as generic
components.
My personal idea is to strip Turbine down to be a lean, mean core that
can kick other web frameworks' ass ;-) What is not really turbine core
can go into additional packages. We already have some talk to strip
the services out into Avalon components and then repackage them to be
separate from the core. But this is future code.
As Jetspeed 1 is probably the biggest and most complex single user of
Turbine, we're more than willing to work with you to get it running on
top of 2.3 as smoothly as possible. If there are bugs cropping up or
simply vital parts missing that can't be replaced by commons stuff, we
can easily build 2.3.1 or 2.3.2 to run Jetspeed 1. Just talk to
us. IMHO it's unfortunate that there are almost no Jetspeed people on
the turbine-dev list.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
