BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations #NoXML: Eliminating XML in Your Spring Projects

#NoXML: Eliminating XML in Your Spring Projects

Bookmarks
01:25:06

Summary

Matt Raible shows how to eliminate XML by configuring Spring beans with JavaConfig and annotations, and how to remove web.xml and configure web components with Java.

Bio

Matt Raible is a well-known figure in the Java community, and has been building web applications for most of his adult life. For over 15 years, he has helped companies adopt open source technologies (Spring, Hibernate, GWT, Grails, Bootstrap, jQuery) and use them effectively.

About the conference

This is a one-of-a-kind conference for application developers, solution and data architects: people who develop business applications, create multi-device aware web applications, process vast quantities of enterprise data, design cloud architectures, and manage high performance infrastructure. The sessions are specifically tailored for Developers and Architects using the popular open source Spring IO Projects, Groovy & Grails, Cloud Foundry, RabbitMQ, Redis, Geode, Hadoop and Tomcat technologies. Whether you're building mission-critical web or business applications, crunching huge amounts of distributed data, or designing the next killer cloud native application, SpringOne2GX will keep you up to date with the latest enterprise technology.

Recorded at:

Mar 11, 2016

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • I still prefer XML

    by Mauro Molinari,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Although this new trend to use JavaConfig. I still prefer XML configuration. It's not just a matter of habit, I think it's often more readable and maintainable than JavaConfig (at least most of the times), especially once accompanied by the use of specialized namespaces and supported a good tooling.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT