Jeremias Maerki wrote:

I'd vote for an Avalon Configuration object which can be built easily
from XML and passed through from Cocoon which is also based on Avalon.
Configuration objects are also easily built by hand if necessary.
Right. Lets stop reinventing the wheel (being diving into avalon).

The UserAgent should IMO implement the Configurable interface which
defines an Avalon standard contract how the object is configured.
The problem is that user agent properties are just part of FOP configuration properties. May be we should separate FOP config from User Agent config. Well, I need to avalonize my brain first.

Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel

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

Reply via email to