Ok done, thx :)
On Fri, Jan 29, 2010 at 1:43 PM, Toni Menzel wrote:
> You can use your jira credentials directy. Use the https protol for svn
> checkout.
>
> On 29.01.2010, at 14:38, David Savage wrote:
>
>> Ok so I've got a patch, basically the following code is needed in the
>> j.u.l setup in
You can use your jira credentials directy. Use the https protol for svn
checkout.
On 29.01.2010, at 14:38, David Savage wrote:
> Ok so I've got a patch, basically the following code is needed in the
> j.u.l setup in the service activator:
>
> +LogManager manager = LogManager.getLogM
Ok so I've got a patch, basically the following code is needed in the
j.u.l setup in the service activator:
+LogManager manager = LogManager.getLogManager();
+manager.reset();
+
+// clear out old handlers
+Logger rootLogger = manager.getLogger( "" );
You can solve it directly by committing. No need for patches in jira. The
jira issue we use just to keep track of work to be/done.
On Fri, Jan 29, 2010 at 1:52 AM, David Savage wrote:
> Hi Niclas,
>
> Ok thx no problem I'll do as you suggest and raise a Jira. I tend to
> avoid j.u.l logging too b
Hi Niclas,
Ok thx no problem I'll do as you suggest and raise a Jira. I tend to
avoid j.u.l logging too but it's running in code we don't have the
source to...
I'll have a dig around in our old logging code, I think we j.u.l
config working though we ideally want to move to pax logging as in the
e
Sounds like a bug.
I have never used jdk logging in real systems, and the support for it
in Pax Logging was added long time ago "since we can".
I suspect that the jdk logging also has some logging configuration
present that defaults to "to console" which perhaps need to be
disabled "somehow".
Un
Hi there,
I'm currently evaluating switching our internal log management code
over to use pax logging but I'm seeing some odd behaviour wrt j.u.l
handling and I wonder if it's a known problem or something I'm not
doing?
I've installed both the api and service bundles (version 1.4) and
started bot
On Mon, Jan 25, 2010 at 4:49 PM, Lars Fischer wrote:
> I use the Pax ConfMan to provide the logging configuration to Pax Logging.
> My configuration is read on OSGi startup and Pax Logging is working fine
> with it.
>
> I thought Pax ConfMan will observe my configuration-file and provide changes
Hello Niclas,
Niclas Hedhman wrote:
Pax Logging relies on the Configuration Admin service, as specified in
the OSGi Compendium specs.
So, you need a service implementation that can provide the
configuration to Pax Logging, and without it, "nothing" will happen.
I have no current overview of av
On Sun, Jan 24, 2010 at 2:21 AM, Lars Fischer wrote:
> Do I have to trigger an update to apply the changed properties-file?
Pax Logging relies on the Configuration Admin service, as specified in
the OSGi Compendium specs.
So, you need a service implementation that can provide the
configuration
Hello,
I use Pax Logging with Pax ConfMan configured in the
"services/org.ops4j.pax.logging.properties" file.
I thought it would possible to update the logging configuration during
runtime by only changing the contents of this file.
But I don't see a different behavior, while I change the log-le
okay, understood.
Well it was a valid key in the dictionary (with url in value part).
But this has been deprecated, see this section from
http://wiki.ops4j.org/display/ops4j/Pax+Logging
"Deprecation: Pax Logging used to support Log4J-ConfigFile entry in
Dictionary object provided from the Config A
>
>
> config by url: can you point me to "the documentation seems
> to describe this.." ?
>
What I understand here, it's I have to put the URL with Log4J-ConfigFile key
:
http://www.ops4j.org/projects/pax/logging/reference/configuration.html
>
> On Mon, May 25, 2009 at 10:08 PM, Stéphane Je
config by url: can you point me to "the documentation seems to
describe this.." ?
On Mon, May 25, 2009 at 10:08 PM, Stéphane Jeanjean
wrote:
>
>>
>> The dictionary IS your log4j file (content) ! Thats what fileinstall
>> actually does.
>>
> Ok, thanks Toni, now, I understand.
>
> Is there a way
>
> The dictionary IS your log4j file (content) ! Thats what fileinstall
> actually does.
>
Ok, thanks Toni, now, I understand.
Is there a way to set a URL instead of the complete configuration ? The
documentation seems to describe this, but I don't understand how to set this
URL.
> On 25.0
The dictionary IS your log4j file (content) ! Thats what fileinstall
actually does.
On 25.05.2009, at 18:17, Stéphane Jeanjean m> wrote:
If I would like to use the Config Admin Service. I think, I have to
use this sort of code :
config = _confAdmin.getConfiguration("org.ops4j.pax.loggin
If I would like to use the Config Admin Service. I think, I have to use
this sort of code :
config = _confAdmin.getConfiguration("org.ops4j.pax.logging",null);
Dictionary props = config.getProperties();
props.put("log4j", ??)
I am right ?
What to put in the props ? A string with a URL startin
you can use fileinstall from felix.
Then, placeing a file called org.ops4j.pax.logging.cfg into the load
folder with your log4j configuration should be all you need.
Because this also allows dynamic updates right from filesystem this is
probably the simpliest way to start with.
On 5/25/09, Stéphan
Hello
I try to configure the logging of my system.
I have updated my bundle to avoid embeding slf4j and log4j and I have
added an import org.slf4j; provider=paxlogging in my manifest file.
Just to test, I tried to launch my application with mvn pax:provision
-Dorg.ops4j.pax.logging.DefaultSe
Ok, I agree with you.
thank you for the quick support,
Miguel
On Wed, 2009-01-14 at 21:44 +0100, Niclas Hedhman wrote:
> Hedhman
___
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
On Wed, Jan 14, 2009 at 9:05 PM, Miguel wrote:
> I don't get you. It is currently working with the configuration shown in my
> last mail. Why did you say that all that is not necessary?
It is not necessary to be involved in the configuration process for
the propsloader to push a configuration to
I don't get you. It is currently working with the configuration shown in
my last mail. Why did you say that all that is not necessary?
On Wed, 2009-01-14 at 20:50 +0100, Niclas Hedhman wrote:
> On Wed, Jan 14, 2009 at 8:45 PM, Miguel wrote:
>
> > Log4J-ConfigFile with the url of the log4j.pro
Thank you very much Niclas,
the issue about the propsloader was clear, the problem was (both
PropsLoader and org.apache.commons.logging) I was setting just the
property Log4J-ConfigFile with the url of the log4j.properties file but
it didnt work.
I finally use org.osgi.service.cm.ConfigurationAdm
On Wed, Jan 14, 2009 at 8:45 PM, Miguel wrote:
> Log4J-ConfigFile with the url of the log4j.properties file but it didnt
> work.
Correct, that feature was dropped pre-1.0 as it was not really useful.
> The first time you load this properties, congig.getProperties() is null
> because no configur
On Wed, Jan 14, 2009 at 6:33 PM, Niclas Hedhman wrote:
> I have tried with org.ops4j.pax.configmanager_0.2.2.
This is also known as the "PropsLoader", a very simple configuration
admin, which loads properties files and make them available as
Configuration instances.
So, you have a org.ops4j.pax
-- Forwarded message --
From: Miguel
Date: Wed, Jan 14, 2009 at 6:17 PM
Subject: Re: [osgi-dev] PAX-logging configuration
To: OSGi Developer Mail List
I have tried with org.ops4j.pax.configmanager_0.2.2.
and I have also tried to log using:
import
I asked on the osgi-dev list as well, and only repeat here for
completeness; Which Config Admin service implementation are you using?
Cheers
Niclas
On Wed, Jan 14, 2009 at 5:04 PM, Miguel wrote:
> Hello,
>
> we are trying to configure the pax logging service in our applications. we
> are current
Hello,
we are trying to configure the pax logging service in our applications.
we are currently use the following bundles:
1 ACTIVE org.ops4j.pax.logging.pax-logging-api_1.3.0
[...]
10 ACTIVE org.ops4j.pax.logging.pax-logging-service_1.3.0
We use org.osgi.service.cm.ConfigurationAdmin
There are two problems around the request;
1. Propsloader is a really simple Configuration Admin agent, and there
might be others that are much better, that could have configuration
spread out in several location to create a single Configuraion
instance.
2. Log4j is really a hierarchy based syste
Forwarded from another mailing list:
=
Hi,
I want to use pax logging in a couple of eclipse plugins and I want each
plugin to have it's own log configuration. How can I configure pax logging
to use different log configurations for my plugins ?
I followed the "How to configure pax logging (for
Hi David,
I agree we need to find a balance between Maven and other sources of
"generated" docs and the wiki, which is more of a standalone thing.
Any suggestions are most welcome - we have not been able to find any
good integration points for this ...
/peter
GTalk: neubauer.peter
Skype peter.neu
Main source of documentation was transferred from Wiki to Maven
generated docs some years ago. Have you come across
http://www.ops4j.org/projects/pax/logging ?? I know it is not
comprehensive, but I would prefer to not maintain multiple doc
sources.
In that case, it would be really nice to rew
On Sat, Aug 9, 2008 at 2:03 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 7, 2008 at 9:46 PM, Matthew Roy <[EMAIL PROTECTED]> wrote:
>
> Thanks. It is somewhat amusing to read "not miss any events" and
> "getting unwanted events" in the same problem description.
>
:-)
>> 1. Does it ma
On Thu, Aug 7, 2008 at 9:46 PM, Matthew Roy <[EMAIL PROTECTED]> wrote:
Thanks. It is somewhat amusing to read "not miss any events" and
"getting unwanted events" in the same problem description.
> 1. Does it make sense to use the
> org.ops4j.pax.logging.DefaultServiceLog.level property within the
Hello all,
I've been trying to get my head around how pax logging works during the
initial start-up of an osgi container and how all the different
configuration properties affect what logging events end up on the
console/appenders. Here is my understanding of what I am seeing when I
start-up my o
On Mon, Jul 21, 2008 at 1:20 AM, Ulrik Sandberg
<[EMAIL PROTECTED]> wrote:
> I've been looking around a bit, but can't really find a good tutorial for
> how to configure Pax Logging. There are some brief pointers to things like
> Config Admin and Pax ConfMan, but being a newbie to this, it's hard t
Done.
On Mon, Jul 21, 2008 at 11:09 AM, Alin Dreghiciu <[EMAIL PROTECTED]>
wrote:
> That sounds right. So, you can now add this to a page about how to
> configure pax logging on ops4j wiki? :)
>
> On Mon, Jul 21, 2008 at 10:44 AM, Ulrik Sandberg
> <[EMAIL PROTECTED]> wrote:
> > I haven't yet foun
That sounds right. So, you can now add this to a page about how to
configure pax logging on ops4j wiki? :)
On Mon, Jul 21, 2008 at 10:44 AM, Ulrik Sandberg
<[EMAIL PROTECTED]> wrote:
> I haven't yet found out how to solve (1), and I haven't examined the config
> admin service in order to do (2), b
Typo in folder name:
Add a file runner/configuration/services/org.ops4j.pax.logging.propertieswith
contents:
>
should be:
Add a file
> myapp/runner/configurations/services/org.ops4j.pax.logging.properties with
> contents:
>
On Mon, Jul 21, 2008 at 10:44 AM, Ulrik Sandberg <[EMAIL PROTECTED]>
w
I haven't yet found out how to solve (1), and I haven't examined the config
admin service in order to do (2), but I do seem to have a solution to (3):
- Create folder myapp/runner/configurations/services
- Add a file
runner/configuration/services/org.ops4j.pax.logging.properties with
I've been looking around a bit, but can't really find a good tutorial for
how to configure Pax Logging. There are some brief pointers to things like
Config Admin and Pax ConfMan, but being a newbie to this, it's hard to get
any further. Also, I use Equinox, which might affect how it's done.
I woul
Anyone know why I'm getting petabytes of the following message shoved
down my throat?
51714 [ModificationWatcher Task] DEBUG wicket.util.thread.Task - Run
the job: [EMAIL PROTECTED]
51714 [ModificationWatcher Task] DEBUG wicket.util.thread.Task -
Finished with job: [EMAIL PROTECTED]
I'd REALL
42 matches
Mail list logo
