My JavaOne 2012 and Community Day Activities (=Java Vacations) 📎
- NetBeans Community Day
Date: Sunday, September 30
I would like to demo, what I'm usually not presenting: NetBeans Java EE wizards, helpers and magic (10:30am-11:15am). In all remaining JavaOne sessions, I will still use NetBeans, but without theses helpers. It would be an unfair competition :-)
Location: Moscone West, Level 2
Room: MW-L2-2004
Time: 9am - 3pm
-
GlassFish Community Event at JavaOne 2012
Sunday, September 30, 2012 from 11:00 AM to 1:00 PM (PDT)
I would shortly explain during: "12:15 - 01:00: Customer Testimonials" why I use and like GlassFish.
-
Full-featured Java EE applications can be built with just a minimal amount of code. A create, read, update, and delete (CRUD) application with a RESTful interface can be implemented in just a few minutes. Hence, because an hour is far too long to build a Java EE CRUD application, this session covers as many Java EE features as possible, using a minimal set of business logic: a classic case of overengineering. In the session, the presenter interactively codes Java EE functionality such as plug-ins, lazy injection, configuration, real-time push, a RESTful interface, asynchronous processing, batch jobs, and periodic timers.
-
A pragmatic combination of Java EE 6/7 APIs makes the platform extremely productive. With Java EE 6/7, most of the J2EE patterns become obsolete. Even the popular Gang of Four (GOF) patterns are part of the platform and can be “activated” with a single annotation. This tutorial focuses on the lean Java EE 6 way of software development—99 percent business logic and 1 percent infrastructure—and covers the full lifecycle from inception to DevOps. The tutorial involves replacing existing best practices and introduces pragmatic approaches interactively and with executable code.
-
Most JavaFX 2 samples look and feel great, but they are often developed within a single class, in a completely unrealistic way. This session discusses how to implement real-world JavaFX applications with back-end access, unit and integration tests, Maven builds, and data binding. It also demonstrates the separation of concerns with the model-view-presenter pattern, with real-world code. This is probably the only JavaFX 2 session without special effects, animations, and custom components.
-
In the context of Java EE 6, unit tests are nice but worthless. Unit and integration tests execute chunks of the business logic in a single thread. Back-end resources and shared states are simulated with mocks. After the initial deployment, your application will never be executed again in a single thread. Strangely enough, most applications aren’t load-tested until shortly before the deadline and are put into production regardless of the results. This session shows how to continuously stress-test your Java EE applications with open source tools and lots of fun!
And a few weeks after: see you at Java EE Workhops at MUC Airport (October 22nd-24th)!