Consolidating configuration specifications

David Leangen dleangen at canada.com
Thu Feb 23 17:56:48 EST 2006


Great! It sounds like things are really moving forward. Good job!

One question: is the Magic build process essentially the same as before?
Would it be compabitle with an OSGi build?


Cheers,
Dave



> -----Original Message-----
> From: dev-dpml-bounces at lists.ibiblio.org
> [mailto:dev-dpml-bounces at lists.ibiblio.org]On Behalf Of Stephen McConnell
> Sent: 24 February 2006 04:29
> To: 'DPML Development'
> Subject: Consolidating configuration specifications
>
>
>
> With the DPML suite now fully functional I've been going over the general
> architecture with a pre. 1.0 review point-of-view.  There are a couple of
> topics which have come up - the first of which I'll address in this email.
>
> Issue:
>
>   1. We have two deployment specifications
>       (a) Transit's plugin model
>       (b) Metro's part model
>   2. And two deployment formats
>       (a) Properties file in Transit
>       (b) XML (JSR-57) in Metro
>   3. Transit deployment strategy is hard-wired (bad) within the
> plugin spec
>   4. The JSR-57 is not so human friendly (specifically
>      the old Merlin container definitions were much easier
>      to read and understand).
>
> To address these issues I have:
>
>   1. Moved Transit plugin from properties to XML
>   2. Defined an XML DTD that separates:
>       a. deployment strategy information
>       b. classloader chain information
>   3. Enable plugin deployment strategy customization such that an
>      plugin file reader can resolve a dedicated plugin handler.
>   4. And I'm in the process of updating Metro such that it is an example
>      of a custom deployment handler.
>
> I have also put in place formal DTD for:
>
>   a) the transit configuration
>   b) transit plugins
>   c) modules and libraries
>   d) component definitions (in progress)
>
> If your running against HEAD you should note the following:
>
>   a) the Transit configuration has changed to
> local:xml:dpml/transit/standard
>   b) modules files that contained the <module base="some-dir-value"/>
> statement
>      need to be changed to <module file="some-dir-value/module.xml"/>
>
> If you encounter any issues or warning messages please post a note to the
> list.
>
> Cheers, Steve.
>
> --------------------------
> Stephen McConnell
> mailto:mcconnell at dpml.net
> http://www.dpml.net
>
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml




More information about the dev-dpml mailing list