This session focuses on the various ways of using the Spring container to Dependency Inject objects such as the traditional XML language, the extensible namespaces, the @Autowired and @Component annotations, but also the innovative JavaConfig project that is capable of configuring Java objects using @Bean annotations. Each has drawbacks and advantages and this session will discuss which one you should choose in what scenario. After this code-intensive session, you will walk away with a clear understanding of when XML is a good choice for configuration and when to opt for one of the annotation-based options.
Although the default ‘language’ for Spring is XML based, it could just as easily be written in something else. There are groovy and ruby based applicationcontext dsl’s out there for Spring.
So saying that Spring sucks because they use XML, is a strange conclusion at best.
Peter Lawrey
IMHO, XML is fine for data if performance is not an issue but a bit rubbish for programming, which is often how it is misused.
Part of the problem is a lack of tool set. For a proper programming language you have a debugger, profiler, re factoring tools, code analysis. etc. You are starting to see IDE support for XML configuration, but it still has a long way to go.
Although the default ‘language’ for Spring is XML based, it could just as easily be written in something else. There are groovy and ruby based applicationcontext dsl’s out there for Spring.
So saying that Spring sucks because they use XML, is a strange conclusion at best.
IMHO, XML is fine for data if performance is not an issue but a bit rubbish for programming, which is often how it is misused.
Part of the problem is a lack of tool set. For a proper programming language you have a debugger, profiler, re factoring tools, code analysis. etc. You are starting to see IDE support for XML configuration, but it still has a long way to go.