> > Why not use the standard XML way to include files in other files, i.e. > > using entities? The above seems a bit like reinventing the wheel. > > I've used entities to include XML files before and I don't them for the > following reasons: > > * It's difficult to figure out exactly where a problem occurs if it's in > line 347 of the combined file. Since everything is referenced through > entities, you have to figure out which file and which real line you're > dealing with. > > * It doesn't allow you to take advantage of XML editors like IDEA that > are DTD aware as your included entities are only XML snippets. Here's > an example of what I mean: > > [--- a.xml ---] > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE document [ > <!ENTITY section1 SYSTEM "b.xml"> > ]> > > <document> > §ion1; > </document> > > [--- b.xml ---] > <?xml version="1.0"?> > > <document> > <ack/> > </document> > > The unrolled a.xml is > > <document> > <document> > <ack/> > </document> > </document> > > which is not what you want.
I agree with this. If we support it natively (not via the XML parser), we could let every single config file remain valid. -Pat ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
