Book Image

Spring Essentials

Book Image

Spring Essentials

Overview of this book

Spring is an open source Java application development framework to build and deploy systems and applications that run on the JVM. It is the industry standard and the most popular framework among Java developers with over two-thirds of developers using it. Spring Essentials makes learning Spring so much quicker and easier with the help of illustrations and practical examples. Starting from the core concepts of features such as inversion of Control Container and BeanFactory, we move on to a detailed look at aspect-oriented programming. We cover the breadth and depth of Spring MVC, the WebSocket technology, Spring Data, and Spring Security with various authentication and authorization mechanisms. Packed with real-world examples, you’ll get an insight into utilizing the power of Spring Expression Language in your applications for higher maintainability. You’ll also develop full-duplex real-time communication channels using WebSocket and integrate Spring with web technologies such as JSF, Struts 2, and Tapestry. At the tail end, you will build a modern SPA using EmberJS at the front end and a Spring MVC-based API at the back end.By the end of the book, you will be able to develop your own dull-fledged applications with Spring.
Table of Contents (14 chapters)
Spring Essentials
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Building UI templates using Handlebars


The primary UI authoring technology in Ember.js is Handlebars. Handlebars templates allow HTML fragments to embed dynamic content using Handlebars expressions placed inside double curly braces ({{ }}), the dynamic scripting blocks. Handlebars expressions perform data binding with attributes of routes, models, controllers, components, services, utils, and even application instances. Here is a sample Handlebars expression:

<h3>Welcome <strong>{{loggedInUser.fullName}}.</strong></h3>

This code snippet expects an object (preferably derived from Ember.Object, though it binds with normal JS objects too) with the name loggedInUser, present somewhere in the context in the parent context hierarchy (template, controller, route, or application). Then, it establishes a one-way data binding with the fullName attribute of the loggedInUser object; hence, it just displays the value of the bound attribute.

Handlebars helpers

Handlebars relies on...