STS (3.6.1 and others), Spring 4.1.x (latest), Spring Integration 4.1.2
In many of the Spring projects I'm working on in Eclipse / STS, we have a lot of Referenced bean not found warnings. They often refer to internal Spring beans / classes, and not to the legitimate misconfiguration of our own beans.
Here is an example from one of our Data JPA configurations:
Referenced bean 'jpaMappingContext' not found [config set: cr-core/primary]
Appropriate configuration:
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jpa="http://www.springframework.org/schema/data/jpa" xmlns:context="http://www.springframework.org/schema/context" xmlns:tx="http://www.springframework.org/schema/tx" xmlns:jdbc="http://www.springframework.org/schema/jdbc" xmlns:mongo="http://www.springframework.org/schema/data/mongo" xsi:schemaLocation="http://www.springframework.org/schema/data/mongo http://www.springframework.org/schema/data/mongo/spring-mongo-1.5.xsd http://www.springframework.org/schema/jdbc http://www.springframework.org/schema/jdbc/spring-jdbc-4.0.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.1.xsd http://www.springframework.org/schema/data/jpa http://www.springframework.org/schema/data/jpa/spring-jpa-1.3.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-4.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-4.1.xsd"> <jpa:repositories base-package="com.xyz.persistence" />
In our Spring integration configuration, we get even more warnings:
Referenced bean 'Create Text$child.Build Transmission.handler' not found [config set: cr-integration/primary] Referenced bean 'Create Text$child.Store ControlNumber in Header.handler' not found [config set: cr-integration/primary] Referenced bean 'Create Text$child.Store Parameters in Header.handler' not found [config set: cr-integration/primary] Referenced bean 'Create Text$child.Write IC to String.handler' not found [config set: cr-integration/primary] Referenced bean 'FilePoller.source' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.channel.interceptor.WireTap#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.channel.interceptor.WireTap#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.channel.interceptor.WireTap#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.handler.MessageHandlerChain#0$child.Store GS info in Header.handler' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.handler.MessageHandlerChain#0$child.Store IC info in Header.handler' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.integration.json.JsonToObjectTransformer#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.jms.listener.DefaultMessageListenerContainer#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.jms.listener.DefaultMessageListenerContainer#0' not found [config set: cr-integration/primary] Referenced bean 'org.springframework.scheduling.support.PeriodicTrigger#0' not found [config set: cr-integration/primary]
It seems that the more we use the Spring Integration namespaces namespaces, the more of them are displayed.
There are other related questions on older STS forums, and some of the SOs are similar to this one , whose accepted answer doesn't help at all. I tried several iterations of clearing, enabling and disabling the Spring bean link check, but no matter what I do, these false warnings always return when the check is turned on.
We repeat, these are not actual problems due to incorrect configuration or the "import support" function in STS (as described here ). And applications behave correctly at runtime; this is clearly a problem with STS.
We strive to keep our projects clean from all warnings, so they clog and hide legitimate warnings that really need our attention.
Is there a way to fix these problems and ultimately fix them? Are they even due to the same underlying problem or are there different problems here?