Home/ Questions/Q 7711561
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T01:24:25+00:00

I know the question I’m asking must be answered somewhere but I cant find

  • 0

I know the question I’m asking must be answered somewhere but I cant find an example on the net with some guidelines.

I wish to swap out the Spring 3.0 bean definition at build and runtime for a common codebase. I’m also using Maven profiles to build different versions of the same code.

Currently my bean def is

<bean id="somebean" class="com.x.SomeImpl" >

I will need to replace and deploy it at some times as

<bean id="somebean" class="com.x.SomeOtherImpl" >

Now the approaches I’m thinking of are

1) Use Maven profiles to switch out the complete applicationContext.xml to some other applicationContextB.xml based on the Maven profile.

2) Use Maven profiles to somehow? replace only the bean id definition for “somebean”

My questions are:

a) How can Option 2 be achieved?

b) These approaches still compile and package both SomeImpl and SomeOtherImpl during build. How can I pick only one and not the other for compliation and packaging into EAR?

I know Spring 3.1 has env profiles for the beans, but presently that’s not an option.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You could consider using the maven resources and filtering feature available. You could have placeholders in your context file and a property file per profile holding values. In each profile, you could use a different property file and appropriately have your context file filtered.

    • 0