Comments on: Spring Java Configuration Moving Ahead

By: SpringSource Team Blog » See you at SpringOne Europe!

SpringSource Team Blog » See you at SpringOne Europe! — Tue, 24 Mar 2009 17:46:52 +0000

[...] moving the core Spring Java Configuration model to the Spring Framework project: something I think is particularly exciting. Several SpringOne sessions will cover Spring 3.0 features, demonstrating important new features [...]

By: SpringSource Team Blog » Spring Dependency Injection & Java 5 (including slides and code)

Tue, 18 Mar 2008 16:16:49 +0000

[...] Spring Java Configuration Moving Ahead by Rod Johnson [...]

By: Joris Kuipers

Joris Kuipers — Sat, 08 Dec 2007 12:17:10 +0000

[quote comment="61370"]What I would like to see is support for 'environment dependent' properties. We like to keep all our properties in a single property file (we don't want to make separate wars/ears for different environments), with property values for the different environments the application is deployed to (e.g. development, testing, staging, production).[/quote]
One way to do this with JavaConfig is to create a common configuration class and subclasses per environment. Then determine the subclass to use at startup based on your system property. I've implemented this exact solution for a talk I gave at SpringOne this year; have a look at the code here: http://blog.interface21.com/main/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/

By: Rick Hightower

Rick Hightower — Thu, 15 Nov 2007 00:19:58 +0000

I don't think it needs more features to go 1.0. I like the set it ships with now. Let this set be 1.0.

The sooner it goes 1.0 the better. )

By: It’s Only Software » Spring 2.5 RC2 out, Includes new Spring MVC Tutorial

Wed, 14 Nov 2007 12:41:22 +0000

[...] The tutorial seems to have been written without consideration for the new annotation-based configuration introduced in Spring 2.5 – indeed, there's nary a mention of annotations (except for the ubiquitous @Override) in the entire document. I'm not sure why this is, considering that claims of easier annotation-based configuration have been common in Spring 2.5 announcements and even on the Interface21 blog. [...]

By: Barbarian » Spring Java Configuration Moving Ahead

Barbarian » Spring Java Configuration Moving Ahead — Mon, 12 Nov 2007 08:29:22 +0000

[...] Career College News wrote an interesting post today onHere's a quick excerptRod Johnson. Several users have asked whether we are committed to Spring Java Configuration, and how it sits with the annotation configuration option introduced in Spring 2.5. The answer is yes, we are committed to Java Config; … [...]

By: Solomon

Solomon — Thu, 08 Nov 2007 15:55:04 +0000

Congrats to both Interface21 and Chris Beams.

I look at JavaConfig and annotation configuration as a 1-2 punch combination. Not only do I think that "there is even no reason that both couldn't be used in the same application," but I think that there is every reason to use both of them in the same application.

The "simpler" annotation configuration approach takes less work to implement, but simply isn't as powerful as the JavaConfig approach for a variety of reasons. The JavaConfig approach is a logical extension point for an annotation configured application, much more so than the vastly different "traditional" XML approach. Such an approach would be similar in nature to Guice's annotation/provider combination.

Explaining where annotation configuration can be used and where JavaConfig is required would go a long way in helping both technologies.

Using common annotations would also be a valuable addition. @Component/@Service/@Repository/@Controller are roughly equivalent to @Bean. @ExternalBean/@ExternalValue are roughly equivalent to @Qualifier and custom Qualifiers.

I think that the ResourceBundle lookup and the @ExternalValue setting of values is a great addition. It can and should be used in the annotations configuration approach as well.

Overall, I would think that Mark Fisher and Chris Beams should have a long talk about a unified approach to Spring Annotations.

By: Tim Pijpops

Tim Pijpops — Wed, 07 Nov 2007 23:24:40 +0000

Hello Rod,

What I would like to see is support for 'environment dependent' properties. We like to keep all our properties in a single property file (we don't want to make separate wars/ears for different environments), with property values for the different environments the application is deployed to (e.g. development, testing, staging, production).

Currently we have implemented this with a custom subclass of java.util.Properties for the Propertyplaceholderconfigurer in Spring's XML config. This means that we can use property files like this:

name=John Doe
name{dev}=Mike Keets
name{test}=An Meyers
age=45
busy=false

If no environment is specified, 'John Doe' is used as the name value. However, if an enviroment 'dev' is specified (as a system property, e.g. -Denv=dev) the value 'Mike Keets' is used.

Especially for the configuration of resources (database properties, transaction managers, messaging queues) this is a handy feature since we use a lightweight (Tomcat) server for development and a heavier weight (commercial) one for production.

Best regards,
Tim

By: simply24 » Blog Archive » Spring Java Configuration Moving Ahead

simply24 » Blog Archive » Spring Java Configuration Moving Ahead — Wed, 07 Nov 2007 07:23:44 +0000

[...] more here [...]

By: software configuration management » Spring Java Configuration Moving Ahead

software configuration management » Spring Java Configuration Moving Ahead — Tue, 06 Nov 2007 12:15:33 +0000

[...] vivek wrote an interesting post today onHere's a quick excerptSeveral users have asked whether we are committed to Spring Java Configuration, and how it sits with the annotation configuration option introduced in Spring 2.5. The answer is yes, we are committed to Java Config; and these two … [...]