Re: [Springframework-developer] Import tag for XML bean definitions

[Timo V. <sic...@gm...>]

Hi!

Maybe the XInclude Candidate Recommendation from W3C should be=20
considered for the syntax (http://www.w3.org/TR/xinclude/). Future XML=20
Editors might provide support for it.

Regards,

Timo


Am Freitag, 4. Juni 2004 10:29 schrieb j=FCrgen h=F6ller [werk3AT]:
> We've got an enhancements request in JIRA, currently for the 1.0.3
> timeframe:
>
> http://opensource.atlassian.com/projects/spring/browse/SPR-137
>
> Essentially, it's about an <import> tag that allows to specify
> imports within an application context XML file rather than in an
> external "contextConfigLocation" setting - imports driven by the XML
> file itself rather than from the outside.
>
> <import file=3D'imported.xml'/>
>
> <beans>
>
>   ...
>
> </beans>
>
> Something similar can already be achieved with XML entity includes,
> but those are arguably not very convenient to use. XWork has such an
> <import> tag, BTW; Mike Cannon-Brookes has already suggested this for
> Spring a couple of months ago too.
>
> I wouldn't mind adding such an option, although I still prefer
> external contextConfigLocations. It does have some effects on our
> XmlBeanDefinitionReader/Parser signatures, though, as a
> ResourceLoader is needed by the parser now for resolving those import
> locations. This indicates that it might be better to introduce this
> for 1.1 rather than for 1.0.3, I guess.
>
> Thoughts?
>
> Juergen
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
> installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-develope
>r