Scott,

That would be great, and indeed, an argument would do the job as well.

dirk

> -----Original Message-----
> From: Scott Deboy [mailto:[EMAIL PROTECTED] 
> Sent: vrijdag 25 februari 2005 19:18
> To: Log4J Users List
> Subject: RE: Specify chainsaw config file in webStart link
> 
> 
> Good idea...
> 
> I'll look into the best way to implement this (maybe by 
> adding a 'configurationURL' argument to the JNLP - you'd then 
> set up each shortcut/batch script to call javaws explicitly, 
> passing in the URL and providing the configurationURL argument.
> 
> Scott
> 
> 
> -----Original Message-----
> From: OOMS DIRK [mailto:[EMAIL PROTECTED]
> Sent: Fri 2/25/2005 6:30 AM
> To:   'Log4J Users List'
> Cc:   
> Subject:      RE: Specify chainsaw config file  in webStart link
> After having looked more into it, i believe i need to clarify 
> my earlier
> question. I would like to start chainsaw via webStart and 
> each time it is
> launched it has to use another 'plugin-config' file. So it is not the
> log4j.configuration (which describes the logging of chainsaw 
> itself) that is
> changing. In the chainsaw code i noticed that this 
> 'plugin-config' file is
> specified as a property named configurationURL in the file
> chainsaw.settings.properties. 
> 
> My requirement would be met if this property could be set as a System
> Property in e.g. the .JNLP file (e.g. named
> log4j.chainsaw.pluginconfiguration?). This would require only 
> a small change
> to the chainsaw code (reading the system property and if it is defined
> overwriting the value of configurationURL). Does this make sense?
> 
> dirk
> 
> > -----Original Message-----
> > From: OOMS DIRK 
> > Sent: donderdag 24 februari 2005 18:43
> > To: 'Log4J Users List'
> > Subject: RE: Specify chainsaw config file in webStart link
> > 
> > 
> > Scott,
> > 
> > I tried out your below suggestion: adding <property
> > name="log4j.configuration" 
> > value="http://myServer/myLog4jConfig.xml"; />to
> > the resources section of the .jnlp file, but it does not seem 
> > to work (I
> > also tried it with "file:" and "ftp:"). Is the "should" in 
> > your reply a
> > "should" or a "must". In the former case I could try to trace 
> > down whether
> > something goes wrong in the chainsaw code.
> > 
> > Cheers,
> > dirk
> > 
> > > -----Original Message-----
> > > From: Scott Deboy [mailto:[EMAIL PROTECTED] 
> > > Sent: vrijdag 21 januari 2005 17:30
> > > To: Log4J Users List
> > > Subject: RE: Specify chainsaw config file in webStart link
> > > 
> > > 
> > > If you take the existing .jnlp file and turn it into a jsp 
> > > that you host on your site, you should be able to specify the 
> > > log4j.configuration 'property' as the URL you're generating.
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From:     OOMS DIRK [mailto:[EMAIL PROTECTED]
> > > Sent:     Fri 1/21/2005 7:58 AM
> > > To:       'log4j-user@logging.apache.org'
> > > Cc:       
> > > Subject:  Specify chainsaw config file  in webStart link
> > > Hello,
> > > 
> > > I am thinking of building a web application that allows 
> the user to
> > > configure a subset of the log4j configuration parameters 
> in a 'user
> > > friendly' way (so he/she does not have to know all log4j 
> > configuration
> > > details). At the same time I will generate the corresponding 
> > > chainsaw config
> > > file on my web server and give the user the opportunity to 
> > > start Chainsaw
> > > with this generated config file. Is there a way to specify 
> > > the config file
> > > in the webStart link?
> > > 
> > > dirk
> > > 
> > > 
> > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to