Re: phoenix.tools.installer (about config.xml split)

[Paul Hammant]

Peter,

>Hi,
>
>Okay I got bored and didn't wait for your patch ;)
>
Me? Sorry dude.  I was actually thinking about it and had poked around 
in src.

>I actually implemented the ability to do
>
><config:include location="helloworld.xml"/>
>
>but found out I didn't really like it at all - was very non-intuitive.
>
>
>So what I would suggest doing is adding a definition of an entity at top of 
>config file and then using the entity in xml file. SO it would end up looking 
>something like
>
><!DOCTYPE config [
>    <!ENTITY helloworld SYSTEM "helloworld.xml">
>]>
>
><config>
>
>  <!-- this next line will load and expand the helloworld.xml file -->
>  &helloworld; 
>
></config>
>

A neat solution that allows SAX/DOM to sort it out.

I was thinking of a solution that worked at Sar construction stage. 
 Some form of Ant task that would make a config.xml from constituent parts:

<xmlcombine dest="build/conf/config.xml">
   <fileset> .....  </fileset>
</xmlcombine>

It could be reused for assembly.xml etc.  Or even for ejb-jar.xml ( or 
Beans.xml for EOB )

- Paul




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>