Play Framework workshop: full stack java web app

The document discusses CodeIgniter, an open source PHP MVC framework, and provides information about CodeIgniter features such as controllers, models, views, helpers, libraries, and working with databases using CodeIgniter's active record functions. It also covers topics like installing CodeIgniter, creating controllers and models, and loading views, helpers, and libraries.

Pam Selle Co-author of Choosing a JavaScript Framework, thewebivore.com Tuesday, Oct 20th 4:20 pm - Design/UX/UI

The document provides information about high performance Android app development. It begins with a history of Android performance features from early versions through Jellybean and Project Butter. It then compares the three Android programming models (SDK, NDK, RenderScript) in terms of workflow, execution model, and performance. A case study on the performance features of the Google Chrome browser for Android is presented, covering its multi-process architecture, hardware acceleration, networking, and VSync scheduling. The document concludes with a questionnaire on topics like multi-core vs GPU, Android vs Chrome, and developments beyond Android.

Play and Grails are Java web frameworks that aim to enhance developer experience. The author developed the same application using both frameworks to compare their features. Some key differences included: - Database configuration and schema generation were simpler in Grails using GORM, while Play used EBean and evolutions. - URL mapping was defined in a Groovy file in Grails, and a routes file in Play. - Grails used Groovy Server Pages for views with tags, while Play used Scala templates. - Both supported features like validation, jobs, feeds, and email, but implementations differed, such as using plugins in Grails and direct APIs in Play. - Testing was supported through plugins

Learn the inner workings of JavaScript to learn what makes things slow and how to speed them up. Heavily focused on DOM manipulation and UI updates.

Gradle is an open source build automation tool that uses Groovy for its build configuration files rather than XML like Maven. It offers features like incremental compilation, parallel task execution, and a built-in dependency management system. Projects can be configured as multi-module builds with hierarchical or flat layouts. Gradle supports plugins for tasks like compilation, testing, packaging, and publishing. It integrates with IDEs like IntelliJ, Eclipse, and NetBeans and can be used to build Java EE applications and other projects.

This document provides an overview of managed beans in IBM Domino applications. It discusses key concepts such as what managed beans are, how they are configured and used, and when they make sense to use over traditional server-side JavaScript. It then outlines steps to create a basic managed bean, including creating the Java class, adding properties and getters/setters, configuring in faces-config.xml, and using the bean in an XPage. The document also covers debugging managed beans and presents an example application where managed beans would be well suited to address complexity and persistence needs.

CDI portable extensions are one of greatest features of Java EE allowing the platform to be extended in a clean and portable way. But allowing extension is just part of the story. CDI opens the door to a whole new eco-system for Java EE, but it’s not the role of the specification to create these extensions. Apache DeltaSpike is the project that leads this brand new eco-system by providing useful extension modules for CDI applications as well as tools to ease the creation of new ones. In this session, we’ll start by presenting the DeltaSpike toolbox and show how it helps you to develop for CDI. Then we’ll describe the major extensions included in DeltaSpike, including 'configuration', 'scheduling' and 'data'.

This session discusses the promise of interoperability in the Java EE 7 platform and what has been done—even now, at its time of release—to maintain this. The session shows how a Java EE 7 application can be easily built using NetBeans and JBoss development tools. This application can then be deployed on JBoss, GlassFish, and Oracle WebLogic, showing the promise of interoperability. The state of Java EE 7 compliance for different application servers is discussed and demonstrated.

This document provides an agenda and summary for a workshop on developing MongoDB applications on OpenShift presented by Shekhar Gulati. The agenda includes getting started with OpenShift, developing a location-aware Java EE application using JAX-RS and CDI for REST services, and MongoDB for the database. The document discusses OpenShift, JAX-RS, CDI, and MongoDB concepts. It also outlines code samples and steps to create and deploy a sample Twitter-like application on OpenShift that supports creating, finding, and geo-searching statuses.

This document discusses using the Play Framework for web application development on Google App Engine (GAE). It provides an overview of Play and GAE, how they work together, and some tradeoffs. Specifically, it covers how Play abstracts away the GAE infrastructure, limitations of the GAE sandbox environment, options for running Play 2 applications on GAE including using a WAR file or custom runtime, and the pros and cons of the Play Framework on GAE approach.

This document discusses Java 8 features like lambdas and streams. It begins with an introduction to lambdas, providing an example of using a lambda expression with the setHostnameVerifier() method instead of an anonymous class. Lambdas allow passing functions as parameters and rely on functional interfaces. The document then covers streams, showing how to iterate over a certificate array using streams instead of a for loop. Additional examples demonstrate sorting a list of sandwiches using different comparator constructions and handling exceptions. The key benefits of lambdas and streams are cleaner, more readable code that encourages a functional programming style.