Java – Spring 3.1 bean visibility using bean definition profiles

applicationcontextjavamavenspring

I have been experimenting with using Spring 3.1's bean definition profiles and nested beans. I had hoped that I could define different beans depending on the active profile. Consider the following heavily over simplified example such that my Spring context contains something like

<bean id="say" class="test.Say" p:hello-ref="hello"/>

<beans profile="prod">
    <bean id="hello" class="test.Hello" p:subject="Production!"/>
</beans>

<beans profile="dev">
    <bean id="hello" class="test.Hello" p:subject="Development!"/>
</beans>

I get the following error:

Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'say' defined in class path resource
[applicationContext.xml]: Cannot resolve reference to bean 'hello'
while setting bean property 'hello'; nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No
bean named 'hello' is defined at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1360)
aJava Result: 1

I was expecting that the hello bean would be defined according to the active Maven profile (in my case prod or dev). I'm starting to think that the Spring active profiles (spring.profiles.active) may be completely unrelated to Maven profiles.

Could somebody please explain where I am going wrong? (Is this even possible using profiles?).

Best Answer

I was expecting that the hello bean would be defined according to the active Maven profile (in my case prod or dev). I'm starting to think that the Spring active profiles (spring.profiles.active) may be completely unrelated to Maven profiles.

That's true, they are unrelated.

Here is how you can fix it:

Make sure that the web.xml that you have in src/main/webapp/WEB-INF/ folder has the following context setting:

<context-param>
    <param-name>spring.profile.active</param-name>
    <param-value>${profileName}</param-value>
</context-param>

And then make sure that the maven-war-plugin has filtering turned on for the web.xml:

<plugin>
    <artifactId>maven-war-plugin</artifactId>
    <version>2.3</version>
    <configuration>
        <filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
    </configuration>
</plugin>

And then lastly in your profiles:

<profiles>
    <profile>
        <id>dev</id>
        <properties>
            <profileName>dev</profileName>
        </properties>
    </profile>
    <profile>
        <id>prod</id>
        <properties>
            <profileName>prod</profileName>
        </properties>
    </profile>
</profiles>

You could also add a default value in the normal properties section:

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <profileName>dev</profileName>
</properties>

So if you run without the -P option the dev spring profile will be used.

When running mvn package the web.xml will have the correct value for the spring.profile.active.

Related Solutions

Java – how to wire the hibernate session factory manually in spring config

This work for me

<bean id="hibernateSessionFactory"
                class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
        <property name="configLocation">
            <value>classpath:/hibernate.cfg.xml</value>
        </property>
        <property name="dataSource" ref="dataSource">
        </property>
</bean>


<bean id="hibernateTransactionManager"
        class="org.springframework.orm.hibernate3.HibernateTransactionManager">
        <property name="sessionFactory" ref="hibernateSessionFactory" />
</bean>


<bean class="com.vaannila.dao.RegistrationDAOimpl"
        id="registrationDAO">
        <property name="sessionFactory">
            <ref bean="hibernateSessionFactory" />
        </property>
</bean>

Spring Java Configuration No bean named ‘entityManagerFactory’ is defined

One possible solution.

public class MyRepositoryImpl extends JdbcDaoSupport implements MyRepository {

    @Qualifier("odsDataSource")
    @Autowired(required = true)
    private DataSource ds;

    public MyRepositoryImpl() {
    }

    @PostConstruct
    void postConstruct() {
        setDataSource(ds);
    }

    ...
}

If you develop your repositories by extending JdbcDaoSupport (and also a few other Spring-provided helpers), then they will default to attempting to wire by name on the default "entityManagerFactory". So you need to initialise them by injecting your alternatively-named data beans.

Another possibility assuming you are using JPA.

@Repository
public class MyRepositoryImpl implements MyRepository {
    @PersistenceContext(unitName="MyPersistenceUnit")
    private EntityManager entityManager;

    public List<MyModel> findAll() {
        return entityManager.createNamedQuery("MyModel.findAll").getResultList();
    }
}

Update: For folks coming across this issue more recently, using Spring Boot and Spring Data JPA, I wrote a blog post running through the essentials of getting that working: http://scattercode.co.uk/2016/01/05/multiple-databases-with-spring-boot-and-spring-data-jpa/

Best Answer

Related Solutions

Java – how to wire the hibernate session factory manually in spring config

Spring Java Configuration No bean named ‘entityManagerFactory’ is defined

Related Topic