JDO TCK Conference Call Friday, June 5, 9 am PDT

[Michelle Caisse]

Hi,

We will have our regular meeting Friday, June 5 at 9 am PDT to discuss 
JDO TCK issues and status.


Dial-in numbers are:
Domestic (toll-free):  866 230-6968
International (caller-paid):  +1 213 787-0528
Access code :  294-0479#

Agenda:

1. JDOQL & Querydsl
2.  Other issues

Action Items from weeks past:

[May 25 2007]  AI everyone download the Grails demo from grails.org  and 
check it out. Also look at Grails/Groovy ExpandoMetaClass that  has the 
magic to avoid reflection and enhancement.


[May 25 2007] AI Matthew Adams prepare a proposal with just the basics 
of schema synchronization with jdo and orm metadata.


-- Michelle

Re: JDO TCK Conference Call Friday, June 5, 9 am PDT

[Craig L Russell]

Sorry for the late notice; it looks like I'll be delayed until 9:30 or  
10:00 at the latest. I just found out about my daughter's school play  
that is on tomorrow.


If it's not too late to reschedule the meeting, I'm fine with that,  
but otherwise I'll dial in when I can. Others have the host code.


I have not had a chance to look at querydsl.

Craig

On Jun 4, 2009, at 8:27 PM, Michelle Caisse wrote:


Hi,

We will have our regular meeting Friday, June 5 at 9 am PDT to  
discuss JDO TCK issues and status.


Dial-in numbers are:
Domestic (toll-free):  866 230-6968
International (caller-paid):  +1 213 787-0528
Access code :  294-0479#

Agenda:

1. JDOQL & Querydsl
2.  Other issues

Action Items from weeks past:

[May 25 2007]  AI everyone download the Grails demo from grails.org   
and check it out. Also look at Grails/Groovy ExpandoMetaClass that   
has the magic to avoid reflection and enhancement.


[May 25 2007] AI Matthew Adams prepare a proposal with just the  
basics of schema synchronization with jdo and orm metadata.


-- Michelle




































Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: JDO TCK Conference Call Friday, June 5, 9 am PDT

[mcaisse]

Rescheduling for 10 am works for me.

-- Michelle

> Sorry for the late notice; it looks like I'll be delayed until 9:30 or
> 10:00 at the latest. I just found out about my daughter's school play
> that is on tomorrow.
>
> If it's not too late to reschedule the meeting, I'm fine with that,
> but otherwise I'll dial in when I can. Others have the host code.
>
> I have not had a chance to look at querydsl.
>
> Craig
>
> On Jun 4, 2009, at 8:27 PM, Michelle Caisse wrote:
>
>> Hi,
>>
>> We will have our regular meeting Friday, June 5 at 9 am PDT to
>> discuss JDO TCK issues and status.
>>
>> Dial-in numbers are:
>> Domestic (toll-free):  866 230-6968
>> International (caller-paid):  +1 213 787-0528
>> Access code :  294-0479#
>>
>> Agenda:
>>
>> 1. JDOQL & Querydsl
>> 2.  Other issues
>>
>> Action Items from weeks past:
>>
>> [May 25 2007]  AI everyone download the Grails demo from grails.org
>> and check it out. Also look at Grails/Groovy ExpandoMetaClass that
>> has the magic to avoid reflection and enhancement.
>>
>> [May 25 2007] AI Matthew Adams prepare a proposal with just the
>> basics of schema synchronization with jdo and orm metadata.
>>
>> -- Michelle
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:craig.russ...@sun.com
> P.S. A good JDO? O, Gasp!
>
>

Re: JDO TCK Conference Call Friday, June 5, 9 am PDT

[Michael Bouschen]

+1

Regards Michael

Rescheduling for 10 am works for me.

-- Michelle

  

Sorry for the late notice; it looks like I'll be delayed until 9:30 or
10:00 at the latest. I just found out about my daughter's school play
that is on tomorrow.

If it's not too late to reschedule the meeting, I'm fine with that,
but otherwise I'll dial in when I can. Others have the host code.

I have not had a chance to look at querydsl.

Craig

On Jun 4, 2009, at 8:27 PM, Michelle Caisse wrote:



Hi,

We will have our regular meeting Friday, June 5 at 9 am PDT to
discuss JDO TCK issues and status.

Dial-in numbers are:
Domestic (toll-free):  866 230-6968
International (caller-paid):  +1 213 787-0528
Access code :  294-0479#

