[SPR-1142] Load files in <import resource=.../> only once Created: 15/Jul/05  Updated: 15/Jan/19

Status: Open
Project: Spring Framework
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: Waiting for Triage

Type: Improvement Priority: Major
Reporter: Martin Zeltner Assignee: Juergen Hoeller
Resolution: Unresolved Votes: 67
Labels: bean-visibility-and-overriding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File SPR-1142-xml-application-context-import-once-2010-01-05.patch    
Issue Links:
Relate
relates to SPR-9526 Ignore duplicated import files or pro... Open
relates to SPR-7607 When a bean definition is overridden,... Closed
Days since last comment: 6 days ago
Last commented by a User: true
Last updater: Spring Issuemaster

 Description   

Example:

file1.xml:
<beans>
<import resource="classpath:common/common-config.xml"/>
...
</beans>

file2.xml:
<beans>
<import resource="classpath:common/common-config.xml"/>
...
</beans>

If I load now an application context which has "file1.xml" and "file2.xml" as config locations, the file "common-config.xml" will be loaded twice. I suggest to remember the url of already loaded config files.

Thanks,
Martin



 Comments   
Comment by Sébastien Launay [ 05/Jan/10 ]

Because this issue is opened for many years I was thinking of proposing a solution because our spring configuration uses lots of XML files decomposed with imports and lots of AOP configuration and computing unused bean definitions is expensive at runtime.

So here is a patch for loading application context resources only once against the trunk.
It contains:

  • modification to keep a list of previously imported resource URLs in order to know if this is an already imported resource (if this is the case it is ignored with an INFO log entry)
  • test cases
  • a paragraph in the reference documentation

This feature is enabled by setting the bean property importOnce to true on *XmlApplicationContext.
This property is false by default for backward compatibility purpose.

I do not know if this is interesting but I do not modified JavaConfig classes to reflect such behavior with @Import.

Let me know if this approach is right or if I need to go in another direction.

Comment by Tim Ducheyne [ 12/Aug/10 ]

Just a small remark about the patch:
I think it would be better to use URIs instead of URLs

There is a problem with the hashcode and equals implementation of URL
http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html

brgds,
Tim

Comment by Felix Simmendinger [ 30/Sep/10 ]

This behaviour is espacially then problematic, because BPP are executed multiple times if they are declared as anonymous beans or defined via a namespace eg. <context:property-placeholder ... . For the latter it is impossible to define an id. Since there are special beans that can be defined only once eg. the multipartresolver this problem means you cannot hide the multipartresolver in a xml file hierarchy as it may be loaded twice.

Comment by Dennis Homann [ 17/Feb/11 ]

This is a real pain and punishes people who modularize their application context in multiple smaller XML files.
Please consider fixing this issue in 3.1 instead of 3.2.

Comment by Keith Donald [ 19/Feb/11 ]

Can someone provide more info on why you would import the same file more than once? I'm curious what is trying to be accomplished where this comes up, as I've never encountered this myself in practice.

Comment by Dale Wyttenbach [ 19/Feb/11 ]

It typically happens indirectly:
A imports B imports C
A imports D imports C
It's an old problem, in C the #ifndef directive was used in similar situations.
I have opened a related issue SPR-7607, which I think would make the log messages a lot easier
to interpret in these situations.

Comment by Andy Schäfer [ 26/Mar/11 ]

Some additional thoughts to the comment of Dale Wyttenbach in answer to Keith Donald:

In order to ensure, that C isn't loaded twice we import in the topmost application.spring.xml all configurations (A, B, C and D). So the import of C is done only there, nowhere else.
Problem solved but other problems arise with this approach:

1) Design-flaw: dependencies between configurations aren't expressed explicitly

2) Running Tests: In order to run tests concerning for example B we had to load the configuration of B and C. Assumed C gets a dependency to a new configuration-file E, ALL tests of A,B,C AND D had to be changed. Instead we load the complete application-context for our tests. But now D and A are unnecessarily loaded for our B-test -> turnaround time increases.

Maybe there are approaches better than the one I outlined (interested to hear of them), but this issue would be handy to solve the problem in a simple way:

1) dependencies can be expressed explicitly (e.g. B imports C)
2) Each test had to load only the configuration of it's own module - dependent configurations are loaded transparently

Comment by Neha [ 04/Mar/14 ]

Since this issue had been logged around 9 years back and is still unresolved, I was just wondering if there is some major reason for it?
We were thinking of including our own classes in our project to handle this problem, so wanted to know if there is possibility of some side-effects, before moving the code to production?

Comment by Lucian Yao [ 10/Jun/15 ]

Please fix this issue. I was blamed by the peers by using the import in lower-level modules to save a lot of time in config and deploy.

Comment by Spring Issuemaster [ 14/Jan/19 ]

The Spring Framework has migrated to GitHub Issues. Please visit spring-projects/spring-framework#5845 for further activity, or to subscribe to receive notifications.

Generated at Mon Jan 21 09:25:17 UTC 2019 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.