This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
There are a couple of well known best practices when dealing with .xml. Netbeans could warn when these appear. Netbeans could warn about <import> presence on the .xml as a bad practice See point 6 http://www.onjava.com/pub/a/onjava/2006/01/25/spring-xml-configuration-best-practices.html <quote> 6. Prefer assembling bean definitions through ApplicationContext over imports Like imports in Ant scripts, Spring import elements are useful for assembling modularized bean definitions. For example: <beans> <import resource="billingServices.xml"/> <import resource="shippingServices.xml"/> <bean id="orderService" class="com.lizjason.spring.OrderService"/> <beans> However, instead of pre-assembling them in the XML configurations using imports, it is more flexible to configure them through the ApplicationContext. Using ApplicationContext also makes the XML configurations easy to manage. You can pass an array of bean definitions to the ApplicationContext constructor as follows: String[] serviceResources = {"orderServices.xml", "billingServices.xml", "shippingServices.xml"}; ApplicationContext orderServiceContext = new ClassPathXmlApplicationContext(serviceResources); </quote>