The following is intended to outline ourgeneral product direction. It is intended forinformation purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Introduction Functional vs. What’s an enterprise application anyway? Non-functional 4
Architecture Business rules/validations Domain objects UI rendering Data storage Transactions Client-side validation ConsistencyPresentation Navigation Business Data Data Logic Logic Logic Access Screen/workﬂow Object/relational mapping management Invoking Enterprise Information Systems 7
Let’s get started... So, what’s the typical example of an enterprise application? 8
Downsides of Java EE?• KISS, DRY, and YAGNI –Instead of only talking about them you now have to prove them in practice• More bugs per # LOC ;-)• Small deployments –OH: “So they spent 3 months building this app and it’s ONLY a 100k WAR file?” 23
So... With Java EE 6 in winter, who needs Spring? it sucks anyway... 24
More info• Bert Ertman• Twitter: @BertErtman• E-mail: firstname.lastname@example.org• Paul Bakker• Twitter: @pbakker• E-mail: email@example.com 25