|
From: Colin S. <col...@ex...> - 2005-09-20 22:20:18
|
That's the exact question I thought of when I saw your blog post last night. You are supposed to be able to include one DTD in another. I've never really done it myself, but it looks basically to be very similar to how you include one XML fragment in another: <!ENTITY % mylists SYSTEM "dtds/listfrag.ent"> ... %mylists; or <!ELEMENT combo (A, X)> <!ENTITY % dtd_start SYSTEM "http://www.foo.com/start.dtd"> <!ENTITY % dtd_end SYSTEM "http://www.foo.com/end.dtd"> %dtd_start; %dtd_end; See this description: http://www.xml.com/pub/a/2001/03/28/qanda.html Colin Keith Donald wrote: > I’ve described a significant new feature for enhancing the modularity > of a SWF webflow definition here: > http://www.jroller.com/page/kdonald?entry=web_flows_as_application_modules > > I’ve already committed this enhancement to CVS head and the sellItem > sample code has been updated to demonstrate it. > > There is only one issue with the enhancement, and I’d like feedback on > it: I had to temporarily turn of XML dtd validation of > spring-webflow.dtd as I saw no way to easily import spring-beans.dtd > to allow for webflow-scoped bean definitions. In fact, with DTD-based > validation the only approach I can see for allowing bean definitions > within a webflow definition is just to duplicate the spring-beans.dtd > elements in spring-webflow.dtd. > > Does anyone know a better way? It’s not the end of the world if there > is some dtd duplication to support validation and code completion, but > I’d obviously like to avoid it if possible. > > Thanks, > > Keith > |