You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Ole Bulbuk <Ol...@ebp.de> on 2002/04/23 13:58:36 UTC
(Excalibur)ComponentManager extending AbstractLogEnabled
Hi (not only) Berin,
I understand that ECM is extending AbstractLoggable for compatibility
reasons. I suppose it will be replaced one day by something that is
extending AbstractLogEnabled instead. In order to to be able to use
something else than LogKit it would be nice to have an
(Excalibur)ComponentManager that is extending AbstractLogEnabled.
The server I am developing consists mainly of a package with all the
algorithms, etc. Of course this package is logging quite a lot. But this
package should be reusable in other applications and servers that might not
use LogKit. And of course it would be nice for the user to edit only one
configuration file and to watch only one log file. So it would be very nice
for me if there would exist something like ECM that extends
AbstractLogEnabled.
Any thoughts?
Regards,
Ole
--
Ole Bulbuk Tel.: 0331/74759/60
Ernst Basler + Partner Fax: 0331/74759/90
Tuchmacherstr. 47 E-Mail: mailto:ob@ebp.de
14482 Potsdam WWW: http://www.ebp.de
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (Excalibur)ComponentManager extending AbstractLogEnabled
Posted by Berin Loritsch <bl...@apache.org>.
Torsten Curdt wrote:
>>To remind everyone: The ECM has to be backwards compatible with
>>components that use the Loggable interface. THERE IS NO WAY TO GET
>>THE LOGKIT LOGGER FROM THE FRAMEWORK LOGGER WRAPPER. If you think
>>there still might be a way, reread that last sentence.
>>
>>If you want a new "ECM" compatible container, that does not have to
>>deal with backward incompatibilities, then by all means create one.
>>It just can't be the ExcaliburComponentManager. New entities have
>>new contracts.
>>
>>If you don't have *any* components that use Loggable, and they have
>>all been converted to LogEnabled, then you can either use fortress
>>which has some fine-tuning or create an equiv. to the ECM.
>
>
> sorry for the (maybe) stupid question - but what is fortress?
Check Excalibur CVS. It is the new name for excalibur.system
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (Excalibur)ComponentManager extending AbstractLogEnabled
Posted by Torsten Curdt <tc...@dff.st>.
> To remind everyone: The ECM has to be backwards compatible with
> components that use the Loggable interface. THERE IS NO WAY TO GET
> THE LOGKIT LOGGER FROM THE FRAMEWORK LOGGER WRAPPER. If you think
> there still might be a way, reread that last sentence.
>
> If you want a new "ECM" compatible container, that does not have to
> deal with backward incompatibilities, then by all means create one.
> It just can't be the ExcaliburComponentManager. New entities have
> new contracts.
>
> If you don't have *any* components that use Loggable, and they have
> all been converted to LogEnabled, then you can either use fortress
> which has some fine-tuning or create an equiv. to the ECM.
sorry for the (maybe) stupid question - but what is fortress?
--
Torsten
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: (Excalibur)ComponentManager extending AbstractLogEnabled
Posted by Berin Loritsch <bl...@apache.org>.
Ole Bulbuk wrote:
> Hi (not only) Berin,
>
> I understand that ECM is extending AbstractLoggable for compatibility
> reasons. I suppose it will be replaced one day by something that is
> extending AbstractLogEnabled instead. In order to to be able to use
> something else than LogKit it would be nice to have an
> (Excalibur)ComponentManager that is extending AbstractLogEnabled.
> The server I am developing consists mainly of a package with all the
> algorithms, etc. Of course this package is logging quite a lot. But this
> package should be reusable in other applications and servers that might not
> use LogKit. And of course it would be nice for the user to edit only one
> configuration file and to watch only one log file. So it would be very nice
> for me if there would exist something like ECM that extends
> AbstractLogEnabled.
>
> Any thoughts?
To remind everyone: The ECM has to be backwards compatible with
components that use the Loggable interface. THERE IS NO WAY TO GET
THE LOGKIT LOGGER FROM THE FRAMEWORK LOGGER WRAPPER. If you think
there still might be a way, reread that last sentence.
If you want a new "ECM" compatible container, that does not have to
deal with backward incompatibilities, then by all means create one.
It just can't be the ExcaliburComponentManager. New entities have
new contracts.
If you don't have *any* components that use Loggable, and they have
all been converted to LogEnabled, then you can either use fortress
which has some fine-tuning or create an equiv. to the ECM.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>