Starting with Java EE
was never easier
Kaloyan Raev
WTP PMC Member
SAP Labs Bulgaria
1

Typical Java EE application design
Servlet, JSP
Presentation JSF
EJB, JTA
Business Logic
JMS, JNDI
Persistency JPA, JDBC
Problem: Too many technologies! Where to start from?
2

One possible implementation
JSF Pages
JSF MBeans
Session Bean
EJB
CRUD Façade
JPA JPA Entities
Solution: Follow well-established patterns!
3

The Eclipse Pave project
 Frameworks for building patterns
Definition
Pattern – a frequently executed sequence of operations that
transforms the state of the workspace in an error proof way by
following well-established conventions.
4

Let’s start!
 Download Eclipse IDE for Java EE Developers
 Add Eclipse Pave plug-ins
 Configure Java EE application server (e.g. GlassFish)
 Configure Database (e.g. Derby)
Tutorial - EclipseLink/Derby/Glassfish
5

Eclipse IDE for Java EE Developers
6

Add Eclipse Pave plug-ins
Download
 http://eclipse.org/pave/downloads.php
Installation tutorial
 http://eclipse.org/pave/install.php
7

Model for the Demo application
8

High-level architecture
uses
Pave UI
extends Pave Core
WTP Commons
extends
WTP Data Model Framework UI
uses
WTP Data Model Framework Core
9

Pattern action sequence
10

Why the WTP Data Model Framework?
 Features
 Data Models provide an intelligent mechanism for data collection
 Data Model Operations simplify operation execution
 Data Model Wizards simplify wizard generation and extension
 Extensible framework
 Widely adopted in WTP
11

Data Model Operations in WTP
 Over 200 Data Model Operations in WTP
 More in adopter’s products
 Use cases
 Creation of project and artifacts
 Import and Export
 Refactoring and Update
 Migration
12

Features
 Framework
 Descriptive declaration of patterns – in plugin.xml
 Patterns are context sensitive
 Default UI entry point for patterns – the Apply Pattern wizards
 Patterns are extensible
 Synchronizers for Data Models
 Headless execution of patterns
 Exemplary patterns
 Session CRUD Façade
 CRUD Application
13

Short-term plan
Submit project proposal.
Construct web site with documentation and tutorials.
Creation review.
Prepare project infrastructure.
Initial contribution and IP review.
Release of version 0.5.
 Release of version 0.7. This release includes changes in
response to the community feedback.
 Consider move to Eclipse WTP Commons, Eclipse Tools or
Eclipse Platform and commit a Move review.
14

Future outlook
 Graduate to mature project – version 1.0
 Become part of the Common Discovery Site
 Become part of the Simultaneous Release Train
 Expand data binding mechanisms
 JFace data binding
 EMF
 More cool features
 Re-apply pattern
 Undo pattern
15

Links
 http://eclipse.org/pave
 http://wiki.eclipse.org/Pave
16