We could follow the same approach we have for node configuration. Basically:
1) It can be loaded from an external (xml) file
2) It can be programmatically configured using DSL style java methods
The syntax can be something like:
<nodeFactory>
<domains>
<domain uri="..." registry="..."/>
</domains>
... <!-- other configurations for system services declared in the
META-INF/services -->
</nodeFactory>
Thanks,
Raymond
--------------------------------------------------
From: "Raymond Feng" <[email protected]>
Sent: Tuesday, February 02, 2010 9:05 AM
To: <[email protected]>; <[email protected]>
Subject: Re: Our story for Domain/Node
I'm open to have a general configuration so we can control the settings of
extension points and extensions too.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Tuesday, February 02, 2010 2:07 AM
To: <[email protected]>
Subject: Re: Our story for Domain/Node
On Fri, Jan 29, 2010 at 9:43 PM, Raymond Feng <[email protected]>
wrote:
4) TBD: The NodeFactory can be configured with a mapping between
domainURIs
and registryURIs so that NodeFactory knows the registryURI for a given
domain.
* The initial mapping can be populated by the hosting environment (for
example, from an property file)
* A map can be added to NodeFactory to allow it to be configured
programmatically.
How about having a more general config options map on the NodeFactory
and the registry config is just one of those options in that map, so
we can also use that map for other config things like schema
validation, overriding rankings etc.
...ant
