"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>Fulcrum was never released. There has also been some work backporting
>code from Fulcrum into the turbine-2 code base. I would anticipate that
>there will be even more work to get the remaining services backported as
>well.
>The current plan is NOT to use Fulcrum for version 2.3. We do want to
>be able to Avalon components. Considering that we want this ability in
>2.3 and we don't currently use Fulcrum, I see no reason not to modify
>Fulcrum to use Avalon.
Hi,
actually, I don't plan on backporting any more stuff than the
CryptoService (which was done by something resembling "find . -name
\*.java | xargs sed -e 's/fulcrum/turbine.services/g'") and the
extended DB Security Service which is painstakingly difficult, took
most of my Saturday and Sunday and still is not in there.
I do this, because there is demand from Users. To me, 2.3 is the last
release with coupled services. Actually, in our internal repository,
we're using a stripped down turbine-2 called turbine-light with
fulcrum since quite a while. I can send you the sources if you want
to.
Basically, pre-Avalonization, the Fulcrum and Turbine-2 code was
identical except that you had to substitute "turbine.services" with
"fulcrum". That made code moving back and forth easy. That's why at
least I want to delay the complete assimi^Wavaloniziation until post
Turbine-2.3. Which at least in my personal road map is planned End
January.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
