atom feed38 messages in org.apache.ode.devRe: JPA DAO refactoring.
FromSent OnAttachments
Jeff YuMar 3, 2010 10:01 pm 
Jeff YuMar 3, 2010 10:21 pm 
Aaron AndersonMar 4, 2010 12:37 pm 
Jeff YuMar 4, 2010 9:26 pm 
Aaron AndersonMar 7, 2010 11:27 pm 
Jeff YuMar 8, 2010 7:35 am 
Jeff YuMar 8, 2010 11:05 pm 
Jeff YuMar 9, 2010 12:40 am 
Aaron AndersonMar 9, 2010 6:22 pm 
Jeff YuMar 9, 2010 9:02 pm 
Aaron AndersonMar 12, 2010 10:36 am 
Jeff YuMar 12, 2010 8:14 pm 
Aaron AndersonMar 14, 2010 7:25 pm 
Jeff YuMar 15, 2010 7:53 am 
Aaron AndersonMar 15, 2010 10:06 am 
Aaron AndersonMar 16, 2010 7:13 am 
Jeff YuMar 16, 2010 8:29 pm 
Aaron AndersonMar 25, 2010 1:49 pm 
Jeff YuMar 25, 2010 10:17 pm 
Aaron AndersonMar 26, 2010 6:27 am 
Rafal RusinMar 26, 2010 10:23 am 
Aaron AndersonMar 28, 2010 3:31 pm 
Jeff YuMar 29, 2010 2:40 am 
Rafal RusinMar 29, 2010 2:52 am 
Jeff YuMar 29, 2010 7:58 am 
Aaron AndersonMar 29, 2010 8:31 am 
Jeff YuMar 29, 2010 10:18 pm 
Aaron AndersonApr 2, 2010 5:33 pm 
Jeff YuApr 5, 2010 11:12 pm 
Aaron AndersonApr 6, 2010 6:24 pm 
Jeff YuApr 8, 2010 3:47 am 
Aaron AndersonApr 12, 2010 8:03 am 
Jeff YuApr 12, 2010 8:15 pm 
Aaron AndersonApr 23, 2010 7:25 am 
Jeff YuApr 26, 2010 7:44 am 
Aaron AndersonApr 29, 2010 7:25 am 
Jeff YuApr 30, 2010 5:56 am 
Jeff YuMay 2, 2010 10:12 am 
Subject:Re: JPA DAO refactoring.
From:Jeff Yu (jeff@gmail.com)
Date:Mar 25, 2010 10:17:40 pm
List:org.apache.ode.dev

Hi Aaron,

The code is great. IMHO, below are the things that we need to be done for getting this big patch applied.

1. axis2-war module test case code is out-of-update, it still refers to the old dao package, like 'org.apache.ode.bpel.dao.", It seems to me that we didn't compile and run test case for this module, do we? 2. use the buildr build to check if we can get it build with this. I know this might be the hard part here, unless you are familiar with buildr. We may ask other devs here to see if they are interested picking up this task. But I will try to build with that firstly to see how many problems we have right now.

BTW, this refactoring work is so great that I am thinking that migrate it into Apache ODE 1.x branch, how much effort do you think it would cost for this move? We are trying to add the clustering support for 1.x code base, one first thing here would be to implement the JPA based DAO impl for scheduler module.

Regards Jeff

On Fri, Mar 26, 2010 at 7:49 AM, Aaron Anderson <aaro@acm.org>wrote:

Hi Jeff,

I completed the new JPA based SimpleScheduler DAO implementation. Now there is JDBC based implementation (refactored original delegate implementation), a JPA OpenJPA implementation (default now), and a JPA Hibernate implementation. I did not create a new non-JPA Hibernate implementation since to my knowledge JPA will be the persistence implementation of choice for ODE.

One last think that needs to be done is to update the JPA DDL module to include additional indexes in case the SQL generator does not index everything that needs them.

Also as part of my refactoring I added transactional operations to the DAOConnection interface so that it can hide the underlying transactional mechanism in case JTA is not used. To me it makes the DAO usage more concise. Perhaps in the future the engine and runtime code can be modified to utilize the DAO transactional operations instead of directly manipulating the JTA transaction manager.

Please take a look and let me know what more needs to be done for the JPA refactoring effort.

Regards,

---------------- blog: http://jeff.familyyu.net