Dazed & Confused

Apparently the newest version of Spring can replace methods of instances through XML configuration. Ok, so it might be a cool feature as Craig Walls writes, and sometimes come in handy, it must be extremely confusing if it is used without discipline. It’s not always easy following source around with methods, xml mappings and code generation. I bet I would feel quite lost if I had to consider methods not beeing run because it was actually replaced in XML.

Wow. This is extensive. Check out the FAQ here.

Via java.no.

Jeff Genender writes about propagating dependency versions in the POM to sub-modules. He uses XML entity references.

In our current project we’re using a build mechanism of several modules, but propagate settings and POM info through the projext.xml extend element. We have one master project.xml file, that all other modules extend. If one of the other modules has other dependencies/info you can override/add it in the local project.xml file. This should propagate both POM and normal properties.