<include> is not parsed for ioc
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
What steps will reproduce the problem?
1. Create a ioc XML that defines a <include> tag to another beans XML.
2. Run the application.
What is the expected output? What do you see instead?
The expected is to have both XML files loaded and all beans created.
What happens instead is that the parser will complain for the <include>
node not having an id (it's treating it as a <%custom%> tag), and even if
the id is present, it will attempt and fail to register the bean "".
What version of the product are you using? On what operating system?
Lowra533
Original issue reported on code.google.com by juansot...@gmail.com
on 13 Nov 2009 at 7:02