[#IDE-653] Spring's import element is not supported during validation

Spring IDE

Spring's import element is not supported during validation

Created: 16/Jul/07 12:11 AM Updated: 21/Jan/08 07:21 PM

Component/s:

beans.core

Affects Version/s:

2.0

Fix Version/s:

2.0.3

Time Tracking:

Not Specified

Description

« Hide

Let's use this ticket to summarize all the issues with Spring IDE's support for the <import> statement:

Only the simplest form (e.g. <import resource="services.xml> as shown in Spring's reference manual chapter http://static.springframework.org/spring/docs/2.0.x/reference/beans.html#beans-factory-xml-import 3.2.2.1. Composing XML-based configuration metadata) is supported. Here the imported file is expected to be in the same or relavtive to the directory of the importing file.
As stated in ticket #402 the classpath isn't checked for the importing file from the simple form mentioned in issue 1.
As stated in ticket #334 or #630 imports using the classpath protcol (as defined in Spring's refence manual chapter http://static.springframework.org/spring/docs/2.0.x/reference/resources.html#resources-resourceloader 4.4. The ResourceLoader) like <import resource="classpath:services.xml> are not supported.
As stated in ticket #358 or #397 imports with classpath wildcards (as defined in Spring's reference manual chapter http://static.springframework.org/spring/docs/2.0.x/reference/resources.html#resources-classpath-wildcards 4.7.2.2. The classpath*: prefix) like <import "classpath*:META-INF/spring/*/.xml"> are not supported.

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Torsten Juergeleit added a comment - 16/Jul/07 12:12 AM

At first some technical information regarding Spring IDE's validation of BeansConfig files:

1. Spring IDE's BeansConfigValidator only validates the entities of the internally managed BeansCoreModel. The BeansConfig XML files are not parsed during validation.
1. The BeansConfig XML files are only parsed while (lazily) populating the BeansCoreModel or after a modification of a BeansConfig file (callback from Eclipse's workspace via

IResourceChangeListener

).
1. The

IBean

instances or

IBeansComponent

instances (XML namespace) of a BeansConfig file in the BeansCoreModel are populated with the information available from Spring's tooling support interface

IReaderEventListener

. This interface provides callbacks for the different artifacts Spring's

XmlBeanDefinitionReader

finds during parsing a BeansConfig XML file, e.g. beans, components (namespaces), aliases and imports.

Ok, now some issues with the support of the classpath protocol

<import>

tag with the aforementioned approach:

1. How do we get the imported BeansConfig files and it's artifacts into the BeansCoreModel?[[BR]]Here we need some help from Spring's tooling support (refer to the http://opensource.atlassian.com/projects/spring/browse/SPR-3536 JIRA ticket SPR-3536) first.
1. How do we get an

IResource

for artifacts which are not part of the Eclipse workspace (no

IResource

available), e.g. entities in an Eclipse Web Tools dynamic web project or a Maven repository added to the classpath of a SpringProject via an Eclipse !ClasspathContainer?
1. How do we get informed about a modification of a BeansConfig file which is not part of the Eclipse workspace?

[ Permlink | « Hide ]

gk5885@kickstyle.net added a comment - 09/Aug/07 09:07 PM

[ Permlink | « Hide ]

mattrose added a comment - 04/Jan/08 05:37 PM

Even if you ignored artefacts from outside of the workspace, allowing imports specified by file name along inter-eclipse-project classpaths would meet all of my team's needs.

I imagine that's a more common case than external bean definitions in general?