At 02:12 1/2/01 -0500, Sam Ruby wrote:
>I'm not sure why there isn't more reuse going on within Jakarta, but my
>_theory_ is that the cost associated with versioning issues exceed the
>costs associated with dual maintenance.
I have another theory ;) Reuse occurs vertically not horizontally. For
instance Cocoon reuses a lot of Avalon code and when a bit of code reaches
a certain "generality" threshold in C2 it is bubbled back into Avalon (ie
DataSource pools just did so recently). I assume the same thing occurs with
Turbine-Jetspeed (didn't some of Jetspeeds security/user-management bubble
back ???).
However there is little to no cross-talk between the Avalon-J2EE-Turbine
camps because each of them is working within their own framework rather
than as an API. ie If you adopt component Foo from framework Bar then you
also get the "baggage" associated with Bar. For instance if you use Turbine
services you got to deal with their propertie files + singleton structure.
If you use the Avalon framework you got to deal with XML style
configurations and separation of every concern to the n'th degree ;) No
idea on struts et al.
To get collaboration we would have to build a lower-level framework or
build API-like code that is wrapped in framework code. API-like code is
generally harder to write and ends up looking like a bunch of beans. Is the
effort to write beans rather than framework components worth it ? I would
say yes but only in time ;) Have a look at how long it took to get Avalon
rolling and it is only just starting to separate out framework specific
from non-framework specific.
I guess the best way to enable sharing would be to get a bunch of people
from different projects that have code in common. Turbine/Jetspeed +
Catalina + Avalon + Slide are the ones that jump out at me but I am sure
there are others. We could then migrate framework-nonspecific code into a
central repository and play though polic to keep backwards
compatability/deprecation trends happening ;)
CJAN would of course make this much easier as you could reuse components at
a finer level.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