Agenda:

1. JDOQL & Querydsl
2.  Other issues

Action Items from weeks past:

[May 25 2007]  AI everyone download the Grails demo from grails.org
and check it out. Also look at Grails/Groovy ExpandoMetaClass that
has the magic to avoid reflection and enhancement.

[May 25 2007] AI Matthew Adams prepare a proposal with just the
basics of schema synchronization with jdo and orm metadata.

-- Michelle


































  

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!






  



--
*Michael Bouschen*
*Prokurist*

akquinet t...@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bousc...@akquinet.de
Url:www.akquinet.de 

akquinet t...@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

Minutes: JDO TCK Conference Call Friday, June 5, 9 am PDT

[Craig L Russell]

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. JDOQL & Querydsl: looks interesting, along the lines of JPA except  
JPA uses Java 6 APT whereas it looks like Querydsl uses a static  
preprocessor. Not much of a difference; Querydsl could use the APT  
approach as well. The big advantage in both approaches is compile-time  
checking.


Looks simple at first glance. But what does it look like with more  
complex queries like joins, projections, collection navigation, maps,  
subselects, etc.? How well does it cover the JDOQL query space?


2.  Other issues

Metadata API changes to update method names and change interface name  
from ComponentMetadata to TypeMetadata. Patches type-2.patch and lower- 
case-d-in-metadata.patch are ready to go. Request DataNucleus folks to  
review and commit when they are ready.


All JDO 2.3 JIRAs have been assigned owners. To improve the schedule,  
feel free to volunteer to take already owned items.


Action Items from weeks past:

[May 25 2007]  AI everyone download the Grails demo from grails.org   
and check it out. Also look at Grails/Groovy ExpandoMetaClass that   
has the magic to avoid reflection and enhancement.


[May 25 2007] AI Matthew Adams prepare a proposal with just the basics  
of schema synchronization with jdo and orm metadata.


-- Michelle



































Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: Minutes: JDO TCK Conference Call Friday, June 5, 9 am PDT

[Timo Westkämper]

Hi.

Some comments on the Querydsl aspects :

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. JDOQL & Querydsl: looks interesting, along the lines of JPA except 
JPA uses Java 6 APT whereas it looks like Querydsl uses a static 
preprocessor. Not much of a difference; Querydsl could use the APT 
approach as well. The big advantage in both approaches is compile-time 
checking.

Querydsl uses Java 6 APT. But we provide support for Java 5 APT as well.



Looks simple at first glance. But what does it look like with more 
complex queries like joins, projections, collection navigation, maps, 
subselects, etc.? How well does it cover the JDOQL query space?
Collection and Map navigation is supported, and subselects are at least 
supported in the JPAQL/HQL module, haven't tested it with JDOQL.


Examples of more complex queries will be in the tests and documentation 
of the next release.



Here is a comparison of queries I posted on Linda de Michiel's JPA 2 
blog  
(http://blogs.sun.com/ldemichiel/entry/java_persistence_2_0_proposed#comments) 
:


JPA 2 query :

QueryBuilder qb = ...
CriteriaQuery q = qb.create();
Root cust = q.from(Customer.class);
Join order = cust.join(Customer_.orders);
Join item = order.join(Order_.lineitems);
q.select(cust.get(Customer_.name))
 .where(qb.equal(item.get(Item_.product).get(Product_.productType),"printer"));


Querydsl query (for HQL) : 


HQLQuery query = new HQLQueryImpl(session);
QCustomer cust = QCustomer.customer; 
QOrder order = QOrder.order; 
QLineItem lineItem = QLineItem.lineItem;


List customerNames = query.from(cust) 
 .innerJoin(cust.orders, order)

 .innerJoin(order.lineitems, lineItem)
 .where(lineItem.product.productType.eq("printer"))
 .list(cust.name);  


(QCustomer, QOrder and QLineItem are Querydsl metamodel types, they are 
immutable and can be reused over queries)


JPAQL query :

SELECT c.name
FROM Customer c JOIN c.orders o JOIN o.lineitems i
WHERE i.product.productType = 'printer'


Compare the filter expression of JPA 2

 qb.equal(item.get(Item_.product).get(Product_.productType),"printer")

with the Querydsl version

  lineItem.product.productType.eq("printer") 



Br,
Timo Westkämper / Mysema Ltd