You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2002/08/26 14:38:30 UTC
FW: log4j fired, Avalon logKit hired
I thought you guys would like to know....
> -----Original Message-----
> From: Mike Stover [mailto:mstover1@apache.org]
> Sent: Friday, August 23, 2002 5:03 PM
> To: jmeter-dev@jakarta.apache.org
> Subject: log4j fired, Avalon logKit hired
>
>
> I've switched all the code to use Avalon's LogKit, which
> seems easier to use, and
> less over-designed. I created some simple categories for
> logging, and the logging
> levels of each category can be changed by editing
> jmeter.properties. The default
> is to log to jmeter.log in the /bin directory.
>
> I'll work on removing System.out calls now.
>
> --
> Michael Stover
> mstover1@apache.org
> Yahoo IM: mstover_ya
> ICQ: 152975688
>
> --
> To unsubscribe, e-mail:
> <mailto:jmeter-dev-> unsubscribe@jakarta.apache.org>
> For
> additional commands,
> e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Paul Hammant wrote:
> Nicola,
>
>>> And it is great. Are you going to take back your words-in-my-mouth
>>> "Phoenix == Avalon RI" jibe?
>>
>>
>> Are you going to take away the "Phoenix BlockContext == de-facto
>> standard"?
>> No, because in a sense both of us are right.
>
>
> No. I did not claim Avalon RI was Phoenix. You said I did.
Ok, I misunderstood your question.
I mean this:
You never claimed that Avalon RI was Phoenix.
I did.
I never said that Phoenix BlockContext == de-facto standard".
You did.
Happy?
Has this gotten us some progress?
Gee, I get more done in the discussion with Peter than with you, loosen
up, man!
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Paul Hammant <Pa...@yahoo.com>.
Nicola,
>> And it is great. Are you going to take back your words-in-my-mouth
>> "Phoenix == Avalon RI" jibe?
>
>
> Are you going to take away the "Phoenix BlockContext == de-facto
> standard"?
> No, because in a sense both of us are right.
No. I did not claim Avalon RI was Phoenix. You said I did.
-ph
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Paul Hammant wrote:
> Nicola,
>
>>> Kewl. I find A-F's lifecycle is the easiest thing to market in work
>>> and out of all of the Avalon projects aspects.
>>
>>
>>
>> I agree.
>> That's why we wrote Tweety, that explains basically lifecycle in a
>> simple way.
>
>
> And it is great. Are you going to take back your words-in-my-mouth
> "Phoenix == Avalon RI" jibe?
Are you going to take away the "Phoenix BlockContext == de-facto standard"?
No, because in a sense both of us are right.
Phoenix in a sense has already been seen and used as a RI of Avalon,
from a server perspective.
I have no problem in saying it, it's true, and you implied it too.
Now, because of the *user* need of Component interoperability between
Containers, we must define the contracts better, and make any Component
workable in any container.
----
This is the scenario I have in mind:
Let's say I want to use a ComponentA written for ContainerA in ContainerB.
ContainerA ---(hosts)---( ComponentA )
ContainerB- ?
We have a common descriptor format, so ContainerB can look in the
descriptor and see if it's capable of running it.
If it can, great, Bob's your uncle :-D
ContainerB ---(hosts)---( ComponentA )
This must not only define the lifecycle needed, but also which Context,
which keys in the Context, etc are needed, which Merlin does IIUC.
If not, I can see if the Component declares an extension can solve the
issue. If it does, Bob's your uncle again, and it can get the extension
handler and use that.
ContainerB ---(hosts)---( ComponentA )
\
\
--< ExtensionA >
This is done by Merlin/Fortress, and is not mandatory.
Finally, it can happen that something needed is not really doable by
ContainerB.
It should be able to automatically get ContainerA, and ask him to be
given a handle to ContainerA.
We'll have:
ContainerB ---(hosts)---( ContainerA ---(hosts)---( ComponentA ) )
This info is needed in the descriptor, or in some registry, so that the
Container can delegate things to a Container that acts as a Component
that manages our ComponentA.
How can it be specified?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Paul Hammant <Pa...@yahoo.com>.
Nicola,
>> Kewl. I find A-F's lifecycle is the easiest thing to market in work
>> and out of all of the Avalon projects aspects.
>
>
> I agree.
> That's why we wrote Tweety, that explains basically lifecycle in a
> simple way.
And it is great. Are you going to take back your words-in-my-mouth
"Phoenix == Avalon RI" jibe?
- Paul
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Paul Hammant wrote:
> Berin,
>
> Kewl. I find A-F's lifecycle is the easiest thing to market in work and
> out of all of the Avalon projects aspects.
I agree.
That's why we wrote Tweety, that explains basically lifecycle in a
simple way.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Paul Hammant <Pa...@yahoo.com>.
Berin,
Kewl. I find A-F's lifecycle is the easiest thing to market in work and
out of all of the Avalon projects aspects.
- Paul
>Well, Mike was fed up fighting with Log4J. I tried pushing
>him toward the Avalon logging abstraction (he already has it
>in the Avalon Framework jar he is using for the config object).
>That can be a next step...
>
>
>
>>-----Original Message-----
>>From: Paul Hammant [mailto:Paul_Hammant@yahoo.com]
>>Sent: Monday, August 26, 2002 8:56 AM
>>To: Avalon Developers List
>>Subject: Re: FW: log4j fired, Avalon logKit hired
>>
>>
>>Berin,
>>
>>Its good news in a way. If can't help feeling sorry for Ceki
>>though....
>> Pehaps we should be more interested in A-F's logging
>>abstraction than
>>LogKit per se, and market that more that LogKit. Especially as
>>Commons-Logging is an equally good choice (shh I did not say that).
>>
>>- Paul
>>
>>
>>
>>>I thought you guys would like to know....
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Mike Stover [mailto:mstover1@apache.org]
>>>>Sent: Friday, August 23, 2002 5:03 PM
>>>>To: jmeter-dev@jakarta.apache.org
>>>>Subject: log4j fired, Avalon logKit hired
>>>>
>>>>
>>>>I've switched all the code to use Avalon's LogKit, which
>>>>seems easier to use, and
>>>>less over-designed. I created some simple categories for
>>>>logging, and the logging
>>>>levels of each category can be changed by editing
>>>>jmeter.properties. The default
>>>>is to log to jmeter.log in the /bin directory.
>>>>
>>>>I'll work on removing System.out calls now.
>>>>
>>>>--
>>>>Michael Stover
>>>>mstover1@apache.org
>>>>Yahoo IM: mstover_ya
>>>>ICQ: 152975688
>>>>
>>>>--
>>>>To unsubscribe, e-mail:
>>>><mailto:jmeter-dev-> unsubscribe@jakarta.apache.org>
>>>>For
>>>>additional commands,
>>>>e-mail: <ma...@jakarta.apache.org>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>--
>>>To unsubscribe, e-mail:
>>>
>>>
>><mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
>>
>>
>>>For
>>>
>>>
>>additional commands,
>>e-mail:
>>
>>
>>><ma...@jakarta.apache.org>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>><mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
>>For
>>additional commands,
>>e-mail: <ma...@jakarta.apache.org>
>>
>>
>>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: FW: log4j fired, Avalon logKit hired
Posted by Berin Loritsch <bl...@apache.org>.
Well, Mike was fed up fighting with Log4J. I tried pushing
him toward the Avalon logging abstraction (he already has it
in the Avalon Framework jar he is using for the config object).
That can be a next step...
> -----Original Message-----
> From: Paul Hammant [mailto:Paul_Hammant@yahoo.com]
> Sent: Monday, August 26, 2002 8:56 AM
> To: Avalon Developers List
> Subject: Re: FW: log4j fired, Avalon logKit hired
>
>
> Berin,
>
> Its good news in a way. If can't help feeling sorry for Ceki
> though....
> Pehaps we should be more interested in A-F's logging
> abstraction than
> LogKit per se, and market that more that LogKit. Especially as
> Commons-Logging is an equally good choice (shh I did not say that).
>
> - Paul
>
> >I thought you guys would like to know....
> >
> >
> >
> >>-----Original Message-----
> >>From: Mike Stover [mailto:mstover1@apache.org]
> >>Sent: Friday, August 23, 2002 5:03 PM
> >>To: jmeter-dev@jakarta.apache.org
> >>Subject: log4j fired, Avalon logKit hired
> >>
> >>
> >>I've switched all the code to use Avalon's LogKit, which
> >>seems easier to use, and
> >>less over-designed. I created some simple categories for
> >>logging, and the logging
> >>levels of each category can be changed by editing
> >>jmeter.properties. The default
> >>is to log to jmeter.log in the /bin directory.
> >>
> >>I'll work on removing System.out calls now.
> >>
> >>--
> >>Michael Stover
> >>mstover1@apache.org
> >>Yahoo IM: mstover_ya
> >>ICQ: 152975688
> >>
> >>--
> >>To unsubscribe, e-mail:
> >><mailto:jmeter-dev-> unsubscribe@jakarta.apache.org>
> >>For
> >>additional commands,
> >>e-mail: <ma...@jakarta.apache.org>
> >>
> >>
> >>
> >
> >
> >--
> >To unsubscribe, e-mail:
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> >For
> additional commands,
> e-mail:
> ><ma...@jakarta.apache.org>
> >
> >
> >
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For
> additional commands,
> e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: FW: log4j fired, Avalon logKit hired
Posted by Paul Hammant <Pa...@yahoo.com>.
Berin,
Its good news in a way. If can't help feeling sorry for Ceki though....
Pehaps we should be more interested in A-F's logging abstraction than
LogKit per se, and market that more that LogKit. Especially as
Commons-Logging is an equally good choice (shh I did not say that).
- Paul
>I thought you guys would like to know....
>
>
>
>>-----Original Message-----
>>From: Mike Stover [mailto:mstover1@apache.org]
>>Sent: Friday, August 23, 2002 5:03 PM
>>To: jmeter-dev@jakarta.apache.org
>>Subject: log4j fired, Avalon logKit hired
>>
>>
>>I've switched all the code to use Avalon's LogKit, which
>>seems easier to use, and
>>less over-designed. I created some simple categories for
>>logging, and the logging
>>levels of each category can be changed by editing
>>jmeter.properties. The default
>>is to log to jmeter.log in the /bin directory.
>>
>>I'll work on removing System.out calls now.
>>
>>--
>>Michael Stover
>>mstover1@apache.org
>>Yahoo IM: mstover_ya
>>ICQ: 152975688
>>
>>--
>>To unsubscribe, e-mail:
>><mailto:jmeter-dev-> unsubscribe@jakarta.apache.org>
>>For
>>additional commands,
>>e-mail: <ma...@jakarta.apache.org>
>>
>>
>>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>