At 08:33  23/3/01 -0500, Geir Magnusson Jr. wrote:
>> >However, this is a really good point and a discussion we should have in
>> >Commons-land.  Please come and join if interested.
>>
>> yes and after that you really should standardize on logging. Oh and then
>> standardize on lifecycle because thats important too. 
>
>Not really sure a bean utility library/component will need lifecycle and
>logging, nor configuration for that matter

I am not even sure how to answer this? I am not sure if you are serious or
not.

>A Database Connection Pool is another story, but we can look a the
>17,000 or so implementations already in Jakarta and find the best
>practice, and then punt and use log4j :)

Adopt log4j, block avalon/james/cocoon from using component and presumably
taglib/struts when they adopt the J2EE standard. Way to achieve sharing !

>> ! How long do you think before my final prediction bears true? If already
>> you are talking about "standardisation" when that was explicitly one of the
>> non-goals then ...
>
>With this kind of FUD, you should have been in software marketing :)

Whats the FUD about it? One of the non-goals was to not devolve into a
framework. For any semi-complex problem domain you need some support
(unless you invent your own for that component). And if you have 50
components with 50 different sets of internal frameworks then...

>I wasn't suggesting that we should *standardize* on anything, but rather
>*discuss* how something like this can be realized since it appears to be
>an important issue if we want to succeed in our goal

You mean discuss a strategy that components should conform to so as to
interact with other frameworks? ... And if components don't implement this
strategy (aka standard) do they go straight to jail without passing go and
without collecting $200? 

>which is sharable
>components, and a place for cross-project collaboration.

If you honestly wanted to achieve sharing you wouldn't have turned off so
many projects. 

>There seem to be *plenty* of things that are standardized and
>successful.  The java API, for example.  (Can you imagine if we all had
>to roll our own 'int'?)  Household electricity.  The alchoholic content
>of beer...

So you are after standardisation (aka framework) - I see. Glad we cleared
that up.

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]

Reply via email to