Gary P Russell shows an application used for managing and monitoring apps built with Spring Integration, and overviews the JMX support provided by Spring Integration.
Jon Brisbin explains how to expose JPA entities via the Spring Data Repository abstraction and then exporting them to HTTP using Spring Data REST.
Bill Burke discusses using REST from Java, overviewing JAX-RS 1.1 and detailing some of the new features coming in JAX-RS 2.0 – Async HTTP, Filters/Interceptors, Client framework-.
Robin Zimmermann lays out the broad architectural details of server applications with a web-based client exchanging messages over WebSockets and JMS.
Arun Gupta presents the current developments on Java EE7 as a PaaS in the cloud and current work on Project Avatar which simplifies HTML5, Websockets and JSON programming for Java developers.
Oliver Gierke demoes using Spring Data JPA to create repositories using a Domain-driven Design approach.
Jerome Dochez unveils the features planned for Java EE 7: Cloud Computing support, Modularity enhancements, richer Web Tier – Web Socket, HTML5, JSON-, JMS 2.0, and JPA 2.1, plus the roadmap.
Uri Cohen presents the key characteristics of SQL and NoSQL databases and how to create a layer on top of distributed data stores in order to use SQL to query for data. For further information please contact Gigaspaces.
Jürgen Höller presents some of the most important Java EE6 features, underlining similarities and differences between EE6 and the Spring Framework, showing what is the best configuration using both technologies.
Stefan Norberg introduces Domain Event-Driven Architecture, how it helps SOA, and how it has been used by Unibet to make its architecture less coupled, resulting in better performance and scalability. Norberg offers practical advice, presenting technical details of the technologies used: JMS, XML, JSON, Google Protocol Buffers, ActiveMQ and Spring.
Rod Johnson talks about Java’s evolution, in particular J2EE, presenting the lessons to be learned from its failures, like committee-led standards and container-managed frameworks, preparing to avoid such mistakes in the future.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture such as changing the team culture, removing obsolete technologies, allowing mistakes to be made (and learned from), transitional architectures, introducing bounded contexts, refactoring and emergent simplicity, and rotating through roles.