Stephen, >> We're _not_ using one codebase then? > > > > Correct - the phonix code base for component assembly reads in an > xinfo based on a phoneix specific DTD and the Merlin system reads in > an xinfo based on the excalibur/meta type DTD. The DTDs describe > similar things but the structures are different. In the > excalibur/meta DTD you have the addition of context, extensions and > stage depedencies which do not exist in the Phoenix meta. In > addition, all of the second level elements can contain attribute > defintions (which don't exist in the Phoenix DTD). > > Basically, excalibur/meta is a superset of the Phoenix meta. Merlin > can describe a Phoneix block using the excalibur/meta but the reverse > is not true. Take a look at the page > http://jakarta.apache.org/avalon/excalibur/meta/type.html for an > example of a excalibur/meta type description.
I knew that. I still felt it was possible to generate multiple outputs. Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
