Comments on: A Java configuration option for Spring

By: tanyue123

tanyue123 — Mon, 09 Jan 2012 03:03:50 +0000

Home Theater ProjectorJan 1, 2012 ... The Top 10 Home Theater Projectors are broken into two resolution categories: 1080p and 720p. To help you find features important to you, ... Cheap 1080P ProjectorFeb 27, 2008 ... Certainly many people are jumping on the 1080p bandwagon these days because the price of projectors is ridiculously cheap. But now that ... LCD Projector ScreenProjector Screens by Da-Lite Screens. Projector Screen specials that include free shipping. Over 3000 ... Da-Lite Manual Model B Projector Screen 70" x 70" ... Conference ProjectorJan 1, 2012 ... Below are the Popular Conference Room Projectors for both small and large rooms. The major difference between these two groups is the ... HID KitWelcome to HID Kits, the world's top retailer of HID lights & HID headlights. This week enjoy free shipping on all HID conversion kits, bulbs and ballasts within ...

By: hiren

hiren — Wed, 08 Jun 2011 06:55:58 +0000

I m using this demo with Hibernate and Spring 3.0.2.
I m getting error while deploying application .
It,s jar files problem…
Can i know which jar files i need to add..?

By: birkenstock outlet

birkenstock outlet — Fri, 06 May 2011 17:45:30 +0000

This summer wear the to choose all kinds of shoes you need here.

By: Garde d'Enfants

Garde d'Enfants — Tue, 29 Jun 2010 18:24:36 +0000

Nice stuff. It opens the door to many possibilities.
I like the idea to keep the configuration stuff outside of the pojos. Also it makes refactoring easier and this is cool.
It reminds me the code of the ServiceLocator I used to implement

By: HID Kit

HID Kit — Mon, 21 Jun 2010 03:58:59 +0000

Great initiative !!! And unmissable tool in the spring-core !
Sincerely, I was very despite of the lack of Java config support in Spring 2.0
At I21 you use to say that people are more open to XML config solution, but I don't think that they are Java developer's. As many guys said before, there is 2 level of configuration to address:
1. Developement configuration (Java config)
2. Infrastucture config (XML or Groovy like … )
The Dev config is more general and give support to infrastructure config, deciding where to allow or not the override.
Another aspect is that, the Java developement is more easy with Java5/6 features than java1.4 and less. So, for me, Spring 2.0 is more a support for old java programming, and that is good for all those who are stucked on java 1.4 or 1.3 for many legitime reasons, but very bad choice for those who could go up with new Java 1.5 projects.

Today, I know that JEE5 have a big success, having take in his account the Spring idea in a new environment, and looking Spring as very complicated beacause of XML config. Don't forget that we are in a Java world and smart Developers want only one source tracking.

So, It is time to split the future releases of Spring in 2 branchs:
1. to support the old java style applications
2. to support the new java specifications (JEE5 , EJB3 JAVA5/6)

By: Programmer

Programmer — Fri, 12 Dec 2008 11:56:26 +0000

Excellent article. I've been using Spring for two years and it is fantastic

By: 빛�?� 담고 세�? 넓히기 » Spring Dependency Injection 정리

빛�?� 담고 세�? 넓히기 » Spring Dependency Injection 정리 — Fri, 18 Apr 2008 11:47:50 +0000

[...] code from 'A Java configuration option for Spring' by Rod Johnson' [...]

By: Prosolution

Prosolution — Fri, 11 Apr 2008 05:33:37 +0000

I am Very thank full the owner of this blog. Becouse of this blog is very imformative for me.. And I ask u some thiing You make more this type blog where we can get more knowledge.

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

Tue, 18 Mar 2008 16:19:27 +0000

[...] A Java Configuration Option for Spring by Rod Johnson [...]

By: Adam

Adam — Fri, 08 Feb 2008 18:11:27 +0000

JavaConfig is great, I love the type safety I get from building config in Java. I am extending ConfigurationSupport in one of my @Configuration-annotated classes and using getBean() to inject dynamically specified beans (ie, they are dynamically specified via a property file or command line parameter). So far, so good… but now I also want to be able to specify string-values that would normally run through Spring's registered Property Editors (without hooking back into XML-specified ). For example, maybe a new function called getProperty() similar to getBean() that maybe works like this:

myNewBean.setEnumValue(
(MyEnumClass)getProperty( "STRING_ENUM_TYPE", MyEnumClass.class ) );

Maybe something to put on feature list?

As for a catchy name, can I suggest "Coil" = "Configuring Objects In Language"?