Stephen McConnell wrote:
Stefano Mazzocchi wrote:
3) how open are you/avalon to changes to this DTD?
Totally open.
However, a better question is how reasonable is it to extend the deployment and composition object model instances. This implies implementation of readers and writers that capture domain specific (e.g. Cocoon value-added content) together with the underlying Avalon structures. Readers and writers currently include XML and serialized forms. In principal an extended form will be possible - and more to the point - will be required independently of Cocoon specific requirements simply to meet evolutionary needs in our object model.
I.e. think in terms of meta-model class extension - as opposed to DTD proliferation.
Here are the links to the immutable serializable meta-data classes that should be extended:
http://avalon.apache.org/merlin/api/org/apache/avalon/composition/data/ContainmentProfile.html
http://avalon.apache.org/merlin/api/org/apache/avalon/composition/data/DeploymentProfile.html
From here the next subject focusses on linking in a custom model defintion that implements the following:
http://avalon.apache.org/merlin/api/org/apache/avalon/composition/model/ContainmentModel.html
http://avalon.apache.org/merlin/api/org/apache/avalon/composition/model/DeploymentModel.html
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
