Maybe you can reuse some code from Jakarta ANT for dealing with the get/set
methods. ANT's approach works well and makes it easy to write components
that can be configured via XML. It should be easy to adapt to support
configuration via property files, as well. ANT uses reflection to achieve
this.
> -----Original Message-----
> From: Anders Kristensen [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 22, 2001 1:01 PM
> To: LOG4J Users Mailing List
> Subject: Re: Why more set(....) APIs than get(....) APIs in log4j ?
>
>
> Jin,
>
> Funny you should ask, because the getters you ask for have
> actually been
> applied to the log4j version in the CVS repository and will
> be included
> in the next release. However, we've been discussing the option of
> changing the current option OptionHandler configuration strategy from
> something based on
>
> void setOption(String key, String value) { ... }
> String getOption(String key) { ... }
> String[] getOptionsStrings()
>
> to something based on regular Java setters and getters, e.g.
>
> void setFilename(String name)
> String getFilename() { ... }
>
> and then use a Beans-like strategy or reflection or something
> to figure
> out which parameters a log4j component knows about. That seems to be a
> better approach but requires a bit more work.
>
> Anders
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
