ApacheCon: Core Europe 2015

Introduced in the late 2000’s, Apache Cordova solved a major problem developers faced with maintaining separate code bases for different platforms their products supported - iOS, Android, Windows, etc. Today’s version of Apache Cordova now supports 15 platforms for mobile, web, desktops and television, empowering developers to use the same codebase to to many native environments with experiences so refined users have a hard time telling them apart.

In this session, attendees will learn about the Apache Cordova project, its benefits and proper usage, as well as how to start developing apps today using it. In no time at all, applications that once lived on one or two platforms can quickly be ported to numerous other platforms, making a big impact on a business’ bottom line without a significant development burden.

Java evolution is getting faster these days, and that's a great thing. Nowadays, one jave version is deprecated every 2 years:
- Java 5:october 2009
- Java 6: february 2013
- Java 7: march 2015 (really? already?)
- Java 8: march 2017 (with that one, you'll discover new types of incompatibilities...)
And you, or your applications, how do you manage upgrades?

Come and see how Apache Maven and its tooling (Animal Sniffer, Toolchains, ...) help you upgrade with confidence, at your own pace and without headaches.

This talk celebrates the awesome parts of the Groovy language and the Groovy ecosystem. You'll see some exciting examples of Groovy and it's application. Everything from domain specific languages, dynamic typing, the extensible static typing system, Android programming, concurrency, enterprise programming made productive, functional programming and a host of interesting frameworks and tools.

Composite Oriented Programming (COP) was a term coined in the Qi4j project in 2007. It is defining a whole new paradigm of how software is written, where INTENT is expressed and enforced by execution environment, helping developers to be disciplinary and in return improving efficiency and clarity. COP allows composition of Fragments into Composites, where Fragments are more cohesive than classes, allowing better encapsulation of different roles within an object.
Qi4j joined the Apache Software Foundation in 2015, as the Apache Zest project, where it lives as the reference implementation of COP using regular Java to achieve it.
In this hands-on presentation, Niclas will make a brief introduction to COP concepts, then proceed to how to work with Zest Qi4j to compose an application, and integrating it with the Restlet framework.
Classes are Dead = Long Live Interfaces.

One of the most exciting opportunities for Docker is its role in production. Apache Brooklyn and Clocker, an Apache Licensed application for Brooklyn, are designed to help with this. We wanted to make it easy to deploy the same application across a range of environments, from local testing to shared user acceptance and staging, and on to production. Brooklyn uses YAML blueprints to describe applications, including affinity/anti-affinity and policies for scaling or resilience. Clocker allows easy colonisation of cloud environments with a pool of Docker instances, compatible with Swarm and Compose. SDN support from both Weave and Project Calico is included, ready for multi-host, complex application deployments.

We show how to use these tools to design a blueprint for your application, test it using an Apache Maven plugin and deploy it to a managed Docker infrastructure.

Container technology are being evaluated by software developers and administrators with a great deal of interest. Developers want to focus on what they do best: Creating and coding new applications. That shouldn't have to change just because they need to deploy an application to a different environment. Administrators want the environment to stay reliable and stable, keeping changes at a minimum. By following a strategy that embraces good Architecture, use of Containers, DevOps philosophy, Apache Mesos and a Cloud based environment, developers and operators can create, consume and collaborate on the infrastructure configuration over the time, deploy Java EE applications and test your application infrastructure consistently regardless of the stage of the development life cycle.