I like it, that sounds very useful indeed, and changing to the <import> tag to stay with the Spring DTD will be very good. Nice job work! Community frameworks are the greatest!

Chris


On Oct 21, 2006, at 6:26 PM, Sean Corfield wrote:

On 10/20/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote:
I've rolled up an include-tag-handling mechanism in my local DefaultXmlBeanFactory.cfc... it prevents infinite recursion, will include n-nested included files (includes within includes), and requires that the include tag be an immediate child of the beans tag.

Jared and I have been discussing this and Spring has an <import> tag
that is close to this include so in the interest of staying (nearly)
Spring-compatible, we both think the actual implementation should be:

<import resource="path/to/file.xml"/>

We also noted that Spring only supports a relative path, e.g.,
includes/myfile.xml or ../other.xml which probably ought to be
supported as well (a little tricky when using recursive includes :) as
well as the originally intended absolute path and mapped path (which,
of course, Spring does *not* support!).
-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


Reply via email to