5 ms·
How long has it been that you used Spring? You don't need that much XML for a Spring 3.0 application. Almost everything can be done with annotations. Why do yo
by mschulze 13y ago
How long has it been that you used Spring? You don't need that much XML for a Spring 3.0 application. Almost everything can be done with annotations.
Why do you compare Spring with J2EE when in fact JEE took a lot of the good stuff from Spring?
The main point of Spring is to help develop consistent applications with enterprise requirements (integration, security, batch jobs, mvc, ...) and it does that incredibly well. Especially integration in a nightmare of systems at a large corporation.
- bsaul 13y agoI do agree that IOC coupled with strong interface definitions and enforcement make a good starting point for building enterprise components in large corporations. Yet, after using Spring for a while, i really wondered how come there couldn't be any simpler solutions to that problem: any compiled language with a good support for interfaces should be able to reach that objective. I think the bloat came from wanting to decouple compilation time from component assembling time, using xml files. I never understood the reason for that choice (who in its right mind would change a component without recompiling for type checking and retesting the code anyway ?). I suppose it probably was the easiest way to accomplish that in Java at some point, and i'm really happy to see that latest Spring versions enable you to use Java configuration classes instead. But as enterprise means long-time support and never ending backward compatibility, i really doubt the bloat culture will fade away any time soon.
- sfjailbird 13y agoI wouldn't say incredibly well, more like a passing mark. In fact I would compare Spring to Maven: It gets the job done, it's probably even the best of the alternatives, it still leaves a bad taste in the mouth. I find that for many of the configuration use cases that Spring is supposed to solve I am better off doing things programmatically (heresy in the Java world). Yes, this can be done and still have testable, decoupled configuration. (As for changing configuration on the fly, nobody does that. It is a leftover from the "Deployer" role defined by Sun's J2EE specification.)