You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Christopher Kohlhaas <ko...@bonn.edu> on 2002/08/05 21:46:33 UTC
PATCHES Fortress
Appended are two Patches for the Fortress Container.
The "ContextBuilder.patch" fixes a copy and paste typo in
ContextBuilder.java
The "ContextManager_Linkage_Error.patch" makes the initialization of
the DefaultConfigurationBuilder lazy. DefaultConfigurationBuilder
calls SAXParserFactory.newInstance() in the Constructor and this will
rise a LinkageError in some environments (for example when you use ant
to start fortress). With the patch this error will not arise, when a
Configuration-object is given.
There is also a small inconvenience with the creation of the
LogKitManager in the initializeLoggerManager() in the ContextManager
file.
The logkit-configuration initialization-DEBUG-information always
appears in the console, no matter what logging configuration you use.
The logger responsible for this output is created in the Constructor
of LogKitManager(String prefix). It is only used during the
initialization.
Instead the default logger from the ContextManager should be used.
LogKitLoggerManager logManager = new LogKitLoggerManager(
logCategory
,new org.apache.log.Hierarchy()
,new getLogger());
could be a possible solution.
BTW
Regards
Christopher
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: PATCHES Fortress
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Thanks, these are both committed.
Cheers,
Leif
Christopher wrote:
>Here are the files.
>
>Christopher Kohlhaas [kohlhaas@bonn.edu] wrote:
>
>
>>Appended are two Patches for the Fortress Container.
>>
>>The "ContextBuilder.patch" fixes a copy and paste typo in
>>ContextBuilder.java
>>
>>The "ContextManager_Linkage_Error.patch" makes the initialization of
>>the DefaultConfigurationBuilder lazy. DefaultConfigurationBuilder
>>calls SAXParserFactory.newInstance() in the Constructor and this will
>>rise a LinkageError in some environments (for example when you use ant
>>to start fortress). With the patch this error will not arise, when a
>>Configuration-object is given.
>>
>>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: PATCHES Fortress
Posted by Christopher <zi...@gmx.de>.
Here are the files.
Christopher Kohlhaas [kohlhaas@bonn.edu] wrote:
> Appended are two Patches for the Fortress Container.
>
> The "ContextBuilder.patch" fixes a copy and paste typo in
> ContextBuilder.java
>
> The "ContextManager_Linkage_Error.patch" makes the initialization of
> the DefaultConfigurationBuilder lazy. DefaultConfigurationBuilder
> calls SAXParserFactory.newInstance() in the Constructor and this will
> rise a LinkageError in some environments (for example when you use ant
> to start fortress). With the patch this error will not arise, when a
> Configuration-object is given.
>
>
> There is also a small inconvenience with the creation of the
> LogKitManager in the initializeLoggerManager() in the ContextManager
> file.
>
> The logkit-configuration initialization-DEBUG-information always
> appears in the console, no matter what logging configuration you use.
> The logger responsible for this output is created in the Constructor
> of LogKitManager(String prefix). It is only used during the
> initialization.
>
> Instead the default logger from the ContextManager should be used.
>
> LogKitLoggerManager logManager = new LogKitLoggerManager(
> logCategory
> ,new org.apache.log.Hierarchy()
> ,new getLogger());
>
> could be a possible solution.
>
>
> BTW
>
>
>
> Regards
>
> Christopher
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Christopher Kohlhaas
Bungartstr 11a
53111 Bonn
RE: PATCHES Fortress
Posted by Berin Loritsch <bl...@apache.org>.
Could you try again? the patches didn't make it to the list.
> -----Original Message-----
> From: Christopher Kohlhaas [mailto:kohlhaas@bonn.edu]
> Sent: Monday, August 05, 2002 3:47 PM
> To: avalon-dev@jakarta.apache.org
> Subject: PATCHES Fortress
>
>
> Appended are two Patches for the Fortress Container.
>
> The "ContextBuilder.patch" fixes a copy and paste typo in
> ContextBuilder.java
>
> The "ContextManager_Linkage_Error.patch" makes the
> initialization of the DefaultConfigurationBuilder lazy.
> DefaultConfigurationBuilder calls
> SAXParserFactory.newInstance() in the Constructor and this
> will rise a LinkageError in some environments (for example
> when you use ant to start fortress). With the patch this
> error will not arise, when a Configuration-object is given.
>
>
> There is also a small inconvenience with the creation of the
> LogKitManager in the initializeLoggerManager() in the
> ContextManager file.
>
> The logkit-configuration initialization-DEBUG-information
> always appears in the console, no matter what logging
> configuration you use. The logger responsible for this output
> is created in the Constructor of LogKitManager(String
> prefix). It is only used during the initialization.
>
> Instead the default logger from the ContextManager should be used.
>
> LogKitLoggerManager logManager = new LogKitLoggerManager(
> logCategory
> ,new org.apache.log.Hierarchy()
> ,new getLogger());
>
> could be a possible solution.
>
>
> BTW
>
>
>
> Regards
>
> Christopher
>
> --
> 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>