Buzzword compliance in my project

While reading "J2EE without EJB" I'm just wondering how long it will be before the book "J2EE without Spring" comes out. Just joking but not totally. Dealing with all the SpringBean dependancies is almost as much a "meta-data hell" as EJB deployment descriptors. The advantage of testing out of the container is good but otherwise I see the overall productivity problem as just being moved a little and renamed something else.

Otherwise here are the ways that the buzzwords are injected and weaved in our current application.

• we're using the Spring WebApplicationContext with Struts to get access to stuff throughout the web app. We can say we are using a "lightweight container"
• we're using Spring Beans to initalize a navigation tree via an XML file. We can say we're using "IoC Dependancy Injection"
• we're using another Spring bean to have remote access to Session EJB's. For testing we replace them with the Bean classes directly so we don't have to use JBoss thus using a cross-cutting AOP.
• ... I'm sure there's lots of others that I'm not aware of but I'll try to remember to say "IoC constructor injection" instead of "constructor" until these too are replaced with something else.