bean ref not found

[jbetancourt]

Installed Spring-ide version 1.1.1 in Spring 3.01, and use Spring 1.2 rcX.
Added nature to project and added context files to project.
Problem: beans that are referenced with "ref bean" are not being found.

In my applicationContext-db.xml file I have:

    <bean id="propertyConfigurer" class="org.springframework.beans.
            factory.config.PropertyPlaceholderConfigurer">
        <description>Use the 'run.properties' file to 
               override the properties 
               used in the Spring container</description>
        <property name="properties"><ref  
             bean="runProperties"></ref></property>        
    </bean>

This refers to the bean in the root applicationContext.xml file:

    <bean id="runProperties" class="org.springframework.beans.
         factory.config.PropertiesFactoryBean">
        <description></description>
        <property name="locations">
            <list>
                <value>file&#58;run.properties</value>
            </list>
        </property>        
    </bean>

All context files are flagged as in error in Eclipse. The app compiles and runs fine. I must be missing something about Spring-ide?

[Christian Dupuis]

Hi jbetancourt,

Spring IDE 1.1.1 ships with spring-core.jar version 1.1.5. Please don't use any features from the upcoming Spring 1.2 release e.g. inline values or refs. This is because the Spring IDE Xml parser (xerces) validates against the shipped dtd.

If this does not help please provide the full spring config files as well as the .springProject file from your eclipse project.

Greetings
Christian

[Torsten Juergeleit]

Did you create a config set for your depending config files?

Otherwise Spring IDE doesn't know anything about a relationship of certain config files and it validates every config file on it's own. With the existance of config sets config files which are part of a config set are validated within the context of a BeanFactory created from the config files belonging to the same config set.

This way the bean references can be resolved during validation.

Cheers,
Torsten

[jbetancourt]

That fixed it, thanks.

Did you create a config set for your depending config files?

Otherwise Spring IDE doesn't know anything about a relationship of certain config files and it validates every config file on it's own. With the existance of config sets config files which are part of a config set are validated within the context of a BeanFactory created from the config files belonging to the same config set.

This way the bean references can be resolved during validation.

Cheers,
Torsten

[memelet]

Did you create a config set for your depending config files?

This works if all the config-files are in the same project. But when some (or most) of the ref'ed beans are defined in config-files from other projects the I cannot eliminate the errors. (see http://springide.org/project/ticket/77)

Is there some other workaround?

Also when I remove the spring nature, the error markers remain. How can I get rid of the error markers after removing the spring nature?

[Torsten Juergeleit]

This works if all the config-files are in the same project. But when some (or most) of the ref'ed beans are defined in config-files from other projects the I cannot eliminate the errors.

For referencing config files in a different Spring project you have to select this external Spring project in the list of "Project References" in your Spring project's properties first. This way Spring IDE get's aware of your externally defined Spring config files. Now you can add the Spring config files of the external Spring project to config sets defined in your Spring project. The Java build path isn't checked for Spring projects because it's available for Java projects only. Spring projects don't have to be Java projects.

Also when I remove the spring nature, the error markers remain. How can I get rid of the error markers after removing the spring nature?

To get rid of the problem markers you have the following options:

• remove the config files from the Spring project via project properties dialog "Spring Beans / Config"
• turn of displaying Spring IDE's problem markers at all (via the problem views' filter setting by deselecting "Spring Problem Marker")

I have added these questions to the Spring IDE FAQ: http://springide.org/project/wiki/SpringideFaq

Your ticket (http://springide.org/project/ticket/77) is updated as well.

[memelet]

For referencing config files in a different Spring project you have to select this external Spring project in the list of "Project References" in your Spring project's properties first. This way Spring IDE get's aware of your externally defined Spring config files.

I forgot to mention that I tried this (because it was indicated on the wiki somewhere), but it did not work. Even with the depedent project selected I was not offered the option to select config files from that project.

(This is 1.2 running M7 BTW)

[Torsten Juergeleit]

Even with the depedent project selected I was not offered the option to select config files from that project.

Your are only offered to add them while creating / editing a config set ;-).

I have updated the FAQ http://springide.org/project/wiki/SpringideFaq. Please edit entry 2.1 in this wiki page if it's not clearly defined yet . Thanx.

Cheers,
Torsten

[memelet]

Ok, I works now. Almost. Now I get a popup containing:

Errors during build.
Errors running builder "Spring Project Builder" on project bbt.liquidityarbitrage.
An error occurred while traversing resources.

The entry in the log contains:

java.lang.IllegalArgumentException: Path for project must have only one segment.
	at org.eclipse.core.internal.utils.Assert.isLegal(Assert.java:60)
	at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:134)
	at org.springframework.ide.eclipse.beans.core.internal.model.BeansModel.getProject(BeansModel.java:125)
	at org.springframework.ide.eclipse.beans.core.internal.model.BeansModelUtils.getConfig(BeansModelUtils.java:55)
	at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfigValidator.validate(BeansConfigValidator.java:96)
	at org.springframework.ide.eclipse.beans.core.internal.project.BeansProjectValidator.build(BeansProjectValidator.java:69)
	at org.springframework.ide.eclipse.core.internal.project.SpringProjectBuilder.build(SpringProjectBuilder.java:154)
	at org.springframework.ide.eclipse.core.internal.project.SpringProjectBuilder.access$0(SpringProjectBuilder.java:150)
	at org.springframework.ide.eclipse.core.internal.project.SpringProjectBuilder$Visitor.visit(SpringProjectBuilder.java:109)
	at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:103)
	at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:50)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:81)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:85)
	at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:85)
	at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:126)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:60)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:101)
	at org.eclipse.core.internal.resources.Resource.accept(Resource.java:80)
	at org.springframework.ide.eclipse.core.internal.project.SpringProjectBuilder.build(SpringProjectBuilder.java:91)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:585)
	at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1029)
	at org.eclipse.core.runtime.Platform.run(Platform.java:775)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
	at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1029)
	at org.eclipse.core.runtime.Platform.run(Platform.java:775)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:200)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

The error only occurs with spring-nature enabled -- remove the spring-nature and the error is not issued.

[Torsten Juergeleit]

Ok, I works now. Almost. Now I get a popup containing:

Errors during build.
Errors running builder "Spring Project Builder" on project bbt.liquidityarbitrage.
An error occurred while traversing resources.

I opened a new ticket: http://springide.org/project/ticket/80