1 / 16

LIBeLIS

LIBeLIS. JDO verleiht Flügel Enterprise Information Access Scalable, robust JDO solutions « JDO: Just Do Objects !  ». Alexander v. Zitzewitz alexander.zitzewitz@libelis.com  info@libelis.com  www.libelis.com. Business Card. Enterprise Information Access Vendor Found ed in 2000

caldwell-beasley
Download Presentation

LIBeLIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LIBeLIS JDO verleiht Flügel Enterprise Information Access Scalable, robust JDO solutions « JDO: Just Do Objects ! » Alexander v. Zitzewitz alexander.zitzewitz@libelis.com  info@libelis.com  www.libelis.com

  2. Business Card • Enterprise Information Access Vendor • Founded in 2000 • by experts in DBMS and J2EE technologies • Worldwide operations • Direct operations in UK, Germany and France (+Spain) • Distributed in USA & Canada • Investors • First funding round in November 2002 • Strong commitment to Java standards • Member of the Java Community Process (JCP) • Active Member of the JDO Expert Group • Charter Member of JDOCentral • Board Member of the ObjectWeb consortium

  3. LiDO • LiDO : Flagship product • NAViLIS as a side-product (eBusiness browser) • FileDB a light & fast 100% Java embedded DB • First JDO 1.0 implementation • Enterprise level, scalable, robust JDO implementation • Production ready • Available since July 2001 • >25.000 downloads worldwide • Very active community

  4. The JDO standard Java Data Objects The new specification for Java object persistence from Sun

  5. JDO • The Java standard for data access • Final Approval in March 2002 • Main contributors • Sun, IBM, BEA, Oracle, SAP ... & LIBeLIS • +O/R mapping tools vendors + ODBMS vendors • Does not replace but complement JDBC and EJB • Goals • Transparent persistence • Not intrusive in Business Objects • Universal Data Access • RDBMS, ODBMS, binary, XML, text, Legacy, applications, TP monitors, MOM... • Independant deployment • Java level: embedded J2ME, client-server J2SE, distributed J2EE • Might be embedded within in a future JDK release • Books

  6. JDO programming LiDO from the developer point of view Transparent data access with full Java support

  7. LiDO Object model: no restriction public class Employee extends Person { public String name; private java.util.Date birthday; private int salary; public Company company; public IActivity activity; Vector awards; public void bonus(int more) { salary += more; } } No need for any javax.jdo import Inheritance Interfaces Collections No need for accessors / mutators This is a persistent class ! If you can write it in Java, any JDO engine should store it.

  8. LiDO build cycle • Enhancement is fully defined by the JDO spec. • Enhanced byte-code is portable across JDO implementations • Enhanced byte-code remains the same for any data source • Allows debugging and profiling (JPDA) • Allows fully transparent persistence any JDO enhancer source code javac compiler byte code byte code Mapping (xml file) LiDO java JVM

  9. Programming with LiDO rdbms odbms LiDO   Business objects Application objects Some explicit JDO calls: Fully Transparent (no JDO calls): • Navigation between objects • Connection(*) • Query • Data manipulation in Java • Automatic data mapping • Client cache, object identity • Transaction(*) Java VM (*) : in a J2EE context, connections and transactions are managed by the application server itself !

  10. JDO within an Enterprise Application design LiDO from the architect point of view Efficient Enterprise Information Access

  11. How LiDO complementsJ2EE JSP Any Data Source Session Entity Java JDO is already perceived as one of the most critical Java extensions as it perfectly complements J2EE !

  12. LiDO Design Universal & Scalable JDO Implementation « JDO: Just Do Objects ! »

  13. LiDO architecture JDO implementation Transaction, JDO QL, State Manager Specification implementation Caches, Dual Query Engine, JCA Connection pool, ... Core technology Storage Managers Data source dependant layer RDBMS ODBMS Binary files ... The only JDO solution that is more than just another O/R mapping tool !

  14. JDO Demo LiDO Live ! It doesn’t only run on PowerPoint 

  15. LiDO Delivers • 20 to 50% LESS source code to write • Typical number of lines within the business object models used to store and retrieve these objects: 30% and this may increase should your model be complex. • Significant Performance Improvements • 5 to 40 times faster than EJB CMP • Significant Reduction of complexity • No modelling restrictions

  16. Conclusion • Too Good to be True ? • Do not trust us… just Download and Check it out ! www.libelis.com EMail: alexander.zitzewitz@libelis.com • Trust our Customers: • Societe Generale, France Telecom, Orange, CARDIF, SANOFI, Raytheon, FGM, Rothschild Bank, CRIL, LineData Services …

More Related