Vadim Gritsenko wrote:
> Carsten Ziegeler wrote:
>
> >It's reality - the next version will be 2.0 (if any).
> >
> >Look here:
> >
> >http://www.apache.org/dist/avalon/logkit/jars/
> >
> >
>
> I took
> http://www.apache.org/dist/avalon/logkit/source/logkit-1.2.2-src.zip and
> found 1.2.2-*dev* insi
-Mensagem original-
De: Antonio Gallardo [mailto:[EMAIL PROTECTED]
> + Va de retro, satanas!!
Hey, I *can* understand that! ;-)
This is not personal, and I don't want to be in flames either...
But ASF is heavily based on Community work and Community consensus. Even if
I can't do it better, I can and should tell what I fell about any proposal.
The Community shall decide what is best, and AFAIK that's what happening
now.
B
-Mensagem original-
De: Pier Fumagalli [mailto:[EMAIL PROTECTED]
>> I don't understand what you base that "yes" on. Will the classloading
>> work? Yes, it will. But will *the* *rest* of the system work? You have
>> no guarantee at all.
>
> I wrote 3 servlet containers in my life... :-) I
-Mensagem original-
De: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> Yes, totally. And we already have it working and solved with this new
> container. Why would we trash it to move to JMX? what would that buy us?
Would you put an instrumentation layer on it? If yes, then consider JMX.
-Original Message-
From: Pier Fumagalli
> There are some similarities on the ideas, but JINI (as far as people
> explained it to me when I was working @ Sun) is supposed to be
> completely distributable on multiple network nodes. And I don't think
> that as far as Cocoon is involved, so
-Mensagem original-
De: Pier Fumagalli [mailto:[EMAIL PROTECTED]
> So, what's the point in "guaranteeing" the availability of a component?
> Much _much_ better to make you completely aware that someone can
> disconnect that wiring at any time, and you'll write your code to
> handle it.
-Mensagem original-
De: Thor Heinrichs-Wolpert [mailto:[EMAIL PROTECTED]
> So I think JMX can be a bolt on, or an underpinning depending on how
> you use it. I'd be surprised if it didn't meet the core of what you
> described blocks needed. If a block has a consistent API (Interface)
-Mensagem original-
De: Ralph Goers [mailto:[EMAIL PROTECTED]
> It is interesting to see the discussion on "Avalon". Avalon itself is
> actually pretty small. However, when you add on Excalibur it becomes much
> larger. I'm never clear when the discussion is about Avalon whether the
> dis
-Mensagem original-
De: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> Cocoon and Avalon worked together for a long time and several mistakes
> were made in Avalon due to Cocoon pressure (ComponentSelectors, for
> example).
Aha! So finally we have found the guilty guys.
> The idea of ha
-Mensagem original-
De: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
> IMHO the current perception that Cocoon is a "big thing" is largely due
> to the complexity imposed by Avalon,
Sorry. Can't agree with that.
Avalon was born from Cocoon codebase. What was imposed to Cocoon? Its sh
-Mensagem original-
De: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
> Sure. But if the next Cocoon Core is sufficiently small (and
> *perceived* as such) and powerful, people might want to use it "just"
> as a container, even for simple things...
As an ex-avaloner I second that. :-)
-Mensagem original-
De: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> But this gets pretty hairy with CVS and a distributed workgroup, believe
me.
Well, we use CVS. The two basic rules was:
- You do not upload generated code to CVS
- You do not upload generated code to CVS!!
:-)
But it
-Mensagem original-
De: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> Just keep in mind that everytime you do code generation IDEs that need
> to compile classes to operate (like Eclipse or Idea) choke big time.
Haven't had this experience. All the time things got out-of-date I ran an
An
Sorry to put my noose in this discussion :-)
-Mensagem original-
De: Gianugo Rabellino [mailto:[EMAIL PROTECTED]
> I'm no JMX expert at all, but I understand that basic JMX support can be
> easily "piggybacked" on existing code, as long as you're basically happy
> with monitoring and sm
-Mensagem original-
De: Leo Sutic [mailto:[EMAIL PROTECTED]
> Check 'em out and vote for release:
+1
--
hammett
Easy, Carsten and Leo Sutic are working on a release by now. It will be
ready real soon.
regards,
hammett
-Mensagem original-
De: Ralph Goers [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 26 de fevereiro de 2004 13:55
Para: '[EMAIL PROTECTED]'
Assunto: excalibur-component
I gue
17 matches
Mail list logo
