-
TopLink
. Current Release: TopLink 10.1.3 Next Release: TopLink 11g see also EclipseLink Documentation: Docs Java Docs (11g) Examples
Keyword tags:
None
Last updated:
Jan 23 2008, 9:11 AM EST by
-
JPA
JDeveloper . Oracle is also involved in several JPA related open source projects. Eclipse Persistence Services ( EclipseLink ) : JPA
Last updated:
Jan 16 2008, 2:15 PM EST by
-
EclipseWorld 2008
and see how these issues are addressed by EclipseLink MOXy, a component of the Java Persistence Platform. EclipseLink provides a rich OXM solution
Last updated:
Sep 10 2008, 2:24 AM EDT by
-
How to convince others to adopt ADF & JDeveloper
from ADF & JDeveloper and Oracle, namely Eclipselink as a EJB3-JPA-Toplink derivative, and Apache Trinidad as a JSF component set. Toplink
Last updated:
Sep 5 2008, 8:34 AM EDT by
-
ADF Methodology - Work in Progress
:.... where does EclipseLink fit into this?) EJB tba (CM note: I assume this implies older EJB choices separate to JPA
Last updated:
Sep 22 2008, 9:20 AM EDT by
-
List of Oracle-related blogs
Coekaerts EclipseLink Team Paul Gallagher Alison Holloway Christopher Jones Sergio Leunissen Martin K. Petersen Liming Lian
Last updated:
Thursday, 4:15 PM EDT by
-
Why not EJBs?
Well, if you look in to JDeveloper 11g evolution, form Tp1 to Tp4, you will notice:
1. In TP1-TP2, EJBs were technology choice in Fusion Application stack.
2. In TP1-TP2, EJBs support was much improved (data controls, bindings, wizards...) compared to 10g. For me it was clearly visible that Oracle is investing in EJBs as well as into EclipseLink.
3. After TP3, BCs are again put in the middle again (Fusion dev stack now again is ADF RC + BCs). EJBs support was staled – no new wizards, empty placeholders in wizards for EJBs etc.
Coinciding with Oracles numerous acquisitions (BEA WebLogic), latency in Fusion AS 11g production (migration of old PL/SQL code to true ADF RC multitier Web UI), I beleive they decided to drop EJBs as platform for porting 11g (as it is much easier with BCs when you have a lot of legacy PL/SQL code and SPs). While EJB 3.1 and JPA 2.0 is much advanced and Java-friendly that BCs, they decided to postpone support for EJBs in R1 (both Fusion 11g AS and JDev 11g) as they don't need them right now and they will be ready when new standards are in place (they will got some breathing space with just porting UI to ADF RC while middle-tier is good enough even on BCs).
Regarding declarative validation, please note that JPA 2.0 will support Bean Validation annotations (JSR-303). So, BCs declarative validation is nothing special and is much simplified compared to JSR-303.
So, if we neglect Oracles emotive relation to BCs as well as pragmatic reasons (hurry to deliver new, fancy, Rich UI to their apps), the future of EJBs is much brighter than BCs. You can promote ADF Methodology with BCs is focus, but you will make a bad influence on many developers which will go that way and learn (in year or two) that there is something much better out there (named EJBs, in core of JEE 6 coming next year).
Posted:
Jul 14 2008, 2:33 PM EDT by
|
|
