Jump to: navigation, search

Difference between revisions of "About : BIRT JPA or JDO Connector"

(Getting the source)
(Developement)
Line 52: Line 52:
  
 
== Developement ==
 
== Developement ==
 +
=== The "Statement" class  ===
 +
 +
The "Statement" class, prepare the result set metadata of the query (containing column name, column type, and entity name that belong), execute the query, and fetches the data rows from the Data Source.
 +
 +
==== Problems found in developed whit JPA in this class: ====
 +
 +
1. To get attributes of the entities (field names and field types) found into the query e.g.: 
 +
 +
SELECT d.departmentIdentifier, d.name FROM Department d
 +
 +
Was necessary know the complete path, like “jfabian.model.department.entity.Department”, an option was write this in the query as is possible in hibernate but this idea was discard becouse JPA not allow it.
 +
 +
The solution was getting the name of entity and searches the complete path into “persistence.xml” file, this implemented in
 +
“JPAUtil.findEntityOnPersistenceXML(entityName, classNodes)” function.
 +
 +
2. Other aspect to take into consideration are the entity alias, this to retrieve the corresponding column e.g.:
 +
 +
SELECT d.departmentIdentifier, d.name,
 +
e.employeeIdentifier  , e.firstName
 +
FROM Department d, Employee e
 +
 +
In this query the alias for Department is “d”, and its columns are “departmentIdentifier” and “name”, to retrieve the columns types I need know the entity name (with path complete), and column or field name.
 +
 +
And the functionality should be correct if the column order is not the same to instance of the entities, e.g.:
 +
 +
SELECT e.firstName, d.name,
 +
e.employeeIdentifier, d.departmentIdentifier
 +
FROM Department d, Employee e
 +
 +
For this task was implemented “extractColumns(qry)”, that return a “List<List<String>>” containing the entity alias and column name.
 +
Other was “getReturnEntities( String query )”, that return a “List<List<String> >” containing entity name and entity alias.
  
 
== References ==
 
== References ==

Revision as of 02:11, 1 September 2008

Abstract

The Java Persistence API (JPA)is the Java API for the management of persistence and object/relational mapping for Java EE and Java SE environments. The persistence consists of three areas:

  • the API, defined in the javax.persistence package
  • the Java Persistence Query Language
  • object/relational metadata

The purpose of this project proposal is to implement a Connector JPA for BIRT framework, and so able to handle data source from the persistence API. Is so great the importance of the project because JPA is a specification that is being used widely in the development of applications, precisely from the advantages it.

The implementation is to make the JPA ODA driver, extending each one of the interface required in the Data Tools Plataform given in the package org.eclipse.datatools.connectivity.oda.

Finalizing it first part will be an improvement approaching also advanced options in regard to the parameters and also will be implemented JPA ODA IU extensions.

Participants

  • Student: Victoriano Alfonso Phocco Diaz <vphocco@gmail.com> -

http://alfonso777.blogspot.com/

http://code.google.com/p/birt-jpa-connector/

Planned Features

  1. Handling of configuration file: persistence.xml.
  2. JPA utilities for get current EntityManager and EntityManagerFactory
  3. JPQL queries validation.
  4. Get the metadata information such as column names, column types, column class for the query .
  5. Instantiation of ResulSetMetaData, DataSetMetaData, ResulSet.
  6. Soport in the preparement and execution of Queries.
  7. Working good with the implementations de JPA: Hibernate and TopLink.


Should Have

  • Handling of other configuration file: orm.xml
  • Soport more advance of Parameters into queries.

Nice to have

  • Soport JDO and JPA at the same time.


Community proposals

Feel free to add your comments and ideas.

Getting the source

ViewCVS: http://code.google.com/p/birt-jpa-connector/source/browse [1]

CVS: https://birt-jpa-connector.googlecode.com/svn/trunk/


Developement

The "Statement" class

The "Statement" class, prepare the result set metadata of the query (containing column name, column type, and entity name that belong), execute the query, and fetches the data rows from the Data Source.

Problems found in developed whit JPA in this class:

1. To get attributes of the entities (field names and field types) found into the query e.g.:

SELECT d.departmentIdentifier, d.name FROM Department d

Was necessary know the complete path, like “jfabian.model.department.entity.Department”, an option was write this in the query as is possible in hibernate but this idea was discard becouse JPA not allow it.

The solution was getting the name of entity and searches the complete path into “persistence.xml” file, this implemented in “JPAUtil.findEntityOnPersistenceXML(entityName, classNodes)” function.

2. Other aspect to take into consideration are the entity alias, this to retrieve the corresponding column e.g.:

SELECT d.departmentIdentifier, d.name,

e.employeeIdentifier  , e.firstName

FROM Department d, Employee e

In this query the alias for Department is “d”, and its columns are “departmentIdentifier” and “name”, to retrieve the columns types I need know the entity name (with path complete), and column or field name.

And the functionality should be correct if the column order is not the same to instance of the entities, e.g.:

SELECT e.firstName, d.name,

e.employeeIdentifier, d.departmentIdentifier

FROM Department d, Employee e

For this task was implemented “extractColumns(qry)”, that return a “List<List<String>>” containing the entity alias and column name. Other was “getReturnEntities( String query )”, that return a “List<List<String> >” containing entity name and entity alias.

References

BIRT References

  • Eclipse Resources:

http://www.eclipse.org/resources/?category=BIRT

  • The plug-in extension examples from Integrating and Extending BIRT

http://www.actuate.com/products/products-resources.asp?ArticleId=11719

JPA References

  • JPA specification:

http://jcp.org/en/jsr/detail?id=317

  • Documentation JPA API:

http://java.sun.com/javaee/5/docs/api/javax/persistence/package-tree.html

  • GlassFish Project - Java Persistence Example:

https://glassfish.dev.java.net/javaee5/persistence/persistence-example.html

  • Master the New Persistence Paradigm with JPA

http://www.devx.com/Java/Article/33650

  • Persistence Pays Offs: Advanced Mapping with JPA

http://www.devx.com/Java/Article/33906

http://www.oracle.com/technology/pub/articles/marx-jpa.html

  • Book: Mike Keith, Merrick Schincariol, "Pro EJB 3: Java Persistence API", Apress.
  • JPQL

http://edocs.bea.com/kodo/docs40/full/html/ejb3_langref.html

Other Important References

  • Documentation Hibernate API:

http://www.hibernate.org/hib_docs/v3/api/org/hibernate/Query.html

  • Documentation TopLink API:

http://www.oracle.com/technology/products/ias/toplink/doc/10131/main/b28219/index.html

  • JFire Project - BIRT datasource for JDO:

http://www.jpox.org/docs/1_2/examples/jfire.html

  • OpenMRS - BIRT ODA Plugin User Guide:

http://openmrs.org/wiki/BIRT_ODA_Plugin_User_Guide

  • Example about JasperReports with JPA:

http://www.jroller.com/marceloverdijk/entry/ejbql_query_support_added_in