Apache Directory Project - Re: [jira] Created: (DIRSERVER-611) An OSGi Activator can allow

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > April 2006 > Re: [jira] Created: (DIRSERVER-611) An OSGi Activator can allow





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: [jira] Created: (DIRSERVER-611) An OSGi Activator can allow
John E. Conlon

2006-04-28, 1:11 pm

On Fri, 2006-04-28 at 00:54 -0400, Enrique Rodriguez wrote:
> John Conlon (JIRA) wrote:
> ...
>
> Was this intentional ^^^ to use 'configuration' as the extension? In
> the comment, below, you use props.

Yes it was intentional. As you mentioned in a previous email the
standard way to pass log4j configuration was with a command line like:
java -Dlog4j.configuration=file://$(pwd)/conf/log4j.properties -jar
bin/felix.jar

Earlier version of felix required a property in the config.properties
file to pass system properties through to bundles. I used one like this.

log4j.configuration=${log4j.configuration}

Recent version of felix seem to 'pass' the system property through to
the bundles with out need for the pass through property in
config.properties so I just commented out the above property and use the
command line. If I want to hard code the location I can just uncomment
the property and use it, without putting it in the startup script.

> This why your SCR logging died?

All other non-scr bundles continued to log to the console (including the
apacheDS backend) but not the one bundle I tested with scr. After I
changed that bundle back to servicebinder it then sent its logs (and
System.out.println just fine.

regards,
John






Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com