Configuration is actually an Interface. It is therefore possible to use
something other than an XML document to configure the Configurable Object.
At one time I tinkered with using an LDAP respository as a Configuration
parameter. There is even somewhere in the code base an example of such a
beast. Unsure about the lifestyle extension stuff ,however.
Having said that I suspect that most people use XML documents.
|---------+---------------------------->
| | Justin Permar |
| | <[EMAIL PROTECTED]>|
| | |
| | 14/04/2004 13:29 |
| | Please respond to|
| | "Avalon framework|
| | users" |
| | |
|---------+---------------------------->
>----------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Configuration
|
|Classification: |-------------------|
|
| | ( ) In-Confidence |
|
| | (*) Unclassified |
|
| |-------------------|
|
|
|
>----------------------------------------------------------------------------------------------------------------|
I'm curious as to why a Configuration object is passed to a
Configurable instead of a general-purpose XML document? Is it
possible to use XML configuration for a component (maybe a
lifecycle extension that provides that capability)?
****************************************************************
NOTICE - This message is intended only for the use of the
addressee named above and may contain privileged and
confidential information. If you are not the intended recipient
of this message you are hereby notified that you must not
disseminate, copy or take any action based upon it. If you
received this message in error please notify HIC immediately.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of HIC.
****************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
