You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michelle Caisse <Mi...@Sun.COM> on 2006/06/22 23:51:51 UTC
JDO TCK Conference Call Friday, June 23 9 am PST [UPDATED]
Hi,
We will have our regular meeting Friday, June 23 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO maintenance release content (Craig)
2. JDO2 Annotations (Craig)
3. Subqueries in JDOQL, further comments? (Matthew, Craig)
4. Updates to embedded field, date field relected in owning object, JIRA
382 (Michelle)
5. Other issues (any and all)
Action Items from weeks past:
[Jun 16 2006] AI: Everyone respond to Matthew's email dated June 9.
[Jun 2 2006] Additional query tests are in Craig's workspace. AI Craig:
file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[May 26 2006] The spec describes handling of oid fields (application
identity) where the field is a persistence capable type. The
description says that the type of the oid field must be the same type
as the persistence capable class, but actually the type of the oid
field must be the type of the oid of the referenced class. AI Craig:
update the spec and the wiki change log. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, August 11, 9 am PST
Posted by Michael Bouschen <mb...@spree.de>.
Hi Andy,
this is great news! I must have missed that you changed back JPOX to the
behavior of 1.1.0 with respect to object deletion.
I can confirm that the TCK passes uses the latest JPOX SNAPSHOT. There
is only one query failure (see JIRA JDO-390 for details), but this is
not related to the issue of object deletion (JDO-392).
Regards Michael
>> Current TCK against the current JPOX snapshot fails in tearDown due
>> to foreign key constraint violations. The TCK might need to change
>> based on the resolution of JDO-392. AI Erik change JPOX to allow the
>> TCK to use the old behavior; the TCK might need a PMF flag for interim.
>>
>
> JPOX (nightly builds, available on our Maven repo) has for the last several
> weeks used the same behaviour that was used at 1.1.0 ... namely
> * if delete-dependent then delete dependents
> * else if nullable null the FK
> * else leave to the DB
>
> It has no such issue with any TCK snapshot that i've checked out over the last
> 2 months. Not sure what people are using there.
>
>
> I totally agree with Jorg that the use of <foreign-key> should be taken into
> account in this process. What it should be IMHO is
> 1. If delete-dependent, then delete dependents
> 2. If not dependent, but an FK is specified leave to the DB to sort it out
> 3. If not dependent, and no FK, null the FK (if nullable)
> 4. Else leave it to see what happens.
>
> The code for this is in JPOX CVS commented out (for 1-1, 1-N, M-N, N-1
> relations), but am waiting on JDO-392 to consider the issue before I enable
> it. If JDO-392 (and the content of the spec on this issue) doesn't get any
> action in the near future then it will become a JPOX extension.
>
>
>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: Minutes: JDO TCK Conference Call Friday, August 11, 9 am PST
Posted by Andy Jefferson <an...@jpox.org>.
> Current TCK against the current JPOX snapshot fails in tearDown due
> to foreign key constraint violations. The TCK might need to change
> based on the resolution of JDO-392. AI Erik change JPOX to allow the
> TCK to use the old behavior; the TCK might need a PMF flag for interim.
JPOX (nightly builds, available on our Maven repo) has for the last several
weeks used the same behaviour that was used at 1.1.0 ... namely
* if delete-dependent then delete dependents
* else if nullable null the FK
* else leave to the DB
It has no such issue with any TCK snapshot that i've checked out over the last
2 months. Not sure what people are using there.
I totally agree with Jorg that the use of <foreign-key> should be taken into
account in this process. What it should be IMHO is
1. If delete-dependent, then delete dependents
2. If not dependent, but an FK is specified leave to the DB to sort it out
3. If not dependent, and no FK, null the FK (if nullable)
4. Else leave it to see what happens.
The code for this is in JPOX CVS commented out (for 1-1, 1-N, M-N, N-1
relations), but am waiting on JDO-392 to consider the issue before I enable
it. If JDO-392 (and the content of the spec on this issue) doesn't get any
action in the near future then it will become a JPOX extension.
--
Andy
Minutes: JDO TCK Conference Call Friday, August 11, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Martin Zaun, Erik
Bengtson, Craig Russell
Administrative: The next two meetings are canceled due to vacations.
The next regular meeting will be on September 1 (this is Labor Day
weekend in the US).
Agenda:
1. JDO annotations proposal. AI everyone: update the wiki page.
2. JDOQL subqueries proposal. Experts have had a chance to review
this proposal and it can not become part of the change log for
maintenance of the JDO spec. AI Craig write up the change log
proposal; AI Michael start work on the specification update.
3. Apache JDO downloads no longer at http://www.apache.org/dyn/
closer.cgi/java-repository/javax.jdo/jars. The maven repository
structure in Apache has changed to reflect the differences between
maven 1 and maven 2. This broke the JDO downloads page on the web
site. AI Michelle: file a JDO JIRA "site and infrastructure" and fix it.
4. Other issues
Current TCK against the current JPOX snapshot fails in tearDown due
to foreign key constraint violations. The TCK might need to change
based on the resolution of JDO-392. AI Erik change JPOX to allow the
TCK to use the old behavior; the TCK might need a PMF flag for interim.
Michael is trying to use a List where the ordering is specified by a
field in the element class. This is JDO-193 which has not been
implemented yet. So it might work and it might not. No one can prove
it works yet. AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
Action Items from weeks past:
[Aug 4 2006] AI everyone: review Michael's proposal for subqueries in
JDOQL in an email dated 26-Jul 2:41 PM PDT Subject Re: JDOQL Subquery
proposals and provide feedback.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning
a copy.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached
to JDO-403 as a straw proposal for JDO2 annotations..
[Jul 21 2006] Deletion of objects when foreign-key is present
(JDO-392) Craig thinks that we need to add metadata to specify the
behavior of the JDO implementation. AI: Craig propose wording and new
metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
RE: Minutes: JDO TCK Conference Call Friday, September 8, 9 am PT
Posted by er...@jpox.org.
Hi,
I've been so busy that I forgot today is Friday... I have one issue that
I noticed recently when playing with classloaders. It's the following:
1-Jdo.jar loaded by JDOClassLoader
2-Jpox.jar loaded by JPOXClassLoader (has access to JDOClassLoader)
3-Persistent Classes loaded by PersistentClassesClassLoader (has access
to JDOClassLoader)
4-Persistence Code loaded by PersistenceClassLoader (has access to
PersistentClassesClassLoader and JDOClassLoader)
5-Derby.jar loaded by DerbyClassLoader
The current thread invokes the Persistent Code. The current thread has
none of these classes/libraries in the class path. The Persistence Code
is the following:
pmf = JDOHelper.getPMF(props, JPOXClassLoaderReference);
The JPOX PMF impl is created but when JPOX wants to connect to the
database, it tries to instantiate the derby driver, however it is not
found in the classpath.
With this classpath configuration it's not currently possible to run the
application using the JDO standard (only with a proprietary
PMF.setUserClassLoader())
How about adding a method to include an user classloader at the end of
the class path search?
Regards,
Erik Bengtson
> -----Original Message-----
> From: Craig.Russell@Sun.COM [mailto:Craig.Russell@Sun.COM]
> Sent: Friday, September 08, 2006 7:12 PM
> Cc: jdo-dev@db.apache.org; JDO Expert Group
> Subject: Minutes: JDO TCK Conference Call Friday, September 8, 9 am PT
>
> Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig
> Russell
>
> Agenda:
>
> 1. Relationships mapped with mapped-by
>
> Proposal was reviewed by Joerg, Michael, and Matthew. One-many case
> certain updates are conflicting, but no discussion of throwing an
> exception. The spec does require an exception to be thrown. Matthew
> would like to add examples of conflicts with one-one relationships.
> AI Matthew: write up the conflict case for one-one relationships.
> Additionally, the case of a one-one relationship implemented using a
> join table is not discussed. It should not make a difference. Joerg's
> desired behavior is still not possible. AI Craig reply to Joerg's
email.
>
> 2. JDO annotations Matthew still has the AI to review separating the
> mapping from the object model.
>
> 3. JDOQL subqueries: Michael and Craig still have the AI to write up
> spec changes.
>
> 4. Other issues
>
> Michelle noticed that there are ERRORs in the JPOX regarding not
> finding the xsd files on the internet. Seems that these should be
> WARNINGs instead.
>
> Michelle created a new test case that test Map relationships. The
> test fails, and she filed a patch on the new test. Michelle will
> check it in to allow JPOX to fix the bug.
>
> Action Items from weeks past:
>
> [Sep 1 2006] AI Matthew: look into a cleaner separation for object
> model vs. mapping annotations. AI Craig check into default handling
> to accommodate different defaults based on context.
>
> [Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
> subqueries for community review.
>
> [Sep 1 2006] AI Michelle update download page to refer to ibiblio
> (JDO-406).
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Aug 4 2006] AI: Craig call for a negative vote to approve returning
> a copy.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
> when foreign-key is present .
>
> [Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
> ask for review by EG. AI Martin look at what Hibernate and TopLink
> support for Enum types. In progress
>
> [Jun 2 2006] Additional query tests for projecting variables are in
> Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
> 1.5 issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, September 8, 9 am PT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig
Russell
Agenda:
1. Relationships mapped with mapped-by
Proposal was reviewed by Joerg, Michael, and Matthew. One-many case
certain updates are conflicting, but no discussion of throwing an
exception. The spec does require an exception to be thrown. Matthew
would like to add examples of conflicts with one-one relationships.
AI Matthew: write up the conflict case for one-one relationships.
Additionally, the case of a one-one relationship implemented using a
join table is not discussed. It should not make a difference. Joerg's
desired behavior is still not possible. AI Craig reply to Joerg's email.
2. JDO annotations Matthew still has the AI to review separating the
mapping from the object model.
3. JDOQL subqueries: Michael and Craig still have the AI to write up
spec changes.
4. Other issues
Michelle noticed that there are ERRORs in the JPOX regarding not
finding the xsd files on the internet. Seems that these should be
WARNINGs instead.
Michelle created a new test case that test Map relationships. The
test fails, and she filed a patch on the new test. Michelle will
check it in to allow JPOX to fix the bug.
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object
model vs. mapping annotations. AI Craig check into default handling
to accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406).
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning
a copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, September 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Martin Zaun, Michelle
Caisse, Craig Russell
Agenda:
1. Relationships mapped with mapped-by. Abe White filed a new JDO
TCK bug regarding 15.3 on relationships. This is invalid based on the
errata in the ChangeLog. This highlights the need for an explicit
test case for the clarified behavior.
2. JDO annotations. Matthew is looking at the JPOX implementation.
Still looking into how the two models can be separated.
3. JDOQL subqueries. No news.
4. Other issues
Ilan has filed a request for enhancement of the TCK to permit
reflective implementations. This request has more implications that
the community will need to discuss. AI Craig discuss on aliases.
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object
model vs. mapping annotations. AI Craig check into default handling
to accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning
a copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, September 22, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Martin Zaun
1. JDOQL subqueries
Re Wes's proposal (Re: JDOQL Subquery proposals, 9/17/2006): Basically
good, solves some existing problems, but syntax is not intuitive.
Michael will reply on jdo-dev with an augmented proposal. Also mentioned
2. Other issues
Annotations: Matthew feels that it may be difficult to make a clean
separation. Will discuss the separation, especially how JPA did the
separation versus the JDO perspective, next week.
Discussed List test (JDO-430). Agreed that it is preferable in this
test case for order information to be contained in a database column
only, not in a field of the class.
Discussion on JDO-416. The existing poms are built by maven and loaded
into the local maven repository, generated from project.xml. They are
not correct maven2 poms. There is no place currently to store maven2
poms in subversion. Need to figure out what to do with Matthew's maven2
pom.
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 6, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Martin
Zaun, Craig Russell
Agenda:
1. Test challenge issues and status: All but one challenge have been
resolved. Challenge 9 has been accepted and is pending a patch for
2.0.1. Challenge 10 will need to be split into multiple challenges
because some are valid and some are not. 10a, 10b, 10c, and 10d are
Michelle's suggestions. Some more research is needed on whether
serializing a deleted instance is legal. In any case, the deleted
instance should not be treated as detached at serialization.
Persistent-nontransactional-dirty instances should not be allowed to
be serialized.
2. Reflection based implementations: No one opposed it; Ilan Kirsch
liked it. No one volunteered to help with the work. This work will be
dropped from 2.1 unless someone volunteers to help.
3. JDOQL subquery proposal: No reply to Craig's reply to Wes and
Michael; assume it is the basis for moving forward.
4. Other issues
Discussion on a method by which the user could get a reference to a
thread-local PersistenceManager. This would allow web applications to
use an application static to store the PersistenceManager. AI Craig:
discuss on expert group alias.
JDO-430 Why is there a mapped-by attribute on element element? We
already have it on the field. Answer: for convenience it might be
better for the user to put the mapping information into an element
under field or embedded. AI Michelle change the test case to use
field mapped-by instead of element mapped-by.
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK
to permit reflective implementations on aliases. Done. No one
opposed it; Ilan Kirsch liked it. No one volunteered to help with the
work.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object
model vs. mapping annotations. AI Craig check into default handling
to accommodate different defaults based on context. In progress.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review. In progress. Wes Biggs proposed a
new API that allows both single-string and API versions of subqueries
that looks good.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). Done.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning
a copy from getFetchGroups. Done.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present. Done.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Oct 13, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Martin Zaun, Craig Russell
Agenda:
1. Test challenge status: All challenges have been resolved. No
escalations have been filed yet. Only one issue was resolved as
invalid (hollow should be a permitted state after attaching a
detached instance). Patches were created for the others and a new
workspace was created to hold the updated TCK tests.
2. Proposal for new method to get a ThreadLocal PM: Some good
feedback was received. No one really objects to the ThreadLocal PM,
but concerns were raised that this might not be sufficient for all
purposes. More work needs to be done to see if this really is very
useful.
3. Proposal for alignment with JPA: This proposal to position JDO
PersistenceManager and PersistenceManagerFactory with regard to JPA
was well-received, with just a few comments. Another proposal to
create interfaces that extend both JDO and JPA interfaces had some
discussion with more needed.
4. Other issues
We're pretty close to finalizing the contents of a maintenance
release of JDO 2.1. AI Craig notify aliases and seek additional input.
A new test case was written for checking the TargetClass of an
instance of a persistent interface acquired by pm.newInstance(Class
interface). The test passes on JPOX.
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object
model vs. mapping annotations. AI Craig check into default handling
to accommodate different defaults based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be
reviewed. Done. JDO-344 was resolved. A new JIRA was filed JDO-435
because the test case fails on JPOX.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Oct 27, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Matthew Adams, Martin Zaun, Michael Bouschen, Michelle Caisse
1. JDO 2.1 maintenance release: current DB time
Consensus is to have a JDOQL function similar to SUM, AVG that would
return the current time. Do we need just one or several returning date,
time, timestamp? More work is needed on how to conversions and
comparisons of java.util.Date and SQL timestamp types..
2. JDO annotations - split between JDO and ORM
AI: Everyone take a look at Andy's proposal attached to JDO-403. Some
feedback from those companies who originally asked for split JDO-ORM
annotations (i.e Versant) would be welcomed. The existence of these
features in the .jar doesn't require their use, so it is does not have
much practical import. AI: Matthew add comment to JDO-403. Discussion of
how to annotate a package. Martin stated that this was possible.
Matthew thought it used package-info.java..
3. Other issues
Michael is about to update JDO dependencies (JDO-440). Glassfish
repository generates a warning, but download still works.
Michael has a test case that is failing on a Collection of Strings in a
relationship. AI: send email to jdo-dev.
JDO 2 Change Log has been published to the JCP site.
For next week's agenda: discuss new subprojects for JDO support of JDK 1.5.
Action Items from weeks past:
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 2, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michael Bouschen, Craig Russell
Agenda:
1. Date arithmetic in queries: There are at least two different
issues here:
1a. Retrieving the date from the server. In Oracle, you can SELECT
CURRENT_DATE FROM DUAL. In JDOQL, we have no special persistent class
that has a singleton, to request that exactly one element is
returned. We could use void.class, or null as the candidate class, or
JDOHelper, or PersistenceManagerFactory. The query would look like
"Select xxx From void". Another way to handle this would be to add an
API to PersistenceManagerFactory, e.g. Xxx currentDate().
1b. Using the date in the WHERE clause. Most of the interesting
methods on Date have been deprecated in favor of Calendar. We could
use Calendar.getInstance() which would return the instance in the
time zone and locale of the server. We can support comparisons of
this Calendar with fields of type Date. In order to support date
arithmetic, we could use the add(int field, int amount) method to
change various fields. For portability, we should specify which
calendar fields must be supported by an implementation, e.g.
Calendar.DAY_OF_MONTH. An issue is that the signature of add returns
void. So you can't use the result of add for anything. I suppose we
could follow the example of StringBuffer and have the result of add
be a Calendar, returning this. Similarly, methods roll, set, setTime,
setTimeInMillis, getTime, and getTimeInMillis might be considered as
required or optional. This should depend on the common functionality
of database back ends for the required methods, and implementations
could choose to add more supported methods.
If the candidate collection is an extent or the result of an extent
query, then the Calendar functionality refers to the database back
end. If the candidate collection is a collection, then it refers to
the VM.
2. New subprojects for JDK 1.5 support: There are two ways to
distinguish the artifacts. One is to use a different artifact id; the
other is to use a different version number. The projects that need
different content are the api20 and tck20 projects. These probably
will be branched for the different artifacts. The trunk should
continue with the jdk15 support; the earlier support would be branched.
3. Other issues
none
Craig
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov 2, 9 am PST
Posted by Martin Zaun <Ma...@Sun.COM>.
Hi Michelle, Craig,
I'm on vacation and travelling through next Thursday
and won't be able to dial in tomorrow. I'll dial in
next Friday.
Martin
Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, November 2 at 9 am PST to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Date arithmetic in queries
>
> 2. New subprojects for JDK 1.5 support
>
> 3. Other issues
>
> Action Items from weeks past:
>
> [Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
> between JDO and ORM annotations..
>
> [Sep 1 2006] AI Craig check into default handling to accommodate
> different defaults for annotations (?) based on context. In progress.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user tries
> to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
> Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 16, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Martin Zaun, Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Moving forward with JDO maintenance release. The maintenance
review has almost completed; there were requests for an Item
Exception Review received. The release strategy has been discussed in
email, and it looks like we will create two new projects based on the
two projects that will need jdk 1.5 support. AI: Craig send a [VOTE]
message to formalize the plan.
2. Follow-up on suggestion for new PMF setting
javax.jdo.ClassLoader. The proposal by Erik looks good and might be
included in the maintenance release. Two issues came up: is the
pattern really just one ClassLoader, or is it possible that multiple
class loaders are used? Answer: Multiples. So the API should use the
add/remove pattern instead of set. Second issue: JDOPermission needs
to protect the add/remove operations. AI Craig ask PMO if we can
include this as a comment feedback.
Other issues
3. Erik is changing the query processor for projections and needs to
know if there is some sample code in Apache that evaluates queries in
memory. Yes, but the implementation doesn't support projections. It's
support is for JDO 1 query only.
4. We will not have a meeting next week due to the Thanksgiving holiday.
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Dec 1, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Eric Bengtson, Martin Zaun
- Updating license files JDO-441. We need to check that LICENSE.txt
and NOTICE.txt are up-to-date and run a script on the source files to
modify the license text in accordance with the new policy from Apache.
May only be required for projects that will be released in the future.
- JPOX announced a branching of their nightly release. This should not
affect JDO users.
- A response is needed to the question from Christiaan des Bouvrie on
jdo-user about whether the proposal for retrieving date/time from the
server will be in JDO 2.1. We believe that this and other small
features that are proposed between now and the release date can go
through an additional approval process and make it into the release, but
Craig needs to confirm this.
-- Michelle
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Dec 8, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Erik Bengtson, Craig Russell
Agenda:
1. Moving forward with JDO maintenance release. The plan is to make
an action item list of approved items from the maintenance review and
determine what additional test cases need to be developed for both
1.5 and 1.3 (legacy) api and tck. Once a number of the common items
have been developed, the legacy projects will be forked (svn copy)
and the 1.5-only work can be done.
How to promote JDO 2.1? Maybe a ServerSide article on the differences
from JDO 2.0 and perhaps a deep dive on comparing the persistence
alternatives?
2. Other issues
Items for maintenance that missed the initial maintenance review can
still be developed. Another maintenance review will be done for those
items that we can agree on, including access to time in JDOQL queries.
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Dec 15, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
Thanks for the heads-up on your project plans.
Craig
On Dec 16, 2006, at 2:56 AM, Andy Jefferson wrote:
>> Focus now on the changes that need updated interfaces so we can give
>> JPOX advance notice of the change. Looking in particular at the Query
>> Chapter 14 and BNF.
>
> For information, JPOX 1.2.0-beta-1 is out and JPOX 1.2 will form
> the basis of
> where all changes for JDO2.1 will be performed (on JPOX CVS HEAD).
>
> In terms of changes necessary for using JPOX 1.2 as an RI with the
> JDK1.5
> updates required by JDO2.1, you will, in the future, need jpox-
> java5.jar in
> project.xml as well as jpox.jar.
>
>
> --
> Andy
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Dec 15, 9 am PST
Posted by Andy Jefferson <an...@jpox.org>.
> Focus now on the changes that need updated interfaces so we can give
> JPOX advance notice of the change. Looking in particular at the Query
> Chapter 14 and BNF.
For information, JPOX 1.2.0-beta-1 is out and JPOX 1.2 will form the basis of
where all changes for JDO2.1 will be performed (on JPOX CVS HEAD).
In terms of changes necessary for using JPOX 1.2 as an RI with the JDK1.5
updates required by JDO2.1, you will, in the future, need jpox-java5.jar in
project.xml as well as jpox.jar.
--
Andy
Minutes: JDO TCK Conference Call Friday, Dec 22, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Watsek, Michael Bouschen, Matthew Adams, Michelle
Caisse, Craig Russell
NOTE: Next phone meeting will be after the New Year, on Friday
January 5, 2007.
Agenda:
1. Moving forward with JDO maintenance release. Significant progress
has been made on the items that were approved by the JCP. All of the
updates that do not involve new APIs or new test cases have been made
to the working draft of the 2.1 specification.
JDO-445 discussion. What about close()? Since the life cycle of the
delegate is managed by the server, and the life cycle of the proxy is
unbounded, close() should probably throw an exception. What about
commit() and rollback()? Since the transaction is by definition
managed by the server, these methods should throw an exception. Is
the proxy for use only with JTA? Other possible use cases include
"extended persistence context" within the server as well as Java SE.
In these cases, where there is no TransactionSynchronizationRegistry
assistance, a ThreadLocal would be needed, and the implementation is
not as straightforward. For example, to support multiple
PersistenceManagerFactories, a Map of pmf to pm would be needed in
the ThreadLocal. And the API would need to be told which factory to
use. AI Craig update the JIRA issue with this discussion.
The date issue has two components. One is to retrieve the date from
the server, which could be done via JDOQL or simply an API on
PersistenceManager or PersistenceManagerFactory. Another is to
perform date arithmetic using queries such as to compare a date field
with another date field plus 2 days. Both uses are in scope for the
maintenance release. AI everyone reply to emails on this subject.
2. Other issues
Looking at the DTDs, they have a notation that they are actually xml.
Should these be removed? AI everyone reply to JDO-454.
JDO-441 License update. Michael used the perl scripts on the Apache
committers site and found a number of files with missing licenses.
The scripts have already been updated to reflect the standard use
of .jdo, .orm, and .jdoquery file name suffixes that are actually xml
format. But .conf files used in tck are actually properties files,
although this is just our usage pattern; there is nothing "standard"
about this usage. AI Michael create a wiki page with the scripts used
to update the files.
Action Items from weeks past:
[Dec 15 2006] AI Michelle ask Bill Shannon if fscontext and
providerutil will be available for automatic download from maven
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more
work in the annotation handler and doesn't provide for compile-time
checking of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 26, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell, Erik Bengtson, Martin
Zaun, Matthew Adams
Agenda:
1. Proposal for Service Discovery: Looks reasonable. Requires a few
changes to the JDOHelper to discover PersistenceManagerFactories.
Uses the same pattern as used by JPA. Should avoid a hard dependency
from JDOHelpler to OSGi.
2. JDO2 Annotations: Discussion is ongoing on the JIRA that contains
the working draft of the annotations. AI everyone look at the
annotations and comment.
3. Other issues
none.
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink
support for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Feb 16, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Martin Zaun, Michelle
Caisse, Erik Bengtson, Craig Russell
Agenda:
1. getPersistenceManagerProxy discussion: There were some questions
from the field. The implementation doesn't implement the thread
local, and was just an idea. AI: don't ship the
PersistenceManagerProxyImpl as part of the api jar, but as part of
the runtime2 or util2 implementation.
2. JDO-460 StateTransitions test - different transitions expected for
hollow vs. persistent nontransactional instance: JPOX fails on the
state transition test when detaching a hollow instance. But the test
might give the implementation a persistent-nontx instance when it
should give a hollow instance. AI: Michelle and Craig investigate.
3. Other issues
An avid user of JDO 1 requested enhancer support for JDK 1.5. The
support exists but has not been released. The user will have to build
the jar file himself. AI: Martin reply to the message.
Review of the patch attached to JDO-445:
a. The version number of the PersistenceManager needs to be updated
to 2.1.
b. The spec needs to require an inheritable ThreadLocal for storing
the delegate PersistenceManager. And if a child thread closes the
proxy, causing the delegate to be closed, other threads using the
proxy will get an exception when they try to use it.
c. Should we declare constants for the two resource types JTA or
RESOURCE_LOCAL? Can be declared in PersistenceManagerFactory since
that's the only place they are used.
d. Add a reference to JSR-220 in the javadoc of get/
setPersistenceUnitName.
e. For setServerTimeZoneID, null is an acceptable value. Non-null
values will be checked against the TimeZone.getAvailableIDs and an
exception is thrown if the value does not match one of these.
AI: Everyone review the patch when it's sent around again and please
VOTE.
Action Items from weeks past:
[Feb 9 2006] AI Craig send Server TimeZone proposal to the expert
group for a vote.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Feb 23, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Michelle Caisse, Erik
Bengtson, Craig Russell
Agenda:
1. Persistent interface specification clarification proposals
usage in pm.newInstance:
In order for the newInstance method to be used with a persistent
interface, the parameter interface must be completely mapped. That
is, the interface must be declared in metadata using the interface
element.
Additionally, for relational implementations,
o the interface must be mapped to a table; portable applications will
use the table attribute for this purpose
o all persistent properties must be mapped to columns; portable
applications will use the column attribute of the property element
contained in the interface element
o interfaces that are of types of relationships declared as
persistent properties of the parameter interface must all be
completely mapped
o to be portable, all implementations of persistent interfaces will
share a common concrete persistence-capable base class
If any of the above conditions is not met, JDOUserException is thrown
by the newInstance method.
note: a persistent interface should use the same rules as persistent
classes for deciding whether a property is persistent or not; the
generated class will contain proper implements of non-persistent
properties
usage in field type:
Metadata requirements for persistence-capable classes that implement or
use persistence-capable interfaces
Note PC classes that "java implement" pc interfaces don't even need
the implements clause of the metadata
For persistence-capable classes that implement persistence-capable
interfaces, if the persistence-capable class employs property-level
interception for the persistence-capable interface's property, or
if the
persistence-capable class employs field-level interception for the field
that stores the value of the persistence-capable interface's property
and the field's name and type matches the property's name and type, then
no additional metadata is required.
Query usage: If the persistence-capable class
employs field-level interception for the field that stores the value the
persistence-capable interface's property and the field's name or type
differs from the property's name or type, the "class" element must
include the "implements" element, which for each unmatched property and
field, must include a "property" element whose "name" attribute matches
the persistence-capable interface's property name and whose "field-name"
attribute is the name of the field that stores the value of the
persistence-capable interface's property.
For persistence-capable classes that contain a field or property of a
persistence-capable interface type, no additional metadata is
required. If the user wishes to restrict the type of instances that
can be stored in this field, the field-type attribute is used.
The application is portable if all implementations of the
persistence-capable interface share a common persistence-capable
superclass; if they do not, then the application is not portable.
The inclusion of the "property" element within the "implements" element
is primarily intended to support query filter expressions that traverse
fields of interface types.
AI: All review Matthew's examples
usage in query:
If the metadata for a persistence-capable interface indicates (via
the explicit or implicit setting of the requires-extent attribute)
that an extent is managed for the interface, then the extent consists
of the datastore objects of the persistence-capable classes
implementing the interface including the datastore objects created
with PersistenceManager.newInstance.
The candidate class of a JDOQL query may be a persistence-capable
interface. In this case the candidate class name scope includes the
persistent properties as explicitly or implicitly defined as
persistent properties in the metadata of the persistence-capable
interface.
JDOQL supports navigation through a field or property of the type of
a persistence-capable interface. Such an expression may then be
further decomposed in order to access persistent properties.
</proposal>
Another remark:
Section18.3 ELEMENT interface says: "The requires-extent attribute is
optional. If set to "false", the JDO implementation does not need to
support extents of factory-made persistent instances."
I understand that "factory-made persistent instances" refers to
instances created by PM.newInstance. Then I propose to remove
"factory-made", because the extent of a persistence-capable interface
may consist of the extents of the persistence-capable classes
implementing the interface and then there are no "factory-made"
persistence instances are involved.
interface requires-extent means that an extent of factory-made
instances is managed and getExtent can be executed on the interface.
The extent of the interface includes all factor-made instances plus
all instances of pc classes that both implement the interface and
manage an extent.
Note that if an interface is defined as "detachable" then the
implementation must generate a Serializable class for the interface.
AI Craig: Formalize the above concepts and send to community for review.
2. Forking codeline for JDK 1.5 support: Planning on forking api2-
legacy "now". Next week we will change the JIRA for 1.5 support.
groupId, artifactId, versionId for these projects
3. JDOHelper enhancements: AI Matthew: send proposal
4. Callback annotations: AI Matthew: send proposal
5. Groovy integrations: AI Matthew: send proposal
6. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 9, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
NOTE: Daylight Savings Time begins next week in the U.S. Next week's
meeting will be at 9 AM PDT.
Attendees: Erik Bengtson, Matthew Adams, Michelle Caisse, Michael
Bouschen, Martin Zaun, Craig Russell
Agenda:
1. Named PMF proposal
Question: What if the user already has a configuration.properties
file? Answer: This still works.
Question: What if the user adds the same listener with a different
set of listened classes? Answer: The spec needs to be changed to be
consistent with the proposed xml. AI Craig: Update the spec to
require that the key of the listener is the class name of the listener.
Question: Why are there no constants defined for the PMF options?
Answer: We should add them to PMF.
Question: What if there are multiple jdoconfig.xml files and the name
requested is not in any of them? Answer: Use the Persistence approach
to get the factory. You can get the instance of Persistence.class by
reflection and invoke getEntityManagerFactory(String) and cast the
result to a PersistenceManagerFactory.
2. Delete by object id Might not be needed after all. AI All discuss
on email list.
3. Other issues
Disk space usage on Apache: Can we get rid of jdo2 beta and jdo2 rc1?
Yes. AI Michelle get rid of these old releases.
Action Items from weeks past:
[Mar 2 2007] AI: All review issue http://issues.apache.org/jira/
browse/JDO-467
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Mar 2 2007] AI: Craig and Michelle - TOI on updating Sun web site
for JDO-379
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 16, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Erik Bengtson, Martin Zaun, Michelle
Caisse, Craig Russell
Agenda:
1. Delete by object id. Matthew has voted against his proposal, so it
will be dropped.
2. Persistent properties for classes questions. Erik had some
questions on the specification.
If a user declares a persistent property then there must not be a
persistent field of the same name. So, the field of the same name and
type in the same class should be defaulted to not persistent. But a
persistent property of the same name and type as a persistent field
in a superclass is disallowed. The persistence semantics of a
persistent property in a superclass cannot be modified by a
persistent subclass. For example, you cannot declare a persistent
property in a subclass where the same property name is already
persistent in a superclass.
We should probably look at cases where a subclass implements a
persistent interface and the persistent properties are actually
implemented as persistent properties or persistent fields in the
superclass.
With user exceptions thrown from the use of setters of persistent
properties by the JDO implementation, the exception is wrapped by a
JDOUserException and if done as part of flush, all these exceptions
are collected in the failed object array as other exceptions are
handled today. If during the beforeCompletion actions of commit same
as above plus, the transaction is rolled back. The first such failure
causes the implementation to abandon that persistent object.
Clarification needed for retainValues and restoreValues for
persistent properties. These properties should be implemented similar
to the behavior for fields. That is, properties are cleared to their
Java default values or restored to their before image.
3. Problem with JDO 2 xsd JIRA issue has been filed on this subject.
4. Other issues
Clarify the behavior of detach, retrieve, and refresh with regard to
the fetch group parameter. AI Erik file a JIRA.
Matthew has filed a patch for parsing the jdoconfig.xml file, and
needs some test cases, especially negative ones. And if anyone has
spare cycles to review the patch, please do so.
Action Items from weeks past:
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 9 2007] AI Michelle: Get rid of old beta and rc1 releases using
disk space on Apache.
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Mar 23, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
> Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
> Russell
>
> Agenda:
>
> https://issues.apache.org/jira/browse/JDO-472 Use of jdo.xsd with JDK
> 5 xml parser. Apparently there is a problem using the standard parser.
> For the api20 project, we use the Apache xerces parser which
> apparently does not complain.
>
> The error seems to occur in the definition of the <extension> element.
> The current definition requires <extension> to be either first or last
> in the sub-elements of several elements. It might be possible to relax
> this requirement and make <extension> peer to other elements. AI
> Michael investigate. Also check the api20 xml test to be sure it
> catches all exceptions.
I double checked the api20 xml test and it catches all the exceptions. I
was confused by the negative xml test. Here an exception is expected and
should not be reported as test result. Sorry for the false alarm.
Regards Michael
>
> [...]
--
Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
Buelowstr. 66 Fax.: +49/(0)30/217 520-12
10783 Berlin mailto:mbo.tech@spree.de
Geschaeftsfuehrung: Dr. Gerhard Mueller-Proefrock
Anna-Kristin Proefrock
Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
Minutes: JDO TCK Conference Call Friday, Mar 23, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
https://issues.apache.org/jira/browse/JDO-472 Use of jdo.xsd with JDK
5 xml parser. Apparently there is a problem using the standard
parser. For the api20 project, we use the Apache xerces parser which
apparently does not complain.
The error seems to occur in the definition of the <extension>
element. The current definition requires <extension> to be either
first or last in the sub-elements of several elements. It might be
possible to relax this requirement and make <extension> peer to other
elements. AI Michael investigate. Also check the api20 xml test to be
sure it catches all exceptions. AI Craig try to find an xml expert to
help. For example, is there a need to define a jdo:any element?
https://issues.apache.org/jira/browse/JDO-467 is getting close to
ready. AI all please review the code, especially
JDOHelper.getPMFFromEMF.
Action Items from weeks past:
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Apr 6 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Challenge of
org.apache.jdo.tck.lifecycle.StateTransitionsReturnedObjects. The
challenge looks valid; we need to write a patch since this test is
way too important to put into the exclude list. AI: Michelle file and
fix JIRA issue.
The test probably should test that persistent-nontransactional-dirty
instances should transition to detached-dirty on either detach or
serialization. AI Craig: resolve this in the spec.
2. xml library error on api20: Linkage Error running the xml tests
using JDK 1.5. The version of the class that the API was compiled
against is different from the class found at runtime. AI: Matthew
filed JIRA issues http://issues.apache.org/jira/browse/JDO-477 and
http://issues.apache.org/jira/browse/JDO-478
3. Other issues
Michelle is working on negative tests for newInstance. JPOX 1.1.7
doesn't support enhancement of Abstract Persistent Classes, which
means the enhancement fails. AI Michelle file a JIRA.
http://issues.apache.org/jira/browse/JDO-476 may be related to this
issue.
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 27 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
On Apr 27, 2007, at 1:23 AM, Erik Bengtson wrote:
> Quoting Andy Jefferson <an...@jpox.org>:
>
>>> Another issue: deletePersistentAll((Object[]) null) (and similars
>>> operations) behavior not specified if arg is null
>>
>> See 12.6 at the end "Null management".
>>
>
> Andy,
>
> That section refers to PM methods and only with arguments Object or
> Object[].
The text refers to Object[ ] and Collection arguments.
> Another similar section should be added to Query api too.
I agree. The text can probably just be lifted and adapted slightly to
achieve the same effect: Null-valued Object[ ], Collection, and Map
arguments throw NullPointerException. The reason to throw NPE instead
of JDOUserException is that there is a standard meaning for NPE (a
reference type cannot be null for this method), and that there would
be no added value wrapping in a JDO exception.
Craig
>
> query.deletePersistentAll((Object[]) null)
> etc
>
> Another non specified behavior is for Map and Collection
>
> query.deletePersistentAll((Map) null)
> pm.makePersistentAll((Collection)null)
> pm.deletePersistentAll((Collection)null)
>
> For the below methods, I don't know if this is in the spec but JPOX
> currently
> throws JDOUserException for
>
> pm.getObjectById((Collection)null)
> pm.getObjectById((Collection)null,boolean)
>
> I have only looked at a few methods, so other methods might need
> review too.
>
> Regards,
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 27 , 9 am PDT
Posted by Erik Bengtson <er...@jpox.org>.
Quoting Andy Jefferson <an...@jpox.org>:
> > Another issue: deletePersistentAll((Object[]) null) (and similars
> > operations) behavior not specified if arg is null
>
> See 12.6 at the end "Null management".
>
Andy,
That section refers to PM methods and only with arguments Object or Object[].
Another similar section should be added to Query api too.
query.deletePersistentAll((Object[]) null)
etc
Another non specified behavior is for Map and Collection
query.deletePersistentAll((Map) null)
pm.makePersistentAll((Collection)null)
pm.deletePersistentAll((Collection)null)
For the below methods, I don't know if this is in the spec but JPOX currently
throws JDOUserException for
pm.getObjectById((Collection)null)
pm.getObjectById((Collection)null,boolean)
I have only looked at a few methods, so other methods might need review too.
Regards,
Re: JDO TCK Conference Call Friday, Apr 27 , 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> Another issue: deletePersistentAll((Object[]) null) (and similars
> operations) behavior not specified if arg is null
See 12.6 at the end "Null management".
- Andy (Java Persistent Objects - http://www.jpox.org)
CANCELLED: JDO TCK Conference Call Friday, May 11
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
Because a number of the usual participants are at JavaOne this week,
there will be no JDO TCK meeting this Friday, May 11. Our next meeting
will be on May 18.
-- Michelle
Re: JDO TCK Conference Call Friday, Apr 27 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Martin Zaun, Erik
Bengtson, Craig Russell
Agenda:
1. JDO metadata: XSD changes: The proposal to loosen restrictions had
one negative reply, since there is more work to do by the jdo
implementation. AI Erik reply to the issue and supply more
information if there is still a problem.
2. Support specification of ForeignKey, PrimaryKey within @Join and
@Element annotations (JDO-486)
The basic request seems valid. Anything that can be specified with
xml should have a corresponding annotation as well. AI Craig reply to
JDO-403 discussion.
3. Other issues
Null-valued arguments for Collection, Object[ ], and Map. The entire
Query API should be examined for the possibility of null arguments.
But we don't expect to find many cases where a null value should be
accepted. AI Craig review Query API and send email to experts.
Erik sent a discussion topic for JPA style transactions, which was
rejected by the Apache spam filter. AI Erik file a JIRA and attach
the document to it. The idea is to synchronize as much as possible
with the JPA transaction requirements.
Action Items from weeks past:
[Mar 30 2007] AI Eric: Post a number of scenarios regarding JDO2/JPA
transaction types for discussion.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, May 4 , 9 am PDT
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michelle Caisse, Martin Zaun, Michael Bouschen, Craig Russell
Agenda:
1. JPA style transactions
No one had time to look at the tables that Erik sent out.
2. Other issues
New test cases that Michelle Caisse wrote are causing failures during
tearDown trying to remove AAddress instances. Might be a problem with
the mapping suffix.
Action Items from weeks past:
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Jun 15, 2007, at 11:20 AM, Andy Jefferson wrote:
> Hi Craig,
>
>> Looks like this will be available for testing this weekend (once the
>> HEAD gets pushed out). Right?
>
> HEAD (and RELEASE_1_1) is built every night at approx 01:00 GMT, so
> yes.
>
> PS. Any JDO2.1 TCK will, at some point, need jpox-java5-1.2-
> SNAPSHOT.jar
> including in its project.xml. This JPOX jar was previously (til
> last night)
> including the JDO2.1 annotations in the jar, but I've now stripped
> them out
> to use those in the jdo2-api-SNAPSHOT.jar so things should be in
> about the
> right places now :-)
Great. Still have just a few iterations of the annotations to go.
Thanks for all the work you put into the annotation preview.
Craig
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Andy Jefferson wrote:
>PS. Any JDO2.1 TCK will, at some point, need jpox-java5-1.2-SNAPSHOT.jar
>including in its project.xml. This JPOX jar was previously (til last night)
>including the JDO2.1 annotations in the jar, but I've now stripped them out
>to use those in the jdo2-api-SNAPSHOT.jar so things should be in about the
>right places now :-)
>
>
I have this in my workspace now and will check it in sometime soon.
-- Michelle
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig,
> Looks like this will be available for testing this weekend (once the
> HEAD gets pushed out). Right?
HEAD (and RELEASE_1_1) is built every night at approx 01:00 GMT, so yes.
PS. Any JDO2.1 TCK will, at some point, need jpox-java5-1.2-SNAPSHOT.jar
including in its project.xml. This JPOX jar was previously (til last night)
including the JDO2.1 annotations in the jar, but I've now stripped them out
to use those in the jdo2-api-SNAPSHOT.jar so things should be in about the
right places now :-)
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Cool.
Craig
On Jun 15, 2007, at 2:28 PM, Michael Bouschen wrote:
> Hi Andy, hi Craig,
>
> I ran the TCK with JDO metatdata files referring the 2.1 XSD
> against the latest JPOX and it works great!
>
> I will file a JIRA issue for chaning the metadata files and attach
> a patch.
>
> Regards Michael
>>
>> On Jun 15, 2007, at 10:33 AM, Andy Jefferson wrote:
>>
>>>> 3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
>>>> definition. AI Michael file a blocker JIRA to get the JPOX fixed.
>>>
>>> You mean this ?
>>> http://www.jpox.org/servlet/jira/browse/CORE-3300
>>
>> Looks like this will be available for testing this weekend (once
>> the HEAD gets pushed out). Right?
>>
>> Thanks,
>>
>> Craig
>>
>>>
>>> --Andy (Java Persistent Objects - http://www.jpox.org)
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
>
> --
> Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
> Buelowstr. 66 Fax.: +49/(0)30/217 520-12
> 10783 Berlin mailto:mbo.tech@spree.de
> Geschaeftsfuehrung: Anna-Kristin Proefrock
> Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
This is great! I'm also making progress on annotations tests and will
probably have something to check in early next week so it would be cool
if we could branch tck20 soon.
-- Michelle
Michael Bouschen wrote:
> Hi Andy, hi Craig,
>
> I ran the TCK with JDO metatdata files referring the 2.1 XSD against
> the latest JPOX and it works great!
>
> I will file a JIRA issue for chaning the metadata files and attach a
> patch.
>
> Regards Michael
>
>>
>> On Jun 15, 2007, at 10:33 AM, Andy Jefferson wrote:
>>
>>>> 3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
>>>> definition. AI Michael file a blocker JIRA to get the JPOX fixed.
>>>
>>>
>>> You mean this ?
>>> http://www.jpox.org/servlet/jira/browse/CORE-3300
>>
>>
>> Looks like this will be available for testing this weekend (once the
>> HEAD gets pushed out). Right?
>>
>> Thanks,
>>
>> Craig
>>
>>>
>>> --Andy (Java Persistent Objects - http://www.jpox.org)
>>
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
>
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi Andy, hi Craig,
I ran the TCK with JDO metatdata files referring the 2.1 XSD against the
latest JPOX and it works great!
I will file a JIRA issue for chaning the metadata files and attach a patch.
Regards Michael
>
> On Jun 15, 2007, at 10:33 AM, Andy Jefferson wrote:
>
>>> 3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
>>> definition. AI Michael file a blocker JIRA to get the JPOX fixed.
>>
>> You mean this ?
>> http://www.jpox.org/servlet/jira/browse/CORE-3300
>
> Looks like this will be available for testing this weekend (once the
> HEAD gets pushed out). Right?
>
> Thanks,
>
> Craig
>
>>
>> --Andy (Java Persistent Objects - http://www.jpox.org)
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
--
Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
Buelowstr. 66 Fax.: +49/(0)30/217 520-12
10783 Berlin mailto:mbo.tech@spree.de
Geschaeftsfuehrung: Anna-Kristin Proefrock
Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
On Jun 15, 2007, at 10:33 AM, Andy Jefferson wrote:
>> 3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
>> definition. AI Michael file a blocker JIRA to get the JPOX fixed.
>
> You mean this ?
> http://www.jpox.org/servlet/jira/browse/CORE-3300
Looks like this will be available for testing this weekend (once the
HEAD gets pushed out). Right?
Thanks,
Craig
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> 3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
> definition. AI Michael file a blocker JIRA to get the JPOX fixed.
You mean this ?
http://www.jpox.org/servlet/jira/browse/CORE-3300
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> The errors that I see now are related to changing boolean to String in
> the annotations classes. Presumably this will be fixed in an upcoming
> build of jpox and I can proceed with the test development.
All handling changes for boolean/String were made earlier today and I've just
run the nightly build so you should now be able to download latest of
jpox-core-1.2-SNAPSHOT.jar
jpox-enhancer-1.2-SNAPSHOT.jar
jpox-java5-1.2-SNAPSHOT.jar
-- Andy (Java Persistent Objects - http://www.jpox.org)
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Craig L Russell wrote:
> Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Martin
> Zaun, Craig Russell
>
> 1. Annotations update Annotations were checked in to the api2
> project. Michelle is trying to get JPOX enhancer to work with
> annotations instead of using .jdo and .orm metadata files.
The errors that I see now are related to changing boolean to String in
the annotations classes. Presumably this will be fixed in an upcoming
build of jpox and I can proceed with the test development.
-- Michelle
Re: JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Martin
Zaun, Craig Russell
1. Annotations update Annotations were checked in to the api2
project. Michelle is trying to get JPOX enhancer to work with
annotations instead of using .jdo and .orm metadata files.
What about defining an enum like TriStateBoolean with TRUE, FALSE,
UNDEFINED. AI Matthew write up a proposal.
Some of the enums have a trailing "Type" in their names. But not all
of them. Should we drop the trailing "Type"? AI Michelle write up a
proposal for the discussion list.
2. Feedback on JDO 2.1 draft spec: The spec didn't make it to the jdo-
dev at apache alias so it will have to be posted in some other place.
AI Craig put it somewhere else.
3. Update TCK to use 2.1 xsd: Enhancer has a problem with 2.1 xsd
definition. AI Michael file a blocker JIRA to get the JPOX enhancer
fixed.
4. Other issues
JDO-501 refers to the manifest seed file that needs to have the osgi
information on exported packages for the api2 and api2-legacy but not
other projects. AI Michelle assign JDO-501 to self.
Need to resolve the new Name property for PMF. AI Craig resolve on
email discussion, open a JIRA to add Name property to api2 and api2-
legacy.
Action Items from weeks past:
[Jun 7 2007] AI Craig file a JIRA to improve javadoc for the test
classes. Done JDO-500
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, July 27, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> [From Craig, by email]: The tck with annotations isn't working yet,
> although it does get past the enhancement step. There are issues with
> relationships and embedded null values.
Hi all,
I ran the TCK today (with latest JPOX CVS) and all annotations tests pass
except for the persistent-interface case. JPOX prior to this morning didn't
support the "embeddedMapping" element on @Element, @Key, @Value, but it now
does. Grab the latest jars in the nightly build area and you should be fine.
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Minutes: JDO TCK Conference Call Friday, Aug 10, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> 2. Annotations: discuss custom settings for enum-valued elements. We
> need better javadoc for UNKNOWN, and in fact we might change UNKNOWN
> to UNSPECIFIED so it's more clear from the name itself. AI Matthew
> raise this issue on the alias. It also seems like adding a new value
> of CUSTOM is unnecessary because if the user specifies a custom
> value, the annotation processor just uses it, and verifies that the
> standard strategy enum value is UNSPECIFIED.
@Persistence "valueStrategy"
@DatastoreIdentity "strategy"
+1 to rename of UNKNOWN to UNSPECIFIED, and use of "customStrategy"
(@DatastoreIdentity) / "customValueStrategy" (@Persistent) as per Craigs
proposal.
@Inheritance also has "strategy"
To allow implementations to define their own inheritance strategies can we
make the following changes
1. InheritanceStrategy : add UNSPECIFIED
2. @Inheritance : change "strategy" to have default of UNSPECIFIED
3. @Inheritance : add "customStrategy"
I was going to raise this a JIRA for this but Apache JIRA seems to be dead ...
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Embedding fields of non-persistent types even when field-type is
used
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Jul 30, 2007, at 12:51 AM, Andy Jefferson wrote:
> Hi Craig,
>
>> I agree that we're getting a bit far from reality with the framework
>> that we set up for deepEquality testing. It appears that a
>> reflection-
>> based approach might work if we are unsuccessful in getting JPOX to
>> work with this artificial setup.
>>
>> Michelle and I have already prototyped a reflective approach for
>> comparing two object graphs. So that's our Plan B in case it's too
>> much work to force-fit JPOX persistent interface.
>
> Plan B shouldn't be needed. If all patches from JDO-503 are applied
> and latest
> JPOX is used then companyAnnotatedNoRelationshipsPIPM test passes ;-)
Yay. Nice work!
Craig
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Embedding fields of non-persistent types even when field-type is used
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig,
> I agree that we're getting a bit far from reality with the framework
> that we set up for deepEquality testing. It appears that a reflection-
> based approach might work if we are unsuccessful in getting JPOX to
> work with this artificial setup.
>
> Michelle and I have already prototyped a reflective approach for
> comparing two object graphs. So that's our Plan B in case it's too
> much work to force-fit JPOX persistent interface.
Plan B shouldn't be needed. If all patches from JDO-503 are applied and latest
JPOX is used then companyAnnotatedNoRelationshipsPIPM test passes ;-)
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Embedding fields of non-persistent types even when field-type is
used
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
I agree that we're getting a bit far from reality with the framework
that we set up for deepEquality testing. It appears that a reflection-
based approach might work if we are unsuccessful in getting JPOX to
work with this artificial setup.
Michelle and I have already prototyped a reflective approach for
comparing two object graphs. So that's our Plan B in case it's too
much work to force-fit JPOX persistent interface.
Craig
On Jul 27, 2007, at 10:50 PM, Andy Jefferson wrote:
> Hi Craig, Michelle,
>
>> The problem is that if you declare the PI* address property in
>> PICompany as
>> PIAddress getAddress()
>> void setAddress(PIAddress)
>>
>> then it doesn't implement ICompany any more, since you also need
>> these from the ICompany interface:
>> IAddress getAddress()
>> void setAddress(IAddress)
>>
>> And of course these are the methods that the e.g. FC classes
>> implement by casting the input IAddress to FCAddress. Which is what
>> we want the generated PICompanyImpl to do because we specify that the
>> type of the field is PIAddress.
>
> There are still places where there is no "types" (annotations) or
> "field-type"
> (XML) specified on overridden interface fields. I'll start from the
> one
> that "companyPMInterface.conf" complains about
>
> PIInsurance has no <property field-type="..."> on field "employee".
> PIDSInsurance has no @Persistent(types=) on field "employee".
>
> Fix those and re-run, you then get the error on
> PIEmployee "dentalInsurance", "medicalInsurance", "department",
> "fundingDept", ...
> PIDSEmployee etc
>
> When those are fixed there are likely some others.
>
> Only when *all* of these are added can we address if JPOX can cope
> with that
> structure or not. As it is currently there are persistent
> properties that are
> not persistent. Maybe JPOX will cope ?
>
>
>
>
> PS. Let's face it, the persistent-interface structure is an
> artificially
> constructed case that is no longer representative of the real
> world, and
> staring at it for several minutes causes madness to set in ...
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Embedding fields of non-persistent types even when field-type is used
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig, Michelle,
> The problem is that if you declare the PI* address property in
> PICompany as
> PIAddress getAddress()
> void setAddress(PIAddress)
>
> then it doesn't implement ICompany any more, since you also need
> these from the ICompany interface:
> IAddress getAddress()
> void setAddress(IAddress)
>
> And of course these are the methods that the e.g. FC classes
> implement by casting the input IAddress to FCAddress. Which is what
> we want the generated PICompanyImpl to do because we specify that the
> type of the field is PIAddress.
There are still places where there is no "types" (annotations) or "field-type"
(XML) specified on overridden interface fields. I'll start from the one
that "companyPMInterface.conf" complains about
PIInsurance has no <property field-type="..."> on field "employee".
PIDSInsurance has no @Persistent(types=) on field "employee".
Fix those and re-run, you then get the error on
PIEmployee "dentalInsurance", "medicalInsurance", "department", "fundingDept", ...
PIDSEmployee etc
When those are fixed there are likely some others.
Only when *all* of these are added can we address if JPOX can cope with that
structure or not. As it is currently there are persistent properties that are
not persistent. Maybe JPOX will cope ?
PS. Let's face it, the persistent-interface structure is an artificially
constructed case that is no longer representative of the real world, and
staring at it for several minutes causes madness to set in ...
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Embedding fields of non-persistent types even when field-type is
used
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Michelle,
The problem is that if you declare the PI* address property in
PICompany as
PIAddress getAddress()
void setAddress(PIAddress)
then it doesn't implement ICompany any more, since you also need
these from the ICompany interface:
IAddress getAddress()
void setAddress(IAddress)
And of course these are the methods that the e.g. FC classes
implement by casting the input IAddress to FCAddress. Which is what
we want the generated PICompanyImpl to do because we specify that the
type of the field is PIAddress.
Craig
On Jul 27, 2007, at 3:45 PM, Michelle Caisse wrote:
> I think that this is just an issue with the declarations in the
> classes. In the PI classes, the address fields were declared as I*,
> whereas I think we really wanted them to be PI*. With this change,
> the address fields are instances of persistent interfaces, and
> there should be no problem
>
> -- Michelle
>
> Craig L Russell wrote:
>
>>
>> On Jul 27, 2007, at 10:03 AM, Michelle Caisse wrote:
>>
>>> JPOX doesn't support embedding fields of non-persistent types
>>> even when the field-type attribute is used to specify the
>>> specific type. The TCK now uses inheritance from non-persistent
>>> interfaces, which allowed us to simplify the coding of new pc
>>> classes, but doesn't work with the embedded Address field.
>>
>>
>> This is an issue. Is JPOX able to fix this? The alternatives are
>> not pretty, since we use both persistent classes and persistent
>> interfaces in the model. The setAddress(IAddress) methods need to
>> be implementable by both the persistence provider and the tck code.
>>
>> Any ideas?
>>
>> Craig
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Embedding fields of non-persistent types even when field-type is
used
Posted by Michelle Caisse <Mi...@Sun.COM>.
I think that this is just an issue with the declarations in the classes.
In the PI classes, the address fields were declared as I*, whereas I
think we really wanted them to be PI*. With this change, the address
fields are instances of persistent interfaces, and there should be no
problem
-- Michelle
Craig L Russell wrote:
>
> On Jul 27, 2007, at 10:03 AM, Michelle Caisse wrote:
>
>> JPOX doesn't support embedding fields of non-persistent types even
>> when the field-type attribute is used to specify the specific type.
>> The TCK now uses inheritance from non-persistent interfaces, which
>> allowed us to simplify the coding of new pc classes, but doesn't
>> work with the embedded Address field.
>
>
> This is an issue. Is JPOX able to fix this? The alternatives are not
> pretty, since we use both persistent classes and persistent
> interfaces in the model. The setAddress(IAddress) methods need to be
> implementable by both the persistence provider and the tck code.
>
> Any ideas?
>
> Craig
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Embedding fields of non-persistent types even when field-type is used
Posted by Craig L Russell <Cr...@Sun.COM>.
On Jul 27, 2007, at 10:03 AM, Michelle Caisse wrote:
> JPOX doesn't support embedding fields of non-persistent types even
> when the field-type attribute is used to specify the specific type.
> The TCK now uses inheritance from non-persistent interfaces, which
> allowed us to simplify the coding of new pc classes, but doesn't
> work with the embedded Address field.
This is an issue. Is JPOX able to fix this? The alternatives are not
pretty, since we use both persistent classes and persistent
interfaces in the model. The setAddress(IAddress) methods need to be
implementable by both the persistence provider and the tck code.
Any ideas?
Craig
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 27, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Matthew Adams, Michael Bouschen, Michelle Caisse, Martin Zaun
Annotations news:
[From Craig, by email]: The tck with annotations isn't working yet,
although it does get past the enhancement step. There are issues with
relationships and embedded null values.
The annotation element boundTypes has been changed to types for all
annotations with this element.
Michelle will take a look Andy's issue of field-type used in the tck
for concrete classes. This is not necessary.
JPOX doesn't support embedding fields of non-persistent types even when
the field-type attribute is used to specify the specific type. The TCK
now uses inheritance from non-persistent interfaces, which allowed us to
simplify the coding of new pc classes, but doesn't work with the
embedded Address field.
Other issues:
Matthewstill has on his plate to write additional tests for persistence
unit name, named pmf stuff.
Question from Matthew regarding the meaning of the Multithreaded flag.
It is a hint to the implementation that the pm may be used by multiple
threads.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 10, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Chris Beams, Matthew Adams, Michelle Caisse, Craig Russell
Agenda:
1. Changes to build script. SNAPSHOT vs. 2.1-SNAPSHOT
2. Annotations: discuss custom settings for enum-valued elements. We
need better javadoc for UNKNOWN, and in fact we might change UNKNOWN
to UNSPECIFIED so it's more clear from the name itself. AI Matthew
raise this issue on the alias. It also seems like adding a new value
of CUSTOM is unnecessary because if the user specifies a custom
value, the annotation processor just uses it, and verifies that the
standard strategy enum value is UNSPECIFIED.
3. Attach (makePersistent) a detached instance always merges changes
into the cache. Can this behavior be changed to make the parameter
instance change its state, throwing an exception if there already is
an instance in the cache, based on a user-specified property? Seems
like this would be a good addition to the spec. AI Chris prepare a
proposal for the jdo expert group alias.
4. Other issues
Matthew points out that the spec doesn't call out the behavior if
there is no version strategy specified.
Matthew put together some "standard interfaces" for the enhancer and
schema manager.
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Aug 31, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Draft proposal for CopyOnAttach property
Waiting on the proposal from Chris. We could discuss on the aliases
once Chris has a starting point. Need to consider two cases: new PM
and existing PM. Should focus on use cases for the web server.
2. Update on managed relationship classes. Test cases are mostly
written and almost ready for posting to the JIRA for review. JPOX
currently fails on the pre-condition when executing contains(Object)
as the first method, as the collection doesn't appear to have been
"hydrated" from the database.
3. Other issues
What's the status of the specification: We're tracking this on http://
wiki.apache.org/jdo/CurrentDevelopment
Major items still to do include the addition of new interfaces to
extend JPA and JDO; update of the BNF for subqueries; serialization
of PersistenceManager; and serialization state transitions.
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Sep 7, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Restriction on <unique> subelements. Erik comments that there is a
valid use case for mixing property, field, and columns in unique
elements. No dissent. AI Craig update specification. The spec should
be clarified to specify that the uniqueness applies to the
combination of mapped columns.
2. Negative test in
org.apache.jdo.tck.query.result.ResultClassRequirements (JDO-524).
Seems like this test is incorrect. AI Michael fix the test.
3. Spec status update Still a few more changes to write up for the
spec. Tracking in ChangeLog and CurrentDevelopment. Query BNF should
be added to the CurrentDevelopment wiki page. AI Michael Bouschen add
it.
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
RE: JDO TCK Conference Call Friday, Sep 7, 9 am PDT
Posted by "Matthew T. Adams" <ma...@matthewadams.org>.
Sorry, but I can't attend today's meeting. Conference call scheduled at the
same time.
-----Original Message-----
From: Michelle.Caisse@Sun.COM [mailto:Michelle.Caisse@Sun.COM]
Sent: Thursday, September 06, 2007 8:26 PM
To: jdo-dev@db.apache.org
Cc: jdo-experts-ext@Sun.COM
Subject: JDO TCK Conference Call Friday, Sep 7, 9 am PDT
Hi,
We will have our regular meeting Friday, September 7 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Restriction on <unique> subelements
2. Negative test in
org.apache.jdo.tck.query.result.ResultClassRequirements (JDO-524)
3. Spec status update
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by cbeams <cb...@gmail.com>.
Yes, I'm in the same training, and thus won't be on the call.
Regarding final field support - thanks for putting it on the agenda.
Feel free to discuss or defer to next week. I'm excited about this
functionality, hopefully it's an option!
- Chris
On Sep 27, 2007, at 4:03 PM, Matthew T. Adams wrote:
> Sorry, giving a training session tomorrow and can't make it!
>
> -----Original Message-----
> From: Michelle.Caisse@Sun.COM [mailto:Michelle.Caisse@Sun.COM]
> Sent: Thursday, September 27, 2007 2:20 PM
> To: jdo-dev@db.apache.org
> Cc: jdo-experts-ext@Sun.COM
> Subject: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
>
> Hi,
>
> We will have our regular meeting Friday, September 28 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Support for final modifier on fields
> 2. Test challenges
> 3. Other issues
>
> Action Items from weeks past:
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> and
> attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of
> JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
RE: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by "Matthew T. Adams" <ma...@matthewadams.org>.
Sorry, giving a training session tomorrow and can't make it!
-----Original Message-----
From: Michelle.Caisse@Sun.COM [mailto:Michelle.Caisse@Sun.COM]
Sent: Thursday, September 27, 2007 2:20 PM
To: jdo-dev@db.apache.org
Cc: jdo-experts-ext@Sun.COM
Subject: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Hi,
We will have our regular meeting Friday, September 28 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Support for final modifier on fields
2. Test challenges
3. Other issues
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 19 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. 2.1 spec and TCK status: The latest specification draft has been
published on the Apache JDO web site. http://db.apache.org/jdo/
releases/jdo_2.1_2007-10-17.pdf
Remaining items for the specification include serialization of
persistence managers, life cycle state changes for serialization,
relationship management for delete, bootstrapping protocols, BNF for
subqueries, and override rules for metadata.
The query API needs more discussion. It's possible to pass an Object
[ ] as an argument by explicitly wrapping it in a new Object[ ], e.g.
executeWithArray(new Object[ ] {arrayParameter}); AI Craig discuss on
expert group.
TCK test status: new tests for JPA annotations and it's almost
working. Still one more bug with Map.
Enum test is failing. Might be JPOX doesn't implement enum support yet.
Subquery tests have not been written.
2. Other issues
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests. https://
issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Enum handling
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Erik,
This example should fit in with what Matthew is doing for more
flexible mapping of enums to fixed precision types.
Craig
On Nov 3, 2007, at 3:34 AM, Erik Bengtson wrote:
> Another use case of enum persistence, is the persistence of arbitrary
> values.
>
> public enum Test {
> RED(1), BLUE(5);
>
> private final int value;
>
> Test(int v)
> {
> this.value = v;
> }
>
> public final int getValue()
> {
> return this.value;
> }
>
> public final static Enum getEnum(int i)
> {
> switch(i)
> {
> case 1: return Test.RED;
> case 5: return Test.BLUE;
> }
> return null;
> }
> }
>
>
> Refer to:
> http://www.jpox.org/servlet/jira/browse/JAVAFIVEPLUGIN-51
>
>
> -----Message d'origine-----
> De : Andy Jefferson [mailto:andy@jpox.org]
> Envoyé : samedi 3 novembre 2007 9:33
> À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
> Objet : Re: Enum handling
>
> Hi Craig, Michelle,
>
>> Makes sense to me, but the spec lead thinks the implementation should
>> check the actual type in the database.
>
> Well while I understand what our spec lead says I also point out :-
>
> 1. All TCK tests so far use the table in 18.4 in the spec to define
> the
> default jdbc-type and that is used by the implementation so they
> have no
> need
> to go to the datastore to validate the tables and hence define how
> they will
>
> be mapped. There presumably will be an entry for java.lang.Enum
> added that
> has VARCHAR as the default jdbc-type.
>
> 2. The only place where the section 18.4 default mappings are not
> used (e.g
> FieldsOfCharacter), the TCK "orm" files add jdbc-type, and so don't
> impose
> on
> the implementation the overhead of having to go to the datastore to
> get this
>
> information there either.
>
> 3. The spec lead has more faith than me in JDBC drivers ;-), and
> some (e.g
> Oracle) are notoriously slow for obtaining basic schema
> information ... and
> then we could refer to a JIRA I raised on Derby a year ago
> http://issues.apache.org/jira/browse/DERBY-1996
> For this reason, and for reasons of portability (not relying on the
> schema
> being identical, but instead imposing the requirements in the mapping
> information) JPOX has always relied on jdbc-type, whilst still
> providing a
> means of validating this mapping definition against the underlying
> datastore
>
> (if the user wishes to do so). Does the spec prohibit this mode of
> operation?
>
> 4. The schema for the FieldsOfEnum has two types of columns ...
> VARCHAR(256)
>
> and CHAR(2). Even if JPOX went to the datastore and found CHAR(2),
> that
> would
> still imply a String based persistence (to me). INTEGER would suggest
> something else.
>
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
RE: Enum handling
Posted by Erik Bengtson <er...@jpox.org>.
Another use case of enum persistence, is the persistence of arbitrary
values.
public enum Test {
RED(1), BLUE(5);
private final int value;
Test(int v)
{
this.value = v;
}
public final int getValue()
{
return this.value;
}
public final static Enum getEnum(int i)
{
switch(i)
{
case 1: return Test.RED;
case 5: return Test.BLUE;
}
return null;
}
}
Refer to:
http://www.jpox.org/servlet/jira/browse/JAVAFIVEPLUGIN-51
-----Message d'origine-----
De : Andy Jefferson [mailto:andy@jpox.org]
Envoyé : samedi 3 novembre 2007 9:33
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : Re: Enum handling
Hi Craig, Michelle,
> Makes sense to me, but the spec lead thinks the implementation should
> check the actual type in the database.
Well while I understand what our spec lead says I also point out :-
1. All TCK tests so far use the table in 18.4 in the spec to define the
default jdbc-type and that is used by the implementation so they have no
need
to go to the datastore to validate the tables and hence define how they will
be mapped. There presumably will be an entry for java.lang.Enum added that
has VARCHAR as the default jdbc-type.
2. The only place where the section 18.4 default mappings are not used (e.g
FieldsOfCharacter), the TCK "orm" files add jdbc-type, and so don't impose
on
the implementation the overhead of having to go to the datastore to get this
information there either.
3. The spec lead has more faith than me in JDBC drivers ;-), and some (e.g
Oracle) are notoriously slow for obtaining basic schema information ... and
then we could refer to a JIRA I raised on Derby a year ago
http://issues.apache.org/jira/browse/DERBY-1996
For this reason, and for reasons of portability (not relying on the schema
being identical, but instead imposing the requirements in the mapping
information) JPOX has always relied on jdbc-type, whilst still providing a
means of validating this mapping definition against the underlying datastore
(if the user wishes to do so). Does the spec prohibit this mode of
operation?
4. The schema for the FieldsOfEnum has two types of columns ... VARCHAR(256)
and CHAR(2). Even if JPOX went to the datastore and found CHAR(2), that
would
still imply a String based persistence (to me). INTEGER would suggest
something else.
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Enum handling
Posted by Craig L Russell <Cr...@Sun.COM>.
On Nov 3, 2007, at 1:33 AM, Andy Jefferson wrote:
> Hi Craig, Michelle,
>
>> Makes sense to me, but the spec lead thinks the implementation should
>> check the actual type in the database.
>
> Well while I understand what our spec lead says I also point out :-
>
> 1. All TCK tests so far use the table in 18.4 in the spec to define
> the
> default jdbc-type and that is used by the implementation so they
> have no need
> to go to the datastore to validate the tables and hence define how
> they will
> be mapped. There presumably will be an entry for java.lang.Enum
> added that
> has VARCHAR as the default jdbc-type.
Good idea. I'll make this change.
>
> 2. The only place where the section 18.4 default mappings are not
> used (e.g
> FieldsOfCharacter), the TCK "orm" files add jdbc-type, and so don't
> impose on
> the implementation the overhead of having to go to the datastore to
> get this
> information there either.
>
> 3. The spec lead has more faith than me in JDBC drivers ;-), and
> some (e.g
> Oracle) are notoriously slow for obtaining basic schema
> information ... and
> then we could refer to a JIRA I raised on Derby a year ago
> http://issues.apache.org/jira/browse/DERBY-1996
> For this reason, and for reasons of portability (not relying on the
> schema
> being identical, but instead imposing the requirements in the mapping
> information) JPOX has always relied on jdbc-type, whilst still
> providing a
> means of validating this mapping definition against the underlying
> datastore
> (if the user wishes to do so). Does the spec prohibit this mode of
> operation?
No, and for portability, I think we need some way to specify the
default so schema generation is possible, and additionally provide
for the user to explicitly tell the implementation what type to
expect from the database.
>
> 4. The schema for the FieldsOfEnum has two types of columns ...
> VARCHAR(256)
> and CHAR(2). Even if JPOX went to the datastore and found CHAR(2),
> that would
> still imply a String based persistence (to me). INTEGER would suggest
> something else.
Yes, and that's what we thought. But I'm persuaded by your arguments
and will make the spec changes. Here's a preview:
<proposed> 15.1
Mapping enums
Mapping an enum to a fixed-precision numeric type uses the ordinal()
value for storage; mapping to a character column type (CHAR, VARCHAR,
etc.) uses the name() value for storage; mapping to any other column
type is not portable.
The default jdbc-type for columns mapped to enums is VARCHAR. This
provides maximum flexibility as the enum evolves, as it uses the name
of the enum for storage. As more enum values are added, the name does
not change, whereas the ordinal value will change if enum values are
added anywhere except at the end.
For portability, if the mapping should use the ordinal value for
storage, then the jdbc-type must be specified in the column metadata
as a fixed precision numeric type. An implementation might support
floating point types for storage, and might auto-detect the column
type but this behavior is not portable.
</proposed>
The tck will need to update the orm files for the enum fields to
specify the jdbc-type for the numeric columns.
Craig
>
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Enum handling
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig, Michelle,
> Makes sense to me, but the spec lead thinks the implementation should
> check the actual type in the database.
Well while I understand what our spec lead says I also point out :-
1. All TCK tests so far use the table in 18.4 in the spec to define the
default jdbc-type and that is used by the implementation so they have no need
to go to the datastore to validate the tables and hence define how they will
be mapped. There presumably will be an entry for java.lang.Enum added that
has VARCHAR as the default jdbc-type.
2. The only place where the section 18.4 default mappings are not used (e.g
FieldsOfCharacter), the TCK "orm" files add jdbc-type, and so don't impose on
the implementation the overhead of having to go to the datastore to get this
information there either.
3. The spec lead has more faith than me in JDBC drivers ;-), and some (e.g
Oracle) are notoriously slow for obtaining basic schema information ... and
then we could refer to a JIRA I raised on Derby a year ago
http://issues.apache.org/jira/browse/DERBY-1996
For this reason, and for reasons of portability (not relying on the schema
being identical, but instead imposing the requirements in the mapping
information) JPOX has always relied on jdbc-type, whilst still providing a
means of validating this mapping definition against the underlying datastore
(if the user wishes to do so). Does the spec prohibit this mode of operation?
4. The schema for the FieldsOfEnum has two types of columns ... VARCHAR(256)
and CHAR(2). Even if JPOX went to the datastore and found CHAR(2), that would
still imply a String based persistence (to me). INTEGER would suggest
something else.
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Craig L Russell <Cr...@Sun.COM>.
Here's the working copy of the spec updates:
<spec update>
6.4.3
Enums
JDO implementations that support Java 5 must support fields of enum
types and collections of as enum types identified above and
optionally arrays of enum types. If arrays are supported, arrays of
enums must be supported.
Portable JDO applications must not depend on whether these fields are
treated as SCOs or FCOs.
6.4.5
Complex enum types
Complex enum types are enums that contain fields that might change
during execution instead of being initialized during class
initialization. While it is possible to manage these singleton
instances persistent state, there are issues with the transaction
isolation of the instances and with the ownership of the instances by
a persistence manager. Therefore, dynamically changing fields of enum
types are not persistent.
15.1
Mapping enums
Mapping an enum to a fixed-precision numeric type uses the ordinal()
value for storage; mapping to a character column type (CHAR, VARCHAR,
etc.) uses the name() value for storage; mapping to any other column
type is an error.
</spec update>
The idea I had was that the jdo implementation would be aware of the
column type being mapped to, but if this is not practical we'll need
to come up with something else...
Craig
On Nov 2, 2007, at 1:04 PM, Michelle Caisse wrote:
> Andy Jefferson wrote:
>
>>> test(org.apache.jdo.tck.models.fieldtypes.TestFieldsOfSimpleEnum)
>>> javax.jdo.
>>> JDODataStoreException: Cannot set String parameter: value = AL
>>> for column
>>> "applicationidentity1.FIELDSOFENUMORDINAL.ENUM94" : Invalid
>>> character
>>> string format for type INTEGER.
>>>
>>> I know this is supposed to work, so maybe you can tell us what's
>>> going
>>> wrong.
>>>
>>
>> Hi Michelle,
>>
>> How are you expecting jPOX to know you want to persist as an
>> numeric rather than String ? JPOX support is based on how we
>> thought it should be implemented (since not defined in the JDO
>> spec explicitly). We rely on "jdbc-type" currently, with default
>> being String-based.
>>
>>
>>
> Makes sense to me, but the spec lead thinks the implementation
> should check the actual type in the database.
>
> -- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Michelle Caisse <Mi...@Sun.COM>.
Andy Jefferson wrote:
>>test(org.apache.jdo.tck.models.fieldtypes.TestFieldsOfSimpleEnum)javax.jdo.
>>JDODataStoreException: Cannot set String parameter: value = AL for column
>>"applicationidentity1.FIELDSOFENUMORDINAL.ENUM94" : Invalid character
>>string format for type INTEGER.
>>
>>I know this is supposed to work, so maybe you can tell us what's going
>>wrong.
>>
>>
>
>Hi Michelle,
>
>How are you expecting jPOX to know you want to persist as an numeric rather
>than String ? JPOX support is based on how we thought it should be
>implemented (since not defined in the JDO spec explicitly). We rely
>on "jdbc-type" currently, with default being String-based.
>
>
>
>
Makes sense to me, but the spec lead thinks the implementation should
check the actual type in the database.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Andy Jefferson <an...@jpox.org>.
> test(org.apache.jdo.tck.models.fieldtypes.TestFieldsOfSimpleEnum)javax.jdo.
>JDODataStoreException: Cannot set String parameter: value = AL for column
> "applicationidentity1.FIELDSOFENUMORDINAL.ENUM94" : Invalid character
> string format for type INTEGER.
>
> I know this is supposed to work, so maybe you can tell us what's going
> wrong.
Hi Michelle,
How are you expecting jPOX to know you want to persist as an numeric rather
than String ? JPOX support is based on how we thought it should be
implemented (since not defined in the JDO spec explicitly). We rely
on "jdbc-type" currently, with default being String-based.
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Nov 2, 2007, at 12:19 PM, Andy Jefferson wrote:
>> 1. Enum tests: Michelle is just about ready to check in. Running last
>> tests. In JPOX, enums are not persistent by default and seem to have
>> trouble with numeric types. AI Michelle check in tests; AI Craig
>> update spec to mandate enums as singleton, immutable objects and
>> allow other enum support;
>
> So are enum fields going to be default "persistent" now ?
I think it makes sense. Just like other immutable object types like
Integer.
I'm open to having them default non-persistent but seems better to
have them default persistent.
> Await to see what tests we are talking about here ... persistence?,
> retrieval?, JDOQL?, something else, because we obviously have some
> of our own
> and test the majority of things.
For starters, just store/retrieve enum values. Take a look at the
tests that Michelle checked in and see if they're ok.
> The only known issue is for JDOQL
> expressions comparing an enum field with the enum value (when it was
> persisted as a numeric). Comparing with the enum ordinal works fine
> in that
> situation.
We haven't discussed adding JDOQL tests. Maybe you could suggest
some, or contribute some.
>
>> Email discussion: Proposed method to ask the persistence manager for
>> managed instances might have a signature Object[ ]
>> getManagedInstances
>> (ObjectState[ ], Class... classes) which filters instances based on
>> their state and class. This could be part of 2.1 or deferred to 2.2.
>> Is this something that JPOX wants to see sooner?
>
> JPOX already has
> Collection PM.getManagedObjects()
> and could have any of the mentioned combinations pretty fast ;-)
Cool. If you could comment further on the specific API we might get
consensus pretty fast. A couple of things we need to discuss: the
return type of Object[ ] vs. Collection; argument type for
ObjectState and Class of Collection<ObjectState> vs ObjectState[ ];
order of parameters if we use ObjectState[ ] because only one can be
varargs.
Craig
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Michelle Caisse <Mi...@Sun.COM>.
Andy Jefferson wrote:
>>1. Enum tests: Michelle is just about ready to check in. Running last
>>tests. In JPOX, enums are not persistent by default and seem to have
>>trouble with numeric types. AI Michelle check in tests; AI Craig
>>update spec to mandate enums as singleton, immutable objects and
>>allow other enum support;
>>
>>
>
>So are enum fields going to be default "persistent" now ?
>Await to see what tests we are talking about here ... persistence?,
>retrieval?, JDOQL?, something else, because we obviously have some of our own
>and test the majority of things. The only known issue is for JDOQL
>expressions comparing an enum field with the enum value (when it was
>persisted as a numeric). Comparing with the enum ordinal works fine in that
>situation.
>
>
Tests were just checked in. Try, for example, models1.conf, where we get:
test(org.apache.jdo.tck.models.fieldtypes.TestFieldsOfSimpleEnum)javax.jdo.JDODataStoreException:
Cannot set String parameter: value = AL for column
"applicationidentity1.FIELDSOFENUMORDINAL.ENUM94" : Invalid character
string format for type INTEGER.
I know this is supposed to work, so maybe you can tell us what's going
wrong.
Other issues: enums not persistent by default in jpox, as you know, and
arrays of enums not supported.
-- Michelle
>
>
>>Email discussion: Proposed method to ask the persistence manager for
>>managed instances might have a signature Object[ ] getManagedInstances
>>(ObjectState[ ], Class... classes) which filters instances based on
>>their state and class. This could be part of 2.1 or deferred to 2.2.
>>Is this something that JPOX wants to see sooner?
>>
>>
>
>JPOX already has
>Collection PM.getManagedObjects()
>and could have any of the mentioned combinations pretty fast ;-)
>
>
>
Re: Minutes: JDO TCK Conference Call Friday, Nov 2
Posted by Andy Jefferson <an...@jpox.org>.
> 1. Enum tests: Michelle is just about ready to check in. Running last
> tests. In JPOX, enums are not persistent by default and seem to have
> trouble with numeric types. AI Michelle check in tests; AI Craig
> update spec to mandate enums as singleton, immutable objects and
> allow other enum support;
So are enum fields going to be default "persistent" now ?
Await to see what tests we are talking about here ... persistence?,
retrieval?, JDOQL?, something else, because we obviously have some of our own
and test the majority of things. The only known issue is for JDOQL
expressions comparing an enum field with the enum value (when it was
persisted as a numeric). Comparing with the enum ordinal works fine in that
situation.
> Email discussion: Proposed method to ask the persistence manager for
> managed instances might have a signature Object[ ] getManagedInstances
> (ObjectState[ ], Class... classes) which filters instances based on
> their state and class. This could be part of 2.1 or deferred to 2.2.
> Is this something that JPOX wants to see sooner?
JPOX already has
Collection PM.getManagedObjects()
and could have any of the mentioned combinations pretty fast ;-)
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: JDO TCK Conference Call Friday, Oct 26 , 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.org>.
Won't be able to join again, giving a training in LA...
On Oct 25, 2007, at 4:41 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, October 26 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Subquery spec update
> 2. Other issues
>
> Action Items from weeks past:
>
> [Oct 12 2007] AI Michael take a look at subquery tck tests. https://
> issues.apache.org/jira/browse/JDO-446
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides
> for the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> and attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of
> the listener is the class name of the listener, for consistency
> with proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a
> string constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink
> support for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of
> JDK 1.5 issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles
> on TheServerSide directing attention to the site. T-shirts,
> logo. AI: Craig write a ServerSide article.
>
> -- Michelle
>
>>
Minutes: JDO TCK Conference Call Friday, Oct 26 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Erik Bengtson, Michelle Caisse, Michael Bouschen, Craig
Russell
Please note: Daylight Savings begins in many places next week. Not in
the US whence the conference call originates. If you are affected,
you now know about it.
Agenda:
1. Subquery spec update. The email sent around has a typo in it. The
proposal should have three new methods, identically named, with three
overloaded variants, for both api2 and api2-legacy; the only
difference being that in api2, the String[] is replaced by String...
Michael will update the patch to include the spec code and new test
case. It looks like the QueryElementHolder would take too many
changes to be updated easily, so the new test case will be hand-
crafted instead of using QueryElementHolder.
2. Other issues
Build error building api2 and api2-legacy with different date
formatter. This issue https://issues.apache.org/jira/browse/JDO-547
is open pending information on the behavior of DateFormat.getInstance().
Erik has proposed two new features for consideration for the 2.1
specification. AI everyone please review and comment.
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests. https://
issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov 2 , 9 am PDT [NOTE: U.S. is still on daylight time]
Posted by Matthew Adams <ma...@matthewadams.org>.
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
Here are said examples. Please review; Craig, if ok, please
incorporate into 2.1 spec.
Sample configuration using standard Java Properties file
"hr.properties" to configure a PMF with one listener for all classes:
================ in file hr.properties
# JDO provider's implementation class
javax.jdo.PersistenceManagerFactoryClass=com.acme.jdo.AcmePmf
# Persistent class instance lifecycle listener
com.example.listener.RoleListener
# configured to listen on lifecycle events for all domain classes
javax.jdo.option.InstanceLifecycleListener.com.example.listener.DomainLi
stener
# remainder of JDO properties...
================
Sample configuration using standard Java Properties file
"hr.properties" with various listeners:
================ in file hr.properties
# JDO provider's implementation class
javax.jdo.PersistenceManagerFactoryClass=com.acme.jdo.AcmePmf
# Persistent class instance lifecycle listener
com.example.listener.RoleListener
# configured to listen on lifecycle events for domain classes User,
Employee, and Manager
javax.jdo.option.InstanceLifecycleListener.com.example.listener.RoleList
ener=com.example.domain.User,com.example.domain.Employee,com.example.dom
ain.Manager
# Persistent class instance lifecycle listener
com.example.listener.ActorListener
# configured to listen on lifecycle events for domain classes Person
& Corporation
javax.jdo.option.InstanceLifeycleListener.com.example.listener.ActorList
ener=com.example.domain.Person,com.example.domain.Corporation
# remainder of JDO properties...
================
Sample META-INF/jdoconfig.xml specifying a PMF named "hr" with one
listener for all classes:
================ in file META-INF/jdoconfig.xml
<jdoconfig
xmlns="http://java.sun.com/xml/ns/jdo/jdoconfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...>
<persistence-manager-factory name="hr"
class="com.acme.jdo.AcmePmf" ...>
<instance-lifecycle-listener
listener="com.example.domain.DomainListener"/>
</persistence-manager-factory>
</jdoconfig>
================
Sample META-INF/jdoconfig.xml specifying a PMF named "hr" with
various listeners:
================ in file META-INF/jdoconfig.xml
<jdoconfig
xmlns="http://java.sun.com/xml/ns/jdo/jdoconfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...>
<persistence-manager-factory name="hr"
class="com.acme.jdo.AcmePmf" ...>
<instance-lifecycle-listener
listener="com.example.domain.RoleListener"
classes="
com.example.domain.User,
com.example.domain.Employee,
com.example.domain.Manager"
/>
<instance-lifecycle-listener
listener="com.example.domain.ActorListener"
classes="
com.example.domain.Person,
com.example.domain.Corporation"
/>
</persistence-manager-factory>
</jdoconfig>
================
Sample META-INF/jdoconfig.xml & META-INF/services/
javax.jdo.PersistenceManagerFactory specifying a PMF named "hr" with
various listeners:
================ in file META-INF/jdoconfig.xml
<jdoconfig
xmlns="http://java.sun.com/xml/ns/jdo/jdoconfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...>
<persistence-manager-factory name="hr" ...>
<instance-lifecycle-listener
listener="com.example.domain.RoleListener"
classes="
com.example.domain.User,
com.example.domain.Employee,
com.example.domain.Manager"
/>
<instance-lifecycle-listener
listener="com.example.domain.ActorListener"
classes="
com.example.domain.Person,
com.example.domain.Corporation"
/>
</persistence-manager-factory>
</jdoconfig>
================ in file META-INF/services/
javax.jdo.PersistenceManagerFactory
com.acme.jdo.AcmePmf
================
Minutes: JDO TCK Conference Call Friday, Nov 2 ,
9 am PDT [NOTE: U.S. is still on daylight time]
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Enum tests: Michelle is just about ready to check in. Running last
tests. In JPOX, enums are not persistent by default and seem to have
trouble with numeric types. AI Michelle check in tests; AI Craig
update spec to mandate enums as singleton, immutable objects and
allow other enum support; AI Matthew propose a mapping of enum
ordinal to database representation in metadata (this would make it
easier to support legacy databases).
2. JDOHelper bootstrap issues: Matthew send around examples of
bootstrapping. AI Craig update the spec. AI Craig continue discussion
of configuration with serialization in mind. The issue is how to
distinguish properties that are requested by the user versus
properties that came out of a config file (either a .properties, a
jdoconfig.xml, or persistence.xml) that might be different in the
other vm where the persistence manager is being deserialized. This
might affect the contract between JDOHelper and implementation
PersistenceManagerFactory.
3. Serialization of PersistenceManager: The biggest issue is how to
handle listeners. Other issue is how to handle classes that are not
serializable. AI Craig write a proposal.
4. Other issues
JDOHelper has no compile time or runtime dependency on
Persistence.class. This is a good thing. The general principle is
that users should not require JPA in their environment if they are
not using the JPA alignment features.
Subqueries: Should we add one more overloaded method addSubquery
(Query outer, String resultExpression)? Probably not because we would
need four more methods. AI Craig update JIRA. AI Michael check in the
patch. This might cause JPOX to fail and all TCK tests to fail.
Email discussion: Proposed method to ask the persistence manager for
managed instances might have a signature Object[ ] getManagedInstances
(ObjectState[ ], Class... classes) which filters instances based on
their state and class. This could be part of 2.1 or deferred to 2.2.
Is this something that JPOX wants to see sooner?
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests. https://
issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
Done. Please review.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov 9 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig
Russell
Note: due to a conflict with ApacheCon, next week's meeting might not
have a quorum. If anyone has agenda items please send them to the
list. If no agenda items have been submitted, the meeting will be
canceled. And the following week is Thanksgiving week; the conference
call is canceled for the day after Thanksgiving.
Agenda:
1. Discuss EnumSet support: AI all read up on EnumSet and express
your opinion as to whether JDO should require support for fields of
EnumSet.
2. JDOHelper methods for PersistenceManagerFactory: Several new
JDOHelper methods are added; some methods delegate to new method
JDOHelper.getPersistenceManagerFactory (Map overrides, String name,
ClassLoader propsLoader, ClassLoader pmfLoader). AI Matthew update
the jira https://issues.apache.org/jira/browse/JDO-545
3. Serialization of PersistenceManager and PersistenceManagerFactory:
In order to materialize a PersistenceManagerFactory in another vm,
the implementation needs to know which properties were specified by
the user directly and which were obtained by the resource. The
proposal is to add a new property javax.jdo.option.ResourceName that
will be added to the map of properties passed to the implementation.
There is a new static method in PersistenceManagerFactory
getPersistenceManagerFactory (Map overrides, Map properties,
ClassLoader pmfLoader) that allows the implementation to distinguish
between properties obtained from looking up a resource (properties)
and properties specified directly by the user (overrides). AI Craig
write up the formal proposal for the expert group.
4. Other issues
https://issues.apache.org/jira/browse/JDO-467 added some protected
fields that appear not to be used. AI Michael see if these fields can
be removed.
Action Items from weeks past:
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml...
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Nov 30 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Serializing PersistenceManager. Changes to
PersistenceManagerFactory have been checked in. Tests are needed for
an implementation to verify that the jdoconfig.xml properties work.
AI Matthew open new JIRAs for new test cases for jdoconfig.xml and
getPersistenceManagerFactory(Map, Map) and serializing
PersistenceManager. Test cases should test using stub PMF class with
the static getPersistenceManagerFactory(Map, Map) method that the
newly defined properties are correctly set in the map parameter.
2. EnumSet support (yes or no?) No, unless someone comes up with a
strong argument to require support.
3. Subquery proposed text. Non-correlated subquery. Perhaps we should
add a description of non-correlated subqueries to the spec:
Non-correlated subqueries
If the subquery has no references to expressions in the outer query
the subquery is non-correlated.
AI Craig update the spec with some assertions. AI Michael implement
the test cases https://issues.apache.org/jira/browse/JDO-446
4. Update/copy by query. These requests are reasonable for discussion
post-JDO 2.1.
AI Kristiaan propose more details.
5. Other issues
Should we remove the ability of using
Persistence.createEntityManagerFactory with JDO 2.1 legacy? AI Craig
ask the experts via email. The issue is creating a test framework to
test this functionality in Java 5 with the api2-legacy jar files.
Action Items from weeks past:
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml.. .
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Dec 7 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Serializing PersistenceManager. AI Craig update the spec and send
around for review.
2. Other issues
Delete consistency. AI everyone review and comment.
Query subquery. Might need some more assertions. AI review the
subquery section.
Query update: Why is it called perform instead of update? Just to
reinforce the idea that you select a number of Java instances and
perform some block action on them. But there's nothing wrong with
calling it update. Question: should we put additional restrictions on
the perform block to map 1-1 with SQL? Perhaps not. In particular,
should it be permitted to use variables to update related instances?
Even if we restrict the operations to only the candidate class,
multiple SQL statements or subqueries might be needed for inheritance
and existential queries. AI Michael reply to email thread.
It looks like the last major issue is serialization of instances for
the life cycle tests. There are still several instances of
UNSPECIFIED in the tests, and these will be reviewed to see which
should be specified for 2.1. Also, CopyOnAttach flag is currently
true in all the tests. There also need to be tests for CopyOnAttach
false.
Action Items from weeks past:
[Nov 30 2007] AI Craig update the spec with some assertions for
subqueries. AI Michael implement the test cases https://
issues.apache.org/jira/browse/JDO-446
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml.. .
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Jan 4 , 9 am PST
Posted by Andy Jefferson <an...@jpox.org>.
> e. There seems to be a typo in Andy's comments posting the SQL. Some
> lines in the innermost WHERE clause are duplicated.
There's no typo. JPOX a week ago had dup'd clauses for the EXISTS join. I
fixed this a few days ago.
http://www.jpox.org/servlet/jira/browse/RDBMS-76
Has no impact on the query result (nor should it since just a dup of an
existing clause).
> Subquery testing: Michael has finished the test creation, and will
> check in the tests to the tck. AI Michael file a new JIRA if JPOX
> fails the tests.
There's no way JPOX can pass any subquery tests since it isn't implemented,
and there's already a JIRA.
http://www.jpox.org/servlet/jira/browse/CORE-3207
I assumed Erik would be doing this as part of his "query refactoring", but
guess he's been too busy with work so this is not resourced currently. Will
be got to when someone has time ... unless we have a willing volunteer ;-)
--
Andy (Java Persistent Objects - http://www.jpox.org)
Minutes: JDO TCK Conference Call Friday, Dec 21 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
NOTE: There will be no meeting next week, December 28, 2007 unless
someone has an agenda item and sends email. The next scheduled
meeting will be January 4, 2008. Happy New Year!
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Wrapping up 2.1 maintenance release.
Still need more test coverage of the new JDOHelper
getPersistenceManagerFactory. AI Craig look at adding some tests in
the tck using jdoconfig.xml.
Need signature tests for enum and annotation classes in api2. AI
Craig update SignatureVerifier and update the signature file.
Subqueries will need JPOX support pretty soon. TCK tests are in
progress.
The draft spec has been published. AI Everyone please review and
comment. Known issues: TOC needs work. Appendix D is missing. Index
pages don't show up in the drawer (bookmarks). Missing assertions in
JDOHelper.getPersistenceManagerFactory.
Since assertions are part of the official spec, but not published in
the public-consumed version, we should publish the spec with
assertions and make it a separate downloadable document from the site.
2. Inconsistency in pm.newInstance() (email from 12/18). Negative
vote had no feedback from the experts so the spec Chapter 18 will be
changed to disallow creating implementation classes where there are
extra methods not part of properties.
3. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Importing xsd and dtd files into the spec
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Michelle,
Thanks, we can look at this in detail tomorrow.
We also need to handle enum files. They also belong in the annotation
chapter...
Craig
On Jan 10, 2008, at 7:19 PM, Michelle Caisse wrote:
> A better version...
>
> -- Michelle
>
> Michelle Caisse wrote:
>
>> Attached is a shell script for extracting the lines to be included
>> in the spec from the annotations files.
>>
>> -- Michelle
>>
>> Craig L Russell wrote:
>>
>>> Hi Michelle,
>>>
>>> Sadly, there is one feature missing that would disallow this to
>>> be used for the annotations chapter. I couldn't find a way to
>>> skip over the boilerplate [1] at the top of each .java file. So
>>> if we used this technique for the annotations chapter, we would
>>> either have to write a script to remove the boilerplate or
>>> include the boilerplate in every file. And if we write a script
>>> we would need to keep the source files up to date if the java
>>> files ever changed.
>>>
>>> Do you know a way around this problem?
>>>
>>> This isn't an issue for the xsd and dtd files because the only
>>> boilerplate is the Apache license which is ok for this purpose.
>>>
>>> Craig
>>>
>>> [1] boilerplate for Column.java
>>> /*
>>> * Licensed to the Apache Software Foundation (ASF) under one or
>>> more
>>> * contributor license agreements. See the NOTICE file
>>> distributed with
>>> * this work for additional information regarding copyright
>>> ownership.
>>> * The ASF licenses this file to You under the Apache License,
>>> Version 2.0
>>> * (the "License"); you may not use this file except in
>>> compliance with
>>> * the License. You may obtain a copy of the License at
>>> *
>>> * http://www.apache.org/licenses/LICENSE-2.0
>>> *
>>> * Unless required by applicable law or agreed to in writing,
>>> software
>>> * distributed under the License is distributed on an "AS IS" BASIS,
>>> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
>>> or implied.
>>> * See the License for the specific language governing
>>> permissions and
>>> * limitations under the License.
>>> */
>>> package javax.jdo.annotations;
>>>
>>> import java.lang.annotation.ElementType;
>>> import java.lang.annotation.Retention;
>>> import java.lang.annotation.RetentionPolicy;
>>> import java.lang.annotation.Target;
>>>
>>> /**
>>> * Annotation for a column in the database.
>>> * Corresponds to the xml element "column".
>>> * * @version 2.1
>>> * @since 2.1
>>> */
>>>
>>> On Jan 4, 2008, at 4:32 PM, Michelle Caisse wrote:
>>>
>>>>
>>>>> 2. Updated spec: in progress. The jdoconfig.xml has been added
>>>>> to Appendix D. Should we also put jdo.xml, orm.xml, and
>>>>> jdoquery.xml to Appendix D? No, probably better to add the dtd
>>>>> version of jdoconfig to Appendix D.
>>>>>
>>>>> AI Michelle look at how to automatically include the xsd and
>>>>> dtd files into the spec.
>>>>>
>>>> From FrameMaker help:
>>>>
>>>>
>>>> Importing by reference
>>>>
>>>> -------------------------------------------------------------------
>>>> -----
>>>>
>>>> You can import by reference by using File > Import > File,
>>>> OLE
>>>> (Windows), Publish and Subscribe (Mac OS), or a graphic inset
>>>> editor (UNIX).
>>>>
>>>> When you double-click a graphic imported by reference you:
>>>>
>>>> * (Windows) Open the application
>>>> * (Mac OS) Open the Object Properties dialog
>>>>
>>>> Importing by reference keeps the imported text or graphics
>>>> linked to the source file. FrameMaker stores the pathname to
>>>> the source file in the document. Each time you open the
>>>> document, FrameMaker locates the file on the disk and
>>>> redisplays it. If the source file was revised, FrameMaker
>>>> updates the document with the latest version. Importing by
>>>> reference can reduce total file size because it lets you use
>>>> the same material in several places without storing the
>>>> contents of imported images or text in the FrameMaker
>>>> document.
>>>> Text imported by reference is called a text inset.
>>>>
>>>> For information on how the pathname is stored when
>>>> importing by
>>>> reference, see Using pathnames when importing by reference.
>>>>
>>>>
>>>> I did a quick test of importing jdo_2_0.xsd. I applied the code
>>>> paragraph style and it looked good with no changes. When you
>>>> import by reference, you cannot edit the text from within Frame.
>>>> When you select the imported text (clicking anywhere within the
>>>> import highlights the entire block), Edit/Text Inset Properties
>>>> brings up a dialog that displays information and offers various
>>>> actions.
>>>>
>>>> -- Michelle
>>>
>>>
>>>
>>> Craig Russell
>>>
>>> Architect, Sun Java Enterprise System http://java.sun.com/
>>> products/jdo
>>>
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>
> #!/bin/sh
> # Read .java files in source directory,
> # copying lines from the first line matching
> # the start pattern to the end of the file
> # to a file of the same name in the target directory
> USAGE="behead <source dir> <target dir>"
> if [ $# -ne 2 ]
> then
> echo $USAGE
> exit -1
> fi
>
> SRCDIR=$1
> TARGETDIR=$2
>
> STARTPATTERN="^@"
>
> for FILE in `ls $SRCDIR/*.java`
> do
> ROOT=`basename $FILE`
> OUTFILE=${TARGETDIR}/${ROOT}
> if [ `grep -c "public enum" $FILE` -gt 0 ]
> then
> echo Skipping ${FILE}, an enum
> else
> echo Copy lines from $FILE to $OUTFILE
> STARTINDEX=`grep --max-count=1 -n $STARTPATTERN $FILE | cut
> -d: -f1 `
> #echo $STARTINDEX
> ENDINDEX=`wc -l $FILE | cut -f1 -d" " `
> #echo $ENDINDEX
> NUMLINES=`expr $ENDINDEX - $STARTINDEX + 1`
> #echo $NUMLINES
> tail --lines ${NUMLINES} $FILE > ${OUTFILE}
> fi
> done
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Importing xsd and dtd files into the spec
Posted by Michelle Caisse <Mi...@Sun.COM>.
A better version...
-- Michelle
Michelle Caisse wrote:
> Attached is a shell script for extracting the lines to be included in
> the spec from the annotations files.
>
> -- Michelle
>
> Craig L Russell wrote:
>
>> Hi Michelle,
>>
>> Sadly, there is one feature missing that would disallow this to be
>> used for the annotations chapter. I couldn't find a way to skip over
>> the boilerplate [1] at the top of each .java file. So if we used this
>> technique for the annotations chapter, we would either have to write
>> a script to remove the boilerplate or include the boilerplate in
>> every file. And if we write a script we would need to keep the source
>> files up to date if the java files ever changed.
>>
>> Do you know a way around this problem?
>>
>> This isn't an issue for the xsd and dtd files because the only
>> boilerplate is the Apache license which is ok for this purpose.
>>
>> Craig
>>
>> [1] boilerplate for Column.java
>> /*
>> * Licensed to the Apache Software Foundation (ASF) under one or more
>> * contributor license agreements. See the NOTICE file distributed with
>> * this work for additional information regarding copyright ownership.
>> * The ASF licenses this file to You under the Apache License,
>> Version 2.0
>> * (the "License"); you may not use this file except in compliance with
>> * the License. You may obtain a copy of the License at
>> *
>> * http://www.apache.org/licenses/LICENSE-2.0
>> *
>> * Unless required by applicable law or agreed to in writing, software
>> * distributed under the License is distributed on an "AS IS" BASIS,
>> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> * See the License for the specific language governing permissions and
>> * limitations under the License.
>> */
>> package javax.jdo.annotations;
>>
>> import java.lang.annotation.ElementType;
>> import java.lang.annotation.Retention;
>> import java.lang.annotation.RetentionPolicy;
>> import java.lang.annotation.Target;
>>
>> /**
>> * Annotation for a column in the database.
>> * Corresponds to the xml element "column".
>> * * @version 2.1
>> * @since 2.1
>> */
>>
>> On Jan 4, 2008, at 4:32 PM, Michelle Caisse wrote:
>>
>>>
>>>> 2. Updated spec: in progress. The jdoconfig.xml has been added to
>>>> Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml
>>>> to Appendix D? No, probably better to add the dtd version of
>>>> jdoconfig to Appendix D.
>>>>
>>>> AI Michelle look at how to automatically include the xsd and dtd
>>>> files into the spec.
>>>>
>>> From FrameMaker help:
>>>
>>>
>>> Importing by reference
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> You can import by reference by using File > Import > File, OLE
>>> (Windows), Publish and Subscribe (Mac OS), or a graphic inset
>>> editor (UNIX).
>>>
>>> When you double-click a graphic imported by reference you:
>>>
>>> * (Windows) Open the application
>>> * (Mac OS) Open the Object Properties dialog
>>>
>>> Importing by reference keeps the imported text or graphics
>>> linked to the source file. FrameMaker stores the pathname to
>>> the source file in the document. Each time you open the
>>> document, FrameMaker locates the file on the disk and
>>> redisplays it. If the source file was revised, FrameMaker
>>> updates the document with the latest version. Importing by
>>> reference can reduce total file size because it lets you use
>>> the same material in several places without storing the
>>> contents of imported images or text in the FrameMaker document.
>>> Text imported by reference is called a text inset.
>>>
>>> For information on how the pathname is stored when importing by
>>> reference, see Using pathnames when importing by reference.
>>>
>>>
>>> I did a quick test of importing jdo_2_0.xsd. I applied the code
>>> paragraph style and it looked good with no changes. When you import
>>> by reference, you cannot edit the text from within Frame. When you
>>> select the imported text (clicking anywhere within the import
>>> highlights the entire block), Edit/Text Inset Properties brings up a
>>> dialog that displays information and offers various actions.
>>>
>>> -- Michelle
>>
>>
>>
>> Craig Russell
>>
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>
>> 408 276-5638 mailto:Craig.Russell@sun.com
>>
>> P.S. A good JDO? O, Gasp!
>>
>>
>
>------------------------------------------------------------------------
>
Re: Importing xsd and dtd files into the spec
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attached is a shell script for extracting the lines to be included in
the spec from the annotations files.
-- Michelle
Craig L Russell wrote:
> Hi Michelle,
>
> Sadly, there is one feature missing that would disallow this to be
> used for the annotations chapter. I couldn't find a way to skip over
> the boilerplate [1] at the top of each .java file. So if we used this
> technique for the annotations chapter, we would either have to write a
> script to remove the boilerplate or include the boilerplate in every
> file. And if we write a script we would need to keep the source files
> up to date if the java files ever changed.
>
> Do you know a way around this problem?
>
> This isn't an issue for the xsd and dtd files because the only
> boilerplate is the Apache license which is ok for this purpose.
>
> Craig
>
> [1] boilerplate for Column.java
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package javax.jdo.annotations;
>
> import java.lang.annotation.ElementType;
> import java.lang.annotation.Retention;
> import java.lang.annotation.RetentionPolicy;
> import java.lang.annotation.Target;
>
> /**
> * Annotation for a column in the database.
> * Corresponds to the xml element "column".
> *
> * @version 2.1
> * @since 2.1
> */
>
> On Jan 4, 2008, at 4:32 PM, Michelle Caisse wrote:
>
>>
>>> 2. Updated spec: in progress. The jdoconfig.xml has been added to
>>> Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml
>>> to Appendix D? No, probably better to add the dtd version of
>>> jdoconfig to Appendix D.
>>>
>>> AI Michelle look at how to automatically include the xsd and dtd
>>> files into the spec.
>>>
>> From FrameMaker help:
>>
>>
>> Importing by reference
>>
>> ------------------------------------------------------------------------
>>
>> You can import by reference by using File > Import > File, OLE
>> (Windows), Publish and Subscribe (Mac OS), or a graphic inset
>> editor (UNIX).
>>
>> When you double-click a graphic imported by reference you:
>>
>> * (Windows) Open the application
>> * (Mac OS) Open the Object Properties dialog
>>
>> Importing by reference keeps the imported text or graphics
>> linked to the source file. FrameMaker stores the pathname to
>> the source file in the document. Each time you open the
>> document, FrameMaker locates the file on the disk and
>> redisplays it. If the source file was revised, FrameMaker
>> updates the document with the latest version. Importing by
>> reference can reduce total file size because it lets you use
>> the same material in several places without storing the
>> contents of imported images or text in the FrameMaker document.
>> Text imported by reference is called a text inset.
>>
>> For information on how the pathname is stored when importing by
>> reference, see Using pathnames when importing by reference.
>>
>>
>> I did a quick test of importing jdo_2_0.xsd. I applied the code
>> paragraph style and it looked good with no changes. When you import
>> by reference, you cannot edit the text from within Frame. When you
>> select the imported text (clicking anywhere within the import
>> highlights the entire block), Edit/Text Inset Properties brings up a
>> dialog that displays information and offers various actions.
>>
>> -- Michelle
>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
Re: Importing xsd and dtd files into the spec
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Michelle,
Sadly, there is one feature missing that would disallow this to be
used for the annotations chapter. I couldn't find a way to skip over
the boilerplate [1] at the top of each .java file. So if we used this
technique for the annotations chapter, we would either have to write
a script to remove the boilerplate or include the boilerplate in
every file. And if we write a script we would need to keep the source
files up to date if the java files ever changed.
Do you know a way around this problem?
This isn't an issue for the xsd and dtd files because the only
boilerplate is the Apache license which is ok for this purpose.
Craig
[1] boilerplate for Column.java
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed
with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License,
Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package javax.jdo.annotations;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
/**
* Annotation for a column in the database.
* Corresponds to the xml element "column".
*
* @version 2.1
* @since 2.1
*/
On Jan 4, 2008, at 4:32 PM, Michelle Caisse wrote:
>
>> 2. Updated spec: in progress. The jdoconfig.xml has been added to
>> Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml
>> to Appendix D? No, probably better to add the dtd version of
>> jdoconfig to Appendix D.
>>
>> AI Michelle look at how to automatically include the xsd and dtd
>> files into the spec.
>>
> From FrameMaker help:
> Importing by reference
>
> You can import by reference by using File > Import > File, OLE
> (Windows), Publish and Subscribe (Mac OS), or a graphic inset
> editor (UNIX).
>
> When you double-click a graphic imported by reference you:
>
> (Windows) Open the application
> (Mac OS) Open the Object Properties dialog
> Importing by reference keeps the imported text or graphics linked
> to the source file. FrameMaker stores the pathname to the source
> file in the document. Each time you open the document, FrameMaker
> locates the file on the disk and redisplays it. If the source file
> was revised, FrameMaker updates the document with the latest
> version. Importing by reference can reduce total file size because
> it lets you use the same material in several places without storing
> the contents of imported images or text in the FrameMaker document.
> Text imported by reference is called a text inset.
>
> For information on how the pathname is stored when importing by
> reference, see Using pathnames when importing by reference.
>
> I did a quick test of importing jdo_2_0.xsd. I applied the code
> paragraph style and it looked good with no changes. When you import
> by reference, you cannot edit the text from within Frame. When you
> select the imported text (clicking anywhere within the import
> highlights the entire block), Edit/Text Inset Properties brings up
> a dialog that displays information and offers various actions.
>
> -- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Importing xsd and dtd files into the spec
Posted by Michelle Caisse <Mi...@Sun.COM>.
> 2. Updated spec: in progress. The jdoconfig.xml has been added to
> Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml to
> Appendix D? No, probably better to add the dtd version of jdoconfig
> to Appendix D.
>
> AI Michelle look at how to automatically include the xsd and dtd
> files into the spec.
>
From FrameMaker help:
Importing by reference
------------------------------------------------------------------------
You can import by reference by using File > Import > File, OLE
(Windows), Publish and Subscribe (Mac OS), or a graphic inset
editor (UNIX).
When you double-click a graphic imported by reference you:
* (Windows) Open the application
* (Mac OS) Open the Object Properties dialog
Importing by reference keeps the imported text or graphics linked
to the source file. FrameMaker stores the pathname to the source
file in the document. Each time you open the document, FrameMaker
locates the file on the disk and redisplays it. If the source file
was revised, FrameMaker updates the document with the latest
version. Importing by reference can reduce total file size because
it lets you use the same material in several places without
storing the contents of imported images or text in the FrameMaker
document. Text imported by reference is called a text inset.
For information on how the pathname is stored when importing by
reference, see Using pathnames when importing by reference.
I did a quick test of importing jdo_2_0.xsd. I applied the code
paragraph style and it looked good with no changes. When you import by
reference, you cannot edit the text from within Frame. When you select
the imported text (clicking anywhere within the import highlights the
entire block), Edit/Text Inset Properties brings up a dialog that
displays information and offers various actions.
-- Michelle
Re: JDO TCK Conference Call Friday, Jan 4 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig
Russell
Agenda:
1. Query test failure: Michael ran the test against Oracle. Some
difficult issues with schema naming and teardown. It looks like
Oracle returns the expected number of rows.
Issues found while working this problem:
a. Oracle treats "application0.PERSONS" different from Derby. Oracle
expects a user called application0; Derby expects a schema called
application0. AI Michael file a JIRA for discussion
b. A minor bug in QueryTest in using variable pm from the superclass;
the variable might not have been initialized.
c. Sometimes the test testMultipleProjectionWithConstraints succeeds;
sometimes it fails. Might be related to query optimization by Derby.
AI Craig update DERBY JIRA.
d. Logging has changed from JPOX 1.1 to 1.2. The logging categories
need to be updated in the tck2 src/conf/log4j.properties. AI Michael
update the properties in tck2 and tck2-legacy.
e. There seems to be a typo in Andy's comments posting the SQL. Some
lines in the innermost WHERE clause are duplicated.
f. Using Oracle, the correct number of rows is returned for all the
queries.
2. Updated spec: in progress. The jdoconfig.xml has been added to
Appendix D. Should we also put jdo.xml, orm.xml, and jdoquery.xml to
Appendix D? No, probably better to add the dtd version of jdoconfig
to Appendix D.
AI Michelle look at how to automatically include the xsd and dtd
files into the spec.
3. Other issues
Subquery testing: Michael has finished the test creation, and will
check in the tests to the tck. AI Michael file a new JIRA if JPOX
fails the tests.
While working the subquery test issue, we notice that none of the
tests supports memory queries using candidate collection. AI Craig
file a JIRA for future release to better test memory queries. Should
a couple of query tests be added, or try to run all of the existing
query tests against memory?
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 18, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Craig L Russell wrote:
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
>
> - Michelle is working on publishing the latest draft of the
> specification.
The latest draft spec is available from
http://db.apache.org/jdo/specifications.html
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 18, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Are we all happy with the functionality of the current JDO 2.1? We
have feedback from Andy Jefferson. AI everyone: please discuss on the
email thread.
2. Remaining work for 2.1 release
- BNF for query in progress.
- AI Craig update JIRA issues so only 2.1 issues are marked as 2.1.
- http://issues.apache.org/jira/browse/DERBY-3301 is showing progress.
Thanks to the Derby team.
3. Other issues
- Michael tried to set up the TCK with Oracle and ran into some
problems with schema handling. http://issues.apache.org/jira/browse/JDO-570
- Michelle is working on metadata overrides tests.
- Michelle is working on publishing the latest draft of the
specification.
Action Items from weeks past:
[Jan 11 2008] AI Michael update the BNF for the specification.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Feb 1, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. ServiceLoader (JDO-556) This issue has been taken out of JDO 2.1
because the API doesn't match exactly what the JDO PMF requires. AI
Matthew see what would be needed to update the PMF contract to support
ServiceLoader.
2. Query BNF (JDO-569) Michael has updated the bnf and will attach it
to the jira.
3. JDOHelper Security (JDO-555) The JDOHelper class has been updated
with several new methods that call privileged methods within a
doPrivileged block. The issue now is how to test that all of the
methods that need privileges have been wrapped. Need to add an extra
maven goal that sets up security or modify the goal to include
security. Look at jdo ri11 project for examples.
4. Derby bug causing query test failure (JDO-435, Derby 3301) The
Derby bug fix will be checked in to the Derby code base targeted for
10.4.x.x scheduled for release in April. AI Craig create a new test
case and put the failing test(s) into it, and exclude the test case
for now.
5. Other issues
a. JDO 2.1 release status: Craig submitted the Maintenance Review to
the JCP. The 30 day review ends the first week in March.
b. Michael sent comments on the Query chapter. Question: do we support
exclude subclasses in subqueries? I think so.
Question: Should we include more examples in 14.10? Yes, I think so.
c. The API was changed recently to swap parameters in the evict, pin,
and unpin methods but the signature files were accidentally left out.
AI Michael has volunteered to update to update the signature files.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Feb 15, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. TCK tests of jdoconfig.xml, persistence.xml: jdoconfig.xml tests
are running but no tests for registered listeners yet. persistence.xml
tests don't work because JDOHelper assumes that an EMF can be cast to
a PMF. AI Craig update JDOHelper to use
getPersistenceManagerFactory(Map, Map) for PUName case.
2. JDO 2.1 spec status: expect to publish new version this weekend.
New material includes the subquery text and examples from Michael's
review. AI review Craig's message from 8 Feb.
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday Mar 7, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse
Recursion depth: Email discussion suggested that 0 should be no-op. But
what does this mean? Also, a user might expect any negative value to be
infinite recursion depth, given that -1 is defined that way. We will
continue discussion in email.
Craig's status:
> 1. JDOHelper is almost done. With the pending changes, and new test
> cases for JDOHelper overrides for PersistenceUnitName, and the latest
> JPOX SNAPSHOT, everything passes. So I have no concerns about the
> current ship quality of JPOX.
>
> I still need to do a small bit of reorganization of the JDOHelper
> code before I check it in. So far, I've refactored
> getPersistenceManagerFactory(Map overrides, String name, ClassLoader
> resourceLoader, ClassLoader pmfLoader) so it is one page and much
> more readable.
>
> 2. I've briefly looked at Andy's proposed changes to the recursion
> depth text and if there's no further discussion, I'll update the spec.
Open issues for JDO 2.1: The patch on JDO-555 needs to be reviewed. Need
to review other JIRAs and change fix for release flag for some.
-- Michelle
Minutes: JDO TCK Conference Call Friday Mar 14,
9 am Pacific Daylight Time {NOTE US TIME CHANGE!!!)
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Recursion depth discussion in spec. Ship it.
2. Jdoconfig tests fail on tck2-legacy (JDO-581). This turned out to
be a bug in the tck and a confusing error message from JPOX. The bug
in the tck has been fixed. JPOX has been notified of the confusing
error message (left JDO-581 open for this).
3. Work remaining for 2.1 release: The last bug for this release is
almost done (JDO-579 minor reporting bug in case of failure). Michele
will spin a release. Craig will update the specification. Both the
release artifacts and the specification will be put to a vote next week.
ACTION: Please look for the release vote notice and test the release.
4. Other issues
none.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday Mar 21,
9 am Pacific Daylight Time {NOTE US TIME CHANGE!!!)
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. JDO 2.1 status: Voting is going well. No negative votes yet. The
vote closes on Monday. Michelle is testing 2.1-rc2 on Windows. We need
a process for updating release notes possibly after the release is
out. AI Michelle propose a process.
2. JDO 2.2 plan Several items have been proposed already for post-2.1
activities. AI everyone reply to issues on email and file JIRA issues
to track them.
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday Apr 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Next week's meeting (April 11) is canceled due to vacations and
conflicting meetings.
Attendees: Michelle Caisse, Matthew Adams, Craig Russell
Agenda:
1. JDO 2.2 plans: Craig sent mail soliciting input for the release. A
few responses so far. Can we have a shorter release cycle? Perhaps 3
to 6 months.
Items suggested for this release include:
Dynamic fetch plans (also add method setRecursionDepth on FetchPlan)
Service Loader pattern for JDOHelper.getPersistenceManagerFactory
Add new constructors for exceptions
Support for multiple datastores
JMX management/monitoring model
OSGi Service (Similar to JDO-556)
The long awaited enhancer API
Schema synchronization API (generates/modifies schema)
level of standardisation of transaction isolation
AI Everyone who proposed a feature, please add a JIRA issue and assign
it to a volunteer who will implement the feature. Discussion can then
continue around the JIRA issues.
2. Plan to promote JDO 2.1. AI Craig write up a release announcement
for posting to Apache, ServerSide, etc.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Date correction: JDO TCK Conference Call Friday Apr 4, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Friday, April 4
-- Michelle
Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, April 3 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. JDO 2.2 plans
> 3. Other issues
>
> Action Items from weeks past:
>
> [Feb 1 2008] AI Matthew see what would be needed to update the PMF
> contract to support ServiceLoader.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
Minutes: JDO TCK Conference Call Friday, May 30, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Richard Schilling, Michelle Caisse, Craig
Russell
On May 29, 2008, at 6:24 PM, Michelle Caisse wrote:
Agenda:
1. JDO 2.2 plans: Is the trunk ok? Seem to have some failing tests
since shipping 2.1. AI everyone build and run tests.
There was an issue building the site with maven 1.0.2. This was
resolved.
JDO trunk builds and runs with one test case failing (in each of
datastore and application identity) due to bad SQL generation.
2. Other issues
none.
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Awais Bajwa <aw...@gmail.com>.
Good catch Craig,
That was the reason, may be we can put this note in the instructions page:
Overall tested successfully! (Please refer to only one failure attached)
+1
Awais Bajwa
On 8/6/08, Craig L Russell <Cr...@sun.com> wrote:
>
> Hi Awais,
>
> Maybe you also need to refer to the real Maven remote repository in your
> properties file: *repo*1.*maven*.org
>
> I've not had to refer to it myself, but I haven't needed to download a
> non-SNAPSHOT artifact for a while.
>
>
> Regards,
>
>
> Craig
>
>
> On Aug 5, 2008, at 12:53 PM, Awais Bajwa wrote:
>
> Hi All,
>
> I am actually a first time user of Maven 1, now I am trying to downlaod
> from my home and no proxies so the maven 1 successfully downloaded the jdo
> jars from the remote repository but I am still facing problem with the other
> basic jars .. like junit and others .
>
> I have also noticed that Maven 1 is trying to downalod all the dependencies
> from the following repositories:
> maven.repo.remote =\
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository,\<http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository,/>
> http://www.jpox.org/downloads/maven,\<http://www.jpox.org/downloads/maven,/>
> http://www.jpox.org/downloads/maven-nightly,\<http://www.jpox.org/downloads/maven-nightly,/>
> http://download.java.net/maven/1
>
> after going to the tck direcotry.
>
>
> > maven build
>
> Trying to get missing dependencies (and updated snapshots) required by JDO2
> Technology Compatibility Kit:
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from
> http://download.java.net/maven/1
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
> http://download.java.net/maven/1
> - Attempting to download junit:junit:3.8.1:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download junit:junit:3.8.1:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download junit:junit:3.8.1:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download junit:junit:3.8.1:jar from
> http://download.java.net/maven/1
> - Attempting to download asm:asm:3.0:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download asm:asm:3.0:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download asm:asm:3.0:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download asm:asm:3.0:jar from
> http://download.java.net/maven/1
> - Attempting to download log4j:log4j:1.2.13:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download log4j:log4j:1.2.13:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download log4j:log4j:1.2.13:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download log4j:log4j:1.2.13:jar from
> http://download.java.net/maven/1
> - Attempting to download commons-logging:commons-logging:1.1:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-logging:commons-logging:1.1:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download commons-logging:commons-logging:1.1:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-logging:commons-logging:1.1:jar from
> http://download.java.net/maven/1
> - Attempting to download org.springframework:spring-core:2.0:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.springframework:spring-core:2.0:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download org.springframework:spring-core:2.0:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.springframework:spring-core:2.0:jar from
> http://download.java.net/maven/1
> - Attempting to download org.springframework:spring-beans:2.0:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.springframework:spring-beans:2.0:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download org.springframework:spring-beans:2.0:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.springframework:spring-beans:2.0:jar from
> http://download.java.net/maven/1
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from
> http://download.java.net/maven/1
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
> http://download.java.net/maven/1
> - Attempting to download commons-pool:commons-pool:1.3:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-pool:commons-pool:1.3:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download commons-pool:commons-pool:1.3:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-pool:commons-pool:1.3:jar from
> http://download.java.net/maven/1
> - Attempting to download commons-collections:commons-collections:3.2:jar
> from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-collections:commons-collections:3.2:jar
> from http://www.jpox.org/downloads/maven
> - Attempting to download commons-collections:commons-collections:3.2:jar
> from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-collections:commons-collections:3.2:jar
> from http://download.java.net/maven/1
> - Attempting to download
> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-reposito
> ry
> - Attempting to download
> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
> http://www.jpox.org/downloads/maven
> - Attempting to download
> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
> http://www.jpox.org/downloads/maven-nightly
> - Attempting to download
> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
> http://download.java.net/maven/1
>
> -------------------------------------------------------------------------------
> >> The build cannot continue because of the following unsatisfied
> dependencies:
> - org.apache.derby:derby:10.2.1.6:jar
> - org.apache.derby:derbytools:10.2.1.6:jar
> - junit:junit:3.8.1:jar
> - asm:asm:3.0:jar (try downloading from
> http://maven.objectweb.org/maven2/asm/asm/3.0/)
> - log4j:log4j:1.2.13:jar
> - commons-logging:commons-logging:1.1:jar
> - org.springframework:spring-core:2.0:jar
> - org.springframework:spring-beans:2.0:jar
> - c3p0:c3p0:0.9.0.2:jar (try downloading from
> http://prdownloads.sourceforge.net/c3p0/c3p0-0.9.0.2.bin.zip)
> - commons-dbcp:commons-dbcp:1.2.1:jar
> - commons-pool:commons-pool:1.3:jar
> - commons-collections:commons-collections:3.2:jar
> - org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar
>
> -------------------------------------------------------------------------------
> BUILD FAILED
>
> -------------------------------------------------------------------------------
> Total time : 1 minutes 55 seconds
> Finished at : Tuesday, 5 August 2008 23:45:09 GST
> Final Memory : 1M/4M
>
>
>
>
>
>
> If anyone has any idea then it would save my time, Furhter I have worked
> with Maven 2, and I will see if we can move to Maven 2.
>
> Regards
> Awais Bajwa
>
>
>
> On 8/5/08, Awais Bajwa <aw...@gmail.com> wrote:
>>
>> Hi All,
>>
>> I am having some problem while downloading the artifacts for the Maven and
>> it is throwing the authentication error, I am sitting behind proxy:
>>
>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> Error retrieving artifact from [
>> http://www.jpox.org/downloads/maven-nightly]:
>> org.apache.maven.wagon.authorization.AuthorizationException: Not authorized
>> by proxy.
>> - Attempting to download
>> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
>> http://download.java.net/maven/1
>> Required credentials not available for BASIC <any realm>@
>> download.java.net:80 <http://download.java.net/>
>> Preemptive authentication requested but no default credentials available
>> Credentials cannot be used for NTLM authentication:
>> org.apache.commons.httpclient.UsernamePasswordCredentials
>> org.apache.commons.httpclient.auth.InvalidCredentialsException:
>> Credentials cannot be used for NTLM authentication:
>> org.apache.commons.httpclient.UsernamePasswordCredentials
>> at
>> org.apache.commons.httpclient.auth.NTLMScheme.authenticate(NTLMScheme.java:331)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.authenticateProxy(HttpMethodDirector.java:319)
>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>
>>
>>
>> I am using the following properties
>>
>>
>> maven.proxy.host=japroxy
>> maven.proxy.port=8080
>> maven.proxy.username=awais.bajwa
>> maven.proxy.password=bajwa
>>
>> Any idea?
>>
>> -Awais
>>
>> On 8/2/08, Michelle Caisse <Mi...@sun.com> wrote:
>>>
>>> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy and
>>> current versions) with the projects that they depend on: enhancer, model,
>>> and util.
>>>
>>> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
>>> [0] Don't care
>>> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>>>
>>>
>>>
>>> The TCK can be tested from the staging area,
>>> http://people.apache.org/~mcaisse/jdo2.1.1/dist<http://people.apache.org/%7Emcaisse/jdo2.1-rc2/dist>.
>>> Please follow the directions at
>>> http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for downloading and
>>> testing.
>>>
>>> JDO 2.1.1 provides fixes for the following issues:
>>>
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-584
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-585
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-586
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-593
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-600
>>> -
>>>
>>> http://issues.apache.org/jira/browse/JDO-601
>>>
>>>
>>> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>>>
>>> -- Michelle
>>>
>>>
>>
>
> Craig L Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com <Cr...@sun.com>
>
> P.S. A good JDO? O, Gasp!
>
>
>
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Awais,
Maybe you also need to refer to the real Maven remote repository in
your properties file: repo1.maven.org
I've not had to refer to it myself, but I haven't needed to download a
non-SNAPSHOT artifact for a while.
Regards,
Craig
On Aug 5, 2008, at 12:53 PM, Awais Bajwa wrote:
> Hi All,
>
> I am actually a first time user of Maven 1, now I am trying to
> downlaod from my home and no proxies so the maven 1 successfully
> downloaded the jdo jars from the remote repository but I am still
> facing problem with the other basic jars .. like junit and others .
>
> I have also noticed that Maven 1 is trying to downalod all the
> dependencies from the following repositories:
> maven.repo.remote =\
> http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository,\
> http://www.jpox.org/downloads/maven,\
> http://www.jpox.org/downloads/maven-nightly,\
> http://download.java.net/maven/1
>
> after going to the tck direcotry.
>
>
> > maven build
> Trying to get missing dependencies (and updated snapshots) required
> by JDO2 Technology Compatibility Kit:
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from http://www.jpox.org/downloads/maven
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.apache.derby:derby:10.2.1.6:jar from http://download.java.net/maven/1
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar
> from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar
> from http://www.jpox.org/downloads/maven
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar
> from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.apache.derby:derbytools:10.2.1.6:jar
> from http://download.java.net/maven/1
> - Attempting to download junit:junit:3.8.1:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download junit:junit:3.8.1:jar from http://www.jpox.org/downloads/maven
> - Attempting to download junit:junit:3.8.1:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download junit:junit:3.8.1:jar from http://download.java.net/maven/1
> - Attempting to download asm:asm:3.0:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download asm:asm:3.0:jar from http://www.jpox.org/downloads/maven
> - Attempting to download asm:asm:3.0:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download asm:asm:3.0:jar from http://download.java.net/maven/1
> - Attempting to download log4j:log4j:1.2.13:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download log4j:log4j:1.2.13:jar from http://www.jpox.org/downloads/maven
> - Attempting to download log4j:log4j:1.2.13:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download log4j:log4j:1.2.13:jar from http://download.java.net/maven/1
> - Attempting to download commons-logging:commons-logging:1.1:jar
> from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-logging:commons-logging:1.1:jar
> from http://www.jpox.org/downloads/maven
> - Attempting to download commons-logging:commons-logging:1.1:jar
> from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-logging:commons-logging:1.1:jar
> from http://download.java.net/maven/1
> - Attempting to download org.springframework:spring-core:2.0:jar
> from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.springframework:spring-core:2.0:jar
> from http://www.jpox.org/downloads/maven
> - Attempting to download org.springframework:spring-core:2.0:jar
> from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.springframework:spring-core:2.0:jar
> from http://download.java.net/maven/1
> - Attempting to download org.springframework:spring-beans:2.0:jar
> from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download org.springframework:spring-beans:2.0:jar
> from http://www.jpox.org/downloads/maven
> - Attempting to download org.springframework:spring-beans:2.0:jar
> from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.springframework:spring-beans:2.0:jar
> from http://download.java.net/maven/1
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from http://www.jpox.org/downloads/maven
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download c3p0:c3p0:0.9.0.2:jar from http://download.java.net/maven/1
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from http://www.jpox.org/downloads/maven
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from http://download.java.net/maven/1
> - Attempting to download commons-pool:commons-pool:1.3:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-pool:commons-pool:1.3:jar from http://www.jpox.org/downloads/maven
> - Attempting to download commons-pool:commons-pool:1.3:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-pool:commons-pool:1.3:jar from http://download.java.net/maven/1
> - Attempting to download commons-collections:commons-collections:
> 3.2:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
> - Attempting to download commons-collections:commons-collections:
> 3.2:jar from http://www.jpox.org/downloads/maven
> - Attempting to download commons-collections:commons-collections:
> 3.2:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download commons-collections:commons-collections:
> 3.2:jar from http://download.java.net/maven/1
> - Attempting to download org.apache.geronimo.specs:geronimo-
> jpa_3.0_spec:1.0:jar from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-reposito
> ry
> - Attempting to download org.apache.geronimo.specs:geronimo-
> jpa_3.0_spec:1.0:jar from http://www.jpox.org/downloads/maven
> - Attempting to download org.apache.geronimo.specs:geronimo-
> jpa_3.0_spec:1.0:jar from http://www.jpox.org/downloads/maven-nightly
> - Attempting to download org.apache.geronimo.specs:geronimo-
> jpa_3.0_spec:1.0:jar from http://download.java.net/maven/1
> -------------------------------------------------------------------------------
> >> The build cannot continue because of the following unsatisfied
> dependencies:
> - org.apache.derby:derby:10.2.1.6:jar
> - org.apache.derby:derbytools:10.2.1.6:jar
> - junit:junit:3.8.1:jar
> - asm:asm:3.0:jar (try downloading from http://maven.objectweb.org/maven2/asm/asm/3.0/)
> - log4j:log4j:1.2.13:jar
> - commons-logging:commons-logging:1.1:jar
> - org.springframework:spring-core:2.0:jar
> - org.springframework:spring-beans:2.0:jar
> - c3p0:c3p0:0.9.0.2:jar (try downloading from http://prdownloads.sourceforge.net/c3p0/c3p0-0.9.0.2.bin.zip)
> - commons-dbcp:commons-dbcp:1.2.1:jar
> - commons-pool:commons-pool:1.3:jar
> - commons-collections:commons-collections:3.2:jar
> - org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar
>
> -------------------------------------------------------------------------------
> BUILD FAILED
> -------------------------------------------------------------------------------
> Total time : 1 minutes 55 seconds
> Finished at : Tuesday, 5 August 2008 23:45:09 GST
> Final Memory : 1M/4M
>
>
>
>
>
>
> If anyone has any idea then it would save my time, Furhter I have
> worked with Maven 2, and I will see if we can move to Maven 2.
>
> Regards
> Awais Bajwa
>
>
>
> On 8/5/08, Awais Bajwa <aw...@gmail.com> wrote:
> Hi All,
>
> I am having some problem while downloading the artifacts for the
> Maven and it is throwing the authentication error, I am sitting
> behind proxy:
>
> >
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Error retrieving artifact from [http://www.jpox.org/downloads/maven-nightly
> ]: org.apache.maven.wagon.authorization.AuthorizationException: Not
> authorized by proxy.
> - Attempting to download org.apache.geronimo.specs:geronimo-
> jpa_3.0_spec:1.0:jar from http://download.java.net/maven/1
> Required credentials not available for BASIC <any
> realm>@download.java.net:80
> Preemptive authentication requested but no default credentials
> available
> Credentials cannot be used for NTLM authentication:
> org.apache.commons.httpclient.UsernamePasswordCredentials
> org.apache.commons.httpclient.auth.InvalidCredentialsException:
> Credentials cannot be used for NTLM authentication:
> org.apache.commons.httpclient.UsernamePasswordCredentials
> at
> org
> .apache
> .commons.httpclient.auth.NTLMScheme.authenticate(NTLMScheme.java:331)
> at
> org
> .apache
> .commons
> .httpclient
> .HttpMethodDirector.authenticateProxy(HttpMethodDirector.java:319)
> >
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>
>
> I am using the following properties
>
>
> maven.proxy.host=japroxy
> maven.proxy.port=8080
> maven.proxy.username=awais.bajwa
> maven.proxy.password=bajwa
>
> Any idea?
>
> -Awais
>
> On 8/2/08, Michelle Caisse <Mi...@sun.com> wrote:
> This vote is to release the Apache JDO 2.1.1 TCK and API (both
> legacy and current versions) with the projects that they depend on:
> enhancer, model, and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util
> because:
>
>
> The TCK can be tested from the staging area, http://people.apache.org/~mcaisse/jdo2.1.1/dist
> . Please follow the directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1
> for downloading and testing.
>
> JDO 2.1.1 provides fixes for the following issues:
> http://issues.apache.org/jira/browse/JDO-584
>
> http://issues.apache.org/jira/browse/JDO-585
>
> http://issues.apache.org/jira/browse/JDO-586
>
> http://issues.apache.org/jira/browse/JDO-593
>
> http://issues.apache.org/jira/browse/JDO-600
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
>
>
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Awais Bajwa <aw...@gmail.com>.
Hi All,
I am actually a first time user of Maven 1, now I am trying to downlaod
from my home and no proxies so the maven 1 successfully downloaded the jdo
jars from the remote repository but I am still facing problem with the other
basic jars .. like junit and others .
I have also noticed that Maven 1 is trying to downalod all the dependencies
from the following repositories:
maven.repo.remote =\
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository,\<http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository,/>
http://www.jpox.org/downloads/maven,\<http://www.jpox.org/downloads/maven,/>
http://www.jpox.org/downloads/maven-nightly,\<http://www.jpox.org/downloads/maven-nightly,/>
http://download.java.net/maven/1
after going to the tck direcotry.
> maven build
Trying to get missing dependencies (and updated snapshots) required by JDO2
Technology Compatibility Kit:
- Attempting to download org.apache.derby:derby:10.2.1.6:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download org.apache.derby:derby:10.2.1.6:jar from
http://www.jpox.org/downloads/maven
- Attempting to download org.apache.derby:derby:10.2.1.6:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download org.apache.derby:derby:10.2.1.6:jar from
http://download.java.net/maven/1
- Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
http://www.jpox.org/downloads/maven
- Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download org.apache.derby:derbytools:10.2.1.6:jar from
http://download.java.net/maven/1
- Attempting to download junit:junit:3.8.1:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download junit:junit:3.8.1:jar from
http://www.jpox.org/downloads/maven
- Attempting to download junit:junit:3.8.1:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download junit:junit:3.8.1:jar from
http://download.java.net/maven/1
- Attempting to download asm:asm:3.0:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download asm:asm:3.0:jar from
http://www.jpox.org/downloads/maven
- Attempting to download asm:asm:3.0:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download asm:asm:3.0:jar from
http://download.java.net/maven/1
- Attempting to download log4j:log4j:1.2.13:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download log4j:log4j:1.2.13:jar from
http://www.jpox.org/downloads/maven
- Attempting to download log4j:log4j:1.2.13:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download log4j:log4j:1.2.13:jar from
http://download.java.net/maven/1
- Attempting to download commons-logging:commons-logging:1.1:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download commons-logging:commons-logging:1.1:jar from
http://www.jpox.org/downloads/maven
- Attempting to download commons-logging:commons-logging:1.1:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download commons-logging:commons-logging:1.1:jar from
http://download.java.net/maven/1
- Attempting to download org.springframework:spring-core:2.0:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download org.springframework:spring-core:2.0:jar from
http://www.jpox.org/downloads/maven
- Attempting to download org.springframework:spring-core:2.0:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download org.springframework:spring-core:2.0:jar from
http://download.java.net/maven/1
- Attempting to download org.springframework:spring-beans:2.0:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download org.springframework:spring-beans:2.0:jar from
http://www.jpox.org/downloads/maven
- Attempting to download org.springframework:spring-beans:2.0:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download org.springframework:spring-beans:2.0:jar from
http://download.java.net/maven/1
- Attempting to download c3p0:c3p0:0.9.0.2:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download c3p0:c3p0:0.9.0.2:jar from
http://www.jpox.org/downloads/maven
- Attempting to download c3p0:c3p0:0.9.0.2:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download c3p0:c3p0:0.9.0.2:jar from
http://download.java.net/maven/1
- Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
http://www.jpox.org/downloads/maven
- Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download commons-dbcp:commons-dbcp:1.2.1:jar from
http://download.java.net/maven/1
- Attempting to download commons-pool:commons-pool:1.3:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download commons-pool:commons-pool:1.3:jar from
http://www.jpox.org/downloads/maven
- Attempting to download commons-pool:commons-pool:1.3:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download commons-pool:commons-pool:1.3:jar from
http://download.java.net/maven/1
- Attempting to download commons-collections:commons-collections:3.2:jar
from http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-repository
- Attempting to download commons-collections:commons-collections:3.2:jar
from http://www.jpox.org/downloads/maven
- Attempting to download commons-collections:commons-collections:3.2:jar
from http://www.jpox.org/downloads/maven-nightly
- Attempting to download commons-collections:commons-collections:3.2:jar
from http://download.java.net/maven/1
- Attempting to download
org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
http://people.apache.org/~mcaisse/jdo2.1.1/dist/java-reposito
ry
- Attempting to download
org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
http://www.jpox.org/downloads/maven
- Attempting to download
org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
http://www.jpox.org/downloads/maven-nightly
- Attempting to download
org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
http://download.java.net/maven/1
-------------------------------------------------------------------------------
>> The build cannot continue because of the following unsatisfied
dependencies:
- org.apache.derby:derby:10.2.1.6:jar
- org.apache.derby:derbytools:10.2.1.6:jar
- junit:junit:3.8.1:jar
- asm:asm:3.0:jar (try downloading from
http://maven.objectweb.org/maven2/asm/asm/3.0/)
- log4j:log4j:1.2.13:jar
- commons-logging:commons-logging:1.1:jar
- org.springframework:spring-core:2.0:jar
- org.springframework:spring-beans:2.0:jar
- c3p0:c3p0:0.9.0.2:jar (try downloading from
http://prdownloads.sourceforge.net/c3p0/c3p0-0.9.0.2.bin.zip)
- commons-dbcp:commons-dbcp:1.2.1:jar
- commons-pool:commons-pool:1.3:jar
- commons-collections:commons-collections:3.2:jar
- org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
Total time : 1 minutes 55 seconds
Finished at : Tuesday, 5 August 2008 23:45:09 GST
Final Memory : 1M/4M
If anyone has any idea then it would save my time, Furhter I have worked
with Maven 2, and I will see if we can move to Maven 2.
Regards
Awais Bajwa
On 8/5/08, Awais Bajwa <aw...@gmail.com> wrote:
>
> Hi All,
>
> I am having some problem while downloading the artifacts for the Maven and
> it is throwing the authentication error, I am sitting behind proxy:
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Error retrieving artifact from [
> http://www.jpox.org/downloads/maven-nightly]:
> org.apache.maven.wagon.authorization.AuthorizationException: Not authorized
> by proxy.
> - Attempting to download
> org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
> http://download.java.net/maven/1
> Required credentials not available for BASIC <any realm>@
> download.java.net:80 <http://download.java.net/>
> Preemptive authentication requested but no default credentials available
> Credentials cannot be used for NTLM authentication:
> org.apache.commons.httpclient.UsernamePasswordCredentials
> org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials
> cannot be used for NTLM authentication:
> org.apache.commons.httpclient.UsernamePasswordCredentials
> at
> org.apache.commons.httpclient.auth.NTLMScheme.authenticate(NTLMScheme.java:331)
> at
> org.apache.commons.httpclient.HttpMethodDirector.authenticateProxy(HttpMethodDirector.java:319)
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>
>
> I am using the following properties
>
>
> maven.proxy.host=japroxy
> maven.proxy.port=8080
> maven.proxy.username=awais.bajwa
> maven.proxy.password=bajwa
>
> Any idea?
>
> -Awais
>
> On 8/2/08, Michelle Caisse <Mi...@sun.com> wrote:
>>
>> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy and
>> current versions) with the projects that they depend on: enhancer, model,
>> and util.
>>
>> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
>> [0] Don't care
>> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>>
>>
>> The TCK can be tested from the staging area,
>> http://people.apache.org/~mcaisse/jdo2.1.1/dist<http://people.apache.org/%7Emcaisse/jdo2.1-rc2/dist>.
>> Please follow the directions at
>> http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for downloading and
>> testing.
>>
>> JDO 2.1.1 provides fixes for the following issues:
>>
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-584
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-585
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-586
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-593
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-600
>> -
>>
>> http://issues.apache.org/jira/browse/JDO-601
>>
>>
>> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>>
>> -- Michelle
>>
>>
>
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Awais Bajwa <aw...@gmail.com>.
Hi All,
I am having some problem while downloading the artifacts for the Maven and
it is throwing the authentication error, I am sitting behind proxy:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Error retrieving artifact from [http://www.jpox.org/downloads/maven-nightly]:
org.apache.maven.wagon.authorization.AuthorizationException: Not authorized
by proxy.
- Attempting to download
org.apache.geronimo.specs:geronimo-jpa_3.0_spec:1.0:jar from
http://download.java.net/maven/1
Required credentials not available for BASIC <any realm>@
download.java.net:80
Preemptive authentication requested but no default credentials available
Credentials cannot be used for NTLM authentication:
org.apache.commons.httpclient.UsernamePasswordCredentials
org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials
cannot be used for NTLM authentication:
org.apache.commons.httpclient.UsernamePasswordCredentials
at
org.apache.commons.httpclient.auth.NTLMScheme.authenticate(NTLMScheme.java:331)
at
org.apache.commons.httpclient.HttpMethodDirector.authenticateProxy(HttpMethodDirector.java:319)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I am using the following properties
maven.proxy.host=japroxy
maven.proxy.port=8080
maven.proxy.username=awais.bajwa
maven.proxy.password=bajwa
Any idea?
-Awais
On 8/2/08, Michelle Caisse <Mi...@sun.com> wrote:
>
> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy and
> current versions) with the projects that they depend on: enhancer, model,
> and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>
>
> The TCK can be tested from the staging area,
> http://people.apache.org/~mcaisse/jdo2.1.1/dist<http://people.apache.org/%7Emcaisse/jdo2.1-rc2/dist>.
> Please follow the directions at
> http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for downloading and
> testing.
>
> JDO 2.1.1 provides fixes for the following issues:
>
> -
>
> http://issues.apache.org/jira/browse/JDO-584
> -
>
> http://issues.apache.org/jira/browse/JDO-585
> -
>
> http://issues.apache.org/jira/browse/JDO-586
> -
>
> http://issues.apache.org/jira/browse/JDO-593
> -
>
> http://issues.apache.org/jira/browse/JDO-600
> -
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
>
>
CANCELLED: JDO TCK Conference Call Friday, June 13, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
This week's JDO Conference Call is cancelled. Join us again next week,
Friday, June 20 :-)
-- Michelle
Minutes: JDO TCK Conference Call Friday, June 6, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Richard Schilling, Michael Bouschen, Craig
Russell
NOTE: June 13 Craig will be on vacation and unable to chair the meeting.
Agenda:
1. JDO 2.2 plans. We reviewed the JDO 2.2 JIRA issues that have been
identified to date.
2. Post-release notes (JDO-593)
Craig added a comment on JDO-593 to ask whether we should update the
HowToReleaseJDO file in the root.
3. Other issues
none
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, July 11, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> An interesting option for a JDO implementation is to use a RESTful
> service like Amazon S3 or memcached for the back end. Some obvious
> issues are transactions, object identity, and query. But having an
> object front end for these would have clear productivity benefits
> compared to a user writing the entire thing by hand (tools are pretty
> simple for accessing data from these services).
If someone is interested, they could easily write a DataNucleus plugin to do
that.
1. Would take maybe 2 days to do basic persistence
(insert/update/delete/fetch/locate) - based on previous experiences with
LDAP, XML, Excel, JSON datastores etc we support.
2. JDOQL (and JPQL) could be provided easily using in-memory queries (that
DataNucleus provides), and then extended to make use of whatever Amazon query
language is available at some later stage.
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Andy Jefferson <an...@datanucleus.org>.
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
+1 (not tested). Though is only a character change so ...
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Michelle Caisse <Mi...@Sun.COM>.
+1
I tested the artifacts on Windows 2K.
-- Michelle
Michelle Caisse wrote:
> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy
> and current versions) with the projects that they depend on: enhancer,
> model, and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>
>
> The TCK can be tested from the staging area,
> http://people.apache.org/~mcaisse/jdo2.1.1/dist. Please follow the
> directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for
> downloading and testing.
>
> JDO 2.1.1 provides fixes for the following issues:
>
> *
>
> http://issues.apache.org/jira/browse/JDO-584
>
> *
>
> http://issues.apache.org/jira/browse/JDO-585
>
> *
>
> http://issues.apache.org/jira/browse/JDO-586
>
> *
>
> http://issues.apache.org/jira/browse/JDO-593
>
> *
>
> http://issues.apache.org/jira/browse/JDO-600
>
> *
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Christian Ernst <ce...@versant.com>.
Hi !
+1
Michelle Caisse schrieb:
> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy
> and current versions) with the projects that they depend on: enhancer,
> model, and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>
>
> The TCK can be tested from the staging area,
> http://people.apache.org/~mcaisse/jdo2.1.1/dist. Please follow the
> directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for
> downloading and testing.
>
> JDO 2.1.1 provides fixes for the following issues:
>
> *
>
> http://issues.apache.org/jira/browse/JDO-584
>
> *
>
> http://issues.apache.org/jira/browse/JDO-585
>
> *
>
> http://issues.apache.org/jira/browse/JDO-586
>
> *
>
> http://issues.apache.org/jira/browse/JDO-593
>
> *
>
> http://issues.apache.org/jira/browse/JDO-600
>
> *
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
cheers
Christian
--
Christian Ernst
Software Engineer
Tel: +49-40-60990 338
Fax: +49-40-60990 113
EMail: cernst@versant.com
Versant GmbH
Wiesenkamp 22b
22359 Hamburg
Germany
Think Outside the Grid!
http://www.versant.com
Versant GmbH is incorporated in Germany.
Company registration number: HRB 54723, Amtsgericht Hamburg.
Registered Office: Wiesenkamp 22b, 22359 Hamburg, Germany.
Geschäftsführer: Jochen Witte
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
I'm afraid it's too late to vote, but just in case it's not:
+1
Regards Michael
> This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy
> and current versions) with the projects that they depend on: enhancer,
> model, and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
>
>
> The TCK can be tested from the staging area,
> http://people.apache.org/~mcaisse/jdo2.1.1/dist. Please follow the
> directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for
> downloading and testing.
>
> JDO 2.1.1 provides fixes for the following issues:
>
> *
>
> http://issues.apache.org/jira/browse/JDO-584
>
> *
>
> http://issues.apache.org/jira/browse/JDO-585
>
> *
>
> http://issues.apache.org/jira/browse/JDO-586
>
> *
>
> http://issues.apache.org/jira/browse/JDO-593
>
> *
>
> http://issues.apache.org/jira/browse/JDO-600
>
> *
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Tempelhofer Ufer 23-24, D-10963 Berlin
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Prof. Dr. Christian Roth, Hendrik Saly, Martin Weber
Amtsgericht Berlin-Charlottenburg HRB 86780
USt.-Id. Nr.: DE 225 964 680
Re: [VOTE] Release Apache JDO 2.1.1
Posted by Craig L Russell <Cr...@Sun.COM>.
Looks good.
Checked (some) signatures, downloaded and tested tck-2.1.1 against
special maven repository.
[java] Total tests run: 1593.
[java] All (109) configurations passed.
[java] See file '/Users/clr/JDO/test2.1.1/jdo2-tck-2.1.1/target/
logs/20080804-123638/TCK-results.txt' for details.
[copy] Copying 336 files to /Users/clr/JDO/test2.1.1/jdo2-
tck-2.1.1/target/logs/20080804-123638/configuration
+1
Craig
On Aug 2, 2008, at 9:41 AM, Michelle Caisse wrote:
> This vote is to release the Apache JDO 2.1.1 TCK and API (both
> legacy and current versions) with the projects that they depend on:
> enhancer, model, and util.
>
> [+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
> [0] Don't care
> [-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util
> because:
>
>
> The TCK can be tested from the staging area, http://people.apache.org/~mcaisse/jdo2.1.1/dist
> . Please follow the directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1
> for downloading and testing.
>
> JDO 2.1.1 provides fixes for the following issues:
> http://issues.apache.org/jira/browse/JDO-584
>
> http://issues.apache.org/jira/browse/JDO-585
>
> http://issues.apache.org/jira/browse/JDO-586
>
> http://issues.apache.org/jira/browse/JDO-593
>
> http://issues.apache.org/jira/browse/JDO-600
>
> http://issues.apache.org/jira/browse/JDO-601
>
>
> Please test and vote. Voting will close at noon PDT Tuesday, August 5.
>
> -- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
[VOTE] Release Apache JDO 2.1.1
Posted by Michelle Caisse <Mi...@Sun.COM>.
This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy
and current versions) with the projects that they depend on: enhancer,
model, and util.
[+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
[0] Don't care
[-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:
The TCK can be tested from the staging area,
http://people.apache.org/~mcaisse/jdo2.1.1/dist. Please follow the
directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for
downloading and testing.
JDO 2.1.1 provides fixes for the following issues:
*
http://issues.apache.org/jira/browse/JDO-584
*
http://issues.apache.org/jira/browse/JDO-585
*
http://issues.apache.org/jira/browse/JDO-586
*
http://issues.apache.org/jira/browse/JDO-593
*
http://issues.apache.org/jira/browse/JDO-600
*
http://issues.apache.org/jira/browse/JDO-601
Please test and vote. Voting will close at noon PDT Tuesday, August 5.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 8, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Control over transaction isolation level http://issues.apache.org/jira/browse/JDO-590
The structure of the proposal is well-founded. The discussion now
centers on the permitted parameters to the API.
2. Behavior of an ordering column http://issues.apache.org/jira/browse/JDO-463
The current behavior of the JDO RI is to have the implementation
manage the ordering field, effectively making the ordering field read-
only. This seems to be a good solution for now, leaving more extensive
behavior for a future revision.
3. Dynamic fetch groups http://issues.apache.org/jira/browse/JDO-554
The discussion now is centered on the scope of the new FetchGroup. The
original proposal provides for no local (PersistenceManager) behavior
with an explicit registration of the new FetchGroup with the
PersistenceManagerFactory. A modification of the proposal would make
the new FetchGroup local to the PersistenceManager, deferring the
discussion of how to make the new FetchGroup visible to the
PersistenceManagerFactory.
4. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[done]
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Aug 22, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> 2. There is one issue that is a bug in the reference implementation
> https://issues.apache.org/jira/browse/JDO-573 Is this going to be fixed any
> time soon?
The short answer is no.
The long answer is as follows. The JDOQL process used by the DataNucleus RDBMS
plugin uses the mechanism that TJDO wrote (pretty much the only part of TJDO
that remains in the codebase). This mechanism doesn't have a full expression
tree, and consequently is not a simple process to convert into SQL, nor to
extend. This results in it being difficult to fix very complex queries such
as the one in that test without breaking something else. The strategic
solution is to replace the mechanism by a more generic process that does
create an expression tree, which can then be converted into SQL. The generic
compilation is largely written (and used by all other supported datastores),
but the process of conversion from the expression tree into SQL is not
written. I have the writing of this expression tree to SQL converter down for
DataNucleus AccessPlatform 1.1. Obviously if people offered their time to
work on these things then they'd get done much sooner.
I'd *suggest* that JDO-573 be deferred to a later Apache JDO release.
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: JDO TCK Conference Call Friday, Aug 29, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. JDO 2.2 release timing: There are just 10 issues outstanding.
https://issues.apache.org/jira/browse/JDO-557 needs some analysis but
expect this will be done
https://issues.apache.org/jira/browse/JDO-580 will probably need a new
test class
https://issues.apache.org/jira/browse/JDO-573 It appears that the
Datanucleus bug won't be fixed in time for a 2008 release, so we will
need to reorganize the test case that exposes the issue and put the
failing test into the exclude list.[ There are several tests in the
test case that work fine.]
https://issues.apache.org/jira/browse/JDO-591 Any volunteers to pick
this one?
https://issues.apache.org/jira/browse/JDO-582 There's a need to update
JDOHelper independent of the test case
https://issues.apache.org/jira/browse/JDO-463 Looks like this is ready
to be closed with just a spec update
https://issues.apache.org/jira/browse/JDO-556 should be split into two
parts: this one that will probably be deferred and another that simply
adds the constructor requirement to PersistenceManagerFactory
implementations
https://issues.apache.org/jira/browse/JDO-558 The test case is ready
but there's a change needed in Datanucleus to support serialization
https://issues.apache.org/jira/browse/JDO-590 I'd like some more
discussion on this before we decide whether to do anything. Seems like
there are two different requirements and it's unclear whether just
doing the API without mandating behavior is useful or more
opportunities for divergence.
https://issues.apache.org/jira/browse/JDO-500 This might fall out of
557, but if not, we can probably defer it.
2. Other issues
JDO 2.1.1 release: Michael has volunteered to update JIRA with the
bugs that were resolved in JDO 2.1.1. Yay.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Sep 5, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. JDO 2.2 release timing. Last week to sign up for issues, so we can
close the release, conduct the lazy consensus vote in the JCP, and
release.
A JIRA JDO 2.3 release has been created to put issues that drop off
the 2.2 list.
AI everyone look at the 2.2 list and sign up for anything you want to
fix.
2. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader. Done. Need to add a no-args
constructor to implementations and add static methods to the PMF
interface.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Sept 12, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees also included Richard Schilling and Michael Bouschen.
-- Michelle
Craig L Russell wrote:
> Attendees: Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. JDO 2.2 draft spec: The draft has been published on Craig's Apache
> home page http:people.apache.org/~clr/jdo-2008-09-12.pdf . AI
> everyone please review and comment.
>
> 2. Control over transaction isolation level (JDO-590) Datanucleus has
> implemented the changes and Craig will update the test cases to
> exercise the new apis.
>
> 3. JDOHelper tests (JDO-582, JDO-557)
>
> Looks like the tests are working now. Craig will check in the bug fix
> and new test cases.
>
> 4. Other issues
>
> JDO-580 Michael has investigated the use of methods in query results
> and will publish some test cases to consider.
>
> Action Items from weeks past:
>
> [Feb 1 2008] AI Matthew see what would be needed to update the PMF
> contract to support ServiceLoader.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect. Done.
> See JDO-463.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql
Minutes: JDO TCK Conference Call Friday, Sept 12, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. JDO 2.2 draft spec: The draft has been published on Craig's Apache
home page http:people.apache.org/~clr/jdo-2008-09-12.pdf . AI everyone
please review and comment.
2. Control over transaction isolation level (JDO-590) Datanucleus has
implemented the changes and Craig will update the test cases to
exercise the new apis.
3. JDOHelper tests (JDO-582, JDO-557)
Looks like the tests are working now. Craig will check in the bug fix
and new test cases.
4. Other issues
JDO-580 Michael has investigated the use of methods in query results
and will publish some test cases to consider.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect. Done.
See JDO-463.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Sept 19, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Control over transaction isolation level (JDO-590) The issue with
the test case is that before the first PM is acquired from the PMF the
implementation doesn't know what isolation levels are supported. So
the test case needs to be changed to try all possible isolation levels
and then check whether it succeeded or not. So the TCK test needs to
be adapted. AI Craig adapt the test case.
2. JDOHelper tests (JDO-582, JDO-557) nothing new for this meeting.
3. Other issues
Query tests: Michael has implemented several new queries regarding
using methods in query results. Some fail similar to the failure of an
aggregate on a size. Others fail in other ways. AI Craig propose
changes to the specification. AI Michael update the JIRA with the test
cases and results.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader. Done. looks like a new set of APIs
is needed.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Oct 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Richard Schilling, Craig Russell
Agenda:
1. JDOHelper tests (JDO-582, JDO-557) Nothing new to report.
2. JDO 2.2: JDO 2.2 release can be prepared for a vote. Craig reviewed
and approved Andy's last patch for transaction isolation and updated
the specification to reflect the changes.
DataNucleus that supports JDO 2.2 is now released, so we can spin a
JDO 2.2. release any time. There is a 7 day vote window in Apache and
the 30 day vote in JCP will conclude Oct 13.
3. Other issues
Richard is working on the documentation. Updates to javadoc that
Richard can make this weekend will be applied to the tck code base for
the release.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Sept 26, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> Currently, JDO 2.2 trunk depends on DataNucleus SNAPSHOT. When we
> prepare JDO 2.2. trunk for a beta we should probably depend on a
> DataNucleus beta release. Then, once the JCP approves the JDO 2.2
> Change Log (October 13), we can spin an official release of both JDO
> 2.2 and the RI DataNucleus.
DataNucleus AccessPlatform 1.0.1 was released on Tuesday this week (none
of this "beta" stuff ;-) ), and 1.1.0.M1 was similarly released then. You
should get the same TCK results with either (but makes more sense to base
a release on 1.0.1). Note that if using DN 1.1 the "java5" plugin has gone
and everything is JDK1.5+, and there's a separate "jpa" plugin.
--
Andy
DataNucleus (http://www.datanucleus.org)
Minutes: JDO TCK Conference Call Friday, Sept 26, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Richard Schilling, Craig
Russell
Agenda:
1. TCK query tests (JDO-580) Michael attached a patch with two new
test classes and all of the tests fail. Since the failing tests are
for new features that are not well documented. AI Michael update the
JIRA with the failures and assign the JIRA to Craig.
2. JDOHelper tests (JDO-582, JDO-557) Nothing new to report.
3. Other issues
JDO 2.2 beta can be prepared for a vote. The new test case for
isolation level has a new patch supplied by Andy. AI Craig review and
approve the patch.
Currently, JDO 2.2 trunk depends on DataNucleus SNAPSHOT. When we
prepare JDO 2.2. trunk for a beta we should probably depend on a
DataNucleus beta release. Then, once the JCP approves the JDO 2.2
Change Log (October 13), we can spin an official release of both JDO
2.2 and the RI DataNucleus.
The alternative would be to simply make a final release once the JCP
approves. But it might be a good idea to spin a beta.
Thoughts?
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sept 26, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 26 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. TCK query tests (JDO-580)
2. JDOHelper tests (JDO-582, JDO-557)
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 17, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Richard Schilling, Craig
Russell
Agenda:
1. JDO 2.2 release status: Voting is scheduled to be completed today.
We have enough +1 votes to release, but would still like everyone to
vote!
2. JDO 2.3 planning: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10630&fixfor=12313404
has some open issues. AI Craig update https://issues.apache.org/jira/browse/JDO-556
with the discussion of how to implement this.
3. Other issues
Are we using the latest version of Derby for the TCK? AI Michael
investigate and write a JIRA issue if we need to update the version.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Nov 7, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Methods in the result of an JDOQL query. Seems to be agreement
that this is useful; volunteers for implementing in the Reference
Implementation are hereby solicited.
2. (JDO-591) Enhancer Invocation API. Feedback and discussion are
needed for this item. Seems that the most obvious use case is for
Netbeans and Eclipse plugins. An implementation might use a services
entry to advertise its support. AI everyone provide some feedback on
the JIRA.
3. (JDO-610) Support Nested Transaction or savePoint in JDO 2.3.
Feedback from the community and Reference Implementation is needed. AI
everyone provide some feedback on the JIRA.
4. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies. AI Craig file a JIRA with Maven to track the issue.
5. TCK issues (JDO6-11, 613) JDO-611 is a bug in the TCK which exposes
a bug in the RI. AI Michelle according to policy, we need to make a
branch 2.2.1 to fix the bug, and port the fix to the trunk which is
set up for 2.3-SNAPSHOT. AI Datanucleus fix the bug once the TCK test
has been fixed. Once Datanucleus fixes the bug, the 2.2.1 branch
should reference the Datanucleus release that contains the fix.
JDO-613 patch needs review by a committer and should be checked into
2.2.1 and trunk once approved. AI volunteer needed to review and
commit the fix.
6. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov 21, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. (JDO-591) Enhancer Invocation API: A number of comments have been
posted to the JIRA, mostly positive with regard to using output
directory as a switch to tell enhance-in-place; specifying a class
loader for the input classes; more discussion needed on using file
names vs. resource names.
There is a maven plugin that provides enhancement services that would
be good to review as a use-case for the enhancer API.
2. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies: The trunk has been updated with the suggested patch. One
additional suggestion is to add a pom.xml and explicitly publish api2
as a maven 2 project. This works for the api2 component but isn't
applicable to the other projects. For the tck2, you need to use the
source distribution.
3. Other issues
Deprecate api2-legacy. Any objections to requiring jdk1.5 for JDO 2.3
and subsequent releases? No more planned releases of api2-legacy. AI
Michael file a JIRA with some implementation details for the project
if we deprecate it.
JDO-615 Metadata specification API: Andy suggests adding a
programmatic way to specify metadata. Seems like a good idea
especially for dynamically created classes. AI everyone comment on the
JIRA.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Note: No JDO TCK Conference Call Friday, Nov 28
Posted by Michelle Caisse <Mi...@Sun.COM>.
There will be no conference call on Friday November 28 due to the U.S.
Thanksgiving holiday.
-- Michelle
Re: Querydsl release 0.4.4
Posted by Timo Westkämper <ti...@mysema.com>.
Hi Andy.
> Hi Timo,
>
>
>> The newest release of Querydsl has now support for subqueries for JDOQL.
>> Is there some kind of conformance test suite to validate Querydsl as a
>> JDOQL implementation?
>>
>
> But QueryDSL isn't a JDOQL implementation though is it ? You presumably take
> your API input and convert it into a single-string form of JDOQL for use by
> the actual JDOQL implementation (e.g DataNucleus). You don't execute the
> query on the underlying datastore.
>
> The JDO2 TCK test compliance with the JDO2 spec ... for the JDO
> implementation. Specifically, those tests (in Apache JDO SVN) will use the
> JDOQL API and single-string form, and test the results from those queries
> (after execution on the datastore).
>
Yes, you are correct. Querydsl is just an API layer on top of JDO. What
I meant is that I could use the JDO2 TCK tests to make sure that all
queries can be constructed via Querydsl.
It would be at the same time a reference on how Querydsl queries are
serialized into single string JDOQL form.
Br,
Timo Westkämper.
>
>
>
JDOQL Delete support in Querydsl
Posted by Timo Westkämper <ti...@mysema.com>.
Hello.
Just wanted to let you know that Querydsl v 0.5.4 has now support for
Delete clauses in the JDOQL module.
Here are examples how to use it :
http://source.mysema.com/static/querydsl/0.5.4/reference/html/ch02.html#d0e204
Br,
Timo Westkämper.
Re: Indexed list access for JDO 2.3?
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Timo,
I have no problem putting it into 2.3 as long as:
1. It's implemented.
2. It's got a TCK test case.
My plate is full with other 2.3 activities. Can you follow up with
Andy and create a TCK test?
Thanks,
Craig
On Dec 11, 2009, at 10:17 AM, Timo Westkämper wrote:
> Hi.
>
> Is the following feature going to be implemented for JDO 2.3 : https://issues.apache.org/jira/browse/JDO-633
>
> Best regards,
> Timo Westkämper.
>
> --
> Timo Westkämper <ti...@mysema.com>
> Mysema Ltd, Vilhonkatu 5 A, 00100 Helsinki, Finland
> Mob. +358 (0)40 591 2172 Internet: http://www.mysema.com
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Indexed list access for JDO 2.3?
Posted by Timo Westkämper <ti...@mysema.com>.
Hi.
Is the following feature going to be implemented for JDO 2.3 :
https://issues.apache.org/jira/browse/JDO-633
Best regards,
Timo Westkämper.
--
Timo Westkämper <ti...@mysema.com>
Mysema Ltd, Vilhonkatu 5 A, 00100 Helsinki, Finland
Mob. +358 (0)40 591 2172
Internet: http://www.mysema.com
Re: Querydsl release 0.4.4
Posted by Andy Jefferson <an...@datanucleus.org>.
Hi Timo,
> The newest release of Querydsl has now support for subqueries for JDOQL.
> Is there some kind of conformance test suite to validate Querydsl as a
> JDOQL implementation?
But QueryDSL isn't a JDOQL implementation though is it ? You presumably take
your API input and convert it into a single-string form of JDOQL for use by
the actual JDOQL implementation (e.g DataNucleus). You don't execute the
query on the underlying datastore.
The JDO2 TCK test compliance with the JDO2 spec ... for the JDO
implementation. Specifically, those tests (in Apache JDO SVN) will use the
JDOQL API and single-string form, and test the results from those queries
(after execution on the datastore).
--
Andy (DataNucleus - http://www.datanucleus.org)
Querydsl release 0.4.4
Posted by Timo Westkämper <ti...@mysema.com>.
Hi.
The newest release of Querydsl has now support for subqueries for JDOQL.
Is there some kind of conformance test suite to validate Querydsl as a
JDOQL implementation?
Release specific Querydsl documentation is found here :
http://source.mysema.com/display/querydsl/Documentation
Some query examples using JDOQL can be found on our SVN server :
https://source.mysema.com/svn/mysema/projects/querydsl/trunk/querydsl-jdoql/src/test/java/com/mysema/query/jdoql/
Br,
Timo Westkämper.
Support for if-then-else in JDOQL
Posted by Timo Westkämper <ti...@mysema.com>.
Hello.
I am implementing the shortcut form for if-then-else (x ? y : c) in
Querydsl.
Is there support for it in JDOQL? If not, could it be added?
Br,
Timo Westkämper.
--
Timo Westkämper <ti...@mysema.com>
Mysema Ltd, Vilhonkatu 5 A, 00100 Helsinki, Finland
Mob. +358 (0)40 591 2172
Internet: http://www.mysema.com
Re: Minutes: JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by Timo Westkämper <ti...@mysema.com>.
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<Customer> cust = q.from(Customer.class);
Join<Customer, Order> order = cust.join(Customer_.orders);
Join<Order, Item> 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<String> 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
Minutes: JDO TCK Conference Call Friday, Feb 13, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michael Bouschen, Michelle Caisse, Craig
Russell
Agenda:
1. Enhancer specification proposal. 1. -ecp is good but inconsistent
in the text. 2. Should describe options in the same order as listed in
both places. AI Craig write an enhancer Main class and upload to
JIRA. Feedback needed from other experts.
2. Other issues
Query.cancel changes have been checked in. Don't appear to be any
issues. AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading (multithreaded flag doesn't
need to be true to perform a Query.cancel).
How might an application dynamically tune itself by tracking field
access by use-case? Need a few things: 1. identify which use case
you're in; might have to analyze the stack frames at the time a use-
case was needed, e.g. whenever an instance needed to be fetched or a
query executed 2. associate a use case with a fetch plan 3. modify the
fetch plan based on runtime experience, e.g. which fields were
accessed by the use-case. AI Matthew discuss on email.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Feb 27, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
It looks like I'll be unable to attend this week. Please carry on in
my absence.
Craig
On Feb 26, 2009, at 7:08 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, February 27 at 9 am PST 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. Support for streams https://issues.apache.org/jira/browse/JDO-625
> 2. Query behaviour independent of transactional boundaries https://issues.apache.org/jira/browse/JDO-624
> 3. Other issues
>
> Action Items from weeks past:
>
> [Feb 13 2007] AI Craig update the spec and make clear the
> relationship between Query.cancel and multithreading.
>
> [Feb 13 2007] AI Matthew discuss on email method by which an
> application might dynamically tune itself by tracking field access
> by use-case?
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 6, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Support for streams https://issues.apache.org/jira/browse/JDO-625
Seems like a good idea. Any implementation issues?
Should we add an optional feature flag or make it required?
Should we restrict use of the PersistenceManager (including accessing
unloaded fields of the same or other instances managed by the same
PersistenceManager) while the user is reading the stream?
2. Query behaviour independent of transactional boundaries https://issues.apache.org/jira/browse/JDO-624
.
Seems reasonable to have a flag that mandates the behavior of query
after commit. It's not generally good for the HOLD_CURSORS_OVER_COMMIT
flag to be set in a query, since it requires that the Connection be
held by the PersistenceManager for longer than it otherwise would be.
Where would the flag go? Query? Transaction? PersistenceManager?
PersistenceManagerFactory? Where to get defaults?
Should the feature be optional or required?
Also need to specify the behavior of the Query results so the user can
close them explicitly when done. Otherwise, closing the
PersistenceManager would close the Query (currently not specified, but
implied).
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 6, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Support for streams https://issues.apache.org/jira/browse/JDO-625.
Resources are an issue since the RI doesn't currently support
streaming blobs or clobs. Looks like this feature would be an optional
feature; first thing to do is to remove InputStream and Reader from
the list of proscribed java interfaces as persistent field types.
2. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Mar 20, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. M2 repo error. AI Craig follow up and if no response consult with
the repository folks in Amsterdam.
2. (JDO-623) Query cancel and timeout support (https://issues.apache.org/jira/browse/JDO-623
)
Looks good, including the spec updates. One thing maybe missing:
setQueryTimeoutMillis on PM, to apply to all queries created by the
PM. AI Michael update JIRA and add a patch.
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Mar 27, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> Now might be a good time to migrate to maven 2 for the project.
+1 to move to M2 *if resource is available to do it*.
I switched DataNucleus a few months ago, and am maintaining our M1 build
process and repository really only for the TCK's benefit.
> Should the enhancer API be a required part of an implementation? It
> would make writing the tck easier, since the enhancer is currently the
> biggest difference among implementations.
+1 to make it mandatory. Any current implementation not have an enhancer?
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: Minutes: JDO TCK Conference Call Friday, May 22, 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
Sorry I wasn't on the call -- the family & I were camping for the
holiday weekend and were out of range. Can someone tell me what the
problem with the patch is? There was really nothing more to it than
renaming ComponentMetadata to TypeMetadata and the associated ripples.
EOL issue or some other?
On Fri, May 22, 2009 at 10:14 AM, Craig L Russell <Cr...@sun.com> wrote:
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. New comments on MetaData specification API
> https://issues.apache.org/jira/browse/JDO-615
>
> This seems to be a good idea, since "component" is so overloaded, and "type"
> has a specific meaning in Java. It's still ok to change since the API is
> "early access" status.
>
> AI Everyone with an opinion: update the JIRA with your comments.
>
> The patch doesn't seem quite correct...
>
> 2. Other issues
>
> The instructions on how to release have been updated 22-May-2009 to include
> instructions on synchronizing the m1-ibiblio-rsync-repository.
>
> Several changes are needed in the specification:
>
> There were a small number of cosmetic changes in the 2.3 specification, to
> add a space after the ending period of sentences. Unfortunately, these are
> marked as changes with change bars.
>
> Remove blank from before the fourth bullet p. 126.
>
> SerializeRead property description on p. 158 should state the effect on the
> transaction mode (none) and on the connection (optimistic transaction will
> retain the connection until the end of the transaction since the connection
> holds the lock).
>
> Same discussion in the Query section on p. 171. We need to decide if the
> SerializeRead property should be copied or serialized, so might need to
> update section 14.5 on p. 167.
>
> The 2.3 versions of orm, jdoquery, and jdoconfig need to be updated in the
> spec. The jdoquery should add the timeout option. The 2.3 version of jdo
> also needs to add jdoquery timeout. What about the SerializeRead for the xml
> versions of jdoquery?
>
> The query timeout needs to be added to the query metadata API p. 305.
>
> 27.4 The enhancer API is now defined so this paragraph needs to be edited.
>
> 27.5 The fetch plan API is now defined so this paragraph needs to be edited.
>
> 27.7 There are managed relationships so this paragraph needs to be edited.
>
> The footer for 2.3 EA still has the date May 8.
>
> 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.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
--
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Re: Minutes: JDO TCK Conference Call Friday, Mar 27, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Correction: Matthew Adams joined the call in progress.
Craig
On Mar 27, 2009, at 12:08 PM, Craig L Russell wrote:
> Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
>
> Agenda:
>
> 1. M2 repo error. Should be a straightforward fix. This file was
> autogenerated a while back but never updated for recent releases. AI
> Craig upload a new version of the metadata file to the apache repo
> which then gets synced with the central repo.
>
> Now might be a good time to migrate to maven 2 for the project.
> Using maven 2, the metadata files would be generated correctly
> during packaging. Craig has already created a maven 2 pom for the
> api project; using maven 2 for the tck would require more work,
> probably creating a maven 2 plugin to handle the logic of running
> the iut and ri tests.
>
> 2. (JDO-623) Query cancel and timeout support (https://issues.apache.org/jira/browse/JDO-623
> ) Michael has added patches to the JIRA. AI everyone review
> Michael's comments and patches to the JIRA.
>
> 3. runtck.iut There have been issues running the RI as the iut. AI
> Michelle see if the runtck.iut still works with DataNucleus.
>
> 4. Other issues
>
> Should the enhancer API be a required part of an implementation? It
> would make writing the tck easier, since the enhancer is currently
> the biggest difference among implementations.
>
> Should the tck support the user's choice of maven 1.0.2 or 1.1?
> Seems like maven 1.1 works well enough to make it a requirement. AI
> Michael file a JIRA to update the README for the tck.
>
> Matthew Adams sent an email last week regarding fetch notifications
> (see action item below). AI everyone read and react to the proposals.
>
> There is renewed interest (e.g. cloud computing) in persistence APIs
> that don't have a fully ACID compliant, fully featured SQL back end,
> and yet the data is not simply key-value blob storage. This might be
> a good fit for JDO, assuming that we can adapt the data model and
> query model to make some features optional. Something like a profile
> approach (list a group of features that are required for the basic
> profile distinct from the features that the full profile needs).
>
> Action Items from weeks past:
>
> [Feb 13 2007] AI Craig update the spec and make clear the
> relationship between Query.cancel and multithreading.
>
> [Feb 13 2007] AI Matthew discuss on email method by which an
> application might dynamically tune itself by tracking field access
> by use-case?
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 27, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. M2 repo error. Should be a straightforward fix. This file was
autogenerated a while back but never updated for recent releases. AI
Craig upload a new version of the metadata file to the apache repo
which then gets synced with the central repo.
Now might be a good time to migrate to maven 2 for the project. Using
maven 2, the metadata files would be generated correctly during
packaging. Craig has already created a maven 2 pom for the api
project; using maven 2 for the tck would require more work, probably
creating a maven 2 plugin to handle the logic of running the iut and
ri tests.
2. (JDO-623) Query cancel and timeout support (https://issues.apache.org/jira/browse/JDO-623
) Michael has added patches to the JIRA. AI everyone review Michael's
comments and patches to the JIRA.
3. runtck.iut There have been issues running the RI as the iut. AI
Michelle see if the runtck.iut still works with DataNucleus.
4. Other issues
Should the enhancer API be a required part of an implementation? It
would make writing the tck easier, since the enhancer is currently the
biggest difference among implementations.
Should the tck support the user's choice of maven 1.0.2 or 1.1? Seems
like maven 1.1 works well enough to make it a requirement. AI Michael
file a JIRA to update the README for the tck.
Matthew Adams sent an email last week regarding fetch notifications
(see action item below). AI everyone read and react to the proposals.
There is renewed interest (e.g. cloud computing) in persistence APIs
that don't have a fully ACID compliant, fully featured SQL back end,
and yet the data is not simply key-value blob storage. This might be a
good fit for JDO, assuming that we can adapt the data model and query
model to make some features optional. Something like a profile
approach (list a group of features that are required for the basic
profile distinct from the features that the full profile needs).
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, April 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. M2 repo error. A new file was uploaded to the ibilio rsync
repository in Apache and is awaiting sync to ibiblio. AI Craig follow
up with "repo man". The ibiblio site appears to be down at this point.
2. Embedded object and evict. More email discussion on this topic from
David, Craig, and Christiaan. AI Craig reply to latest post from
Christiaan.
3. runtck.iut. The problem was that the change from jpox to
datanucleus modified the runtck.ri but the runtck.iut was not
similarly modified. A fix was uploaded to the svn repo. Done.
4. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, April 10, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
I'll be in transit during the call. I'll try to dial in but no
promises...
Craig
On Apr 9, 2009, at 8:56 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, April 10 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. Embedded object and evict
> 2. Fetch notifications
> 3. Other issues
>
> Action Items from weeks past:
>
> [Feb 13 2007] AI Craig update the spec and make clear the
> relationship between Query.cancel and multithreading.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, April 17, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Apr 18, 2009, at 2:25 AM, Andy Jefferson wrote:
>> 3. JDO 2.3 beta? Andy has proposed we look at releasing 2.3, which
>> means deferring a number of items that are currently tagged as 2.3.
>> Test case coverage for the new items in 2.3 is weak. AI: everyone
>> respond to Andy's message of 15-Apr-2009. Volunteer to write test
>> cases so we can get this release out.
>
> My initial requirement was for "jdo2-api-2.3-beta.jar".
> I don't see that as meaning that the TCK needs a beta at the same
> time,
> just so that implementations have something in Maven repositories that
> they can build against. While the API jar is in beta we can add the
> missing tests; it just signifies a cut off in new features being
> added so
> implementations can develop the new features.
Thanks for clarifying what your intent was. If we get consensus that
this is what we want to do it's possible.
Other opinions?
Craig
>
>
> --Andy
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, April 17, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> 3. JDO 2.3 beta? Andy has proposed we look at releasing 2.3, which
> means deferring a number of items that are currently tagged as 2.3.
> Test case coverage for the new items in 2.3 is weak. AI: everyone
> respond to Andy's message of 15-Apr-2009. Volunteer to write test
> cases so we can get this release out.
My initial requirement was for "jdo2-api-2.3-beta.jar".
I don't see that as meaning that the TCK needs a beta at the same time,
just so that implementations have something in Maven repositories that
they can build against. While the API jar is in beta we can add the
missing tests; it just signifies a cut off in new features being added so
implementations can develop the new features.
--Andy
Minutes: JDO TCK Conference Call Friday, April 17, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Craig Russell
Agenda:
1. Support specification of exact class in SingleFieldIdentity https://issues.apache.org/jira/browse/JDO-630
Functionality is useful for the user to specify that the class is
known not to have subclasses for this instance. One issue is that the
classes are immutable (by design) so the boolean should be a
constructor parameter. The specification should note that if the class
has no subclasses, the implementation doesn't need the flag; it's only
for cases where the class has subclasses but the application knows
that the key matches the class exactly.
Another issue is the name for the flag. Exact might be too generic.
Perhaps boolean isExactTargetClass()
AI everyone review and comment on the JIRA.
P.S. the patch seems to include some extraneous stuff.
2. MetaData specification API - complete? https://issues.apache.org/jira/browse/JDO-615
AI: everyone see if there is still anything missing. AI: volunteer
needed to write a test case.
3. JDO 2.3 beta? Andy has proposed we look at releasing 2.3, which
means deferring a number of items that are currently tagged as 2.3.
Test case coverage for the new items in 2.3 is weak. AI: everyone
respond to Andy's message of 15-Apr-2009. Volunteer to write test
cases so we can get this release out.
4. Other issues
Query cancel appears to be complete from the api side but the
specification will need to add behavior for canceling a query that is
not executing and what exception to throw if the underlying connection
doesn't support cancel.
Life cycle of embedded instances still has some issues. Craig proposed
defining all SCO instances as transient; additional discussion in last
week's meeting minutes. AI: review and discuss on email.
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, April 24, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Craig Russell
Agenda:
1. Support specification of exact class in SingleFieldIdentity https://issues.apache.org/jira/browse/JDO-630
Overload the semantics of getObjectById(Object oid, boolean validate)
to enhance validate.
If user says validate false and abstract class, throw an exception.
No api change, just spec change.
2. JDO 2.3 beta https://issues.apache.org/jira/browse/JDO/fixforversion/12313404
3. https://issues.apache.org/jira/browse/JDO-619. Several items were
brought up in the comments but not discussed.
We need to discuss the comments in the JIRA before applying the patch.
AI Craig update JIRA to request patch be reverted.
4. Other issues.
https://issues.apache.org/jira/browse/JDO-580 Due to failures in the
RI, these tests have not been included.
https://issues.apache.org/jira/browse/JDO-623 What would a test case
look like? AI Michael update JIRA.
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, April 24, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 24 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. Support specification of exact class in SingleFieldIdentity https://issues.apache.org/jira/browse/JDO-630
2. JDO 2.3 beta https://issues.apache.org/jira/browse/JDO/fixforversion/12313404
3. https://issues.apache.org/jira/browse/JDO-619. Several items were
brought up in the comments but not discussed.
4. Other issues.
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 12, 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
I'm sorry that I've missed the last couple. New gig with stuff to do the
last two Fri mornings. Hopefully I'll make the next one.
-matthew
On Fri, Jun 12, 2009 at 3:03 PM, Craig L Russell <Cr...@sun.com>wrote:
> I am so sorry I totally spaced out and missed this call.
>
> Craig
>
>
> On Jun 11, 2009, at 8:36 PM, Michelle Caisse wrote:
>
> Hi,
>>
>> We will have our regular meeting Friday, June 12 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. Use JDO TCK to test Querydsl query creation?
>> 2. API required for enabling/disabling FOR UPDATE locking for SELECTs
>> https://issues.apache.org/jira/browse/JDO-619
>> 3. 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.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
--
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com<go...@gmail.com>
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Minutes: JDO TCK Conference Call Friday, May 8, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig
Russell
Agenda:
1. [VOTE] Release JDO2.3 "early access"
A few issues with the process: There is no wiki page describing the
testing process similar to http://wiki.apache.org/jdo/ReleaseTesting2dot2
AI Michael create a page http://wiki.apache.org/jdo/ReleaseTesting2dot3
to refer to the 2.3-ea testing. The description needs to be enhanced
to include building the api2(and other tck2 dependencies) jar(s) from
the source distribution.
Are there any issues on naming releases in OSGi? AI Matthew send mail
if any issues.
Andy's key needs to be in the KEYS file. AI Craig check this out and
the signatures/checksums.
2. JDO 2.3-ea : Release process/Maven 2 POM (https://issues.apache.org/jira/browse/JDO-596
) - any remaining issues? AI Craig respond to the issue.
3. Detecting inconsistencies of mapped-by declarations? Discussion
continues on email.
4. Other issues
Google AppEngine discussion on Java and JDO (BigTable). AI Matthew
send links to discussions.
There is a proposed change to the JCP rules. http://jcp.org/aboutJava/communityprocess/maintenance/jsr215/index.html
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: Correction: JDO TCK Conference Call Friday, May 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Correction: Michelle Caisse also attended.
Sorry for the miss.
Craig
On May 15, 2009, at 9:58 AM, Craig L Russell wrote:
> Attendees: Matthew Adams, Michael Bouschen, Craig Russell
>
> Agenda:
>
> 1. Latest JDO 2.3 spec -- comments?
>
> The JDO 2.3 bits have been published and we currently have four +1
> votes from DB PMC members and no other votes. The vote closes on
> Monday.
>
> Canceling a running query: what we specify should only be on the
> client side, not the server side. The spec has been updated slightly
> to clarify this:
>
> javax.jdo.option.QueryCancel
> The JDO implementation supports canceling a running query. The
> underlying datastore must also support canceling a running query.
> The cancel support in the datastore must at least free the client
> thread executing the query. The server cancel behavior is not
> specified.
>
> The strategy for specifying the metadata API is to copy and paste
> the java code into the specification in the same chapter as the
> annotations.
>
> 2. Other issues
>
> Does the change log include only 2.3 changes? No, the PROPOSED
> section has the 2.2 to 2.3 changes. The ACCEPTED section has the 2.0
> to 2.2 changes.
>
> Check out blog.matthewadams.me
>
> Action Items from weeks past:
>
> [Feb 13 2009] AI Craig update the spec and make clear the
> relationship between Query.cancel and multithreading. Done in latest
> spec dated 14-May-2009
>
> [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.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, May 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michael Bouschen, Craig Russell
Agenda:
1. Latest JDO 2.3 spec -- comments?
The JDO 2.3 bits have been published and we currently have four +1
votes from DB PMC members and no other votes. The vote closes on Monday.
Canceling a running query: what we specify should only be on the
client side, not the server side. The spec has been updated slightly
to clarify this:
javax.jdo.option.QueryCancel
The JDO implementation supports canceling a running query. The
underlying datastore must also support canceling a running query. The
cancel support in the datastore must at least free the client thread
executing the query. The server cancel behavior is not specified.
The strategy for specifying the metadata API is to copy and paste the
java code into the specification in the same chapter as the annotations.
2. Other issues
Does the change log include only 2.3 changes? No, the PROPOSED section
has the 2.2 to 2.3 changes. The ACCEPTED section has the 2.0 to 2.2
changes.
Check out blog.matthewadams.me
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading. Done in latest spec dated 14-
May-2009
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, May 29, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1. MetaData specification API patch https://issues.apache.org/jira/browse/JDO-615
Looks like the patch is good, just waiting for DataNucleus to approve
and commit.
2. runtck.iut and datanucleus trunk
There is a conflict if you want to run a different version of
DataNucleus as the iut while still running the standard version of
DataNucleus as the ri.
The issue appears to be running different versions of DataNucleus
without the benefit of a class loader manager like OSGi.
The solution is probably to run DataNucleus as the RI and change the
dependency in project.xml to the same version (not a snapshot).
3. Embedded object and evict
The discussion on the email list continues.
There is a way to find out if a field is embedded, using the new
Metadata API. So to solve the problem that Christiaan is facing, the
application can discover if fields are embedded and therefore need to
be treated as loaded by refreshing the owner or can be loaded directly.
Note that second class objects should be identified as embedded even
for reference types that default to embedded (e.g. Date, Integer,
Collection), not just fields that are explicitly identified as
embedded. AI everyone read the discussion on email and comment. A vote
will be coming up.
4. Other issues
There is a typo in the method name newExtensionMetaData in interface
Metadata. It should be newExtensionMetadata. AI Matthew write a patch;
use the same JDO-615 used for the other metadata API changes so it can
be picked up when DataNucleus applies the patch.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 12, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
I am so sorry I totally spaced out and missed this call.
Craig
On Jun 11, 2009, at 8:36 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, June 12 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. Use JDO TCK to test Querydsl query creation?
> 2. API required for enabling/disabling FOR UPDATE locking for
> SELECTs https://issues.apache.org/jira/browse/JDO-619
> 3. 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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, June 12, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Attendees: Michael Bouschen, Michelle Caisse
>
> 1. Use JDO TCK to test Querydsl query creation?
The Query test suite in the JDO TCK could be used to extract the JDOQL
and use this to generate a query. There is no way to inject the
generated JDOQL into the tests (without rewriting the tests) to compare
the actual against expected result. The schema installation mechanism of
the TCK can be used to set up the database to run tests against (maven
installSchema). The query tests expect certain instances to be in the
database. Based on the configuration files for the test
(src/conf/query.conf), instances whose properties are specified in xml
(src/testdata/org/.../pc/company/companyForQueryTests.xml,
companyForSubqueriesTests.xml) are installed in the database for each
test. Expected results, as well as components of the query, are
specified in an array in the test class. This allowed using the same
data to generate a single string JDOQL query and an API query. The
mechanism for reading and loading test data from xml files is in
src/java/org/.../query/QueryTest.java.
> 2. API required for enabling/disabling FOR UPDATE locking for SELECTs
> https://issues.apache.org/jira/browse/JDO-619
Not clear whether we need this functionality on the instance. When
would this be useful? Does it need to be invoked at the time the object
is read from the data store or later? There are multiple ways of
accessing an instance from the datastore? Is this feature needed for all
access methods? More discussion needed.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, June 19, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> JDO doesn't define an ordering constraint, it is reasonable to assume that
> in JDO a List is an "indexed" List, hence retains the users ordering.
The only case I can think of where there is no "index" column is where the
user specified <order mapped-by="elementField"/>. Can easily just restrict
the use of "List.get(i)" in JDOQL to only be supported for indexed Lists.
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: Minutes: JDO TCK Conference Call Friday, June 19, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Jun 20, 2009, at 2:52 AM, Andy Jefferson wrote:
>> http://issues.apache.org/jira/browse/JDO-633 Don't know how to do
>> this
>> since the absolute order is not required to be in the database, but
>> there might be a way to create the database language (e.g. SQL) to do
>> an ordered subselect and choose the "nth" item from the selection?
>> Database-specific SQL? Can we support this in all databases? Is there
>> a use-case?
>
> Don't understand. A List has an order (whether it is an "indexed"
> List, or
> an "ordered" List (using JPA-style ordering criteria)). The user
> puts items
> in the List and persists the List. The user then wants to grab
> element at
> index 2.
JDO doesn't require that absolute numbers be stored. So the item at
index 2 might have a row order value of 17. It's only in index
position 2 because there's also a row with row order value 3.
What I was (am) concerned about is that in order to get to the item at
index 2 an ordered subquery might be needed, and didn't (don't) know
the complexity for all the use cases to get the right answer.
If you're happy with implementing this, considering all the possible
places where get(2) might be used, then I'm happy. ;-)))
Craig
> Storing the order in the datastore, in some way, is essential to
> support (indexed) Lists, hence querying should be straightforward.
> Since JDO
> doesn't define an ordering constraint, it is reasonable to assume
> that in JDO
> a List is an "indexed" List, hence retains the users ordering.
>
> As far as testing goes, surely all you need to do is persist an
> object with a
> List with some elements in some order, and then do a query, assuming
> the same
> order as they had at the moment of persistence. Where does DB-
> specific SQL
> come into this ? surely that is the problem for the implementation.
>
>
>
> --
> Andy (DataNucleus - http://www.datanucleus.org)
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, June 19, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> http://issues.apache.org/jira/browse/JDO-633 Don't know how to do this
> since the absolute order is not required to be in the database, but
> there might be a way to create the database language (e.g. SQL) to do
> an ordered subselect and choose the "nth" item from the selection?
> Database-specific SQL? Can we support this in all databases? Is there
> a use-case?
Don't understand. A List has an order (whether it is an "indexed" List, or
an "ordered" List (using JPA-style ordering criteria)). The user puts items
in the List and persists the List. The user then wants to grab element at
index 2. Storing the order in the datastore, in some way, is essential to
support (indexed) Lists, hence querying should be straightforward. Since JDO
doesn't define an ordering constraint, it is reasonable to assume that in JDO
a List is an "indexed" List, hence retains the users ordering.
As far as testing goes, surely all you need to do is persist an object with a
List with some elements in some order, and then do a query, assuming the same
order as they had at the moment of persistence. Where does DB-specific SQL
come into this ? surely that is the problem for the implementation.
--
Andy (DataNucleus - http://www.datanucleus.org)
Re: No JDO TCK Conference Call Friday, Sep 4, 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
Darn it. I was actually going to attend today. I'll be out of town
for the next one and will have to miss it. :(
On Thu, Sep 3, 2009 at 9:32 PM, Michelle Caisse<mc...@sonic.net> wrote:
> Hi,
>
> The September 4 meeting is cancelled. We will meet again on September 11.
>
> -- Michelle
>
--
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Minutes: JDO TCK Conference Call Friday, June 19, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Other issues
http://issues.apache.org/jira/browse/JDO-615 How to test the metadata
API? To test that the implementation has represented the xml
correctly, write a program to read the xml metadata and compare the
results against the values read via the API.
http://issues.apache.org/jira/browse/JDO-630 Test case needed for
getObjectById with validate false. Proposed test case scenario was put
into the JIRA.
http://issues.apache.org/jira/browse/JDO-633 Don't know how to do this
since the absolute order is not required to be in the database, but
there might be a way to create the database language (e.g. SQL) to do
an ordered subselect and choose the "nth" item from the selection?
Database-specific SQL? Can we support this in all databases? Is there
a use-case?
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. JDO TCK project.properties changes: JDK1.6 issue; using JDK1.5
causes TCK to fail to compile. There's a way to use profiles in maven
2, but we can also remove the enhancer from the compile class path. AI
Michael file a JIRA.
2. DataNucleus dependencies in JDO TCK: The DataNucleus 1.1-SNAPSHOT
doesn't have the latest TypeMetadata changes, so the version needs to
be updated in the pom.
3. Other issues
4. Is there a DataNucleus version that supports query canceling?
JDOQL2 supports query cancel but doesn't support unbound variables
that are needed for the query cancel test.
5. Need assertions for query cancel and query timeout. AI Craig
include assertions in the specification.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Oct 2, 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
Won't make it this morning, no changes to report for instance callback
annotations...
On Thu, Oct 1, 2009 at 7:56 PM, Michelle Caisse <mc...@sonic.net> wrote:
> Hi,
>
> We will have our regular meeting Friday, October 2 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. javax.jdo.Enhancer fails to pass full path name for the file arguments
> https://issues.apache.org/jira/browse/JDO-641
> 2. Query timeout test still fails.
> https://issues.apache.org/jira/browse/JDO-623
> 3. Add annotations for instance callbacks.
> https://issues.apache.org/jira/browse/JDO-638
> 4. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
--
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Minutes: JDO TCK Conference Call Friday, July 24, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Attendees: Craig Russell, Michelle Caisse
1. Using resource names vs file names: Add javax.jdo.JDOEnhancerMain to
call the enhancer via standard API
https://issues.apache.org/jira/browse/JDO-621
Agree that resource names which don't reference an exact file location
are a good idea. Distinguishing files from directories will depend on
the suffix (extension). AI: Craig update bug report with the revised plan.
2. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
Michelle did not encounter a compile failure with JDK 1.5.0.18 on
Linux. Will wait and see if Michael or others can reproduce the problem
again with a later version than 1.5.0_15. Craig volunteered to try
compiling on the Mac.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Oct 16, 9 am PDT
Posted by Erik Bengtson <er...@jpox.org>.
On Fri, Oct 16, 2009 at 7:21 PM, Craig L Russell <Cr...@sun.com>wrote:
> Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
>
> Agenda:
>
> 1. Update DataNucleus dependencies in tck2
> https://issues.apache.org/jira/browse/JDO-642
>
> It looks like we should go with 2.0.0-m3-SNAPSHOT for now. This give us the
> ability to make changes to DataNucleus to resolve issues. AI Michael track
> down the dependencies and update the project.xml.
>
> 2. Query timeout test - need option to test for support?
> https://issues.apache.org/jira/browse/JDO-623
>
> As a reminder, the original JIRA issue was opened by Andy in February:
>
> JDO doesn't have a mechanism to stop queries from overrunning. JPA2 now
>> allows
>> a persistence property to allow timing them out, and most JDO
>> implementations
>> have allowed this as an extension since JDO1. It would make sense for JDO
>> (2.3) to have the same or a variation. I propose having the following
>>
>> Simple PMF property "javax.jdo.option.queryTimeout" to specify the number
>> of millisecs (or secs) before any query is timed out. Throw a
>> QueryTimeoutException (extends JDOException) when the timeout happens.
>>
>> Add methods Query.setTimeout(int), Query.getTimeout() to allow
>> setting/retrieving the timeout interval on a per-query basis.
>>
>> Add method Query.cancel() to cancel any running query. If an
>> implementation doesn't support cancelling of queries then it should throw a
>> JDOUnsupportedOptionException. Any query execute() that is cancelled will
>> throw a QueryInterruptedException (extends JDOUserException).
>>
>
>
> Subsequently, Andy wrote:
>
> You mean the datastore itself always supports a timeout?or do you mean a
>> JDO
>> implementation can manage a timeout itself ? The former is clearly not the
>> case since there are a wide variety of datastores, some file based, with
>> APIs
>> that don't provide such things as timeouts.
>>
>
> Low-function datastores (file systems, etc.) don't need a timeout because
> the query is executed by the JDO implementation itself. And the JDO
> implementation can add hooks to the execution processing so as to time out
> the function.
>
>
Filesystem Datastores need timeout because: a) Connection: You might need
take an exclusive lock in the file b) Operation: it might take too long to
perform the operation because of the amount of data to process
High-function datastores generally provide a user-specified timeout. Access
> to the underlying connection to the datastore is mediated by the JDO
> implementation, so the expectation is that the JDO implementation will pass
> the user's timeout request directly to the underlying connection.
>
> RDBMS datastores do allow a
>> timeout to be set yet JDBC is so imprecisely defined that you get an
>> SQLException and so have no simple way of knowing that it was a timeout
>> (without having to play around with arbitrary JDBC error numbers).
>>
>
> This is precisely why we want to define the timeout at the JDO user level
> and not require the user to play around with JDBC. There are many features
> in JDO that get translated into datastore-specific methods and this is just
> one more. I expect that for a specific datastore, a query timeout will have
> a specific SQL error code, even if not all datastores implement the same
> codes.
>
> PS, what is the definition of the timeout ? Is it the time taken to
>> communicate with the datastore ?
>>
>
> The user is in control of activities inside the VM, and there's no need for
> a JDO-specific timeout for these. What we want to influence is what happens
> once the query leaves the JDO implementation. So the timeout would be on the
> JDBC statement.execute call.
>
I disagree twice.
1) You suggest the user should handle the timeout differently per database,
sometimes set a timeout on the JDO interface, and sometimes create a timer
on the JVM level. This is not a transparent API anymore.
2) You take the responsibility from the JDO implementation to handle end2end
issues, instead you delegate the responsibility to the driver, if any. You
can delegate the responsability to a driver, but JDO is accountable for it
and must ensure the timeout given by the user is respected.
A concrete example of a driver bug handling timeouts: sometimes Oracle DB
sends a RESET to the driver, but somehow it's ignored since the data is
being transmitted and the RESET just came in between, the driver simple
waits for more data indefinitely. This bug causes threads to wait and
eventually you get errors such as outofmemory.
> or is it the total time for the query
>> execution (which may include compilation) ?
>>
>
> Since the user can compile the query, the timeout should just apply to the
> database processing and not include the preparation or post-query
> processing.
>
>
I dont agree. The user sets a timeout on the total execution of the
operation, and not only on part of it. For example DataNucleus can compile
and evaluate queries in memory, so it never leaves the JDO implementation.
In my opinion we should have two timeout settings: connection timeout and
execution timeout. Execution timeout includes connection timeout.
To me it's also clear that these timeouts should be applicable to all JDO
persistence operations and not only to the query.
However, you might want to mirror JPA functionality, but it's too RDBMS
minded.
Erik
No JDO TCK Conference Call Friday, Sep 4, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
The September 4 meeting is cancelled. We will meet again on September 11.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Sep 11, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. Add javax.jdo.JDOEnhancerMain to call the enhancer via standard API
> https://issues.apache.org/jira/browse/JDO-621 Comments on new patch?
>
> Instead of implementing Constants, should we change Enhancer to
> statically import the constants that are used? AI Craig investigate
> best practice and update if it looks like a good change.
>
> Looks like we can also resolve
> https://issues.apache.org/jira/browse/JDO-591 as well.
>
> Now that the enhancer can enhance an entire directory, should we
> change the approach of listing every class file in the
> project.properties? A new JIRA should be filed for this. Michelle
> volunteered to own the JIRA.
I created a new JIRA: https://issues.apache.org/jira/browse/JDO-639.
Please take a look whether the JIRA covers all the issues. I left the
field "Fix Version/s" field blank, is this JIRA for "JDO 2 maintenance
release 3"?
Regards Michael
>
>
> 2. Add annotations for instance callbacks
> https://issues.apache.org/jira/browse/JDO-638 This is an interesting
> feature but needs some additional work (TCK and RI).
>
> 3. tck2 does not compile with JDK 1.5
> https://issues.apache.org/jira/browse/JDO-635 Issue is ready to be
> closed. Any last comments? Good to go.
>
> 4. Other issues
>
> We're about to close the Maintenance Release. Naming issue of JCP
> Maintenance Revision 4 and JDO Maintenance Release 2.3 to be discussed
> next week.
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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, Sep 11, 9 am PDT
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Add javax.jdo.JDOEnhancerMain to call the enhancer via standard API https://issues.apache.org/jira/browse/JDO-621
Comments on new patch?
Instead of implementing Constants, should we change Enhancer to
statically import the constants that are used? AI Craig investigate
best practice and update if it looks like a good change.
Looks like we can also resolve https://issues.apache.org/jira/browse/JDO-591
as well.
Now that the enhancer can enhance an entire directory, should we
change the approach of listing every class file in the
project.properties? A new JIRA should be filed for this. Michelle
volunteered to own the JIRA.
2. Add annotations for instance callbacks https://issues.apache.org/jira/browse/JDO-638
This is an interesting feature but needs some additional work (TCK
and RI).
3. tck2 does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
Issue is ready to be closed. Any last comments? Good to go.
4. Other issues
We're about to close the Maintenance Release. Naming issue of JCP
Maintenance Revision 4 and JDO Maintenance Release 2.3 to be discussed
next week.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Sep 18, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. tck enhancement should make use of feature to enhance an entire
directory - Does the JIRA capture all relevant information? https://issues.apache.org/jira/browse/JDO-639
2. Naming issue: different numbering for JCP Maintenance Revision 4
and JDO Maintenance Release 2.3
Looks like the only issue is the naming of the Maintenence Draft
Review, which will be Maintenance Draft Review 4 and Maintenance
Release 3 corresponding to JDO 2.3. The numbering scheme is off by one
due to our having had two Maintenance Draft Reviews for JDO 2.1.
3. Other issues
https://issues.apache.org/jira/browse/JDO-640 has errors running with
debug on, NPE with uninitialized fields
Should add this to JDO 2.3.
Status of query cancel tests with the latest DataNucleus
implementation. Looks like query cancel is now working, but query
timeout test still fails. AI update https://issues.apache.org/jira/browse/JDO-623
to show progress and get some feedback from DataNucleus folks.
Andy has updated the JDO/JPA comparison tables which stop with JDO
2.1. Are there any items from JDO 2.2 that should be included?
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Sep 25, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Sep 25, 2009, at 11:30 AM, Andy Jefferson wrote:
>> 1. TCK enhancement should make use of feature to enhance an entire
>> directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
>>
>> Seems to be a bug in the enhancer. The version being used is
>> DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
>> 2.3 tck?
>
> DataNucleus has never had support for passing in directory names to
> any
> method; if we knew what method is in use (on JDOEnhancer presumably)
> there
> may be chance of comment.
The javax.jdo.Enhancer goes through directories and extracts file
names, so the DataNucleus JDOEnhancer never sees them, just the names.
>
>> 2. Query timeout test still fails.
>> https://issues.apache.org/jira/browse/JDO-623
>>
>> Any idea when this feature will be enabled for DataNucleus?
>
> I see no failing tests using SVN trunk of Apache JDO. DataNucleus
> "JDOQL2"
> implementation has had QueryTimeoutException for a long time.
The test isn't in the configurations. You need to run it explicitly
via a -D flag.
Regards,
Craig
>
>
> Regards
> --
> Andy
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Sep 25, 9 am PDT
Posted by Andy Jefferson <an...@persistability.co.uk>.
> 1. TCK enhancement should make use of feature to enhance an entire
> directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
>
> Seems to be a bug in the enhancer. The version being used is
> DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
> 2.3 tck?
DataNucleus has never had support for passing in directory names to any
method; if we knew what method is in use (on JDOEnhancer presumably) there
may be chance of comment.
> 2. Query timeout test still fails.
> https://issues.apache.org/jira/browse/JDO-623
>
> Any idea when this feature will be enabled for DataNucleus?
I see no failing tests using SVN trunk of Apache JDO. DataNucleus "JDOQL2"
implementation has had QueryTimeoutException for a long time.
Regards
--
Andy
Re: Minutes: JDO TCK Conference Call Friday, Sep 25, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> 1. TCK enhancement should make use of feature to enhance an entire
> directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
>
> Seems to be a bug in the enhancer. The version being used is
> DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
> 2.3 tck?
DataNucleus has never had support for passing in directory names to any
method; if we knew what method is in use (on JDOEnhancer presumably) there
may be chance of comment.
> 2. Query timeout test still fails.
> https://issues.apache.org/jira/browse/JDO-623
>
> Any idea when this feature will be enabled for DataNucleus?
I see no failing tests using SVN trunk of Apache JDO. DataNucleus "JDOQL2"
implementation has had QueryTimeoutException for a long time.
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Re: Minutes: JDO TCK Conference Call Friday, Oct 9, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> If no objection from DataNucleus, Michael will update the TCK dependencies
> to version 1.1.6-SNAPSHOT for core and rdbms.
FYI 1.1.6 of core/rdbms are released. This is the final 1.1.x release. So
either switch to that or switch to 2.0.0-m2, or 2.0.0-m3-SNAPSHOT
> Discussion at last week's meeting suggested that all data stores
> support it. Need resolution on this question to know how to proceed.
You mean the datastore itself always supports a timeout ? or do you mean a JDO
implementation can manage a timeout itself ? The former is clearly not the
case since there are a wide variety of datastores, some file based, with APIs
that don't provide such things as timeouts. RDBMS datastores do allow a
timeout to be set yet JDBC is so imprecisely defined that you get an
SQLException and so have no simple way of knowing that it was a timeout
(without having to play around with arbitrary JDBC error numbers).
PS, what is the definition of the timeout ? Is it the time taken to
communicate with the datastore ? or is it the total time for the query
execution (which may include compilation) ?
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Re: JDO TCK Conference Call Friday, Oct 9, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi,
I've had a family emergency come up and I won't be able to dial into
the call this Friday.
My status: I've patched the Enancer and added test cases. I haven't
tried the patched Enhancer with the patched tck. Nothing else.
Regards,
Craig
On Oct 8, 2009, at 7:29 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, October 9 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. Update DataNucleus dependencies in tck2 https://issues.apache.org/jira/browse/JDO-642
> 2. Query timeout test still fails. https://issues.apache.org/jira/browse/JDO-623
> 3. Add annotations for instance callbacks. https://issues.apache.org/jira/browse/JDO-638
> 4. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Oct 23 9 am PDT
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Change JTA 1.1 dependency artifact id from "transaction-api" to
"jta" https://issues.apache.org/jira/browse/JDO-644
Seems innocuous enough. Probably should not change legacy projects
since we have no plans to ship them.
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
Erik replied to the discussion, and we need to continue to discuss on
email.
3. tck enhancement should make use of feature to enhance an entire
directory https://issues.apache.org/jira/browse/JDO-639
Patch looks good.
4. Run TCK using Maven2 for consistency https://issues.apache.org/jira/browse/JDO-647
5. Select new build/project tool https://issues.apache.org/jira/browse/JDO-632
- Close it for lack of volunteers?
See item 4 above. We're looking for someone who can spend some quality
time changing the tck2 build/test process to use maven2. The maven.xml
is pretty complex and it's not a simple task. Seems like the biggest
challenge is to learn enough about maven2 to be able to map the
features of the tck2 maven.xml to plugin functionality.
6. runtime2 project fails to compile https://issues.apache.org/jira/browse/JDO-648
Assigned to Michelle (thanks).
7. Query objects and hashCode() + equals() request from Jörg:
> it would be nice if the spec would mandate that implementations of
> javax.jdo.Query do correctly implement hashCode() and equals().
>
> Alternatively, Query.toString() could be required to return the
> single-string representation of the query, or some dedicated method
> was
> added to provide it.
>
> This would make it easier to e.g. implement some custom cache for
> query
> results, or, more generally, it would make it easier to put Query
> objects as keys into Maps.
As users execute mutator methods on queries, the string representation
would change. And the contract for hashCode and equals is that they
are immutable (for proper use in sets or map keys). So I don't see how
we can mandate that hashCode and equals rely in any internal state.
Having the single-string version of a query is useful but adds
implementation complexity. While there is a requirement for an
implementation to parse a single string query into executable form,
there's no current requirement to create the single string form from
the internal form.
It appears to me that if you want this functionality at the
application framework layer, then the framework can mandate that the
single string form be used and at the time the query is created, the
single string form be used as the key into a framework map.
8. Other issues
Michelle is still investigating query timeouts as they apply to SQL
standard datastores.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday: CANCELLED
Posted by Michelle Caisse <mc...@sonic.net>.
Tomorrow's conference call is cancelled. We will meet again on Friday,
November 13 at 9 am PST.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 13 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Change JTA 1.1 dependency artifact id from "transaction-api" to
"jta" https://issues.apache.org/jira/browse/JDO-644
Patch looks good. Ship it.
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
Issues needing resolution: Should there be a documented option in case
the JDO implementation or the underlying datastore doesn't support a
query timeout? Does the query timeout apply to all "datastore query"
operations including find by key, navigation, and loading lazy
collections? If the datastore has the JDBC standard second resolution,
and there is less than 1000 millis left in the timeout, what should be
the timeout set on the datastore query statement? AI Michael write up
issues with proposed solution.
3. Question re Support for if-then-else in JDOQL
This might make sense for a future release (it's probably too big to
fit into 2.3). AI Michael take a look at what changes would be needed
in the BNF, reply to the original email, and then discuss. The Java
conditional expression maps to the SQL CASE ELSE END expression. More
difficult for non-SQL datastores so it might involve an optional
feature.
4. Other issues
none.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Nov 20 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
NOTE: We will take a brief hiatus for Thanksgiving break; next call
will occur on December 4
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Query timeout in JDO / Update timeout
a. Should we have different settings for query/read versus insert/
update/delete? Jorg says that *update* operations might need their own
setting.
b. Should the timeout apply to *any* in-vm operations, or just to
datastore operations? The original rationale for timeout was
specifically to allow setting the underlying datastore timeout value.
c Should we rename the property/api something like DatastoreRead and
DatastoreWrite? This might make it more clear that queries,
getObjectById, refresh, and others are affected.
AI Craig update the JIRA with new proposal
2. Query objects and hashCode() + equals()
This issue looks like it has been resolved. If further action is
necessary, please file a JIRA.
3. Dependence of RI on JPA2
Looks like this issue is moot. Based on our changes to JDO 2.3 and the
fact that JPA2 is now in JCP vote, there are no timing issues.
4. Other issues
If-then-else support for JDOQL: It looks like JPA2 will support this;
SQL supports it; are there any issues with non-SQL datastores?
Action Items from weeks past:
AI Nov 13 08 Michael: Take a look at what changes would be needed in
the BNF to support for if-then-else in JDOQL, reply to the original
email, open a JIRA
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Dec 4, 9 am Pacific
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Query timeout in JDO / Update timeout (See latest email on the list
from Craig)
The proposal makes it clear that we're not trying to limit resources
in the VM but just when going to the datastore. There is no way to
limit the entire query processing by this proposal.
How would we point people in the direction of DatastoreReadTimeout if
they have QueryTimeout in mind?
What JDOException should be thrown in case of timeout for read, write,
query, delete? Possibly simply a JDODatastoreException? It's a burden
on the implementation to map all possible database result codes and
the user might not even need to know what the specific exception is.
AI Everyone please review the proposal so we can close this last issue
for 2.3.
2. Support for conditional operator in JDOQL https://issues.apache.org/jira/browse/JDO-650
Timo's latest comment is that case statements might be less tricky
than Java conditional expressions, but adding new features to JDOQL
that aren't Java is even more tricky. AI Michael reply to Timo's JIRA
comments.
3. Other issues
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Dec 11, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Query timeout in JDO / Update timeout - Done deal?
No negative feedback. Positive feedback from Jörg and Michael. AI
Craig prepare a patch for discussion of the details.
2. Other issues
Looks like there is agreement on the syntax of the conditional query
proposal. This would be for "the next release".
We should close JDO 2.3 pretty soon. Open JIRA issues:
https://issues.apache.org/jira/browse/JDO-557 AI Michelle update the
status
https://issues.apache.org/jira/browse/JDO-558 AI Craig test with
latest DataNucleus and update status
https://issues.apache.org/jira/browse/JDO-615 needs a simple test case
to exercise all public APIs. Volunteers?
https://issues.apache.org/jira/browse/JDO-616 will be taken care of
with the next printing of the spec
https://issues.apache.org/jira/browse/JDO-619 too late for 2.3. Review
for next release
https://issues.apache.org/jira/browse/JDO-623 AI Craig prepare a patch
with changes as discussed
https://issues.apache.org/jira/browse/JDO-630 needs a simple test
case. Volunteers?
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 8, 9 am PDT
Posted by mc...@sonic.net.
Sorry I missed the meeting. I got stuck in a long meeting at work.
-- Michelle
> apologies for the late notice for the delayed start of the meeting
>
> Attendees: Michael Bouschen, Craig Russell
>
> Agenda:
>
> 1. Query timeout in JDO / Update timeout
>
> https://issues.apache.org/jira/browse/JDO-623 There is a patch
> available that has been reviewed and looks ready for checkin. The RI
> appears not to have implemented anything except a stub.
>
> 2. Other issues
>
> https://issues.apache.org/jira/browse/JDO-630 Exact class for
> getObjectById should have a patch shortly
>
> https://issues.apache.org/jira/browse/JDO-558 Need to rerun this to
> see its current behavior with the RI
>
> https://issues.apache.org/jira/browse/JDO-557 Still waiting for
> Michelle to see if any progress
>
> https://issues.apache.org/jira/browse/JDO-615 Metadata API needs a
> simple test to verify that all methods are implemented to do something.
>
> These are the only issues still pending before release of JDO 2.3. The
> spec will need some substantial updates and these will be published
> when ready for review.
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Minutes: JDO TCK Conference Call Friday, Jan 8, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
apologies for the late notice for the delayed start of the meeting
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Query timeout in JDO / Update timeout
https://issues.apache.org/jira/browse/JDO-623 There is a patch
available that has been reviewed and looks ready for checkin. The RI
appears not to have implemented anything except a stub.
2. Other issues
https://issues.apache.org/jira/browse/JDO-630 Exact class for
getObjectById should have a patch shortly
https://issues.apache.org/jira/browse/JDO-558 Need to rerun this to
see its current behavior with the RI
https://issues.apache.org/jira/browse/JDO-557 Still waiting for
Michelle to see if any progress
https://issues.apache.org/jira/browse/JDO-615 Metadata API needs a
simple test to verify that all methods are implemented to do something.
These are the only issues still pending before release of JDO 2.3. The
spec will need some substantial updates and these will be published
when ready for review.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Jan 8, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
I'm running a bit late.
Can we start at 9:15 today?
Thanks,
Craig
On Jan 7, 2010, at 8:36 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, January 8 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. Query timeout in JDO / Update timeout
> 2. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Mar 26, 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
Once again, I won't be able to make this call. Perhaps, however, you
could add a discussion of JDO-651 to the agenda. I'm thinking that it
would be a JDO 2.4 thing at the earliest.
-matthew
On Thu, Mar 25, 2010 at 8:34 PM, Michelle Caisse <mc...@sonic.net> wrote:
> Hi,
>
> Please note :
> - The U.S. has switched to Daylight Saving Time..
>
> We will have our regular meeting Friday, March 26 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. Query Cancel TCK tests
> 2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
> https://issues.apache.org/jira/browse/JDO-557
> 3. Metadata tests
> 4. Spec updates
> 5. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
--
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Re: Minutes: JDO TCK Conference Call Friday, Mar 19, 11 am PDT
Posted by Awais Bajwa <aw...@gmail.com>.
I fully support the idea of David - it is needed.
Craig : you might be the best person to publish that article. I would be
happy to work with you on this.
Thanks
Awais Bajwa
On Thu, Mar 25, 2010 at 6:11 PM, David Jordan <da...@bellsouth.net>wrote:
>
> It would be good to get some new JDO articles written. I think it would be
> valuable to have articles that compare JDO with JPA and Hibernate, to show
> the simplicity of the code and queries, etc. People think JDO went away
> largely because JPA came along with the full backing of Sun, Oracle, IBM,
> the EJB community. It has seemed to me that Hibernate is the primary
> technology people seem to be using in my area, many have not moved to JPA.
> They also say they think JDO no longer exists, I point out that the
> committee is still actively refining the standard, etc. It would be good to
> get some JDO success stories published by those that are deploying systems
> with it...
>
> And having an article showing use of the JDO API, with an underlying
> non-SQL backend, would be useful to get the non-SQL camp interested in
> giving it a second look...
>
>
> On Mar 25, 2010, at 12:37 PM, Matthew Adams wrote:
>
> I think the second coming is getting close...
>>
>> http://www.sfjava.org/messages/boards/thread/8463961?thread=8463961
>>
>> I'm hearing about more and more people interested in the NoSQL
>> (http://en.wikipedia.org/wiki/NoSQL) movement. Interestingly, there
>> is not a single mention of JDO or DataNucleus on that page.
>>
>> -matthew
>>
>
>
--
Awais Bajwa
+1-862-222-6680
http://www.linkedin.com/pub/awais-bajwa/4/82a/2b9
Re: Minutes: JDO TCK Conference Call Friday, Mar 19, 11 am PDT
Posted by David Jordan <da...@bellsouth.net>.
It would be good to get some new JDO articles written. I think it
would be valuable to have articles that compare JDO with JPA and
Hibernate, to show the simplicity of the code and queries, etc. People
think JDO went away largely because JPA came along with the full
backing of Sun, Oracle, IBM, the EJB community. It has seemed to me
that Hibernate is the primary technology people seem to be using in my
area, many have not moved to JPA. They also say they think JDO no
longer exists, I point out that the committee is still actively
refining the standard, etc. It would be good to get some JDO success
stories published by those that are deploying systems with it...
And having an article showing use of the JDO API, with an underlying
non-SQL backend, would be useful to get the non-SQL camp interested in
giving it a second look...
On Mar 25, 2010, at 12:37 PM, Matthew Adams wrote:
> I think the second coming is getting close...
>
> http://www.sfjava.org/messages/boards/thread/8463961?thread=8463961
>
> I'm hearing about more and more people interested in the NoSQL
> (http://en.wikipedia.org/wiki/NoSQL) movement. Interestingly, there
> is not a single mention of JDO or DataNucleus on that page.
>
> -matthew
Re: Minutes: JDO TCK Conference Call Friday, Mar 19, 11 am PDT
Posted by Matthew Adams <ma...@matthewadams.me>.
I think the second coming is getting close...
http://www.sfjava.org/messages/boards/thread/8463961?thread=8463961
I'm hearing about more and more people interested in the NoSQL
(http://en.wikipedia.org/wiki/NoSQL) movement. Interestingly, there
is not a single mention of JDO or DataNucleus on that page.
-matthew
Re: Minutes: JDO TCK Conference Call Friday, Jan 29, 9 am PDT
Posted by Andy Jefferson <su...@datanucleus.com>.
> 2a. Latest DataNucleus seems to have a problem...
Actually the problem is in Derby in its inability to return a list of
indexes from a schema beyond a certain size. This was raised on Derby back
in about 2006. The issue arose its head again by enabling some additional
functionality, prior to having the time to add the PMF prop to enable it.
That was in DN SVN about 20 hours ago, so in next nightly build.
Minutes: JDO TCK Conference Call Friday, Jan 29, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
NOTE: There will be no meeting next week Friday 5-Feb-2010.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Query cancel and timeout support: Review patch. https://issues.apache.org/jira/browse/JDO-623
The patch looks good. Works with Wednesday's DataNucleus build. OK to
check in.
2. Other issues
2a. Latest DataNucleus seems to have a problem...
[java] RUN Jdoconfig.testGetPMFNamedSpacesOverrides
[java] RUN Persistence.testGetPMFfromNamedPU <== hangs
This test seems to be in a loop running at 100% CPU. Michelle reports
that on Linux JDK 1.5 the test takes half an hour; Craig on MacOSX JDK
1.5 hasn't waited that long; Michael on Windows JDK 1.6 also seems hung.
This is with the latest (Friday AM PST) drop of DataNucleus. [1]
2b. Final JIRA issues before release:
JDO-557 Michelle will do this one
JDO-615 Craig will do this one
JDO-623 Michael will do this one
JDO-616 Michelle will do this one
2c.
The strategy for updating the specification is to copy the changes
since the May 18 version into a text file and update it for review by
the expert group before applying it to the pdf.
[1] 18:12:28,437 (main) INFO [DataNucleus.JDO] - Exception thrown
org.datanucleus.exceptions.NucleusUserException: There is no available
StoreManager of type "". Please make sure you have specified
"datanucleus.storeManagerType" correctly and that all relevant plugins
are in the CLASSPATH
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Running JDO TCK on Eclipse
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Ilan,
The 2.2 TCK (still) uses maven 1. I found a plugin for Netbeans to
support projects with maven 1 format but haven't found one for Eclipse.
So I use Eclipse (or Netbeans) as an editor and use the command line
to actually execute the tests.
So I don't know how to help you without rewriting the tck in maven 2,
which is on the list but not being implemented due to a lack of
volunteers.
Best regards,
Craig
On Mar 8, 2010, at 3:42 AM, Ilan Kirsh wrote:
> Hi,
>
> I am looking for instructions on how to run the JDO TCK 2.2 on
> Eclipse.
> Particularly I am having difficulties in running the
> org.apache.jdo.tck.mapping tests (because unlike most other tests
> they do not run without the conf files).
>
> Any help will be appreciated.
>
> Thanks,
> Ilan Kirsh
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Running JDO TCK on Eclipse
Posted by Ilan Kirsh <ki...@objectdb.com>.
Hi,
I am looking for instructions on how to run the JDO TCK 2.2 on Eclipse.
Particularly I am having difficulties in running the
org.apache.jdo.tck.mapping tests (because unlike most other tests they
do not run without the conf files).
Any help will be appreciated.
Thanks,
Ilan Kirsh
Minutes: JDO TCK Conference Call Friday, Mar 5, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
NOTE: With the acquisition of Sun by Oracle, the conference call
numbers that we use for conference calls will change. Please watch for
the change.
Agenda:
1. Other issues
The spec update is underway. I expect to have sections to review by
next week.
We will look at the metadata tests to read some of the .jdo metadata
files using an xml parser and compare the contents with the metadata
that is available from the metadata api. AI Craig update the JIRA
Michelle will try to have some code to review next week for the
getPersistenceManagerFactory(Map, Map) test.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Apr 8, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
2. Query.executeWithMap(...) should accept unused parameters
This functionality is already in DataNucleus as an option. Propose
deferring this to 2.4. The biggest issue is whether to allow the
strict behavior as an option and if so, what the default should be. AI
discuss on email.
3. Query cancel and timeout support https://issues.apache.org/jira/browse/JDO-623
The datastore timeout tests use a timeout of less than one second,
which might not be possible to achieve with current generation JDBC
drivers. Perhaps a longer timeout should be used for the tests. AI
Michael look at the tests.
4. Spec updates
The spec has been published on http://people.apache.org/~clr/jdo-2010-04-09.pdf
AI everyone review in preparation for a vote next week.
5. Other issues
Tests for JDO-615 Metadata have been checked in.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> 2. Spec updates - ready for a vote?
I think so. Have read the latest spec and don't see any problems.
--
Andy
DataNucleus (http://www.datanucleus.org)
Re: Query test failure with newer derby version (was Re: Minutes:
JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
this is the JDOQL query:
SELECT FROM org.apache.jdo.tck.pc.mylib.PCPoint EXCLUDE SUBCLASSES
WHERE (x == 2) == true
and here is the generated SQL:
SELECT 'org.apache.jdo.tck.pc.mylib.PCPoint' AS
NUCLEUS_TYPE,A0.ID,A0.X,A0.Y
FROM APPLICATIONIDENTITY0.PCPOINT A0
WHERE A0.X = 2 = 1
So the question is: what does SQL define when comparing an integer and a
boolean?
The expression "A0.X = 2" evaluates to a boolean which is then compared
to the integer 1.
Regards Michael
> Hi Craig,
>
> [...]
>>>
>>> (2) query test:
>>>
>>> The failing test is in jdoql.conf: class
>>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
>>> method runTestParenthesesMarkOperatorPrecedence08.
>>> The test runs a JDOQL query with PCPoint as candidate class and "(x
>>> == 2) == true" as filter. It results in an exception thrown by the
>>> derby SQL compiler:
>>>
>>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
>>> are not supported. Types must be comparable. String types must also
>>> have matching collation. If collation does not match, a possible
>>> solution is to cast operands to force them to the default collation
>>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
>>> VARCHAR(128)) = 'T1')
>>>
>>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception.
>>> But it does NOT happen with derby version 10.4.2.0, which we are
>>> using in the maven1 environment.
>>
>> Good catch. Would you have time to file a JIRA with Derby?
>
> First I want to take a look at the generated SQL before filing a JIRA.
> I'll keep you posted.
>
> Regards Michael
>
> [...]
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
Query test failure with newer derby version (was Re: Minutes: JDO
TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
[...]
>>
>> (2) query test:
>>
>> The failing test is in jdoql.conf: class
>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
>> method runTestParenthesesMarkOperatorPrecedence08.
>> The test runs a JDOQL query with PCPoint as candidate class and "(x
>> == 2) == true" as filter. It results in an exception thrown by the
>> derby SQL compiler:
>>
>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
>> are not supported. Types must be comparable. String types must also
>> have matching collation. If collation does not match, a possible
>> solution is to cast operands to force them to the default collation
>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
>> VARCHAR(128)) = 'T1')
>>
>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But
>> it does NOT happen with derby version 10.4.2.0, which we are using in
>> the maven1 environment.
>
> Good catch. Would you have time to file a JIRA with Derby?
First I want to take a look at the generated SQL before filing a JIRA.
I'll keep you posted.
Regards Michael
[...]
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Hi Michael,
On Jan 8, 2011, at 2:33 AM, Michael Bouschen wrote:
> Hi,
>> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>>
>> Agenda:
>>
>> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>>
>> Only two tests are now failing: signature test and a query test.
>> The signature test might be reading the wrong signature file, since
>> there have been a few changes to the signature since 3.0.
>
> I looked at the test failures:
>
> (1) signature test:
>
> The current pom.xml still refers the 3.0 version of jdo-api. The
> test succeeds after switching the dependency to 3.1-SNAPSHOT.
>
> Please note the dependency needs to be changed in exectck and tck!
>
> (2) query test:
>
> The failing test is in jdoql.conf: class
> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence
> method runTestParenthesesMarkOperatorPrecedence08.
> The test runs a JDOQL query with PCPoint as candidate class and "(x
> == 2) == true" as filter. It results in an exception thrown by the
> derby SQL compiler:
>
> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'
> are not supported. Types must be comparable. String types must also
> have matching collation. If collation does not match, a possible
> solution is to cast operands to force them to the default collation
> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS
> VARCHAR(128)) = 'T1')
>
> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception.
> But it does NOT happen with derby version 10.4.2.0, which we are
> using in the maven1 environment.
Good catch. Would you have time to file a JIRA with Derby?
Thanks,
Craig
>
> Regards Michael
>>
>> Maven now has a process for publishing Apache artifacts. We should
>> look into what is needed to use the staging and publishing
>> repositories.
>>
>> 2. Other issues
>>
>> https://issues.apache.org/jira/browse/JDO-643 should add the tck as
>> an affected component. We should also add test cases for average of
>> more of the types that we support, including BigDecimal and
>> BigInteger.
>>
>> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO
>> page needs an update.
>>
>> Action Items from weeks past:
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@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
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@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
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific
Time
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>
> Only two tests are now failing: signature test and a query test. The
> signature test might be reading the wrong signature file, since there
> have been a few changes to the signature since 3.0.
I looked at the test failures:
(1) signature test:
The current pom.xml still refers the 3.0 version of jdo-api. The test
succeeds after switching the dependency to 3.1-SNAPSHOT.
Please note the dependency needs to be changed in exectck and tck!
(2) query test:
The failing test is in jdoql.conf: class
org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method
runTestParenthesesMarkOperatorPrecedence08.
The test runs a JDOQL query with PCPoint as candidate class and "(x ==
2) == true" as filter. It results in an exception thrown by the derby
SQL compiler:
java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' are
not supported. Types must be comparable. String types must also have
matching collation. If collation does not match, a possible solution is
to cast operands to force them to the default collation (e.g. SELECT
tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')
The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But it
does NOT happen with derby version 10.4.2.0, which we are using in the
maven1 environment.
Regards Michael
>
> Maven now has a process for publishing Apache artifacts. We should
> look into what is needed to use the staging and publishing repositories.
>
> 2. Other issues
>
> https://issues.apache.org/jira/browse/JDO-643 should add the tck as an
> affected component. We should also add test cases for average of more
> of the types that we support, including BigDecimal and BigInteger.
>
> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page
> needs an update.
>
> Action Items from weeks past:
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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, Jan 7, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Only two tests are now failing: signature test and a query test. The
signature test might be reading the wrong signature file, since there
have been a few changes to the signature since 3.0.
Maven now has a process for publishing Apache artifacts. We should
look into what is needed to use the staging and publishing repositories.
2. Other issues
https://issues.apache.org/jira/browse/JDO-643 should add the tck as an
affected component. We should also add test cases for average of more
of the types that we support, including BigDecimal and BigInteger.
https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page
needs an update.
Action Items from weeks past:
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
PLEASE NOTE: JDO will be on winter break for the next two weeks. Next
meeting: January 7, 2011
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Mostly done but not completely working. Need to update the version
numbers in the pom to be identical to those used in maven 1. Some
tests cannot find the test data resource. The test data reader is
calling the constructor for the spring xmlbeans reader which cannot
find the file. Class path issue?
2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643
This proposes that integral types and floating point types all return
double for average. Is there a good reason for JDO to be different
from JPA? AI Craig: update JIRA with comment
3. Extend PersistenceManageFactory to return all known entity classes -
new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467
for an interesting idea.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
PLEASE NOTE: JDO will be on winter break for the next two weeks. Next
meeting: January 7, 2011
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Mostly done but not completely working. Need to update the version
numbers in the pom to be identical to those used in maven 1. Some
tests cannot find the test data resource. The test data reader is
calling the constructor for the spring xmlbeans reader which cannot
find the file. Class path issue?
2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643
This proposes that integral types and floating point types all return
double for average. Is there a good reason for JDO to be different
from JPA? AI Craig: update JIRA with comment
3. Extend PersistenceManageFactory to return all known entity classes -
new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467
for an interesting idea.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 3, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Good progress. No hang any longer. Getting the schema loaded. But not
quite working yet. Some tables are not created. Signature test
complains.
2. Other issues
There's a project called naked objects which is now incubating as
Apache Isis. How about a JDO store for the objects?
Check it out: https://issues.apache.org/jira/browse/ISIS-14
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Oct 22, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647.
The classpath problem was resolved as a missing JDO_Test in the
classpath. Everything that the enhancement needs must be on the
classpath, including most of the TCK due to some TCK classes needing
to be enhanced as persistence aware.
2. extend "sequence" metadata to allow specification of start and
allocationSize. Patch for review. https://issues.apache.org/jira/browse/JDO-662
Looks good. AI Craig reply with review comments. Spec update needed.
3. Ability to specify positioning of field 'column(s)' in datastore
"table" https://issues.apache.org/jira/browse/JDO-660
Looks good. Spec update needed.
4. Other issues
JDO repository has a jdo-api2 directory that is empty. Looks like a
booboo. Gone.
Other projects like Objectify and Gora are intended to be JDO-lite
implementations. Some comments from these other projects are that JDO
"is complex". It would be worthwhile to take a look at these projects
to see if an official JDO-lite would make sense. We already have a
JIRA in place to track no-sql datastores.
https://issues.apache.org/jira/browse/JDO-663 Michael will refactor
some of the tck tests to avoid duplication. Spec update also required.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday,Oct 15, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
Questions about enhancing and creating jar files. The enhancer isn't
finding classes that have been put into the enhancer's class loader.
Possibly need to have a parent class loader for the enhancer class
loader. And it might be better to avoid the jar file but simply use
directories for class path entries.
2. JDO Querying reference. AI everyone please see http://www.datanucleus.org/jdoql_quickref.pdf
and comment.
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions for them.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 14, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647.
Changes for parameterizing the version numbers are now checked in. Two
issues remain:
Exception from new Derby version: is the generated SQL correct?
Perhaps not. "Comparisons between 'BOOLEAN' and 'INTEGER' are not
supported." AI Michael: file a JIRA to resolve whether this is a
DataNucleus or Derby issue.
Upgrade to later DataNucleus version: using 2.1.1 now; need 2.2.2-
SNAPSHOT for "average" change. AI Michelle: change the dependency for
the project.
Next: see how to run the tck using an IUT (using profiles).
Also: how can we use the Apache maven release staging repository for
releases? The idea is that the jdo-api could be defined as a maven
dependency and automatically downloaded from the central repository
but the jdo-tck needed to be installed as source. With the tck now
defined as a maven2 project, should it also be usable as a dependency?
Probably no change to the current practice, since the tck is intended
to be executed by itself with no user code involved.
2. Other issues
Action items from past meetings: Craig check into using the Apache
parent pom
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, May 14, 9 am PDT
Posted by mc...@sonic.net.
Agreed. I think only Craig has the host code, anyway.
-- Michelle
> Hi,
>
> I'm not in town today and not able to dial in. Should we skip the call
> for today and send email with the status?
>
> Regards Michael
>
>> Sorry, I'll be on a plane and unable to dial in to this call.
>>
>> I'll send status before the call.
>>
>> Craig
>>
>> On May 13, 2010, at 9:26 PM, Michelle Caisse wrote:
>>
>>
>>> Hi,
>>>
>>> We will have our regular meeting Friday, May 14 at 9 am PDT to
>>> discuss JDO TCK issues and status.
>>>
>>> Dial-in numbers are:
>>> US Toll free: 866 682-4770
>>> Germany Frankfurt 069222216106
>>> Germany Toll free: 08006648515
>>> (Other countries by request)
>>>
>>> To place the call:
>>> 1. Call the toll free number.
>>> 2. Enter the conference number 939-3689#
>>> 3. Enter the security code 1111#
>>>
>>> Agenda:
>>>
>>> 1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>> https://issues.apache.org/jira/browse/JDO-557
>>> 2. Other issues
>>>
>>> Action Items from weeks past:
>>> [May 7 10] AI Craig Notify JCP of recent changes to the spec.
>>>
>>> -- Michelle
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@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
>
Re: JDO TCK Conference Call Friday, May 14, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
I'm not in town today and not able to dial in. Should we skip the call
for today and send email with the status?
Regards Michael
> Sorry, I'll be on a plane and unable to dial in to this call.
>
> I'll send status before the call.
>
> Craig
>
> On May 13, 2010, at 9:26 PM, Michelle Caisse wrote:
>
>
>> Hi,
>>
>> We will have our regular meeting Friday, May 14 at 9 am PDT to
>> discuss JDO TCK issues and status.
>>
>> Dial-in numbers are:
>> US Toll free: 866 682-4770
>> Germany Frankfurt 069222216106
>> Germany Toll free: 08006648515
>> (Other countries by request)
>>
>> To place the call:
>> 1. Call the toll free number.
>> 2. Enter the conference number 939-3689#
>> 3. Enter the security code 1111#
>>
>> Agenda:
>>
>> 1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
>> 2. Other issues
>>
>> Action Items from weeks past:
>> [May 7 10] AI Craig Notify JCP of recent changes to the spec.
>>
>> -- Michelle
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
Re: JDO TCK Conference Call Friday, May 14, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Sorry, I'll be on a plane and unable to dial in to this call.
I'll send status before the call.
Craig
On May 13, 2010, at 9:26 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, May 14 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> US Toll free: 866 682-4770
> Germany Frankfurt 069222216106
> Germany Toll free: 08006648515
> (Other countries by request)
>
> To place the call:
> 1. Call the toll free number.
> 2. Enter the conference number 939-3689#
> 3. Enter the security code 1111#
>
> Agenda:
>
> 1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
> 2. Other issues
>
> Action Items from weeks past:
> [May 7 10] AI Craig Notify JCP of recent changes to the spec.
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, May 20, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Hi Michelle,
Sorry, I assumed that you were going to look at the spec and make a
judgement whether the failures were spec violations.
What's your opinion?
Craig
On May 23, 2010, at 8:49 PM, Michelle Caisse wrote:
>
>> 2. Extra checks in PMF.close tests https://issues.apache.org/jira/browse/JDO-653
>> : Are the observed failures violations of the spec? (11.4 Close the
>> PersistenceManagerFactory)
>>
>> Michelle will verify these changes.
>>
> I'm not clear what else is needed here. I verified that there are RI
> failures and posted a comment on the JIRA. We need a determination
> as to whether the test is correct, i.e. the observed failures are
> spec violations.
>
> -- Michelle
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, May 20, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
> 2. Extra checks in PMF.close tests
> https://issues.apache.org/jira/browse/JDO-653: Are the observed
> failures violations of the spec? (11.4 Close the
> PersistenceManagerFactory)
>
> Michelle will verify these changes.
>
I'm not clear what else is needed here. I verified that there are RI
failures and posted a comment on the JIRA. We need a determination as to
whether the test is correct, i.e. the observed failures are spec violations.
-- Michelle
Re: JDO TCK Conference Call Friday, May 20, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Two steps forward, one back, one to the left, one to the right. Still
in progress.
2. Extra checks in PMF.close tests https://issues.apache.org/jira/browse/JDO-653
: Are the observed failures violations of the spec? (11.4 Close the
PersistenceManagerFactory)
Michelle will verify these changes.
3. Other issues
The notice was sent to the PMO of JCP to start the Maintenance Review
of the Minor Revision. If there are no issues, the review will close
in 30 days, by which time we should have voted on the release artifacts.
There are changes needed in the api schema definitions for the xml
metadata files. Michael will make the updates, which will affect the
RI until corresponding changes are made.
Action Items from weeks past:
[May 7 10] AI Craig Notify JCP of recent changes to the spec. Done.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 28, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
NOTE: We are skipping a phone conference next Friday; status updates
by email please.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
making some progress; still not completely working.
2. Comments on spec: There were some comments on typos in the draft
spec, which apply to a different version of the specification. The
latest specification is correct.
3. Other issues
The process for publishing a new maintenance release is underway.
There are some details like export controls that I'm working through
with the PMO folks.
Michael has proposed changes to the run rules and other tck
documentation. Patch from 24-May should be applied.
Michael will propose changes to the maven build scripts at the top
level, now that we have fewer dependencies for the tck project.
Once the maintenance revision has been approved by the JCP we will
need to update the main JDO page to reflect current status.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, June 18, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch
available for review. https://issues.apache.org/jira/browse/JDO-557
Reviewed with a couple of comments; ok to check in.
2. Status of 3.0 release. Michelle has finished final formatting of
the specification; Craig will check it over and send to JCP. The
IssuesLog which is part of the new JSR maintenance process was created
in the wiki.
Michael has a task to update the maven top level for 3.0.
3. Review JIRAs
JDO-519 is done with 3.0. AI Craig close this JIRA
JDO-615 is done. AI Craig close this JIRA
JDO-616 AI Craig look at this when reviewing the final book.
4. Other issues
JDO-580 looks like a bug in the disabled tests. Will be taken up for
3.1.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, June 25, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Status of 3.0 release.
Craig is building the 3.0 release. We will hold a vote to release the
api and tck once the release is built.
Craig has submitted the spec to the JCP and is waiting for the project
office.
2. Provision of a statically-typed refactor-friendly query capability
for JDOQL https://issues.apache.org/jira/browse/JDO-652
Join the discussion on the JIRA! We just need to be mindful that this
is a pretty big project.
3. Other issues
Moving parts of trunk to legacy. Discuss on mailing list. Probably
should use a different term from legacy, since that term is already in
use for JDK 1.4. Maybe archive or archive-trunk. Once we do this, we
can adapt the maven.xml to remove the references to the old stuff.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 2, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
For the record, I found this in my out-box...
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Restructure JDO repository. Seems like the only issue is the name.
It could be called jdo/trunk-archive or jdo/branches/archive-3.0 or
something like this so we know that it's in the 3.0 time frame.
After the restructuring we will then change the version number in
trunk to 3.1-SNAPSHOT.
2. JDO 3.0 staging release at http://people.apache.org/~clr/dist
Feedback from Andy: the pom.xml has the wrong version number. Thanks!
Michael points out that contrary to Craig's message, we do distribute
the tck sources, just not via the maven repo.
Does anyone know how to make it easy to "attach sources" to an IDE? Is
the current planned distribution via mirrors ok for this purpose? That
is, if a user wants to look at the sources for a Maven dependency, is
there a trivial way to "attach sources" within the IDE dialog if the
user has not already downloaded the sources?
3. Other issues
none.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 9, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Vote on JDO 3.0 release. So far, so good. No neutral or negative
votes. JIRA issues JDO-615 and JDO-619 are now resolved.
2. Provision of a ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
Looks promising, AI everyone please read and comment on this
direction for JDOQL.
3. Other issues
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 16, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
NOTE: Due to holidays there will be no meeting next week. The next
conference call is scheduled for July 30.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Next steps for JDO 3.0 release. The Apache DB PMC approved the
release of the API and TCK artifacts. AI Craig publish the API and TCK
artifacts on the Apache JDO web page.
The JCP EC is currently reviewing the maintenance release. You can
follow the discussion on the JCP release approval at http://wiki.jcp.org/boards/index.php?b=jsr-243-public
(linked from http://jcp.org/aboutJava/communityprocess/maintenance/jsr243/index4.html
)
2. Missing DTD/XSD from SUN/Oracle website. The goal is to have the
2.0, 2.1, 2.2 and 3.0 xsd and dtd artifacts published and downloadable
from the site. AI Craig follow up with Oracle.
3. Fetch configuration. Looks like a good candidate for the next
release. Continue discussion via JIRA and email. AI Andy file a JIRA
(please).
4. Other issues.
Let's see if we can make a quicker spin for JDO 3.1. AI everyone look
at the JIRA for 3.1 and "unscheduled" and discuss which issues should
be in 3.1
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 30, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Craig L Russell
Agenda:
The review period for JDO 3.0 in the JCP has ended. Waiting for
official confirmation from JCP admin.
1. JDO 3.0 artifacts. The artifacts have been uploaded but don't yet
have pointers from the jdo web site. AI Craig update the download page.
2. Missing DTD/XSD from SUN/Oracle website. Now that JDO 3.0 is out,
Craig will get both the missing artifacts and the new artifacts
uploaded.
3. JDO 3.next Nothing new this week.
4. Other issues
https://issues.apache.org/jira/browse/JDO-664 the upload of JDO 3.0
artifacts resulted in the replacement of the jdo2-api metadata.xml
with the new jdo-api metadata. This should not have happened since
there are now two artifact-ids: jdo2-api and jdo-api. AI: Craig follow
up with the Apache repository folks.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Aug 13, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade https://issues.apache.org/jira/browse/JDO-647 the
new pom.xml for api and tck projects have been posted for review.
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD in process
[6 Aug 10] AI Craig update the download page with JDO 3 artifacts done
[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release
nothing yet
[6 Aug 10] AI Michael reply to a poster that we have a new release
with a class missing from JDO 2.3 EA
-- Michelle
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Aug 20, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647.
Making progress. Running mvn install with java 5 has a test case
failure in the api project. Works fine on java 6. The changes to the
api pom.xml in the jira look good.
The exectck mojo is under development. This maven plugin will be
defined in the tck pom.xml to attach to a maven phase and run
automatically. It will be configured by default in the tck pom.xml and
can be overridden via additional elements in the tck pom.xml or by
command line. For example, we might support -DinstallSchema to specify
running the install schema function; -Dconf=mycnf to specify running
only the configuration in the src/conf/mycnf.conf file; -Ddb=mysql to
specify running with the database connection properties in the src/
conf/mysql.db file... The defaults will be to *not* install the
schema, run all tests on the reference implementation with the derby
database. Other possible scenarios would use different goals on the
command line.
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD. no news
[6 Aug 10] AI Craig update the download page with JDO 3 artifacts done.
[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release
It is possible to get publicity with Apache PR. What we need is
something that makes a compelling story.
The best story is from users who can be quoted saying good things
about the new functionality of the release.
Do we have any customers who are willing to be quoted? If not, do we
have customers who can tell us a story (not a direct quote) about why
the new features help them?
If not, we might not have anything worth a press release.
AI Everyone who knows of a customer who can tell us a story: tell us a
story.
[6 Aug 10] AI Michael reply to a poster that we have a new release
with a class missing from JDO 2.3 EA. no news
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday,Oct 8, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade -
https://issues.apache.org/jira/browse/JDO-647
Making progress. Stuck on classpath issue. Maybe resolved; need to
construct a class loader that contains the classes to enhance and the
metadata loadable as resources.
2. Ability to specify positioning of field 'column(s)' in datastore
"table" - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-660
The 3.1 xsd and dtd files have been created. The patch adding the
position can now be reviewed. Outstanding question about superclasses
and how to reorder columns in subclasses.
3. List.get(int) support in JDOQL is missing - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-633
Looks good. AI Michael review and respond to questions in jira.
4. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD
Resolved. All resources are now available on the web.
-- Michelle
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Feb 25, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652
We need more people than have looked at this to take a closer look.
Volunteers? Michael, Craig. In particular, look at the TCK tests where
we run the queries twice: once with String-based and one with the API.
Adding a third option for the typesafe query would expose differences,
mismatches.
http://www.datanucleus.org/products/accessplatform/jdo/jdoql_typesafe.html
http://datanucleus.blogspot.com/2010/11/jdo-typesafe-vs-jpa-criteria.html
2. Inheritance strategy that results in a table per class - patch
provided. https://issues.apache.org/jira/browse/JDO-674
The patch looks good. Ok to check in.
3. Other issues
Dependency on JPA: The JIRA 675 to change tck pom dependency from
Geronimo to Eclipse. Won't fix. There's no need.
Maven2 upgrade: Once we have it all working, we will remove the maven1
support completely.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Mar 11, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Reminder: Next week the US will be on Daylight Savings Time.
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig
Russell
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647
Try using a property like <tck.iut.classpath> in the exectck to set up
the class path.
2. Typesafe ... query capability for JDOQL. https://issues.apache.org/jira/browse/JDO-652
A few method and class name issues that we should discuss and resolve.
Quickly, please.
3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677
Probably doing the check on flush is better.
4. query improvements: downcasting
There don't seem to be any issues here. Just need spec update and TCK
test.
5. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov12, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1. Maven2 upgrade - patch posted with enhance goal. https://issues.apache.org/jira/browse/JDO-647
We can put the version numbers into the parent pom. Starting with
dependencies but we can also put the version number of the components
into the parent pom.
The runtck goal is mostly running. Cannot create a connection with the
underlying database.
2. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 21, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Dependencies have been changed to conform to the maven
DependencyManagement pattern.
Tck dependencies have been updated to the latest DataNucleus version
2.2.2. The dependency should actually be on the exectck project not
the tck project.
To run the tck with an IUT, users will have to edit the pom and
profiles to add their dependent jar files.
The "run-once" tests run twice. Is this ok? Yes.
2. Inheritance strategy http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201101.mbox/browser
Surprising to hear that JPA has a mapping feature that JDO doesn't.
Maybe there is a misunderstanding. AI everyone: Is this scenario
really not supported by JDO?
3. Test case failure: SQLException in
ParenthesesMarkOperatorPrecedence https://issues.apache.org/jira/browse/JDO-672
No progress.
4. Other issues
Dependencies on JPA: the api needs JPA 3.0 and the tck needs JPA 2.0
The issue is with the getProperties() method in
JDOEntityManagerFactory which extends both EntityManagerFactory and
PersistenceManagerFactory. In JDO PersistenceManagerFactory the method
returns Properties and in JPA EntityManagerFactory returns Map<String,
Object>.
Possible solutions: change JDO PersistenceManagerFactory to return
Map<String, Object> or remove the JDOEntityManagerFactory and
JDOEntityManger interfaces. Are these being used by anyone?
AI Michael file a JIRA.
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom. No progress.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Feb 4, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1.Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
There is now a profile to run the tck. To run the tck, run mvn
integration-test. Need to add sub-modules to the parent pom. Upgrade
pom to the latest Derby 10.7.1.1.
It would be good to be able to run the tck on an IUT simply by adding
a profile to the user's settings.xml and not require any changes to
the distributed api, tck, or exectck.
2. Inheritance strategy that results in a table per class... https://issues.apache.org/jira/browse/JDO-674
Seems like proposal 1 doesn't limit what we can do in the future, and
it's a good proposal. AI Craig update the JIRA.
3. Change JPA API dependency to org.eclipse.persistence https://issues.apache.org/jira/browse/JDO-675
There is no official javax.persistence. There is no
org.eclipse.persistence for maven 1. Propose postponing this change
until we leave maven 1. AI Michael update the JIRA.
4. Using Apache parent POM http://www.apache.org/dev/publishing-maven-artifacts.html
, https://issues.apache.org/jira/browse/MPOM
We can start by just adding the Apache parent pom and then the rest
can be added as we work to publish a release.
5. Other issues
Multi-tenancy (cloud) may be a good feature to consider for a future
release. May be similar to openjpa slices?
Use cases as an extension to fetch plan may be a good feature to
consider for a future release. AI Matthew write up a JIRA.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Andy Jefferson <an...@datanucleus.org>.
> 2. Typesafe ... query capability for JDOQL - ready for check-in?.
> https://issues.apache.org/jira/browse/JDO-652
> Some questions: the factory for query instances: should it be PM or
> PMF? Hint: do you really need to have the PM available in order to
> build a query? The PM represents your current connection to the
> database; the PMF represents the object model and mapping.
To build a query you don't need the PM (but then to create a javax.jdo.Query
object you don't really need a PM either :-P). To execute a
(Query/)TypesafeQuery/TypedQuery you need a PM, and if you put constructor on
the PMF then you have to pass the PM into the executeXXX methods.
> Is there a bug in the blog?
Yes there was, fixed thx.
> JDO-678 Set properties on PersistenceManager
> Seems like a good idea. Patch?
Will do.
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Re: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific
Time
Posted by Michelle Caisse <mc...@sonic.net>.
On 03/04/2011 11:02 AM, Craig L Russell wrote:
> ...
>
> 1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
> https://issues.apache.org/jira/browse/JDO-647
>
> Apparently maven doesn't want to encourage items in the settings.xml
> to affect the build, but we do. Specifically, we want to have the
> user's settings.xml to provide settings to run the iut. Any suggestions?
>From
http://maven.apache.org/guides/introduction/introduction-to-profiles.html:
> Profiles specified in external files (i.e in settings.xml or
> profiles.xml) are not portable in the strictest sense. Anything
> that seems to stand a high chance of changing the result of the
> build is restricted to the inline profiles in the POM. Things like
> repository lists could simply be a proprietary repository of
> approved artifacts, and won't change the outcome of the build.
> Therefore, you will only be able to modify the <repositories> and
> <pluginRepositories> sections, plus an extra <properties> section.
>
> The <properties> section allows you to specify free-form key-value
> pairs which will be included in the interpolation process for the
> POM. This allows you to specify a plugin configuration in the form
> of ${profile.provided.path}.
>
I don't understand what they are suggesting be done with a
${profile.provided.path} property.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647
Apparently maven doesn't want to encourage items in the settings.xml
to affect the build, but we do. Specifically, we want to have the
user's settings.xml to provide settings to run the iut. Any suggestions?
2. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652
Some questions: the factory for query instances: should it be PM or
PMF? Hint: do you really need to have the PM available in order to
build a query? The PM represents your current connection to the
database; the PMF represents the object model and mapping.
Also, the name sounds too "inside". Matthew made a similar comment.
I'd like to look at the name: "TypesafeQuery".
Is there a bug in the blog?
List<Object[]> results =
em.createQuery(criteria).getSingleResult(); // should return Object[]?
List<Integer> result =
tq.filter(cand.name.eq("MP3
Extra")).executeResultUnique(Integer.class, cand.value.max()); //
should return Integer?
Method name for returning projection might not be obvious.
Started looking at it in detail with an eye to including in 3.1. Not
done yet.
3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677
Seems like a good idea. Anyone else have comments?
Where would an error be identified? At the time the user modifies a
persistent field? Or defer checking until flush (or commit)?
Portable behavior would probably mean defer checking.
Silently ignoring an update is probably not the right behavior.
4. Other issues
JDO-678 Set properties on PersistenceManager
Seems like a good idea. Patch?
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Mar 11, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 11, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
https://issues.apache.org/jira/browse/JDO-647
2. Typesafe ... query capability for JDOQL.
https://issues.apache.org/jira/browse/JDO-652
3. Ability to mark a class as read-only -
https://issues.apache.org/jira/browse/JDO-677
4. query improvements: downcasting
5. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at Typesafe ...
query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
-- Michelle
JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 4, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile
https://issues.apache.org/jira/browse/JDO-647
2. Typesafe ... query capability for JDOQL - ready for check-in?.
https://issues.apache.org/jira/browse/JDO-652
3. Ability to mark a class as read-only -
https://issues.apache.org/jira/browse/JDO-677
4. Other issues
Action Items from weeks past:
[Feb 25 2011] AI Michael, Craig, other volunteers: Look at Typesafe ...
query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652
-- Michelle
JDO TCK Conference Call Friday, Feb 25, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 25, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Typesafe ... query capability for JDOQL - ready for check-in?.
https://issues.apache.org/jira/browse/JDO-652
2. Inheritance strategy that results in a table per class - patch
provided. https://issues.apache.org/jira/browse/JDO-674
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Feb 4, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 4, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1.Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Inheritance strategy that results in a table per class...
https://issues.apache.org/jira/browse/JDO-674
3. Change JPA API dependency to org.eclipse.persistence
https://issues.apache.org/jira/browse/JDO-675
4. Using Apache parent POM
http://www.apache.org/dev/publishing-maven-artifacts.html,
https://issues.apache.org/jira/browse/MPOM
5. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 28, 9 am Pacific Time
Posted by Craig L Russell <cr...@ORACLE.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1.Interface JDOEntityManagerFactory does not compile with JPA. https://issues.apache.org/jira/browse/JDO-673
I propose that we remove the two interfaces JDOEntityManagerFactory
and JDOEntityManager from the 3.1 release. This is a backward
compatibility issue but never worked with the published JPA 2.0
specification. Since it is impossible to instantiate a class
implementing this interface, it probably is not an issue.
Any objections to removing these two interfaces?
2. Other issues
- Is another mapping needed to cover the JPA Table-per-concrete-class?
See
http://www.datanucleus.org/products/accessplatform_3_0/jdo/orm/inheritance.html
The standard JDO mapping strategies do not cater for concrete
subclasses of concrete superclasses being mapped with both concrete
classes having all fields mapped.
AI: Andy file a JIRA. Seems like a good idea. Need to define exactly
the semantics of having a subclass of a class that is mapped as
complete-table. Can the subclass be mapped as new-table (all new
fields are mapped to the new table), subclass-table (no table is
defined, subclasses must have their fields mapped by the superclass),
superclass-table (no table is defined, all new fields are mapped in
the existing table).
- We should take a look at jsr 338 to see if there are any good ideas
that we can adopt.
- https://issues.apache.org/jira/browse/JDO-672 has had no response yet.
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 28, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 28, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1.Interface JDOEntityManagerFactory does not compile with JPA.
https://issues.apache.org/jira/browse/JDO-673
2. Other issues
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
[Jan 21 2011] AI everyone: Is TABLE_PER_CLASS really not supported by JDO?
-- Michelle
JDO TCK Conference Call Friday, Jan 21, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 21, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Inheritance strategy
http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201101.mbox/browser
3. Test case failure: SQLException in ParenthesesMarkOperatorPrecedence
https://issues.apache.org/jira/browse/JDO-672
4. Other issues
Action Items from weeks past:
[Jan 14 2011] Craig check into using the Apache parent pom
-- Michelle
JDO TCK Conference Call Friday, Jan 14, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 14, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 7, at 9 am Pacific Time
to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
NO JDO TCK Conference Call Friday, Dec 24
Posted by Michelle Caisse <mc...@sonic.net>.
JDO is on winter break. Next meeting: January 7, 2011
-- Michelle
JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 17, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Avg return type - patch available for review
https://issues.apache.org/jira/browse/JDO-643
3. Extend PersistenceManageFactory to return all known entity classes
-new comments https://issues.apache.org/jira/browse/JDO-667
4. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Dec 10, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Hi,
Sorry I'll be in a plane during the call. Enjoy the call.
Craig
On Dec 9, 2010, at 7:02 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, December 10, at 9 am
> Pacific Time to discuss JDO TCK issues and status.
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 10, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 10, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Dec 3, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 3, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 26, 9 am Pacific Time
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Checked in but doesn't quite work.
a. The test hangs after starting the test in another process. The
output and error streams from the started process aren't being handled
properly by the caller. Take a look at the EnhancerTest that has a
somewhat elaborate scheme to handle the streams.
b. The schema information isn't being used by datanucleus. TCK-USER is
being used (default) instead. Take a look at path file names when
invoking the process. The path for the started process might be
different from the way maven 1 handled it due to the exectck project
being called.
2. Other issues
https://issues.apache.org/jira/browse/JDO-669 seems to be resolved. AI
Craig check in the patch and resolve the issue.
Action Items from weeks past:
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Nov 26, 9 am Pacific Time
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 26, at 9 am Pacific
Time to discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 19, 9 am Pacific
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
Making progress but not done yet. AI Michelle check in the partial
code since it doesn't impact running the tck under maven 1.
2. Provision of a typesafe refactor-friendly query capability for
JDOQL - patch available for review. https://issues.apache.org/jira/browse/JDO-652
AI everyone take a look at the patch and comment.
3. Other issues
TCK test issue with datastore identity and managed relationships.
Looks like a valid bug in the tck. All tests that delete an object and
then test for its inclusion in a collection need to be updated. AI
Andy file a JIRA.
Action Items from weeks past:
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Nov 19, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 19, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
2. Provision of a typesafe refactor-friendly query capability for JDOQL
- patch available for review. https://issues.apache.org/jira/browse/JDO-652
3. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
-- Michelle
JDO TCK Conference Call Friday, Nov12, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 12, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - patch posted with enhance goal.
https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
-- Michelle
Minutes: JDO TCK Conference Call Friday, Nov 5, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Reminder: next week California will have changed to Standard Time, so
if you're in another time zone please take note.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade - patch posted with enhance goal. https://issues.apache.org/jira/browse/JDO-647
Working through dependencies in exectck project...
2. Other issues
Action Items from weeks past:
https://issues.apache.org/jira/browse/JDO-668 Looks like no additional
comments on this issue. If Marco agrees, it should be closed.
I agree that https://issues.apache.org/jira/browse/JDO-667 is
worthwhile and we should focus on the API and detailed semantics of
that issue.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Nov 5, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 5, at 9 am PDT to
discuss JDO TCK issues and status.
NOTE that this is one hour earlier than usual in locations that changed
to Standard Time last weekend!!
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - patch posted with enhance goal.
https://issues.apache.org/jira/browse/JDO-647
2. Other issues
NOTE that next Friday, Europe will be on Standard Time and the U.S. will
still be on Daylight Savings Time.
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
-- Michelle
Minutes: JDO TCK Conference Call Friday,Oct 29, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade - patch posted with enhance goal. https://issues.apache.org/jira/browse/JDO-647
Enhancer invocation now seems to work. Install schema is disabled;
runtck is disabled as well. Good progress!
2. Provide quick reference to JDOQL - comments? https://issues.apache.org/jira/browse/JDO-666
Looks good. AI everyone please review and comment on the quick
reference.
3. Extend PersistenceManageFactory to find a Class - https://issues.apache.org/jira/browse/JDO-668
This is related to https://issues.apache.org/jira/browse/JDO-667 which
asks for a list of managed classes. There is a problem with the idea
that JDO implementation should be able to resolve a class given its
name, for exactly the reason identified by the JIRA as a problem: OSGi
might dynamically modify the classes available to the implementation.
AI Craig comment on the JIRAs.
4. Other issues
NOTE that next Friday, Europe will be on Standard Time and the U.S.
will still be on Daylight Savings Time.
Action Items from weeks past:
[28 Oct 10] AI Craig reply tohttps://issues.apache.org/jira/browse/
JDO-662 with review comments. Done.
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday,Oct 29, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 29, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - patch posted with enhance goal.
https://issues.apache.org/jira/browse/JDO-647
2. Provide quick reference to JDOQL - comments?
https://issues.apache.org/jira/browse/JDO-666
3. Extend PersistenceManageFactory to find a Class -
https://issues.apache.org/jira/browse/JDO-668
4. Other issues
NOTE that next Friday, Europe will be on Standard Time and the U.S. will
still be on Daylight Savings Time.
Action Items from weeks past:
[28 Oct 10] AI Craig reply
tohttps://issues.apache.org/jira/browse/JDO-662 with review comments.
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
-- Michelle
JDO TCK Conference Call Friday,Oct 225, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 22, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
2. extend "sequence" metadata to allow specification of start and
allocationSize. Patch for review.
https://issues.apache.org/jira/browse/JDO-662
3. Ability to specify positioning of field 'column(s)' in datastore
"table" https://issues.apache.org/jira/browse/JDO-660
4. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
-- Michelle
JDO TCK Conference Call Friday,Oct 15, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 15, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
2. JDO Querying reference. See http://www.datanucleus.org/jdoql_quickref.pdf and comment.
4. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
-- Michelle
JDO TCK Conference Call Friday,Oct 8, 9 am PDT
Posted by mc...@sonic.net.
Meeting scheduled as usual this morning. Sorry about the late email.
-- Michelle
> Hi,
>
> We will have our regular meeting Friday, October 1, at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> US Toll free: 866 682-4770
> Germany Frankfurt 069222216106
> Germany Toll free: 08006648515
> (Other countries by request)
>
> To place the call:
> 1. Call the toll free number.
> 2. Enter the conference number 939-3689#
> 3. Enter the security code 1111#
>
> Agenda:
>
> 1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
> 2. Ability to specify positioning of field 'column(s)' in datastore
> "table" - patch being reviewed.
> https://issues.apache.org/jira/browse/JDO-660
> 3. List.get(int) support in JDOQL is missing - patch being reviewed.
> https://issues.apache.org/jira/browse/JDO-633
> 4. Other issues
>
> Action Items from weeks past:
> [17 Sep 10] AI everyone review the other open issues and suggest
> resolutions
> [6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
JDO TCK Conference Call Friday,Oct 1, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 1, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
2. Ability to specify positioning of field 'column(s)' in datastore
"table" - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-660
3. List.get(int) support in JDOQL is missing - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-633
4. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 24, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Review patch for install schema portion of Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
Need a utility to copy files from one directory to another inside the
mojo. Take a look at Apache Commons FileUtils.
2. Other issues
Email regarding using j2ee and jdo for updates of an object graph.
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 24, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 24, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Review patch for install schema portion of Maven2 upgrade -
https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 17, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Review patch for install schema portion of Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
The attached file seems to work. Making progress.
Could the progress of install schema be logged instead of sending
messages to system output?
How would a user run the tck on an iut (implementation under test)?
Probably choose the implementation via a property in the pom; also
need to specify the name of the enhancer class as a property; both ri
and iut should be made dependencies in the pom so they are
automatically included in the class path of the tck executables.
2. Other issues
Possible candidates to be resolved for 3.1 (implemented or simply
closed):
JDO-64 Enhancer test cases must be adapted to JDO2
JDO-71 Improve test cases in query.operators package
JDO-594 Add @Documented to all JDO Annotations
JDO-607 Require no-args constructor for PMF implementations and add
static methods to PMF interface
JDO-632 Select new build/project tool
JDO-638 Add annotations for instance callbacks
JDO-643 avg return type
JDO-650 Support for conditional operator ? : in JDOQL
JDO-651 Modify specification to address NoSQL datastores
AI everyone review the other open issues and suggest resolutions
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 170, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 17, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Review patch for install schema portion of Maven2 upgrade -
https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 10, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647.
Making progress. First up: install schema goal.
2. Other issues
There are 33 JIRA issues currently unassigned to a release. AI
everyone look at the list https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630
and propose: close, assign to 3.1, leave for a future release.
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD. Most of the xsd and
dtd files have been published to the web. FYI it's unclear what oracle
will do about xsd name spaces; perhaps change from java.sun.com to
java.jsp.org or just jsp.org. No more information available now.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 10, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 10, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade - https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD (in progress)
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 3, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647 In
progress.
2. Other issues
Mail thread on dynamic table creation. AI Craig provide a generic
response. DataNucleus has a more specific way of doing this.
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD In progress.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 3, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 3, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 27, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647
Mojo will have multiple classes for different functions, e.g. enhance,
installschema, runtck. Enhance would attach to the process-classes
phase and the others to the integration-test phase.
Could use profiles to do a number of things in combination, e.g. run
the tck on derby would be the standard specified in the pom but
running the tck on mysql or oracle database could be a combination of
properties specified in a profile. The mojo would be the same for all
the profiles.
Invoking java programs from within the mojo can be as simple as
invoking the static Main method of a named class. For example, if the
installSchema goal needed to execute the program com.acme.script with
command line parameters -Dfile=xyz you would have a line of java code:
com.acme.script.Main(new String[] {"-Dfile=xyz"});
The properties that we use today to control the execution of the tck
can be processed in a similar way by the mojo, which has access to the
java system properties as well as the properties specified in the
pom.xml in the mojo definition itself as well as profile properties.
2. Other issues
Mail regarding parameterized constructors. Michael will reply.
Mail regarding generate dynamic tables. This is a feature of
implementations (e.g. DataNucleus).
Is the JDO 3.0 api jar file available via maven central?
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD. Still in progress.
Might need to escalate.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 27, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 27, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD
[6 Aug 10] AI Craig update the download page with JDO 3 artifacts
[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release
[6 Aug 10] AI Michael reply to a poster that we have a new release with
a class missing from JDO 2.3 EA
-- Michelle
JDO TCK Conference Call Friday, Aug 20, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 20, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade- https://issues.apache.org/jira/browse/JDO-647
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD
[6 Aug 10] AI Craig update the download page with JDO 3 artifacts
[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release
[6 Aug 10] AI Michael reply to a poster that we have a new release with
a class missing from JDO 2.3 EA
-- Michelle
JDO TCK Conference Call Friday, Aug 13, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 13, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Maven2 upgrade
2. Other issues
Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD
[6 Aug 10] AI Craig update the download page with JDO 3 artifacts
[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release
[6 Aug 10] AI Michael reply to a poster that we have a new release with
a class missing from JDO 2.3 EA
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 6, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig L Russell
Agenda:
1. Missing DTD/XSD from SUN/Oracle website. Craig to follow up.
2. Maven2 upgrade. Michelle has assigned this to herself. The api
project has already been converted to use maven 2, but the artifacts
that are generated need to be checked out. The tck project needs a
maven plugin in order to perform the tck with "run once", "run with
datastore identity", "run with application identity", "run derby",
"run mysql", "run ri", "run iut", etc. The plugin will need to be a
separate project and then the tck would depend on the plugin project.
3. Other issues
The JDO 3.0 artifacts have not yet been referenced by the download
page. AI Craig update the download page.
As an official Apache release, we can get publicity. AI Craig talk to
PR and see what we can talk about.
There was a comment that JDO 3.0 had removed a class that was
published in the JDO 2.3 early access. AI Michael reply to the
original poster that we have a new official release and suggest that
there is a substitute class available in JDO 3.0 that can be used.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 6, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 6, at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Missing DTD/XSD from SUN/Oracle website
2. Maven2 upgrade
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, July 30, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 30 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. JDO 3.0 artifacts.
2. Missing DTD/XSD from SUN/Oracle website
3. JDO 3.next
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, July 16, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 16 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Next steps for JDO 3.0 release.
2. Missing DTD/XSD from SUN/Oracle website
3. Fetch configuration
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, July 9, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 9 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Vote on JDO 3.0 release.
2. Provision of a ... query capability for JDOQL
https://issues.apache.org/jira/browse/JDO-652
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, July 2, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 2 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Restructure JDO repository.
2. JDO 3.0 staging release at http://people.apache.org/~clr/dist
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, June 25, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, June 25 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Status of 3.0 release.
2. Provision of a statically-typed refactor-friendly query capability
for JDOQL https://issues.apache.org/jira/browse/JDO-652
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, June 18, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, June 18 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch
available for review. https://issues.apache.org/jira/browse/JDO-557
2. Status of 3.0 release.
3. Review JIRAs
4. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, June 11, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch
available for review. https://issues.apache.org/jira/browse/JDO-557
The attached patch isn't quite the right patch for review. AI Michelle
upload another patch. Since this is an api test it can be checked in
without affecting the release process.
2. Other issues
Do we really need all the maven goals in the root directory? We have
api and tck as new directories but need some maven goals to execute
the new JDO 3.0 projects. And the JDO 1.1 goals no longer work because
the btree cvs checkout doesn't work. AI Craig: is there a new
repository for this code?
JCP release process: The process is changed from last time. This time
we need the final spec, RI, and TCK for review by the EC of JCP. AI
Craig work with JCP to get the final materials into the JCP.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 11, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, June 11 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch
available for review. https://issues.apache.org/jira/browse/JDO-557
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, May 28, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 28 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Comments on spec
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, May 20, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 20 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Extra checks in PMF.close tests
https://issues.apache.org/jira/browse/JDO-653: Are the observed failures
violations of the spec? (11.4 Close the PersistenceManagerFactory)
3. Other issues
Action Items from weeks past:
[May 7 10] AI Craig Notify JCP of recent changes to the spec.
-- Michelle
JDO TCK Conference Call Friday, May 14, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 14 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Other issues
Action Items from weeks past:
[May 7 10] AI Craig Notify JCP of recent changes to the spec.
-- Michelle
Minutes: JDO TCK Conference Call Friday, May 7, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Extra checks in PMF.close tests https://issues.apache.org/jira/browse/JDO-653
If the patch passes the tck then I'd be open to including it in JDO
3.0. If any problems, defer to next release. AI Michelle see if if
works and if so check it in.
2. JDOHelper getObjectIds (Collection) fails with typed collection -
patch available for review. https://issues.apache.org/jira/browse/JDO-655
Looks good. Check it in.
3. JDO 3.0 Vote The vote to release JDO.next was successful. The vote
to change the name to JDO 3.0 was successful. AI Craig change the sub-
projects api2 and tck2 to simply api and tck. Look at integrating
model20 and enhancer20 into the tck or removing the dependencies. Also
need to notify JCP EC of the newest changes to the spec (dynamic
metamodel, query cancel, and datastore timeouts) that are not yet in
the approved list of changes.
Other issues:
Need an assertion in PersistenceManager for datastore timeouts. Move
datastore timeouts to be 12.6.9 and assertion A12.6.9-1.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 7, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 7 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt 069222216106
Germany Toll free: 08006648515
(Other countries by request)
To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#
Agenda:
1. Extra checks in PMF.close tests
https://issues.apache.org/jira/browse/JDO-653
2. JDOHelper getObjectIds (Collection) fails with typed collection -
patch available for review. https://issues.apache.org/jira/browse/JDO-655
3. JDO 3.0 Vote
5. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Apr 30, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 30 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. Extra checks in PMF.close tests
https://issues.apache.org/jira/browse/JDO-653
2. JDOHelper getObjectIds (Collection) fails with typed collection
https://issues.apache.org/jira/browse/JDO-655
3. JDO 3.0 Vote
5. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
How about we use Skype for this call...
On Apr 30, 2010, at 9:07 AM, Craig L Russell wrote:
> Yes, we do. Oracle sent ambiguous messages about conference call
> numbers that would, then wouldn't be disabled.
>
> On Apr 30, 2010, at 9:04 AM, mcaisse@sonic.net wrote:
>
>> Same problem here. I think we need a new number.
>>
>> -- Michelle
>>
>>> Hi,
>>>
>>> I'm not able to dial in. It says: we are sorry, your conference is
>>> unavailable. Please hang up and try again later. Any idea?
>>>
>>> Regards Michael
>>>
>>>> Hi,
>>>>
>>>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>>> https://issues.apache.org/jira/browse/JDO-557
>>>> 2. Spec updates - ready for a vote?
>>>> 3. Other issues
>>>>
>>>> Action Items from weeks past:
>>>>
>>>> -- Michelle
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Michael Bouschen*
>>> *Prokurist*
>>>
>>> akquinet tech@spree GmbH
>>> Bülowstr. 66, D-10783 Berlin
>>>
>>> Fon: +49 30 235 520-33
>>> Fax: +49 30 217 520-12
>>> Email: michael.bouschen@akquinet.de
>>> Url: www.akquinet.de <http://www.akquinet.de>
>>>
>>> akquinet tech@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
>>>
>>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Yes, we do. Oracle sent ambiguous messages about conference call
numbers that would, then wouldn't be disabled.
On Apr 30, 2010, at 9:04 AM, mcaisse@sonic.net wrote:
> Same problem here. I think we need a new number.
>
> -- Michelle
>
>> Hi,
>>
>> I'm not able to dial in. It says: we are sorry, your conference is
>> unavailable. Please hang up and try again later. Any idea?
>>
>> Regards Michael
>>
>>> Hi,
>>>
>>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>> https://issues.apache.org/jira/browse/JDO-557
>>> 2. Spec updates - ready for a vote?
>>> 3. Other issues
>>>
>>> Action Items from weeks past:
>>>
>>> -- Michelle
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Michael Bouschen*
>> *Prokurist*
>>
>> akquinet tech@spree GmbH
>> Bülowstr. 66, D-10783 Berlin
>>
>> Fon: +49 30 235 520-33
>> Fax: +49 30 217 520-12
>> Email: michael.bouschen@akquinet.de
>> Url: www.akquinet.de <http://www.akquinet.de>
>>
>> akquinet tech@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
>>
>
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by mc...@sonic.net.
Same problem here. I think we need a new number.
-- Michelle
> Hi,
>
> I'm not able to dial in. It says: we are sorry, your conference is
> unavailable. Please hang up and try again later. Any idea?
>
> Regards Michael
>
>> Hi,
>>
>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>> https://issues.apache.org/jira/browse/JDO-557
>> 2. Spec updates - ready for a vote?
>> 3. Other issues
>>
>> Action Items from weeks past:
>>
>> -- Michelle
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@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
>
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
same with me.
Regards Michael
> No can do Skype from work. But go ahead without me ...
>
> -- Michelle
>
>
>> Oops, I get the same recording.
>>
>> Do you have a Skype?
>>
>> Craig
>>
>> On Apr 30, 2010, at 9:02 AM, Michael Bouschen wrote:
>>
>>
>>> Hi,
>>>
>>> I'm not able to dial in. It says: we are sorry, your conference is
>>> unavailable. Please hang up and try again later. Any idea?
>>>
>>> Regards Michael
>>>
>>>
>>>> Hi,
>>>>
>>>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>>> https://issues.apache.org/jira/browse/JDO-557
>>>> 2. Spec updates - ready for a vote?
>>>> 3. Other issues
>>>>
>>>> Action Items from weeks past:
>>>>
>>>> -- Michelle
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>> --
>>> *Michael Bouschen*
>>> *Prokurist*
>>>
>>> akquinet tech@spree GmbH
>>> Bülowstr. 66, D-10783 Berlin
>>>
>>> Fon: +49 30 235 520-33
>>> Fax: +49 30 217 520-12
>>> Email: michael.bouschen@akquinet.de
>>> Url: www.akquinet.de <http://www.akquinet.de>
>>>
>>> akquinet tech@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
>>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>>
>
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Here's my status.
Vote is running on releasing what we've been calling JDO 2.3 and
renaming the release JDO 3.0. Most people who voted so far have voted
positively to both.
The artifacts still need a bit more time. I've changed
getObjectIds(Collection<Object>) to getObjectIds(Collection<?>) and
tested it and it seems to work. So this is ready to check in.
I'll start making the final updates to the spec with the above change
and renaming the release to 3.0 and changing the date. Next week we
should have the conference call numbers organized and the vote on the
specification complete. Then we can have the artifact vote for the api
and tck projects.
Nothing else from me.
Craig
On Apr 30, 2010, at 9:08 AM, mcaisse@sonic.net wrote:
> No can do Skype from work. But go ahead without me ...
>
> -- Michelle
>
>> Oops, I get the same recording.
>>
>> Do you have a Skype?
>>
>> Craig
>>
>> On Apr 30, 2010, at 9:02 AM, Michael Bouschen wrote:
>>
>>> Hi,
>>>
>>> I'm not able to dial in. It says: we are sorry, your conference is
>>> unavailable. Please hang up and try again later. Any idea?
>>>
>>> Regards Michael
>>>
>>>> Hi,
>>>>
>>>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>>> https://issues.apache.org/jira/browse/JDO-557
>>>> 2. Spec updates - ready for a vote?
>>>> 3. Other issues
>>>>
>>>> Action Items from weeks past:
>>>>
>>>> -- Michelle
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Michael Bouschen*
>>> *Prokurist*
>>>
>>> akquinet tech@spree GmbH
>>> Bülowstr. 66, D-10783 Berlin
>>>
>>> Fon: +49 30 235 520-33
>>> Fax: +49 30 217 520-12
>>> Email: michael.bouschen@akquinet.de
>>> Url: www.akquinet.de <http://www.akquinet.de>
>>>
>>> akquinet tech@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
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by mc...@sonic.net.
No can do Skype from work. But go ahead without me ...
-- Michelle
> Oops, I get the same recording.
>
> Do you have a Skype?
>
> Craig
>
> On Apr 30, 2010, at 9:02 AM, Michael Bouschen wrote:
>
>> Hi,
>>
>> I'm not able to dial in. It says: we are sorry, your conference is
>> unavailable. Please hang up and try again later. Any idea?
>>
>> Regards Michael
>>
>>> Hi,
>>>
>>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
>>> https://issues.apache.org/jira/browse/JDO-557
>>> 2. Spec updates - ready for a vote?
>>> 3. Other issues
>>>
>>> Action Items from weeks past:
>>>
>>> -- Michelle
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Michael Bouschen*
>> *Prokurist*
>>
>> akquinet tech@spree GmbH
>> Bülowstr. 66, D-10783 Berlin
>>
>> Fon: +49 30 235 520-33
>> Fax: +49 30 217 520-12
>> Email: michael.bouschen@akquinet.de
>> Url: www.akquinet.de <http://www.akquinet.de>
>>
>> akquinet tech@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
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
>
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Oops, I get the same recording.
Do you have a Skype?
Craig
On Apr 30, 2010, at 9:02 AM, Michael Bouschen wrote:
> Hi,
>
> I'm not able to dial in. It says: we are sorry, your conference is
> unavailable. Please hang up and try again later. Any idea?
>
> Regards Michael
>
>> Hi,
>>
>> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
>> 2. Spec updates - ready for a vote?
>> 3. Other issues
>>
>> Action Items from weeks past:
>>
>> -- Michelle
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon: +49 30 235 520-33
> Fax: +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@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
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
I'm not able to dial in. It says: we are sorry, your conference is
unavailable. Please hang up and try again later. Any idea?
Regards Michael
> Hi,
>
> We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
> https://issues.apache.org/jira/browse/JDO-557
> 2. Spec updates - ready for a vote?
> 3. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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, Apr 23, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Making progress. Found an issue with how the test url class loader is
being set up.
2. Spec updates - ready for a vote?
No objections have been raised to voting on the specification. One
comment was that we should call this JDO 3.0 in light of the major
features: new Metadata API and new Enhancer API that allow tools to
create dynamic classes and then in a standard way specify the metadata
and enhance the classes at runtime.
AI Craig discuss the release number and call for a vote.
3. Other issues
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Apr 23, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 23 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Spec updates - ready for a vote?
3. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Apr 16, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
For the record, found this in my out-box...
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Some progress but still doesn't work. JDOHelper cannot load the test
2. Provision of a statically-typed refactor-friendly query capability
for JDOQL https://issues.apache.org/jira/browse/JDO-652
Sounds good. Volunteers to drive this forward?
3. Spec updates are done and draft version is published. Any comments
before we vote?
4. Other issues
The latest DataNucleus snapshot throws a different exception for
datastore timeouts than is in the specification. AI Michael discuss in
the context of the timeout JIRA.
AI: Craig check the spec for timeout rounding. The implementation
should be able to round the given timeout value up to the values
supported by the driver.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Apr 16, 9 am PDT
Posted by Timo Westkämper <ti...@mysema.com>.
On 04/16/2010 07:46 PM, Craig L Russell wrote:
> 2. Provision of a statically-typed refactor-friendly query capability
> for JDOQL https://issues.apache.org/jira/browse/JDO-652
>
> Sounds good. Volunteers to drive this forward?
Hi.
I propose to split the standardization of the statically typed query
capability into a general part and a JDOQL specific part. A fork of
certain Querydsl parts could provide a foundation for both.
The reason for the splitted approach is that a standardization of the
general model would benefit also other frameworks and could become a
foundation for LINQ in Java.
The general part could be formed of the contents of the following
Querydsl packages :
com.mysema.query
com.mysema.query.types
com.mysema.query.types.custom
com.mysema.query.types.expr
com.mysema.query.types.path
com.mysema.query.types.query
The JDO specific elements could consist of the following elements :
com.mysema.query.jdoql.JDOQLSubQuery -> javax.jdo.query.SubQuery ?!?
com.mysema.query.jdoql.JDOQLQuery -> javax.jdo.query.Query ?!?
of course with some modifications
and a standardization of the code generation (probably also via APT).
What do you think about this approach?
Best regards,
Timo Westkämper.
Minutes: JDO TCK Conference Call Friday, Apr 16, 9 am PDT
Posted by Craig L Russell <cr...@Oracle.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Some progress but still doesn't work. JDOHelper cannot load the test
class from the context class loader.
2. Provision of a statically-typed refactor-friendly query capability
for JDOQL https://issues.apache.org/jira/browse/JDO-652
Sounds good. Volunteers to drive this forward?
3. Spec updates are done and draft version is published. Any comments
before we vote?
4. Other issues
The latest DataNucleus snapshot throws a different exception for
datastore timeouts than is in the specification. AI Michael discuss in
the context of the timeout JIRA.
AI: Craig check the spec for timeout rounding. The implementation
should be able to round the given timeout value up to the values
supported by the driver.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Apr 16, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 16 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Provision of a statically-typed refactor-friendly query capability
for JDOQL https://issues.apache.org/jira/browse/JDO-652
3. Spec updates
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Apr 8, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 8 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. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Query.executeWithMap(...) should accept unused parameters
3. Query cancel and timeout support
https://issues.apache.org/jira/browse/JDO-623
4. Spec updates
5. Other issues
Action Items from weeks past:
Apr 2 2010: AI Craig check in the test.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 26, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Query Cancel TCK tests
With the latest tests it seems that the big job in query is during
ResultSet.next() instead of Statement.execute(). Next try to write
lock some instances and see if that affects the behavior.
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Making progress; a bit of reorganization and testing is still needed.
3. Metadata tests Andy says that the latest snapshots of DataNucleus
contain a fix for the getParent() returning nothing. AI Craig test
with the SNAPSHOT version.
4. Spec updates No changes since last week.
5. Other issues
NoSQL might be a good way to improve JDO's visibility. https://issues.apache.org/jira/browse/JDO-651
JDO was designed to support non-SQL datastores. In fact, the first RI
was a distinctly non-SQL implementation, essentially a key-value
store. What needs to be done for NoSQL in general is to go through the
specification in detail and highlight those parts that cannot now be
implemented reasonably by a key-value store, or a non-transactional
datastore. NoSQL is probably too big a description of the kinds of
datastores that makes sense for JDO to support. Part of the exercise
should be to categorize the NoSQL datastores to focus on those
categories that make sense for JDO.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Apr 2, 9 am PDT
Posted by Craig L Russell <cr...@oracle.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Query Cancel TCK tests. No joy. Looks like Derby doesn't actually
execute the query until ResultSet.next(). Try waiting only one
millisecond. Try write locking the instances. If nothing works, call
the assertion untestable.
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
. No joy. Stuck trying to make a class loader that has both
jdoconfig.xml and the test classes. Try documenting where you're stuck
and ask for help on the dev list.
3. Spec updates. No joy. AI Craig update the spec and send it to
Michelle for printing.
4. Other issues
Success running Metadata test case. AI Craig check in the test.
JDO TCK Conference Call Friday, Apr 2, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 2 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. Query Cancel TCK tests
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
3. Spec updates
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Mar 26, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
Please note :
- The U.S. has switched to Daylight Saving Time..
We will have our regular meeting Friday, March 26 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. Query Cancel TCK tests
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
3. Metadata tests
4. Spec updates
5. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 19, 11 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Query Cancel TCK tests
New tests were checked in. AI run the patched tests with the latest
DataNucleus code. Other comments?
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Progress...
3. Spec updates
Craig sent an updated spec to Michelle for printing. AI Craig check
the assertions for DatastoreTimeout and send mail with the assertion
numbers.
Query cancel assertion is 14.6.1-8: is this correct? AI Craig check
the number.
Changes for 2.3: AI Craig make sure that the changes are identified.
4. Other issues:
Metadata API still needs test case.
Craig L Russell
Assistant Secretary, Apache Software Foundation
Chair, OpenJPA PMC
clr@apache.org http://db.apache.org/jdo
NOTE TIME CHANGE: JDO TCK Conference Call Friday, Mar 12, 11 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
Please note :
- This week's meeting is temporarily at a different time AND
- The U.S. has switched to Daylight Saving Time..
We will have our regular meeting Friday, March 12 at 11 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. Query Cancel TCK tests
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
3. Spec updates
4. Other issues
Action Items from weeks past:
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Mar 12, 9 am PST
Posted by Craig L Russell <Cr...@SUN.com>.
Hi Michelle,
That's great.
Thanks,
Craig
On Mar 13, 2010, at 5:27 PM, Michelle Caisse wrote:
> Craig L Russell wrote:
>>
>> The behead script that removes the first several lines from
>> annotations and enums doesn't work for regular classes and
>> interfaces. It would be nice if the script could also support
>> classes and interfaces.
> I've checked in a new version that supports any .java file with a
> "public class" or "public interface" declaration. I had trouble with
> a couple of files for which the output was one line short. The first
> line (declaration) was missing. Making a no-change edit to the file
> and resaving fixed the issue. Apparently there is something funny
> about the last line in these files. The ones I found were
> Enhancer.java JDOEnhancer.java and JDOReadOnlyException.java.
>
> -- Michelle
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Mar 12, 9 am PST
Posted by Michelle Caisse <mc...@sonic.net>.
Craig L Russell wrote:
>
> The behead script that removes the first several lines from
> annotations and enums doesn't work for regular classes and interfaces.
> It would be nice if the script could also support classes and interfaces.
I've checked in a new version that supports any .java file with a
"public class" or "public interface" declaration. I had trouble with a
couple of files for which the output was one line short. The first line
(declaration) was missing. Making a no-change edit to the file and
resaving fixed the issue. Apparently there is something funny about the
last line in these files. The ones I found were Enhancer.java
JDOEnhancer.java and JDOReadOnlyException.java.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 12, 9 am PST
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Special meeting time for next week only: 11:00 AM Pacific Daylight Time
Agenda:
1. Query Cancel TCK tests
Andy raised a question that the test case doesn't work for
implementations that support query cancel. The main thread doesn't
sleep before canceling the query thread, which probably hasn't started
executing. We should put a sleep into the main thread after starting
the thread and before canceling the query. Depending on how this works
out, we might also need to implement a barrier to make sure that both
threads are running before the cancel executes. AI Michael update the
test case.
A second issue is what the scope of the cancel. It might be that the
user has finished executing the query and has a result that is
iterating. In this case, the cancel might be useful to cancel the
execution of the result set iteration. But it's not clear whether the
underlying implementation can cancel a statement that has finished
executing. In this case, for both JDO and the underlying
implementation, the Query (or Statement) is no longer executing. So if
the Query has given back a result, it can no longer be canceled. The
user should use a datastore timeout to control iteration of the result.
The question is still whether the caller of cancel should be able to
know whether the cancel had any effect. It's not obvious that it's
possible to know with any certainty. The only indication from
Statement.cancel() is an exception if the Statement has been closed.
The behavior if the Statement has returned a result doesn't appear to
be documented. So probably the best we can do is to cancel any
Statement that we know is being executed, which satisfies the main
reason for this API.
AI Craig update the specification.
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
The class that needs to be created for the test just needs to
implement the static method, and not necessarily the PMF interface,
but it can return a proxy for PMF.
3. Spec updates. Matthew Adams commented that the changed spec seems
to require a specific state of the instance even if there is an
existing instance in the cache. AI Craig clarify the spec in this case.
4. Other issues
The behead script that removes the first several lines from
annotations and enums doesn't work for regular classes and interfaces.
It would be nice if the script could also support classes and
interfaces.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Mar 12, 9 am PDT
Posted by Michael Bouschen <mi...@akquinet.de>.
Hi,
I'm not able to dial in, it says "my access code is not recogniszed". Is
there a new phone number and/or a new access code?
Regards Michael
> Hi,
>
> We will have our regular meeting Friday, March 12 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. Query Cancel TCK tests
> 2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
> 3. Spec updates
> 4. Other issues
>
> Action Items from weeks past:
>
> -- Michelle
>
>
>
>
>
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
JDO TCK Conference Call Friday, Mar 12, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 12 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. Query Cancel TCK tests
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
3. Spec updates
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Mar 5, 9 am PDT
Posted by mc...@sonic.net.
Hi,
We will have our regular meeting Friday, February 26 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. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 26, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Create tests ... for JDO implementation's static method
getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
No action on this one.
2. Query cancel and timeout support https://issues.apache.org/jira/browse/JDO-623
"Final" changes were checked in.
3. Other issues
Metadata signatures are checked by the tck but no tests yet for
actually checking that the metadata is consistent with the .jdo files.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 26, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 26 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. Create tests ... for JDO implementation's static method
getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Query cancel and timeout support
https://issues.apache.org/jira/browse/JDO-623
3. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 19, 9 am PDT
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Create tests ... for JDO implementation's static method
getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Michelle will try to get a preliminary test case for next week.
2. Other issues
Specification change outline: AI review by everyone.
Q. How can you use JDO project in Netbeans? The maven 1 plugin doesn't
quite work.
A. You can't build/run from within Netbeans but you can at least
import the project. Tell Netbeans it's a project without a build
script and Netbeans will create one for you (which you can ignore).
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 19, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 19 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. Create tests ... for JDO implementation's static method
getPersistenceManagerFactory(Map,Map)
https://issues.apache.org/jira/browse/JDO-557
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday,Feb 12, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 12 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. Task for JDO 2.3 release
2. Other issues
Action Items from weeks past:
-- Michelle
NO! JDO TCK Conference Call Friday, Jan 29, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
Reminder: There is no conference call tomorrow.
The next meeting will be Friday, February 12 at 9 am PDT to discuss JDO
TCK issues and status.
-- Michelle
JDO TCK Conference Call Friday, Jan 29, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 29 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. Query cancel and timeout support: Review patch.
https://issues.apache.org/jira/browse/JDO-623
2. Other issues
Action Items from weeks past:
-- Michelle
NO JDO TCK Conference Call Friday, Jan 22, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will NOT meet on Friday, January 22. Next meeting will be on Friday,
January 29 at 9 am PDT to discuss JDO TCK issues and status.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Support specification of exact class in SingleFieldIdentity https://issues.apache.org/jira/browse/JDO-630
these review notes will go into the jira
test case review: comment PartTimeEmployee is wrong; should be
FullTimeEmployee
remove system.out.println; replace with log.debug
testConcreteSuperclassExact test case is wrong
should expect exactly Person.class not instanceof test; then should
fail when database access discovers wrong class
message is wrong; should say when accessing database you find out
wrong class
testWrongClass:
message needs improvement
2. Other issues
Metadata API needs a test case. Might be just the API needs to be
exercised but would also be good to try to duplicate the metadata for
the company model.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 15, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 15 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. Support specification of exact class in SingleFieldIdentity
https://issues.apache.org/jira/browse/JDO-630
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Jan 8, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, January 8 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. Query timeout in JDO / Update timeout
2. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Dec 18, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
NOTICE: Due to the holidays, there will be no conference calls on
December 25 or January 1.
The next meeting is scheduled for January 8.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Query timeout in JDO / Update timeout. The patch looks good and was
checked in. AI Michael add the query timeout test. Two test cases
needed: one to test the timeout behavior (read versus write lock
interaction) and one to test the setting of the timeout values in PMF
properties, PMF API, PM API, and Query API.
Also need assertions for the spec which hasn't been written yet. AI
Craig write the spec and add the assertion.
Is there a volunteer to write the test case for setting of the timeout
values?
2. Other issues
Action Items from weeks past:
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 18, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 18 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. Query timeout in JDO / Update timeout
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Dec 11, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 11 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. Query timeout in JDO / Update timeout - Done deal?
2. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Dec 4, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, December 4 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. Query timeout in JDO / Update timeout (See latest email on the list
from Craig)
2. Support for conditional operator in JDOQL
https://issues.apache.org/jira/browse/JDO-650
3. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Nov 20 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 20 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. Query timeout in JDO / Update timeout
2. Query objects and hashCode() + equals()
3. Dependence of RI on JPA2
4. Other issues
Action Items from weeks past:
AI Nov 13 08 Michael: Take a look at what changes would be needed in the
BNF to support for if-then-else in JDOQL, reply to the original email
-- Michelle
JDO TCK Conference Call Friday, Nov 13 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, November 13 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. Change JTA 1.1 dependency artifact id from "transaction-api" to "jta"
https://issues.apache.org/jira/browse/JDO-644
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
3. Question re Support for if-then-else in JDOQL
4. Other issues
Action Items from weeks past:
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Oct 30 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
I'm sorry, I missed the call today. I forgot that the conference call is
one hour earlier for me, because Germany already switched back from
daylight saving time. I checked my email to prepare for the conference
call and found the minutes :-).
Regards Michael
> Attendees: Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. Change JTA 1.1 dependency artifact id from "transaction-api" to
> "jta" https://issues.apache.org/jira/browse/JDO-644
>
> It seems that there is a problem with the patch. Since the only
> artifact affected for maven 2 users is the api2/pom.xml, and maven 1
> is used for everything else, perhaps simply updating the api2 pom
> would be best. AI Michelle test just updating api2 pom and update the
> JIRA.
>
> 2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
>
> Still open AI's to finish the discussion of what exactly query timeout
> means, and whether it's optional.
>
> 3. Other issues
>
> Action Items from weeks past:
>
> 16 Oct 08 AI Michelle: Investigate query timeouts as they apply to SQL
> standard datastores.
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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, Oct 30 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Change JTA 1.1 dependency artifact id from "transaction-api" to
"jta" https://issues.apache.org/jira/browse/JDO-644
It seems that there is a problem with the patch. Since the only
artifact affected for maven 2 users is the api2/pom.xml, and maven 1
is used for everything else, perhaps simply updating the api2 pom
would be best. AI Michelle test just updating api2 pom and update the
JIRA.
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
Still open AI's to finish the discussion of what exactly query timeout
means, and whether it's optional.
3. Other issues
Action Items from weeks past:
16 Oct 08 AI Michelle: Investigate query timeouts as they apply to SQL
standard datastores.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 30 9 am PDT NOTE TIME CHANGE
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 30 at 9 am PDT to
discuss JDO TCK issues and status.
NOTE THAT THE U.S. IS STILL ON DAYLIGHT SAVINGS TIME TODAY!
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Change JTA 1.1 dependency artifact id from "transaction-api" to "jta"
https://issues.apache.org/jira/browse/JDO-644
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
3. Other issues
Action Items from weeks past:
16 Oct 08 AI Michelle: Investigate query timeouts as they apply to SQL
standard datastores.
-- Michelle
JDO TCK Conference Call Friday, Oct 23 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 23 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. Change JTA 1.1 dependency artifact id from "transaction-api" to "jta"
https://issues.apache.org/jira/browse/JDO-644
2. Query timeout test https://issues.apache.org/jira/browse/JDO-623
3. tck enhancement should make use of feature to enhance an entire
directory https://issues.apache.org/jira/browse/JDO-639
4. Run TCK using Maven2 for consistency
https://issues.apache.org/jira/browse/JDO-647
5. Select new build/project tool
https://issues.apache.org/jira/browse/JDO-632 - Close it for lack of
volunteers?
6. runtime2 project fails to compile
https://issues.apache.org/jira/browse/JDO-648
7. Query objects and hashCode() + equals()
http://www.nabble.com/Query-objects-and-hashCode()--%2B-equals()-td25928614.html
8. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 16, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Update DataNucleus dependencies in tck2 https://issues.apache.org/jira/browse/JDO-642
It looks like we should go with 2.0.0-m3-SNAPSHOT for now. This give
us the ability to make changes to DataNucleus to resolve issues. AI
Michael track down the dependencies and update the project.xml.
2. Query timeout test - need option to test for support? https://issues.apache.org/jira/browse/JDO-623
As a reminder, the original JIRA issue was opened by Andy in February:
> JDO doesn't have a mechanism to stop queries from overrunning. JPA2
> now allows
> a persistence property to allow timing them out, and most JDO
> implementations
> have allowed this as an extension since JDO1. It would make sense
> for JDO
> (2.3) to have the same or a variation. I propose having the following
>
> Simple PMF property "javax.jdo.option.queryTimeout" to specify the
> number of millisecs (or secs) before any query is timed out. Throw a
> QueryTimeoutException (extends JDOException) when the timeout happens.
>
> Add methods Query.setTimeout(int), Query.getTimeout() to allow
> setting/retrieving the timeout interval on a per-query basis.
>
> Add method Query.cancel() to cancel any running query. If an
> implementation doesn't support cancelling of queries then it should
> throw a JDOUnsupportedOptionException. Any query execute() that is
> cancelled will throw a QueryInterruptedException (extends
> JDOUserException).
Subsequently, Andy wrote:
> You mean the datastore itself always supports a timeout?or do you
> mean a JDO
> implementation can manage a timeout itself ? The former is clearly
> not the
> case since there are a wide variety of datastores, some file based,
> with APIs
> that don't provide such things as timeouts.
Low-function datastores (file systems, etc.) don't need a timeout
because the query is executed by the JDO implementation itself. And
the JDO implementation can add hooks to the execution processing so as
to time out the function.
High-function datastores generally provide a user-specified timeout.
Access to the underlying connection to the datastore is mediated by
the JDO implementation, so the expectation is that the JDO
implementation will pass the user's timeout request directly to the
underlying connection.
> RDBMS datastores do allow a
> timeout to be set yet JDBC is so imprecisely defined that you get an
> SQLException and so have no simple way of knowing that it was a
> timeout
> (without having to play around with arbitrary JDBC error numbers).
This is precisely why we want to define the timeout at the JDO user
level and not require the user to play around with JDBC. There are
many features in JDO that get translated into datastore-specific
methods and this is just one more. I expect that for a specific
datastore, a query timeout will have a specific SQL error code, even
if not all datastores implement the same codes.
> PS, what is the definition of the timeout ? Is it the time taken to
> communicate with the datastore ?
The user is in control of activities inside the VM, and there's no
need for a JDO-specific timeout for these. What we want to influence
is what happens once the query leaves the JDO implementation. So the
timeout would be on the JDBC statement.execute call.
> or is it the total time for the query
> execution (which may include compilation) ?
Since the user can compile the query, the timeout should just apply to
the database processing and not include the preparation or post-query
processing.
3. javax.jdo.Enhancer fails to pass full path name for the file
arguments https://issues.apache.org/jira/browse/JDO-641
Looks like the patch program did not install the zero-byte test files.
After manually touching the test files, the test now runs. AI Michelle
test the tck to see if this allows the tck change to work and update
the JIRA.
4. Add annotations for instance callbacks. https://issues.apache.org/jira/browse/JDO-638
No news.
5. Other issues
https://issues.apache.org/jira/browse/JDO-643 says avg should not
return the type of the enclosed expression but should always return
double. AI Michelle take a look at the SQL implementations to see what
they do and then we can decide what make sense. This would be an
incompatible change so we need to look at the implications.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 16, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 16 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. Update DataNucleus dependencies in tck2
https://issues.apache.org/jira/browse/JDO-642
2. Query timeout test - need option to test for support?
https://issues.apache.org/jira/browse/JDO-623
3. javax.jdo.Enhancer fails to pass full path name for the file
arguments https://issues.apache.org/jira/browse/JDO-641
4. Add annotations for instance callbacks.
https://issues.apache.org/jira/browse/JDO-638
5. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 9, 9 am PDT
Posted by mc...@sonic.net.
Attendees: Michelle Caisse, Michael Bouschen
- Update DataNucleus dependencies in tck2
https://issues.apache.org/jira/browse/JDO-642
If no objection from DataNucleus, Michael will update the TCK dependencies
to version 1.1.6-SNAPSHOT for core and rdbms.
- Query timeout test still fails.
https://issues.apache.org/jira/browse/JDO-623
Andy suggests that a new javax.jdo.option.* flag is needed to test for
datastore support for query timeout. Discussion at last week's meeting
suggested that all data stores support it. Need resolution on this
question to know how to proceed.
- Add annotations for instance callbacks.
https://issues.apache.org/jira/browse/JDO-638
No news
- javax.jdo.Enhancer fails to pass full path name for the file arguments
https://issues.apache.org/jira/browse/JDO-641
Craig added patch that needs to be tested. Please test. AI Michelle to
test and try changes for https://issues.apache.org/jira/browse/JDO-639
-- Michelle
JDO TCK Conference Call Friday, Oct 9, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 9 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. Update DataNucleus dependencies in tck2
https://issues.apache.org/jira/browse/JDO-642
2. Query timeout test still fails.
https://issues.apache.org/jira/browse/JDO-623
3. Add annotations for instance callbacks.
https://issues.apache.org/jira/browse/JDO-638
4. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Oct 2, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. javax.jdo.Enhancer fails to pass full path name for the file
arguments https://issues.apache.org/jira/browse/JDO-641 This should be
fixed for 2.3. AI Craig improve the test case and fix the bug.
2. Query timeout test still fails. https://issues.apache.org/jira/browse/JDO-623
The "regular" implementation still fails because timeouts are not
supported. The "improved" implementation fails because the query is
not yet supported. AI check in the changed configuration with the
failure.
3. Add annotations for instance callbacks. https://issues.apache.org/jira/browse/JDO-638
No updates to the issue.
4. Other issues
Should we use DataNucleus 1.1.6-SNAPSHOT for trunk? Probably, since
1.1.5 doesn't pass the current TCK.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 2, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, October 2 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. javax.jdo.Enhancer fails to pass full path name for the file
arguments https://issues.apache.org/jira/browse/JDO-641
2. Query timeout test still fails.
https://issues.apache.org/jira/browse/JDO-623
3. Add annotations for instance callbacks.
https://issues.apache.org/jira/browse/JDO-638
4. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 25, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig
Russell
Agenda:
1. TCK enhancement should make use of feature to enhance an entire
directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
Seems to be a bug in the enhancer. The version being used is
DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
2.3 tck?
2. Query timeout test still fails. https://issues.apache.org/jira/browse/JDO-623
Any idea when this feature will be enabled for DataNucleus?
3. Add annotations for instance callbacks: patch added. Comments? https://issues.apache.org/jira/browse/JDO-638
The latest patch suggests ordering of callbacks in case there are
multiple callbacks for the same event. It's not obvious to me that
this is a good enhancement, since the reason to order the callbacks is
internal to the callbacks, and ordering of callbacks can be done by
the user in most cases. The exception would be callbacks implemented
on subclasses and superclasses. We might require ordering of such
callbacks to be subclass first or superclass first. Subclass first
might make sense for some events; superclass first might make sense
for others. There is an ordering specified for callbacks and listeners
defined on the same event.
Also, if an overridden method is declared in a superclass, only the
subclass method is visible (virtual inheritance in Java). But the
implementation should recognize that there is an annotated method in a
superclass, and that method is overridden in a subclass, then
regardless of whether the subclass method is annotated, the method
should be registered for callbacks; and should only be called once for
each event for which it is annotated.
And what about those test cases?
4. Other issues
JDO wiki from Berlin seems to have some issues (reported by Michael).
If he tries the url http://wiki.apache.org/jdo/FrontPage everything
looks normal. But the urls http://wiki.apache.org/jdo/ and http://wiki.apache.org/jdo
redirect to a German page from which the link to the FrontPage is
visible. Suggest to contact infrastructure to troubleshoot.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 25, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 25 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. TCK enhancement should make use of feature to enhance an entire
directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
2. Query timeout test still fails.
https://issues.apache.org/jira/browse/JDO-623
3. Add annotations for instance callbacks: patch added. Comments?
https://issues.apache.org/jira/browse/JDO-638
4. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Sep 18, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 18 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. tck enhancement should make use of feature to enhance an entire
directory - Does the JIRA capture all relevant information?
https://issues.apache.org/jira/browse/JDO-639
2. Naming issue: different numbering for JCP Maintenance Revision 4 and
JDO Maintenance Release 2.3
3. Other issues
Action Items from weeks past:
-- Michelle
JDO TCK Conference Call Friday, Sep 11, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, September 11 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. Add javax.jdo.JDOEnhancerMain to call the enhancer via standard API
https://issues.apache.org/jira/browse/JDO-621 Comments on new patch?
2. Add annotations for instance callbacks
https://issues.apache.org/jira/browse/JDO-638 No objections have been
raised re the last comments added to the issue.
3. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635 Issue is ready to be
closed. Any last comments?
4. Other issues
Action Items from weeks past:
-- Michelle
Re: JDO TCK Conference Call Friday, Aug 28, 9 am PDT
Posted by Craig L Russell <Cr...@SUN.com>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Add annotations for instance callbacks https://issues.apache.org/jira/browse/JDO-638
No reaction to last week's conference call minutes. Michael will
update the JIRA with the discussion.
2. tck2 does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
Documentation for the 1.5 issue was checked in. Michelle will update
HowToReleaseJDO (top level) and run rules in trunk.
3. Other issues
Hang issue running the enhancer test under Windows. Craig added
threads to the test to read the output and error streams; Michael
verified it works. Ready for checkin.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 28, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 28 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. Add annotations for instance callbacks
https://issues.apache.org/jira/browse/JDO-638
2. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
3. Other issues
Action Items from weeks past:
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 21, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Add annotations for instance callbacks https://issues.apache.org/jira/browse/JDO-638
There is a new patch that includes the missing metadata for the
annotations.
An argument can be made that for separation of concerns, multiple
methods with the same annotation are not only acceptable but
encouraged. So in this scenario, the only check would be that the
method be niladic and return void. The order of execution of callbacks/
annotated methods is not defined.
So with this approach, mixing annotations and callbacks isn't an error
condition.
Any other ideas?
I'd also defer checking this in for JDO 2.3 until test cases have been
written.
2. tck2 does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
Since JDK 1.5 will become EOL soon, we should not spend too much
energy on this. Propose to document the issue (need to comment out the
properties line that references the 1.6 pre-processor) in a few places.
3. Other issues
https://issues.apache.org/jira/browse/JDO-621 The enhancer main
program is complete and needs to be reviewed. Michael has tested the
patch on Windows and the subprocess seems to hang. Suggest reading the
standard output and standard error from the subprocess and look for
clues.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Aug 14, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Add annotations for instance callbacks https://issues.apache.org/jira/browse/JDO-638
No objections to adding annotations for this purpose. Should add
@Target and @Retention before going much farther.
2. tck2 does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
This might have to be noted in the release notes.
3. Other issues
http://issues.apache.org/jira/browse/JDO-621 still needs review.
Issue: If the user makes a mistake, the usage message will be printed
to stderr. If the user wants to see the usage, by saying Enhancer ?,
should the usage message be printed to stderr or stdout?
http://issues.apache.org/jira/browse/JDO-623 has been reviewed and is
ok to check in. The implementation isn't ready yet so the JIRA will
remain open until the tests can be run as part of the automatic test
suite.
Action Items from weeks past:
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 14, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 14 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. Add annotations for instance callbacks
https://issues.apache.org/jira/browse/JDO-638
2. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
3. Other issues
Action Items from weeks past:
--
-- Michelle
Re: JDO TCK Conference Call Friday, Aug 7, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Patch to review for https://issues.apache.org/jira/browse/JDO-621
2. tck2 does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
Two possibilities: find a version of 1.5 that ignores the proc option,
or document that you need to comment out the compiler options in tck2/
project.properties.
3. Other issues
The patch for JDO-623 https://issues.apache.org/jira/secure/attachment/12413244/JDO-623-tck2-mbo.patch
needs to be reviewed.
The patch for JDO-621 https://issues.apache.org/jira/secure/attachment/12415203/jdo-621.patch
needs to be reviewed.
Action Items from weeks past:
--
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 7, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, August 7 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. Patch to review for https://issues.apache.org/jira/browse/JDO-621
2. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
3. Other issues
Action Items from weeks past:
--
-- Michelle
JDO TCK Conference Call Friday, July 24, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 24 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. Using resource names vs file names: Add javax.jdo.JDOEnhancerMain to
call the enhancer via standard API
https://issues.apache.org/jira/browse/JDO-621
2. tck2 does not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
3. Other issues
Action Items from weeks past:
--
-- Michelle
Minutes: JDO TCK Conference Call Friday, July 10, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. TCK2 Does not compile with JDK 1.5 https://issues.apache.org/jira/browse/JDO-635
Removing the enhancer jar from the compile classpath seems like the
right answer. AI Michelle investigate and fix the bug.
2. Other issues
Query testing for cancel and timeout. The current DataNucleus release
has two versions of query implementation. Assertion numbers are needed
for section 14.6.1 for the new subheads timeout and cancel.
A14.6.1-7 for query timeout and A14.6.1-8 for query cancel.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 10, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 10 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. oes not compile with JDK 1.5
https://issues.apache.org/jira/browse/JDO-635
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
NO JDO TCK Conference Call Friday, July 31
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will NOT have our regular meeting this week. Back next week.
-- Michelle
NO JDO TCK Conference Call Friday, July 17
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will NOT have our regular meeting this week. Back next week.
-- Michelle
JDO TCK Conference Call Friday, July 3, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, July 3 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. JDO TCK project.properties changes
2. DataNucleus dependencies in JDO TCK
3. 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
Minutes: JDO TCK Conference Call Friday, June 26, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. M2 build process doesn't put correct MANIFEST.MF in jar file https://issues.apache.org/jira/browse/JDO-634
Looks like it's easy to generate OSGi information in the manifest by
using the felix plugin. Anything besides the OSGi missing?
2. List.get(int) support in JDOQL is missing https://issues.apache.org/jira/browse/JDO-633
The change to the specification is one line. Implementation in the RI
sounds straightforward. I'd say it's too late for JDO 2.3 but it can
be implemented and tested with DataNucleus and considered for a future
update.
3. Other issues
http://issues.apache.org/jira/browse/JDO-623 How to create a query
that is "guaranteed" to run slow enough that another thread can cancel
it? Perhaps something like this would work: "SELECT AVG(t0.c1 + t1.c1
+ t2.c1) FROM t0, t1, t2" where t0, t1, and t2 are simply tables with
columns c0 INT, c1 INT. With a relatively small number of rows (100)
you would have the query do an outer join of 100 * 100 * 100 rows
(1,000,000 rows). If the optimizer can calculate the average by
itself, you might add "WHERE t0.c1 > 1 AND t0.c1 < 1000" to avoid the
optimization.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 26, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, June 26 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. M2 build process doesn't put correct MANIFEST.MF in jar file https://issues.apache.org/jira/browse/JDO-634
2. List.get(int) support in JDOQL is missing https://issues.apache.org/jira/browse/JDO-633
3. 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
JDO TCK Conference Call Friday, June 19, 9 am PDT
Posted by mc...@sonic.net.
Hi,
We will have our regular meeting Friday, June 19 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. 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
JDO TCK Conference Call Friday, June 12, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, June 12 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. Use JDO TCK to test Querydsl query creation?
2. API required for enabling/disabling FOR UPDATE locking for SELECTs
https://issues.apache.org/jira/browse/JDO-619
3. 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
Minutes: JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
+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.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>>
>>
>
>
>
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@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
Re: JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by mc...@sonic.net.
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.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 5, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
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
JDO TCK Conference Call Friday, May 29, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 29 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. MetaData specification API patch
https://issues.apache.org/jira/browse/JDO-615
2. untck.iut and datanucleus trunk
3. Embedded object and evict
4. 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
Minutes: JDO TCK Conference Call Friday, May 22, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. New comments on MetaData specification API https://issues.apache.org/jira/browse/JDO-615
This seems to be a good idea, since "component" is so overloaded, and
"type" has a specific meaning in Java. It's still ok to change since
the API is "early access" status.
AI Everyone with an opinion: update the JIRA with your comments.
The patch doesn't seem quite correct...
2. Other issues
The instructions on how to release have been updated 22-May-2009 to
include instructions on synchronizing the m1-ibiblio-rsync-repository.
Several changes are needed in the specification:
There were a small number of cosmetic changes in the 2.3
specification, to add a space after the ending period of sentences.
Unfortunately, these are marked as changes with change bars.
Remove blank from before the fourth bullet p. 126.
SerializeRead property description on p. 158 should state the effect
on the transaction mode (none) and on the connection (optimistic
transaction will retain the connection until the end of the
transaction since the connection holds the lock).
Same discussion in the Query section on p. 171. We need to decide if
the SerializeRead property should be copied or serialized, so might
need to update section 14.5 on p. 167.
The 2.3 versions of orm, jdoquery, and jdoconfig need to be updated in
the spec. The jdoquery should add the timeout option. The 2.3 version
of jdo also needs to add jdoquery timeout. What about the
SerializeRead for the xml versions of jdoquery?
The query timeout needs to be added to the query metadata API p. 305.
27.4 The enhancer API is now defined so this paragraph needs to be
edited.
27.5 The fetch plan API is now defined so this paragraph needs to be
edited.
27.7 There are managed relationships so this paragraph needs to be
edited.
The footer for 2.3 EA still has the date May 8.
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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 22, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 22 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. New comments on MetaData specification API
https://issues.apache.org/jira/browse/JDO-615
2. Other issues
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[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
JDO TCK Conference Call Friday, May 15, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 15 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. Latest JDO 2.3 spec -- comments?
2. Other issues
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[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, May 8, 9 am PDT
Posted by mc...@sonic.net.
Will do, thanks for following up.
-- Michelle
>
> Dear Michelle,
> you can remove the AI Christiaan, seeing the fact that no one responded to
> the feature request in:
> http://www.nabble.com/Feature-request%3A-copy-by-query-to13855888.html#a13855888
>
> Avoiding the roundtrip when creating a copy of an object tree thus
> decreasing memory usage and increasing performance seemed nice to me, but
> appearently I am the only one;-) No need to further analyze it.
>
> kind regards,
> Christiaan
>
> --
> View this message in context:
> http://www.nabble.com/JDO-TCK-Conference-Call-Friday%2C-June-15%2C-9-am-PDT-tp11129570p23519331.html
> Sent from the JDO - Development mailing list archive at Nabble.com.
>
>
Re: JDO TCK Conference Call Friday, May 8, 9 am PDT
Posted by Christiaan <ch...@hotmail.com>.
Dear Michelle,
you can remove the AI Christiaan, seeing the fact that no one responded to
the feature request in:
http://www.nabble.com/Feature-request%3A-copy-by-query-to13855888.html#a13855888
Avoiding the roundtrip when creating a copy of an object tree thus
decreasing memory usage and increasing performance seemed nice to me, but
appearently I am the only one;-) No need to further analyze it.
kind regards,
Christiaan
--
View this message in context: http://www.nabble.com/JDO-TCK-Conference-Call-Friday%2C-June-15%2C-9-am-PDT-tp11129570p23519331.html
Sent from the JDO - Development mailing list archive at Nabble.com.
JDO TCK Conference Call Friday, May 8, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 8 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. [VOTE] Release JDO2.3 "early access"
2. JDO 2.3-ea : Release process/Maven 2 POM
(https://issues.apache.org/jira/browse/JDO-596) - any remaining issues?
3. Detecting inconsistencies of mapped-by declarations?
4. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
Minutes: JDO TCK Conference Call Friday, May 1, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Andy Jefferson, Craig
Russell
Agenda:
1. API required for enabling/disabling FOR UPDATE locking for
SELECTs https://issues.apache.org/jira/browse/JDO-619 Andy has
provided a patch. AI Michael review the patch.
2. Support specification of exact class in SingleFieldIdentity https://issues.apache.org/jira/browse/JDO-630
AI Craig update specification.
3. JDO 2.3 beta? Andy has volunteered to be the release manager for
2.3 early access. We need to decide which JIRA issues need to be part
of the 2.3-ea release. Proposed:
623 query cancel minor change: cancelAll() and cancel(Thread); remove
cancel(); add PMC option javax.jdo.options.QueryCancel to
getSupportedOptions
619 review patch
596 check in new mvn pom.xml
The release process needs some improvement to add the pom.xml and
update the maven-metadata.xml including the new release.
4. Upgrade to maven 2 https://issues.apache.org/jira/browse/JDO-596.
Patch is ready to check in. AI Craig check in the patch.
5. Select new build/project tool https://issues.apache.org/jira/browse/JDO-632
. Assigned to Matthew Adams. Discuss on email.
6. Other issues
Action Items from weeks past:
[Feb 13 2009] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 1, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, May 1 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. API required for enabling/disabling FOR UPDATE locking for SELECTs
https://issues.apache.org/jira/browse/JDO-619
2. Support specification of exact class in SingleFieldIdentity
https://issues.apache.org/jira/browse/JDO-630
3. JDO 2.3 beta?
4. Upgrade to maven 2 https://issues.apache.org/jira/browse/JDO-596
5. Select new build/project tool
https://issues.apache.org/jira/browse/JDO-632
6. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, April 17, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 17 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. Support specification of exact class in SingleFieldIdentity
https://issues.apache.org/jira/browse/JDO-630
2. MetaData specification API - complete?
https://issues.apache.org/jira/browse/JDO-615
3. JD) 2.3 beta?
4. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, April 10, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 10 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. Embedded object and evict
2. Fetch notifications
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, April 3, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, April 3 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. M2 repo error
2. Embedded object and evict
3. runtck.iut
4. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Mar 27, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 27 at 9 am PDT to discuss
JDO TCK issues and status. NOTE that the U.S. has switched to Daylight
Savings Time
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. M2 repo error
2. (JDO-623) Query cancel and timeout support
(https://issues.apache.org/jira/browse/JDO-623)
3. runtck.iut
4. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Mar 20, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 20 at 9 am PDT to discuss
JDO TCK issues and status. NOTE that the U.S. has switched to Daylight
Savings Time
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. M2 repo error
2. (JDO-623) Query cancel and timeout support
(https://issues.apache.org/jira/browse/JDO-623)
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Mar 6, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 6 at 9 am PDT to discuss
JDO TCK issues and status. NOTE that the U.S. has switched to Daylight
Savings Time
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Support for streams https://issues.apache.org/jira/browse/JDO-625
2. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Mar 6, 9 am PST
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, March 6 at 9 am PST 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. Support for streams https://issues.apache.org/jira/browse/JDO-625
2. Query behaviour independent of transactional boundaries
https://issues.apache.org/jira/browse/JDO-624
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Feb 27, 9 am PST
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 27 at 9 am PST 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. Support for streams https://issues.apache.org/jira/browse/JDO-625
2. Query behaviour independent of transactional boundaries
https://issues.apache.org/jira/browse/JDO-624
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
Minutes: JDO TCK Conference Call Friday, Feb 20, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Support for streams https://issues.apache.org/jira/browse/JDO-625
seems reasonable; AI everyone update JIRA with comments
2. Query behaviour independent of transactional boundaries https://issues.apache.org/jira/browse/JDO-624
This issue seems to impact several areas of the specification,
including optimistic/datastore transactions, transaction isolation
level, and cursor holdability (in a JDBC implementation). I'll post
this comment to the JIRA.
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an
application might dynamically tune itself by tracking field access by
use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 20, 9 am PST
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 20 at 9 am PST 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. Support for streams https://issues.apache.org/jira/browse/JDO-625
2. Query behaviour independent of transactional boundaries
https://issues.apache.org/jira/browse/JDO-624
3. Other issues
Action Items from weeks past:
[Feb 13 2007] AI Craig update the spec and make clear the relationship
between Query.cancel and multithreading.
[Feb 13 2007] AI Matthew discuss on email method by which an application
might dynamically tune itself by tracking field access by use-case?
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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
JDO TCK Conference Call Friday, Feb 13, 9 am PST
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 13 at 9 am PST 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. Enhancer specification proposal
2. Other issues
Action Items from weeks past:
[Jan 16 2009] AI Craig update draft enhancer API specification
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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, Feb 6, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. Model API. JDO-615: The changes Andy checked in look good. No
issues.
2. Other issues
Andy's proposed query cancel api was discussed. For ORM
implementations, the JDBC Statement.cancel() method would presumably
be used to implement the dynamic option 3, and we should map the
SQLFeatureNotSupportedException to a JDO exception. Also need to look
at how to report that a non-SQL connection doesn't support canceling a
query. AI Michael reply to Andy's mail. AI Andy raise a JIRA.
Action Items from weeks past:
[Jan 16 2009] AI Craig update draft enhancer API specification
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 6, 9 am PDT
Posted by Michelle Caisse <mc...@sonic.net>.
Hi,
We will have our regular meeting Friday, February 6 at 9 am PST 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. Model API. JDO-615
2. Other issues
Should we change the time for the weekly conference call? No need.
Action Items from weeks past:
[Jan 16 2009] AI Craig update draft enhancer API specification
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 30, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Richard Schilling, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1. Model API. JDO-615 has some updates to make it more type-safe to
create metadata for packages, classes, fields, and methods. AI provide
feedback on the JIRA.
2. Other issues
Should we change the time for the weekly conference call? No need.
Action Items from weeks past:
[Jan 16 2009] AI Craig update draft enhancer API specification
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 30, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 30 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. Model API
2. Other issues
Action Items from weeks past:
[Jan 16 2009] AI Craig update draft enhancer API specification
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, Jan 9, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Richard Schilling, Michael Bouschen, Craig
Russell
Agenda:
1. Enhancer specification text. A few last issues:
a. Can you specify a class name or only the file name (path) of a
class? The advantage of having file and directory names is that it
reinforces the fact that the enhancer works on the byte codes, not
classes. The advantage of class names is usability for some use cases.
So what exactly are the use cases?
b. Can you specify resources vs. files: What is the use case for
specifying a resource name instead of a file or directory name?
c. Should the setOptions API be called setNonstandardOptions? If only
nonstandard options are in the list, this might make it clear that the
standard options are not going to be found here.
d. Enhancement on the fly is enabled by Java 6 instrumentation. How
can this feature be exploited? AI Richard look at Java 6 feature and
discuss on dev alias.
e. Must metadata come from exactly the same location (e.g. jar file,
file system) as the class to be enhanced? The metadata Chapter 18
already specifies a search order for metadata. Should this description
be used for the enhancer as well, with the addition of how to
translate parameters into a metadata search list? And should the
context class loader or just the class loader passed to the enhancer
be used to find metadata files?
2. Other issues
none.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[May 25 2007] AI Matthew Adams prepare a proposal with just the basics
of schema synchronization with jdo and orm metadata.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 9, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 9 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. Enhancer specification text
2. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Dec 19, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
NOTE: The next meeting will be January 9 2009.
Agenda:
1. (JDO-591) Enhancer Invocation API:
A few notes: The requirement for the enhancer is to have access to the
byte codes of the classes to be enhanced. This could consist of files
to be opened or resource names to be found using the class loader. For
output, either the -d directory name or output in place, and with
output in place the resource option is not viable. The directory that
is the subject of the current discussion is a path to the location of
files. A directory can contain class files or metadata files or both.
If the user's intent is for everything in the directory to be
enhanced, then perhaps we should use a more standard option such as "-
r" to recursively search subdirectories.
Many of these issues might be better discussed in light of the
specification. AI: Craig write up the enhancement specification for
review by the group
2. Other issues
none
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 19, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 19 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. (JDO-591) Enhancer Invocation API
2. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Dec 11, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. (JDO-615) MetaData specification API: Michael's patch looks good.
The last issue is to document that the required features don't need to
be valid upon creation but need to be valid when adding the metadata
to the PMF.
2. (JDO-621) Add javax.jdo.JDOEnhancerMain to call the enhancer via
standard API: The API continues to evolve with discussions on the JIRA.
3. (JDO-619) API required for enabling/disabling FOR UPDATE locking
for SELECTs: discussion continues in the green room.
4. Fetch fields dot notation: Discussion is on the jdo expert list and
now the apache jdo list. If it becomes a feature request, someone will
create a JIRA issue for it.
5. timeout first time, then ok: Wrong forum.
6. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 11, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 11 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. (JDO-615) MetaData specification API
2. (JDO-621) Add javax.jdo.JDOEnhancerMain to call the enhancer via
standard API
3. (JDO-619) API required for enabling/disabling FOR UPDATE locking for
SELECTs
4. Fetch fields dot notation
5. timeout first time, then ok
6. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Dec 4, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. (JDO-615) MetaData specification API: Discussion in the JIRA is on
factory methods for single-valued properties; using bean property
patterns for factory methods; setting parent automatically versus
explicitly; provide methods for modifying the structure (remove
methods, unset methods); should factory methods for items that have
required attributes like name also require the attribute as a
parameter; should boolean properties strictly follow the bean pattern.
AI Michael add comments to JIRA.
2. (JDO-591) Enhancer Invocation API: JDO RI now implements the new
API; this JIRA should be closed and new JIRAs opened for follow-on
work. For example, adding a utility Main class in javax.jdo to parse
command line and call the enhancer; adding plugins for eclipse, maven,
netbeans, etc.
3. (JDO-617) JDOQL : Bulk Update and Delete Operations: It would be
nice for this feature to have some justification. AI Craig update JIRA
with more specific comments.
4. (JDO-620) datastore identifier needed for improving replication of
objects: This needs some more discussion to see if JDO is an
appropriate technology for low-level operations like replication.
5. (JDO-619) API required for enabling/disabling FOR UPDATE locking
for SELECTs: It seems useful for real applications. Maybe we can
augment the fetch plan and/or metadata. If set in metadata, and not
overridden at runtime, all getObejctById, navigation, and query would
use the FOR UPDATE. If set in fetch plan, only operations that use the
fetch plan would be affected. AI discuss further on JIRA.
6. Other issues: none
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 4, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 4 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. (JDO-615) MetaData specification API
2. (JDO-591) Enhancer Invocation API
3. (JDO-617) JDOQL : Bulk Update and Delete Operations
4. (JDO-620) datastore identifier needed for improving replication of
objects
5. (JDO-619) API required for enabling/disabling FOR UPDATE locking for
SELECTs
6. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 21, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 21 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. (JDO-591) Enhancer Invocation API
2. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies
3. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Nov 14, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. (JDO-591) Enhancer Invocation API: The focus of this project might
be tools (plugins for maven, ant, Netbeans, Eclipse) to allow standard
invocation of enhancement during development and/or deployment. Andy
has added a patch for review. AI everyone review and comment on the
patch.
Some comments during the meeting, to be formalized by commenting on
the patch: Is a setClassLoader method needed? How do you specify in-
place enhancement? Perhaps by not specifying an output directory? How
do you find an instance of the JDOEnhancer interface?
JDOEnhancerService entry in META-INF/services?
2. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies: An email has been sent to the Apache repository team,
who say that the pom is automatically generated from the maven 1
project.xml. Maven 1 does not have a scope tag that would permit
proper conversion of the project.xml to a maven 2 pom.xml. Maybe we
can include both a pom.xml and project.xml in future releases? AI
Craig follow up with the repository team.
3. TCK issues (JDO-611, 613): Michelle has volunteered for these
issues. Should be resolved within the week.
4. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Nov 14, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 14 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. (JDO-591) Enhancer Invocation API
2. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies
3. TCK issues (JDO-611, 613)
4. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 7, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 7 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. Methods in the result of an JDOQL query
2. (JDO-591) Enhancer Invocation API
3. (JDO-610) Support Nested Transaction or savePoint in JDO 2.3
4. (JDO-612) M2 pom is incorrect, result in problems with transitive
dependencies
5. TCK issues (JDO-6-11, 613)
6. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 31, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
There was no conference call today. We will meet again next week.
-- Michelle
Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, October 31 at 9 am PDT to
> discuss JDO TCK issues and status. NOTE that the U.S. is still on
> daylight savings time.
>
> Dial-in numbers are:
> Domestic (toll-free): 866 230-6968
> International (caller-paid): +1 213 787-0528
> Access code : 294-0479#
>
> Agenda:
>
> 1. Methods in the result of an JDOQL query
> 2. Other issues
>
> Action Items from weeks past:
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
JDO TCK Conference Call Friday, Oct 31, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 31 at 9 am PDT to
discuss JDO TCK issues and status. NOTE that the U.S. is still on
daylight savings time.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. Methods in the result of an JDOQL query
2. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 24, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Richard Schilling, Craig
Russell
Agenda:
1. Methods in the result of an JDOQL query: see https://issues.apache.org/jira/browse/JDO-580
for details. Michael sent a message to gauge interest from the
expert group and from the Reference Implementation team. So far, no
replies.
2. Other issues
JDO 2.2 vote was successful; the JCP vote was successful. Just need to
announce the release and send it out. AI Michelle update the downloads
page. AI Craig update the JCP documentation.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 24, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 24 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. Methods in the result of an JDOQL query
2. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Oct 17, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 17 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. JDO 2.2 release status
2. JDO 2.3 planning
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 10, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. JDO 2.2 release issues. All tests pass in the branch except the
signature test for api2-legacy. Still need to debug this. Planning to
roll the release today. This might be the last release of api2-legacy
unless we find someone in the community willing to own it. Volunteers?
2. Use of class loaders in api2 JDO config tests. The patch that
Richard put together (thanks!) doesn't completely explain the usage of
the URL ClassLoader. The class loader that the tests need don't have a
parent so the loader only can load data supplied by the test case, not
any TCK test classes. So it's not sufficient for the purpose of
actually getting a PMF implementation as needed by some new api2
tests. More work is needed for the new tests. AI Matthew: take a look
at the patch and clarify the "unparent" parameter for the
JDOConfigTestClassLoader. AI Craig: comment on the patch.
3. JDO 2.3 planning: We have a list of features for JDO 2.3. Will
discuss in future conference calls.
4. Other issues
Richard's javadoc issue. No one else can reproduce this. Perhaps a
clean install would be the best course of action.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader. Done.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 10, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 10 at 9 am PDT (7 pm
EEST) 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. JDO 2.2 release issues
2. Use of class loaders in api2 JDO config tests
3. JDO 2.3 planning
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Sept 19, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 19 at 9 am PDT (7 pm
EEST) 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. Control over transaction isolation level (JDO-590)
2. JDOHelper tests (JDO-582, JDO-557)
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Sept 12, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 12 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. JDO 2.2 draft spec
2. Control over transaction isolation level (JDO-590)
3. JDOHelper tests (JDO-582, JDO-557)
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Sep 5, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 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. JDO 2.2 release timing
2. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Aug 29, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, Aug 29 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. JDO 2.2 release timing
2. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 22, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
Agenda:
1. api2-legacy: maintain or dump? Looking for a volunteer to back-port
all of the api2 changes to api2-legacy. To stimulate discussion, Craig
will call for a VOTE on the expert group and dev aliases.
2. JDO 2.2 release timing: There are 12 open issues in JIRA. All
critical issues have owners. Several issues need owners. AI: everyone
sign up to own issues; if we don't have owners for issues, they will
be deferred to a future maintenance release. There is one issue that
is a bug in the reference implementation https://issues.apache.org/jira/browse/JDO-573
Is this going to be fixed any time soon?
AI: Craig update the Change Log for a negative vote in JCP for JDO 2.2.
3. getPMF tests (http://issues.apache.org/jira/browse/JDO-582) No
recent updates.
4. Other issues
JDO 2.1.1 has not got 3 +1 votes and no other votes, so it's ok to
release. Michael verified that the official JSR 243 page links to the
download page where we can update the "latest" release. A new JIRA
release for 2.1.1 has been created and should be updated with the
actual JIRA issues that were fixed by 2.1.1.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 22, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, Aug 22 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. api2-legacy: maintain or dump?
2. JDO 2.2 release timing
3. getPMF tests (http://issues.apache.org/jira/browse/JDO-582)
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 15, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Richard Schilling, Michelle Caisse, Craig Russell
Agenda:
1. Control over transaction isolation level. There does not appear to
be agreement over whether it is possible to completely define
transactional behavior of a jdo implementation. While it is possible
for the implementation to use a user-specified transaction isolation
level for the underlying datastore, it's still not possible to mandate
the behavior associated with, e.g., read-uncommitted.
2. Other issues
Richard downloaded Grails and was impressed. The separation of
persistence specification from the actual class was not so great, but
the overall experience was excellent.
Release schedule for JDO 2.2. Looks like most of the issues can be
done by end of September, so let's try for at least a preview by then.
The last release was done in March, so six month schedule would have a
new release in September. There are some JCP gating processes so we
should try to close on the specification issues soon.
Re: https://issues.apache.org/jira/browse/JDO-556 assigned temporarily
to Craig to add a requirement for a no-args constructor for PMF as a
prerequisite for ServiceLoader.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, Aug 15 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. Control over transaction isolation level
2. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Aug 8, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, Aug 8 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. Control over transaction isolation level
2. Behavior of an ordering column
3. Dynamic fetch groups
4. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 1, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Richard Schilling, Craig Russell
Agenda:
1. Security issue with generated classes. Andy reports that the final
issues with generated classes have been checked into SVN. AI Craig
verify snapshot of datanucleus works correctly.
2. JDO2 API manifest problem. JIRA issue has been filed (twice!) and
Michelle is testing the fix. The intent is to post the jar files on
the m1 snapshot repository for testing and then vote on the 2.1.1
release.
3. Other issues
The issue https://issues.apache.org/jira/browse/JDO-582 needs to have
special setup. Look at the test JDOHelperConfigTest for ideas on
setting up a class loader with multiple JDO implementations.
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 1, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, Aug 1 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. Security issue with generated classes
2. JDO2 API manifest problem
3. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql
Re: Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
[...]
>
> There are some bigger issues when running with security and Windows.
> The result of
>
> springbeans.jarfile =
> ${pom.getDependencyPath('org.springframework:spring-beans')}
>
> is
>
> springbeans.jarfile=D:/users/michael/.maven/repository\org.springframework\jars\spring-beans-2.0.jar
>
>
> This is an internal Maven call that returns mixed "/" and "\" that
> seems to be confusing Java security policy.
>
> To be continued...
I figured out when hard coding the path names in the 'grant codbase'
lines in the security.policy file, I'm able to run with security on
windows. That means something is going wrong when using properties (like
${jdo..tck.jdori.jarfile}) in the security.policy file. Even mixing "/"
and "\" in the path names works, as long as the path names are hard coded.
Any ideas?
Regards Michael
[...]
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Tempelhofer Ufer 23-24, D-10963 Berlin
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Prof. Dr. Christian Roth, Hendrik Saly, Martin Weber
Amtsgericht Berlin-Charlottenburg HRB 86780
USt.-Id. Nr.: DE 225 964 680
Re: Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT
Posted by Andy Jefferson <an...@datanucleus.org>.
> 4. ...
> Andy suggests using DataNucleus as the starting point for this effort,
> as they have already implemented a number of concrete store managers.
> AI look at DataNucleus store manager interface to see what needs to be
> done to run with a cloud data repository.
http://www.jpox.org/servlet/wiki/display/ENG/HOWTO+Support+a+new+datastore
--
Andy (DataNucleus - http://www.datanucleus.org)
Minutes: JDO TCK Conference Call Friday, July 18, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Craig Russell
Agenda:
1. L2 Caching extension. The caching extensions are now checked in. If
there are any comments, please update the JIRA. Do we need a test
case? I think not. I can't see how to test this.
2. Richard has a patch for https://issues.apache.org/jira/browse/
JDO-582. Not uploaded yet.
3. Working on https://issues.apache.org/jira/browse/JDO-555. Most
issues are now resolved. Just a couple of tests now fail when running
maven -o -Djdo.tck.security runtck.jdori
The exception mentioned in JDO-555 Craig Russell - 16/Jul/08 03:14 PM
is still a problem. The ResultObjectFactory constructor requires
getClassLoader permissions if the user requests a java.util.Map result
object. So test ResultClassRequirements.testMap in query.conf fails
with a security violation. Two other security issues are still being
investigated.
There are some bigger issues when running with security and Windows.
The result of
springbeans.jarfile = $
{pom.getDependencyPath('org.springframework:spring-beans')}
is
springbeans.jarfile=D:/users/michael/.maven/repository
\org.springframework\jars\spring-beans-2.0.jar
This is an internal Maven call that returns mixed "/" and "\" that
seems to be confusing Java security policy.
To be continued...
4. An interesting option for a JDO implementation is to use a RESTful
service like Amazon S3 or memcached for the back end. Some obvious
issues are transactions, object identity, and query. But having an
object front end for these would have clear productivity benefits
compared to a user writing the entire thing by hand (tools are pretty
simple for accessing data from these services).
Andy suggests using DataNucleus as the starting point for this effort,
as they have already implemented a number of concrete store managers.
AI look at DataNucleus store manager interface to see what needs to be
done to run with a cloud data repository.
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 11, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Richard Schilling, Craig Russell
Agenda:
1. L2 Caching extension. Andy proposes a simple extension to annotate/
metadate classes and fields to be cacheable or not. Seems easy enough
and no other implications except the addition of new annotation class
@Cacheable and xml element cacheable. Comments? Post replies to Andy's
email. AI Andy make a JIRA.
2. Other issues.
Richard has a patch for https://issues.apache.org/jira/browse/JDO-582.
He will upload a patch this week end.
Working on https://issues.apache.org/jira/browse/JDO-555 it seems that
DataNucleus and or c3p0 need some non-trivial entries.
An interesting option for a JDO implementation is to use a RESTful
service like Amazon S3 or memcached for the back end. Some obvious
issues are transactions, object identity, and query. But having an
object front end for these would have clear productivity benefits
compared to a user writing the entire thing by hand (tools are pretty
simple for accessing data from these services).
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, July 25, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
I'm afraid I won't be able to make today's meeting due to my
attendance at OSCON.
If anyone has cycles, creating a patched JDO 2.1.1-SNAPSHOT and
uploading it to the http://people.apache.org/repo/m1-snapshot-repository/
would be possible anticipating an official release (which will take
at least a week).
I sent a message regarding the security issue for generated classes
and don't have any solution at present.
Craig
On Jul 24, 2008, at 9:35 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, July 25 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. Security issue with generated classes
> 2. JDO2 API manifest problem
> 3. Other issues
>
> Action Items from weeks past:
>
> [Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
> relationships and possibly update the spec to include the rationale.
>
> [Feb 1 2008] AI Matthew see what would be needed to update the PMF
> contract to support ServiceLoader.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
>
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Minutes: JDO TCK Conference Call Friday, July 25, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Richard Schilling
Brief meeting. Michael dropped by, but had to leave due to a conflict
with another meeting. Richard will attach a patch to JDO-582 for review
and comments. Michelle will create a patched JDO 2.1.1 for the extra
space in manifest problem.
-- Michelle
Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, July 25 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. Security issue with generated classes
> 2. JDO2 API manifest problem
> 3. Other issues
>
> Action Items from weeks past:
>
> [Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
> relationships and possibly update the spec to include the rationale.
>
> [Feb 1 2008] AI Matthew see what would be needed to update the PMF
> contract to support ServiceLoader.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
>
--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql
JDO TCK Conference Call Friday, July 25, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 25 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. Security issue with generated classes
2. JDO2 API manifest problem
3. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, July 11, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi,
I'm afraid I cannot join the conference call today, since I'm on a train
on my way back to Berlin. Talk to you next week.
Regards Michael
> Hi,
>
> We will have our regular meeting Friday, July 11 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. L2 Caching extension
> 2. Other issues
>
> Action Items from weeks past:
>
> [Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
> relationships and possibly update the spec to include the rationale.
>
> [Feb 1 2008] AI Matthew see what would be needed to update the PMF
> contract to support ServiceLoader.
>
> [Nov 30 2007] AI Christiaan propose more details on Update/copy by
> query for post-JDO 2.1.
>
> [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.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Sep 2 2005] AI: To recruit members: Articles on TheServerSide
> directing attention to the site. T-shirts. AI: Craig write a
> ServerSide article.
>
> -- Michelle
--
*Michael Bouschen*
*Prokurist*
akquinet tech@spree GmbH
Tempelhofer Ufer 23-24, D-10963 Berlin
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>
akquinet tech@spree GmbH, Berlin
Geschäftsführung: Prof. Dr. Christian Roth, Hendrik Saly, Martin Weber
Amtsgericht Berlin-Charlottenburg HRB 86780
USt.-Id. Nr.: DE 225 964 680
JDO TCK Conference Call Friday, July 11, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 11 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. L2 Caching extension
2. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, June 27, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Richard
Schilling, Craig Russell
NOTE: In light of July 4th, we're canceling next week's meeting. Next
meeting: July 11.
Agenda:
1. Make SingleFieldIdentity classes implement Comparable (JDO-598):
The patch looks clean and has been checked in to both api2 and api2-
legacy. If any problems, raise a JIRA issue. Still outstanding: what
to do for ObjectIdentity e.g. Date.
2. Read-only datastore (JDO-597): The patch looks good and has been
checked in. Still need TCK tests. Should we require fail-fast
behavior? AI: Update the JIRA to discuss.
3. Enhancer Invocation API (JDO-591): The comments to date deal with
the command line and not with an API. This might be most valuable in
the context of Spring Framework invoking the enhancer at runtime
(compared to using the javaagent approach). Make sure it works with
OSGi.
4. Other JDO 2.2 issues: Richard is trying to write a test for https://issues.apache.org/jira/browse/JDO-582
and can't get more than one exception. Looks like a bug in the
implementation. Yay tests.
5. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 27, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 27 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. Make SingleFieldIdentity classes implement Comparable (JDO-598)
2. Read-only datastore (JDO-597)
3. Enhancer Invocation API (JDO-591)
4. Other JDO 2.2 issues
5. Other issues
Action Items from weeks past:
[Jun 20 2008] AI: Craig reply to Joerg regarding bidirectional
relationships and possibly update the spec to include the rationale.
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, June 20, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Read-only datastore: There is an email thread on the topic of
adding an option javax.jdo.ReadOnly. There are a few issues: what
model object does the property belong on (Transaction,
PersistenceManager, PersistenceManagerFactory); which operations might
or are required to trigger an exception (makePersistent,
deletePersistent, delete by query, flush with changed objects, commit
with changed objects, optionally modify an instance); should a
transaction be able to modify objects, add new objects, delete objects
and then roll back; should we declare a new exception to be thrown,
e.g. javax.jdo.JDOReadOnlyException?
AI: anyone with a strong opinion should create/update a JIRA. This is
a candidate for a JDO 2.2 feature.
2. JDO 2.2 plans: Joerg raised an issue regarding bidirectional
relationships, whether changes to one side of the relationship should
immediately cause a change to the other side. We did discuss this
during the JDO 2.1 cycle and concluded that there were some issues
with this strategy. AI: Craig reply to Joerg and possibly update the
spec to include the rationale.
Priority should be given to JDO 2.2 issues that require a spec change
since these will have the most impact on the release schedule.
3. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 20, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 20 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. Read-only datastore
2. JDO 2.2 plans
3. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, June 6, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 6 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. JDO 2.2 plans
2. Post-release notes (JDO-593)
3. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, May 30, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 30 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. JDO 2.2 plans
2. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, May 23, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Richard Schilling, Craig
Russell
Agenda:
1. JDO 2.2 plans: All items that we know about are filed in JIRA and
assigned to the release 2.2. Any other issues should be brought up on
email. It would be good to review the early of JSR-317 for ideas for
the maintenance release.
2. Other issues
Richard is looking at JDO 1.1 RI to see if it can be adapted to use a
memcached as a persistent store (instead of a backing store for
another persistence layer).
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 23, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 23 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free) 866 230-6968 294-0479#
International (caller-paid): +1 213 787-0528
Agenda:
1. JDO 2.2 plans
3. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, May 16, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
NOTE: 213 787-0528 is the new caller-paid conference call number.
Agenda:
1. JDO 2.2 plans. Scrubbed the JIRA issues list for 2.2 release. This
is the tool we will use to manage the release. If any other features
are desired for the release, please file a JIRA and describe the
feature.
2. Other issues
From the mailbox:
jdo-user wants to know why @ annotations aren't @documented. Good
idea, file a JIRA.
jdo-dev wants a quick reference guide like the Kodo two pager. Good
idea, volunteers?
jdo-user reports an issue with interrupting a JDO application.
Probably an implementation bug (Spring, JDO implementation,
application code)
The tck as we distributed it will not automatically download the jta
jar because of repository issues in Glassfish. AI Michael fix the svn
repo. AI Michelle check into how to get information out to users who
download the tck bits but don't check out the svn repo.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader. This is now filed as https://issues.apache.org/jira/browse/JDO-556
and will not be tracked here.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect. This
is now filed as https://issues.apache.org/jira/browse/JDO-463 and will
not be tracked here.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 16, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 16 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.2 plans
3. Other issues
Action Items from weeks past:
[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a
JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday Apr 3, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 3 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.2 plans
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday Mar 28,
9 am Pacific Daylight Time (NOTE US TIME CHANGE!!!)
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Richard Schilling, Michael Bouschen, Michelle Caisse, Craig
Russell
Agenda:
1. JDO 2.2 plans: AI All go through emails to find features we
deferred past 2.1. Include test cases that need to be added for
features where there is insufficient testing. Put feature requests
into JIRA so we can track them.
2. JDO 2.1 status The release is official and many of the artifacts
are available for download. However there are some issues with
downloading the jars and poms. Looks like the jars are ok but the
signature .asc seems to be missing. AI Craig and Michelle fix the
download page. AI Craig get the specification published via the JCP.
AI Richard try to download and run the tck.
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday Mar 28,
9 am Pacific Daylight Time (NOTE US TIME CHANGE!!!)
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 28 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.2 plans
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday Mar 21,
9 am Pacific Daylight Time {NOTE US TIME CHANGE!!!)
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 21 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.1 status
2. JDO 2.2 plan
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday Mar 14,
9 am Pacific Daylight Time {NOTE US TIME CHANGE!!!)
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 14 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Recursion depth discussion in spec
2. Jdoconfig tests fail on tck2-legacy (JDO-581)
3. Work remaining for 2.1 release
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday Mar 7, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 7 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Recursion depth discussion in spec
2. Getting a PMF from an EMF (JDO-556)
3. Work remaining for 2.1 release
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 29, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Erik
Bengtson, Craig Russell
Agenda:
1. Getting a PMF from an EMF (JDO-556) One final issue to be fixed in
JDOHelper. AI Craig fix JDOHelper to use the PersistenceUnitName
property to get a PMF instead of using Persistence class.
2. New draft spec (http://db.apache.org/jdo/releases/
jdo-2008-02-15.pdf) was posted on the jdo web site. AI everyone review
and provide feedback.
3. Work remaining for 2.1 release http://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=issuekey&sorter/order=ASC
4. Other issues
Release of JPOX next week. JPOX 1.2.0 will be released next week. This
release will depend on the JDO 2.1 snapshot jars, and will be official
once the JCP maintenance review is complete and the Apache JDO project
votes to release.
There are currently no tck tests for using size() and max() or other
aggregates in queries. For example, find the Node or Nodes with the
maximum number of children: Select from Node n where n.children.size()
== (select max(children.size()) from Node n). AI Michael write tck
tests for JDO 2.2.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 29, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 29 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Getting a PMF from an EMF (JDO-556)
2. New draft spec (http://db.apache.org/jdo/releases/jdo-2008-02-15.pdf)
3. Work remaining for 2.1 release
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 22, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Order of args for getPersistenceManagerFactory. This is https://issues.apache.org/jira/browse/JDO-577
2. InstanceLifecycleListener tests using jdoconfig.xml properties:
Michelle has some tests under development which are blocked by JDO-577.
3. persistence.xml access: Need to update the specification and the
JDOHelper per https://issues.apache.org/jira/browse/JDO-576. I'd like
to see how the user can ask for a PersistenceManagerFactory that
implements JDOEntitiyManagerFactory. May be a JDO 2.2 issue.
4. Other issues
using size() and max() in queries, e.g. select
max(this.children.size()) from x.y.Node
The SQL version to select the nodes with the maximum number of
children would be
select * from node n2 group by n2.parent having count(*) = (select
max(temp.number) from (select count(*) as number from node n group by
n.parent) as temp)
This is not really a subquery issue. It applies equally to JDO 2.0
where we introduced aggregates.
From the description, it's a bug in the implementation. Now you can
see clearly the benefit of having an object model to query.
Should we add tck tests for this? Definitely not for JDO 2.1. Probably
for 2.2.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 22, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 22 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Order of args for getPersistenceManager
2. InstanceLifecycleListener tests using jdoconfig.xml properties
3. persistence.xml access
4. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Feb 15, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 15 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. TCK tests of jdoconfig.xml, persistence.xml
2. JDO 2.1 spec status
3. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 8, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig
Russell
Agenda:
1. JDO 2.1 spec status: While looking at writing jdoconfig.xml tests,
it became clear that more spec documentation is needed for edge cases
such as the name of the default pmf in jdoconfig.xml and what to
expect when supplying null as the pmf name. AI Michelle write a JIRA
with required updates based on jdoconfig tests.
Query chapter updates are underway.
The JCP has accepted the maintenance review but it hasn't been
announced. AI Craig see where it is.
2. Other issues
Do we need to change our line ending policy based on "Apache
recommendations"? No.
Signature test fails on enum classes when running on Java 6. AI
Michelle send mail to the alias describing the issue.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 8, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 8 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.1 spec status
2. Other issues
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Feb 1, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 1 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. ServiceLoader (JDO-556)
2. Query BNF (JDO-569)
3. JDOHelper Security (JDO-555)
4. Derby bug causing query test failure (JDO-435, Derby 3301)
5. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Jan 25, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1.Changing signature for evictAll(). This is not strictly needed right
now, but if we ever change the Class parameter it will be nice to
reverse the order now, before it's standardized. Seems to be a good
idea. AI everyone please comment on the vote thread.
2. Subquery spec changes. BNF need to be updated for subqueries. Need
to allow aliases just for subqueries and disallow outer queries with
expressions in the FROM clause.
3. DERBY-3301 JDO-453 seems to be progress. The Derby team requested
more test cases. AI Craig provide more test cases.
4. Other issues
Action Items from weeks past:
[Jan 11 2008] AI Michael update the BNF for the specification.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 25, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 25 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1.Changing signature for evictAll()
2. Subquery spec changes
3. DERBY-3301
4. Other issues
Action Items from weeks past:
[Jan 11 2008] AI Michael update the BNF for the specification.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Jan 18, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 18 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Are we all happy with the functionality of the current JDO 2.1?
2. Remaining work for 2.1 release
3. Other issues
Action Items from weeks past:
[Jan 11 2008] AI Michael update the BNF for the specification.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, April 18, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Richard Schilling, Michael Bouschen, Craig Russell
1. JSR 243 will be updated to link to the Apache JDO site and to
download the approved specification.
2. The address for the maven remote repo for Glassfish has changed, so
we need to update the release note for JDO 2.0 TCK. AI: Michael file
a JIRA, send email on how to make people aware of how to run TCK with
this change. We can discuss on the alias how to update the download
page to include this information.
Action Items from weeks past:
[Feb 1 2008] AI Matthew see what would be needed to update the PMF
contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 11, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
My sincere apologies.
Craig
On Jan 12, 2008, at 12:44 PM, Michael Bouschen wrote:
> Hi Craig,
>> Attendees: Michelle Caisse, Craig Russell
> small correction, there was another attendee: Michael Bouschen :-)
>
> Regards Michael
>
> --
> Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
> Buelowstr. 66 Fax.: +49/(0)30/217 520-12
> 10783 Berlin mailto:mbo.tech@spree.de
> Geschaeftsfuehrung: Martin Weber
> Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Jan 11, 9 am PST
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
> Attendees: Michelle Caisse, Craig Russell
small correction, there was another attendee: Michael Bouschen :-)
Regards Michael
--
Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
Buelowstr. 66 Fax.: +49/(0)30/217 520-12
10783 Berlin mailto:mbo.tech@spree.de
Geschaeftsfuehrung: Martin Weber
Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
Minutes: JDO TCK Conference Call Friday, Jan 11, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Remaining spec work for 2.1: We have a plan to import the dtd,
xsd, enums, and annotations directly from text files. The script to
produce these will be checked into the bin directory. AI Michelle
create script to decapitate the .java files to remove the Apache
license and import statements (a.k.a. cruft). AI Craig update the
specification to import the files instead of copy/paste.
2. Other issues
BNF for subqueries. AI Michael update the BNF for the specification.
When running the TCK using Oracle, the schema handling is incorrect.
AI Michael file a JIRA.
JDO-435 is one of two remaining isssues with the TCK/RI. This issue
appears to be a Derby bug. AI Craig follow up with the Derby folks to
see if it can be fixed.
The spec needs to be updated to describe the behavior of fetch plans
associated with a named query. 12.7, 14.6, and 19.3 need to be looked
at. AI Craig discuss updates with expert group.
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 11, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 11 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Remaining spec work for 2.1
2. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Jan 4 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 4 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Query test failure
2. Updated spec
3. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
New draft spec available for review
Posted by Michelle Caisse <Mi...@Sun.COM>.
A new draft of the JDO 2.1 spec is available for review at
http://db.apache.org/jdo/specifications.html.
-- Michelle
JDO TCK Conference Call Friday, Dec 21 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 21 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Wrapping up 2.1 maintenance release
2. Inconsistency in pm.newInstance() (email from 12/18)
3. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Dec 14 , 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Craig Russell
Agenda:
1. Wrapping up 2.1 maintenance release. Looks like just a few more
test cases to write for: Subqueries; JDOUserCallbackException needs
to be added to the api2 and api2-legacy jars but not test case;
Serialization of PersistenceManager and PersistenceManagerFactory;
FetchPlan added to Query. In order to test FetchPlan, we need to
verify that a detached object throws JDODetachedFieldAccessException,
which is the only legal way to tell if a field is loaded or not (the
isLoaded() never made it into this maintenance release).
2. Proposal on annotation overrides. Basically, the proposal is to
specify that overrides can be done at a field/property level, and the
order of acceptance of metadata is class annotations; JPA orm
metadata if persistence.xml is used; then the jdo metadata per
chapter 18 order.
3. Other issues
Do we require a jdo implementation that gets a
PersistenceManagerFactory via persistence.xml to implement
JDOEntityManagerFactory? AI Craig discuss on email.
Action Items from weeks past:
[Nov 30 2007] AI Craig update the spec with some assertions for
subqueries. AI Michael implement the test cases https://
issues.apache.org/jira/browse/JDO-446
[Nov 30 2007] AI Christiaan propose more details on Update/copy by
query for post-JDO 2.1.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 14 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 14 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Wrapping up 2.1 maintenance release
2. Proposal on annotation overrides
3. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Craig update the spec with some assertions for
subqueries. AI Michael implement the test cases
https://issues.apache.org/jira/browse/JDO-446
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Dec 7 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 7 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Serializing PersistenceManager
2. Other issues
Action Items from weeks past:
[Nov 30 2007] AI Craig update the spec with some assertions for
subqueries. AI Michael implement the test cases
https://issues.apache.org/jira/browse/JDO-446
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query
for post-JDO 2.1.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml.. .
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 30 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 30 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Serializing PersistenceManager
2. EnumSet support (yes or no?)
3. Subquery proposed text
4. Update/copy by query
5. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml.. .
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 9 , 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 9 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Discuss EnumSet support
2. JDOHelper methods for PersistenceManagerFactory
3. Serialization of PersistenceManager
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml.. .
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide
directing attention to the site. T-shirts. AI: Craig write a
ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 2 ,
9 am PDT [NOTE: U.S. is still on daylight time]
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 2 at 9 am PDT to
discuss JDO TCK issues and status.
Be aware that the U.S. is still on daylight time this week, whereas
Europe has changed to standard time.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Enum tests
2. JDOHelper bootstrap isses
3. Serialization of PersistenceManager
4. Other issues
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests.
https://issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: multiple databases one PM/TX
Posted by Joerg von Frantzius <jo...@artnology.com>.
Hi Erik,
OK now I got it, you want to support fields within the same PC class to
be persisted to different datasources, right?
Erik Bengtson schrieb:
> Jorg,
>
> An example:
>
> Class product
>
> Field name ; //oracle
> Field price ; //erp
> Field instock ; //erp
>
> With multiple databases feature, you can load an object distributed in multiples databases. As Eric said we will not reinvent JTA.
>
> Each implementation can use JTA to support transactions with multiple datasources, but can use any other mechanism (not defined). JPOX is pluggable and enabled to accept any jta implementation.
>
> If you don't provide an external jta implementation, JPOX will use its internal implementation.
> -- BlackBerry® from Mobistar ---
>
> -----Original Message-----
> From: Joerg von Frantzius <jo...@artnology.com>
>
> Date: Mon, 05 Nov 2007 10:28:55
> To:jdo-dev@db.apache.org
> Cc:jdo-experts-ext@sun.com
> Subject: Re: multiple databases one PM/TX
>
>
> Hi Erik,
>
> there is one thing that I don't understand about this proposed feature
> (which may be just me not seeing the obvious point of course :)
>
> Running 2PC on multiple data sources is handled already by J2EE
> implementations, and, as far as I recall, there are also libraries
> available that provide a JTA without a full blown J2EE server. Why would
> you want to duplicate this already existing and available functionality
> in JDO?
>
> Regards,
> Jörg
>
> Erik Bengtson schrieb:
>
>> In JPOX we are implementing the access to multiple datastores within a single
>> PM/TX. If not too late, I’m wonder if you like to hear a proposal to
>> standardize the configuration of the “jdoconfig” and jdo metadata to be able to
>> handle this scenario. It may sound overkill, but IMO is a major advance over
>> JPA.
>>
>> To introduce the subject, the goal is to handle persistence in multiple
>> databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
>> transaction/ single PM. From the user point of view, there are two items that
>> must be configured, jdo metadata, jdo configuration, in which would be part of
>> this proposal, so I show below an example of the configurations:
>>
>> /jdoconfig/ sequence unbounded PMF
>> /jdoconfig/ sequence unbounded Resource
>>
>> /PMF/
>> /PMF/@Class
>> /PMF/@TransactionTimeout
>> /PMF/@...
>> /Resource/
>> /Resource/@Name
>> /Resource/Connection Settings/
>> /Resource/Connection Settings/@ConnectionFactoryName
>> /Resource/Connection Settings/@ConnectionClientID
>> /Resource/Connection Settings/@ReadOnly
>> /Resource/Connection Settings/@...
>> /Resource/Transaction/
>> /Resource/Transaction/@TwoPhaseCommit
>> /Resource/Transaction/@Timeout
>>
>> ConnectionClientID
>> ----------------------------
>> ConnectionClientID is the identifier for the connection. Some databases such as
>> Oracle use this to identify the end user (not the connection user).
>> ConnectionClientID would accept the values:
>>
>> 1 - CredentialMapping - the CredentialMapping takes the principal of the running
>> application and sets it as client id - eg. ConnectionClientID=CredentialMapping
>> 2 - Identity – the client id is taken from the id right after the Identity word
>> - eg. ConnectionClientID=Identity:MyUser
>>
>> ReadOnly
>> ----------------------------
>> ReadOnly (accepts true, false) will block write operations to this connection
>>
>> TwoPhaseCommit
>> --------------------------
>> Two options:
>>
>> 1 – LastLoggingResource - If the resource is non XA, push down this resource in
>> commit order.
>> 2 – Emulated – Emulates non XA protocol. Heuristics errors could happen
>>
>> Example:
>>
>> <jdoconfig>
>>
>> <pmf name=”snowdog” default-resource=”Oracle”>
>> </pmf>
>>
>> <resource name=”ERP”>
>> <connection connectionfactoryname=”BSCS_Hot”/>
>> </resource>
>>
>> <resource name=”PeopleSoft”>
>> <connection connectionfactoryname=”PS_Onyx”/>
>> </resource>
>>
>> <resource name=”Oracle”>
>> <connection connectionfactoryname=”ORA_Vinci”
>> connection-client-id=”CredentialMapping”/>
>> <transaction two-phase-commit=”LLR” timeout=”30”/>
>> </resource>
>>
>> <resource name=”Xml”>
>> <connection readonly=”true”/>
>> <extension>
>> <jpox:xml file=”file:/usr/home/myxml.xml”/>
>> </extension>
>> </resource>
>>
>>
>> </jdoconfig>
>>
>> <jdo>
>> <package>
>> <class name=”Invoice” resource=”ERP”/>
>> <class name=”ClassData”/> <!-- uses default-resource -->
>> <class name=”Person” resource=”PeopleSoft”/>
>> <class name=”ReferenceData” resource=”Xml”/>
>> </package>
>> </jdo>
>>
>>
>>
>>
>> Quoting Michelle Caisse <Mi...@sun.com>:
>>
>>
>>
>>> Hi,
>>>
>>> We will have our regular meeting Friday, October 26 at 9 am PDT to
>>> discuss JDO TCK issues and status.
>>>
>>> Dial-in numbers are:
>>> 866 230-6968 294-0479#
>>> International: +1 865 544-7856
>>>
>>> Agenda:
>>>
>>> 1. Subquery spec update
>>> 2. Other issues
>>>
>>> Action Items from weeks past:
>>>
>>> [Oct 12 2007] AI Michael take a look at subquery tck tests.
>>> https://issues.apache.org/jira/browse/JDO-446
>>>
>>> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>>>
>>> [June 22 2007] AI Craig discuss svn:eol-style on email.
>>>
>>> [June 22 2007] AI Craig write a proposal on annotation overrides for
>>> the expert group.
>>>
>>> [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.
>>>
>>> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
>>> CurrentDevelopment wiki page
>>>
>>> [Apr 27 2007] AI Craig review Query API and send email to experts.
>>>
>>> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
>>> attach his discussion document to it.
>>>
>>> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
>>> listener is the class name of the listener, for consistency with
>>> proposed xml..
>>>
>>> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
>>> constant "META-INF/jdo.xml" and a new method
>>> getPersistenceManagerFactory taking no arguments.
>>>
>>> [Aug 11 2006] AI Craig propose some semantics for behavior if user
>>> tries to add to a list where the ordering element is incorrect.
>>>
>>> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
>>> corresponding JDO concept.
>>>
>>> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
>>> for Enum types. In progress.
>>>
>>> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>>>
>>> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
>>> issues. In progress
>>>
>>> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
>>> TheServerSide directing attention to the site. T-shirts, logo. AI:
>>> Craig write a ServerSide article.
>>>
>>> -- Michelle
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
Re: multiple databases one PM/TX
Posted by Erik Bengtson <er...@jpox.org>.
Jorg,
An example:
Class product
Field name ; //oracle
Field price ; //erp
Field instock ; //erp
With multiple databases feature, you can load an object distributed in multiples databases. As Eric said we will not reinvent JTA.
Each implementation can use JTA to support transactions with multiple datasources, but can use any other mechanism (not defined). JPOX is pluggable and enabled to accept any jta implementation.
If you don't provide an external jta implementation, JPOX will use its internal implementation.
-- BlackBerry® from Mobistar ---
-----Original Message-----
From: Joerg von Frantzius <jo...@artnology.com>
Date: Mon, 05 Nov 2007 10:28:55
To:jdo-dev@db.apache.org
Cc:jdo-experts-ext@sun.com
Subject: Re: multiple databases one PM/TX
Hi Erik,
there is one thing that I don't understand about this proposed feature
(which may be just me not seeing the obvious point of course :)
Running 2PC on multiple data sources is handled already by J2EE
implementations, and, as far as I recall, there are also libraries
available that provide a JTA without a full blown J2EE server. Why would
you want to duplicate this already existing and available functionality
in JDO?
Regards,
Jörg
Erik Bengtson schrieb:
> In JPOX we are implementing the access to multiple datastores within a single
> PM/TX. If not too late, I’m wonder if you like to hear a proposal to
> standardize the configuration of the “jdoconfig” and jdo metadata to be able to
> handle this scenario. It may sound overkill, but IMO is a major advance over
> JPA.
>
> To introduce the subject, the goal is to handle persistence in multiple
> databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
> transaction/ single PM. From the user point of view, there are two items that
> must be configured, jdo metadata, jdo configuration, in which would be part of
> this proposal, so I show below an example of the configurations:
>
> /jdoconfig/ sequence unbounded PMF
> /jdoconfig/ sequence unbounded Resource
>
> /PMF/
> /PMF/@Class
> /PMF/@TransactionTimeout
> /PMF/@...
> /Resource/
> /Resource/@Name
> /Resource/Connection Settings/
> /Resource/Connection Settings/@ConnectionFactoryName
> /Resource/Connection Settings/@ConnectionClientID
> /Resource/Connection Settings/@ReadOnly
> /Resource/Connection Settings/@...
> /Resource/Transaction/
> /Resource/Transaction/@TwoPhaseCommit
> /Resource/Transaction/@Timeout
>
> ConnectionClientID
> ----------------------------
> ConnectionClientID is the identifier for the connection. Some databases such as
> Oracle use this to identify the end user (not the connection user).
> ConnectionClientID would accept the values:
>
> 1 - CredentialMapping - the CredentialMapping takes the principal of the running
> application and sets it as client id - eg. ConnectionClientID=CredentialMapping
> 2 - Identity – the client id is taken from the id right after the Identity word
> - eg. ConnectionClientID=Identity:MyUser
>
> ReadOnly
> ----------------------------
> ReadOnly (accepts true, false) will block write operations to this connection
>
> TwoPhaseCommit
> --------------------------
> Two options:
>
> 1 – LastLoggingResource - If the resource is non XA, push down this resource in
> commit order.
> 2 – Emulated – Emulates non XA protocol. Heuristics errors could happen
>
> Example:
>
> <jdoconfig>
>
> <pmf name=”snowdog” default-resource=”Oracle”>
> </pmf>
>
> <resource name=”ERP”>
> <connection connectionfactoryname=”BSCS_Hot”/>
> </resource>
>
> <resource name=”PeopleSoft”>
> <connection connectionfactoryname=”PS_Onyx”/>
> </resource>
>
> <resource name=”Oracle”>
> <connection connectionfactoryname=”ORA_Vinci”
> connection-client-id=”CredentialMapping”/>
> <transaction two-phase-commit=”LLR” timeout=”30”/>
> </resource>
>
> <resource name=”Xml”>
> <connection readonly=”true”/>
> <extension>
> <jpox:xml file=”file:/usr/home/myxml.xml”/>
> </extension>
> </resource>
>
>
> </jdoconfig>
>
> <jdo>
> <package>
> <class name=”Invoice” resource=”ERP”/>
> <class name=”ClassData”/> <!-- uses default-resource -->
> <class name=”Person” resource=”PeopleSoft”/>
> <class name=”ReferenceData” resource=”Xml”/>
> </package>
> </jdo>
>
>
>
>
> Quoting Michelle Caisse <Mi...@sun.com>:
>
>
>> Hi,
>>
>> We will have our regular meeting Friday, October 26 at 9 am PDT to
>> discuss JDO TCK issues and status.
>>
>> Dial-in numbers are:
>> 866 230-6968 294-0479#
>> International: +1 865 544-7856
>>
>> Agenda:
>>
>> 1. Subquery spec update
>> 2. Other issues
>>
>> Action Items from weeks past:
>>
>> [Oct 12 2007] AI Michael take a look at subquery tck tests.
>> https://issues.apache.org/jira/browse/JDO-446
>>
>> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>>
>> [June 22 2007] AI Craig discuss svn:eol-style on email.
>>
>> [June 22 2007] AI Craig write a proposal on annotation overrides for
>> the expert group.
>>
>> [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.
>>
>> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
>> CurrentDevelopment wiki page
>>
>> [Apr 27 2007] AI Craig review Query API and send email to experts.
>>
>> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
>> attach his discussion document to it.
>>
>> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
>> listener is the class name of the listener, for consistency with
>> proposed xml..
>>
>> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
>> constant "META-INF/jdo.xml" and a new method
>> getPersistenceManagerFactory taking no arguments.
>>
>> [Aug 11 2006] AI Craig propose some semantics for behavior if user
>> tries to add to a list where the ordering element is incorrect.
>>
>> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
>> corresponding JDO concept.
>>
>> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
>> for Enum types. In progress.
>>
>> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>>
>> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
>> issues. In progress
>>
>> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
>> TheServerSide directing attention to the site. T-shirts, logo. AI:
>> Craig write a ServerSide article.
>>
>> -- Michelle
>>
>>
>
>
>
>
>
>
RE: multiple databases one PM/TX
Posted by Eric Samson <er...@xcalia.com>.
Hello Joerg,
I don't think Erik wants to reinvent JTA.
Probably a multi DBS PMF implementation will rely on a JTA TM.
But you also have to cover non transactional data sources.
I think the proposed options are here to cover this.
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Joerg von Frantzius [mailto:joerg.von.frantzius@artnology.com]
Envoyé : lundi 5 novembre 2007 10:29
À : jdo-dev@db.apache.org
Cc : jdo-experts-ext@sun.com
Objet : Re: multiple databases one PM/TX
Hi Erik,
there is one thing that I don't understand about this proposed feature (which may be just me not seeing the obvious point of course :)
Running 2PC on multiple data sources is handled already by J2EE implementations, and, as far as I recall, there are also libraries available that provide a JTA without a full blown J2EE server. Why would you want to duplicate this already existing and available functionality in JDO?
Regards,
Jörg
Erik Bengtson schrieb:
> In JPOX we are implementing the access to multiple datastores within a
> single PM/TX. If not too late, I’m wonder if you like to hear a
> proposal to standardize the configuration of the “jdoconfig” and jdo
> metadata to be able to handle this scenario. It may sound overkill,
> but IMO is a major advance over JPA.
>
> To introduce the subject, the goal is to handle persistence in
> multiple databases (e.g. derby, oracle, DB4O, Versant, XML) within a
> single JDO transaction/ single PM. From the user point of view, there
> are two items that must be configured, jdo metadata, jdo
> configuration, in which would be part of this proposal, so I show below an example of the configurations:
>
> /jdoconfig/ sequence unbounded PMF
> /jdoconfig/ sequence unbounded Resource
>
> /PMF/
> /PMF/@Class
> /PMF/@TransactionTimeout
> /PMF/@...
> /Resource/
> /Resource/@Name
> /Resource/Connection Settings/
> /Resource/Connection Settings/@ConnectionFactoryName
> /Resource/Connection Settings/@ConnectionClientID /Resource/Connection
> Settings/@ReadOnly /Resource/Connection Settings/@...
> /Resource/Transaction/
> /Resource/Transaction/@TwoPhaseCommit
> /Resource/Transaction/@Timeout
>
> ConnectionClientID
> ----------------------------
> ConnectionClientID is the identifier for the connection. Some
> databases such as Oracle use this to identify the end user (not the connection user).
> ConnectionClientID would accept the values:
>
> 1 - CredentialMapping - the CredentialMapping takes the principal of
> the running application and sets it as client id - eg.
> ConnectionClientID=CredentialMapping
> 2 - Identity – the client id is taken from the id right after the
> Identity word
> - eg. ConnectionClientID=Identity:MyUser
>
> ReadOnly
> ----------------------------
> ReadOnly (accepts true, false) will block write operations to this
> connection
>
> TwoPhaseCommit
> --------------------------
> Two options:
>
> 1 – LastLoggingResource - If the resource is non XA, push down this
> resource in commit order.
> 2 – Emulated – Emulates non XA protocol. Heuristics errors could
> happen
>
> Example:
>
> <jdoconfig>
>
> <pmf name=”snowdog” default-resource=”Oracle”> </pmf>
>
> <resource name=”ERP”>
> <connection connectionfactoryname=”BSCS_Hot”/>
> </resource>
>
> <resource name=”PeopleSoft”>
> <connection connectionfactoryname=”PS_Onyx”/> </resource>
>
> <resource name=”Oracle”>
> <connection connectionfactoryname=”ORA_Vinci”
> connection-client-id=”CredentialMapping”/>
> <transaction two-phase-commit=”LLR” timeout=”30”/> </resource>
>
> <resource name=”Xml”>
> <connection readonly=”true”/>
> <extension>
> <jpox:xml file=”file:/usr/home/myxml.xml”/> </extension> </resource>
>
>
> </jdoconfig>
>
> <jdo>
> <package>
> <class name=”Invoice” resource=”ERP”/> <class name=”ClassData”/> <!--
> uses default-resource --> <class name=”Person” resource=”PeopleSoft”/>
> <class name=”ReferenceData” resource=”Xml”/> </package> </jdo>
>
>
>
>
> Quoting Michelle Caisse <Mi...@sun.com>:
>
>
>> Hi,
>>
>> We will have our regular meeting Friday, October 26 at 9 am PDT to
>> discuss JDO TCK issues and status.
>>
>> Dial-in numbers are:
>> 866 230-6968 294-0479#
>> International: +1 865 544-7856
>>
>> Agenda:
>>
>> 1. Subquery spec update
>> 2. Other issues
>>
>> Action Items from weeks past:
>>
>> [Oct 12 2007] AI Michael take a look at subquery tck tests.
>> https://issues.apache.org/jira/browse/JDO-446
>>
>> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>>
>> [June 22 2007] AI Craig discuss svn:eol-style on email.
>>
>> [June 22 2007] AI Craig write a proposal on annotation overrides for
>> the expert group.
>>
>> [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.
>>
>> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
>> CurrentDevelopment wiki page
>>
>> [Apr 27 2007] AI Craig review Query API and send email to experts.
>>
>> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
>> and attach his discussion document to it.
>>
>> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
>> listener is the class name of the listener, for consistency with
>> proposed xml..
>>
>> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
>> constant "META-INF/jdo.xml" and a new method
>> getPersistenceManagerFactory taking no arguments.
>>
>> [Aug 11 2006] AI Craig propose some semantics for behavior if user
>> tries to add to a list where the ordering element is incorrect.
>>
>> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
>> corresponding JDO concept.
>>
>> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
>> for Enum types. In progress.
>>
>> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>>
>> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
>> issues. In progress
>>
>> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
>> TheServerSide directing attention to the site. T-shirts, logo. AI:
>> Craig write a ServerSide article.
>>
>> -- Michelle
>>
>>
>
>
>
>
>
>
Re: multiple databases one PM/TX
Posted by Joerg von Frantzius <jo...@artnology.com>.
Hi Erik,
there is one thing that I don't understand about this proposed feature
(which may be just me not seeing the obvious point of course :)
Running 2PC on multiple data sources is handled already by J2EE
implementations, and, as far as I recall, there are also libraries
available that provide a JTA without a full blown J2EE server. Why would
you want to duplicate this already existing and available functionality
in JDO?
Regards,
Jörg
Erik Bengtson schrieb:
> In JPOX we are implementing the access to multiple datastores within a single
> PM/TX. If not too late, I’m wonder if you like to hear a proposal to
> standardize the configuration of the “jdoconfig” and jdo metadata to be able to
> handle this scenario. It may sound overkill, but IMO is a major advance over
> JPA.
>
> To introduce the subject, the goal is to handle persistence in multiple
> databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
> transaction/ single PM. From the user point of view, there are two items that
> must be configured, jdo metadata, jdo configuration, in which would be part of
> this proposal, so I show below an example of the configurations:
>
> /jdoconfig/ sequence unbounded PMF
> /jdoconfig/ sequence unbounded Resource
>
> /PMF/
> /PMF/@Class
> /PMF/@TransactionTimeout
> /PMF/@...
> /Resource/
> /Resource/@Name
> /Resource/Connection Settings/
> /Resource/Connection Settings/@ConnectionFactoryName
> /Resource/Connection Settings/@ConnectionClientID
> /Resource/Connection Settings/@ReadOnly
> /Resource/Connection Settings/@...
> /Resource/Transaction/
> /Resource/Transaction/@TwoPhaseCommit
> /Resource/Transaction/@Timeout
>
> ConnectionClientID
> ----------------------------
> ConnectionClientID is the identifier for the connection. Some databases such as
> Oracle use this to identify the end user (not the connection user).
> ConnectionClientID would accept the values:
>
> 1 - CredentialMapping - the CredentialMapping takes the principal of the running
> application and sets it as client id - eg. ConnectionClientID=CredentialMapping
> 2 - Identity – the client id is taken from the id right after the Identity word
> - eg. ConnectionClientID=Identity:MyUser
>
> ReadOnly
> ----------------------------
> ReadOnly (accepts true, false) will block write operations to this connection
>
> TwoPhaseCommit
> --------------------------
> Two options:
>
> 1 – LastLoggingResource - If the resource is non XA, push down this resource in
> commit order.
> 2 – Emulated – Emulates non XA protocol. Heuristics errors could happen
>
> Example:
>
> <jdoconfig>
>
> <pmf name=”snowdog” default-resource=”Oracle”>
> </pmf>
>
> <resource name=”ERP”>
> <connection connectionfactoryname=”BSCS_Hot”/>
> </resource>
>
> <resource name=”PeopleSoft”>
> <connection connectionfactoryname=”PS_Onyx”/>
> </resource>
>
> <resource name=”Oracle”>
> <connection connectionfactoryname=”ORA_Vinci”
> connection-client-id=”CredentialMapping”/>
> <transaction two-phase-commit=”LLR” timeout=”30”/>
> </resource>
>
> <resource name=”Xml”>
> <connection readonly=”true”/>
> <extension>
> <jpox:xml file=”file:/usr/home/myxml.xml”/>
> </extension>
> </resource>
>
>
> </jdoconfig>
>
> <jdo>
> <package>
> <class name=”Invoice” resource=”ERP”/>
> <class name=”ClassData”/> <!-- uses default-resource -->
> <class name=”Person” resource=”PeopleSoft”/>
> <class name=”ReferenceData” resource=”Xml”/>
> </package>
> </jdo>
>
>
>
>
> Quoting Michelle Caisse <Mi...@sun.com>:
>
>
>> Hi,
>>
>> We will have our regular meeting Friday, October 26 at 9 am PDT to
>> discuss JDO TCK issues and status.
>>
>> Dial-in numbers are:
>> 866 230-6968 294-0479#
>> International: +1 865 544-7856
>>
>> Agenda:
>>
>> 1. Subquery spec update
>> 2. Other issues
>>
>> Action Items from weeks past:
>>
>> [Oct 12 2007] AI Michael take a look at subquery tck tests.
>> https://issues.apache.org/jira/browse/JDO-446
>>
>> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>>
>> [June 22 2007] AI Craig discuss svn:eol-style on email.
>>
>> [June 22 2007] AI Craig write a proposal on annotation overrides for
>> the expert group.
>>
>> [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.
>>
>> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
>> CurrentDevelopment wiki page
>>
>> [Apr 27 2007] AI Craig review Query API and send email to experts.
>>
>> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
>> attach his discussion document to it.
>>
>> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
>> listener is the class name of the listener, for consistency with
>> proposed xml..
>>
>> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
>> constant "META-INF/jdo.xml" and a new method
>> getPersistenceManagerFactory taking no arguments.
>>
>> [Aug 11 2006] AI Craig propose some semantics for behavior if user
>> tries to add to a list where the ordering element is incorrect.
>>
>> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
>> corresponding JDO concept.
>>
>> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
>> for Enum types. In progress.
>>
>> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>>
>> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
>> issues. In progress
>>
>> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
>> TheServerSide directing attention to the site. T-shirts, logo. AI:
>> Craig write a ServerSide article.
>>
>> -- Michelle
>>
>>
>
>
>
>
>
>
RE: multiple databases one PM/TX
Posted by Eric Samson <er...@xcalia.com>.
Matthew,
What do you think getConnection()is supposed to return?
A collection of underlying native connections()?
Or is it getConnection(<name>) (whatever <name> could be)?
Do we need to notion of a default data source or not?
In that case getConnection() with no parameter would return that default data source?
In the case the data source is a Web service, what do you expect as a return value for getConnection()?
Best Regards,
....: Eric Samson, Founder & CTO, xcalia
Service your Data!
De : Matthew Adams [mailto:matthew@matthewadams.org]
Envoyé : lundi 29 octobre 2007 20:25
À : Eric Samson
Cc : Erik Bengtson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : Re: multiple databases one PM/TX
Hi all,
I like that JDO allows implementations to support this, and I do feel that this could be a differentiator from JPA. The things that come to my mind are the following:
* this should be an optional feature so that we don't slow down implementations from being compliant
* we should examine the proposed JDO 2.1 metadata formats to ensure that it can support but not require multiple data sources
* we need to examine the impact of configuring multiple data sources on the API (i.e., new method JDOHelper.getPersistenceManagerFactory(String... names), PersistenceManager#getDataStoreConnection() & JDOConnection#getNativeConnection?)
* configuration of JTA and the coordination of transactions across all data sources
* this would slow down work on 2.1 -- can we add in another maintenance release?
-matthew
On Oct 29, 2007, at 10:05 AM, Eric Samson wrote:
Hello Erik,
Once again you start an important topic here! :-)
We also are working on a multi-data sources PMF.
I think the name "resource" could be confusing (I tend to prefer "data source").
Maybe the data source properties should be defined elsewhere (as you can have quite complex configurations when you want to access non-relational data stores)?
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 15:49
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : multiple databases one PM/TX
In JPOX we are implementing the access to multiple datastores within a single
PM/TX. If not too late, I'm wonder if you like to hear a proposal to
standardize the configuration of the "jdoconfig" and jdo metadata to be able to
handle this scenario. It may sound overkill, but IMO is a major advance over
JPA.
To introduce the subject, the goal is to handle persistence in multiple
databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
transaction/ single PM. From the user point of view, there are two items that
must be configured, jdo metadata, jdo configuration, in which would be part of
this proposal, so I show below an example of the configurations:
/jdoconfig/ sequence unbounded PMF
/jdoconfig/ sequence unbounded Resource
/PMF/
/PMF/@Class
/PMF/@TransactionTimeout
/PMF/@...
/Resource/
/Resource/@Name
/Resource/Connection Settings/
/Resource/Connection Settings/@ConnectionFactoryName
/Resource/Connection Settings/@ConnectionClientID
/Resource/Connection Settings/@ReadOnly
/Resource/Connection Settings/@...
/Resource/Transaction/
/Resource/Transaction/@TwoPhaseCommit
/Resource/Transaction/@Timeout
ConnectionClientID
----------------------------
ConnectionClientID is the identifier for the connection. Some databases such as
Oracle use this to identify the end user (not the connection user).
ConnectionClientID would accept the values:
1 - CredentialMapping - the CredentialMapping takes the principal of the running
application and sets it as client id - eg. ConnectionClientID=CredentialMapping
2 - Identity - the client id is taken from the id right after the Identity word
- eg. ConnectionClientID=Identity:MyUser
ReadOnly
----------------------------
ReadOnly (accepts true, false) will block write operations to this connection
TwoPhaseCommit
--------------------------
Two options:
1 - LastLoggingResource - If the resource is non XA, push down this resource in
commit order.
2 - Emulated - Emulates non XA protocol. Heuristics errors could happen
Example:
<jdoconfig>
<pmf name="snowdog" default-resource="Oracle">
</pmf>
<resource name="ERP">
<connection connectionfactoryname="BSCS_Hot"/>
</resource>
<resource name="PeopleSoft">
<connection connectionfactoryname="PS_Onyx"/>
</resource>
<resource name="Oracle">
<connection connectionfactoryname="ORA_Vinci"
connection-client-id="CredentialMapping"/>
<transaction two-phase-commit="LLR" timeout="30"/>
</resource>
<resource name="Xml">
<connection readonly="true"/>
<extension>
<jpox:xml file="file:/usr/home/myxml.xml <file:///\\usr\home\myxml.xml> "/>
</extension>
</resource>
</jdoconfig>
<jdo>
<package>
<class name="Invoice" resource="ERP"/>
<class name="ClassData"/> <!-- uses default-resource -->
<class name="Person" resource="PeopleSoft"/>
<class name="ReferenceData" resource="Xml"/>
</package>
</jdo>
Quoting Michelle Caisse <Mi...@sun.com>:
> Hi,
>
> We will have our regular meeting Friday, October 26 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Subquery spec update
> 2. Other issues
>
> Action Items from weeks past:
>
> [Oct 12 2007] AI Michael take a look at subquery tck tests.
> https://issues.apache.org/jira/browse/JDO-446
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
> attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
> >
>
RE: multiple databases one PM/TX
Posted by Eric Samson <er...@xcalia.com>.
Hey Matthew,
See my comments inline.
Rgds,
....: Eric Samson, Founder & CTO, xcalia
Service your Data!
De : Matthew Adams [mailto:matthew@matthewadams.org]
Envoyé : lundi 29 octobre 2007 20:25
À : Eric Samson
Cc : Erik Bengtson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : Re: multiple databases one PM/TX
Hi all,
I like that JDO allows implementations to support this, and I do feel that this could be a differentiator from JPA. The things that come to my mind are the following:
* this should be an optional feature so that we don't slow down implementations from being compliant
* we should examine the proposed JDO 2.1 metadata formats to ensure that it can support but not require multiple data sources
[Eric Samson] Agreed.
* we need to examine the impact of configuring multiple data sources on the API (i.e., new method JDOHelper.getPersistenceManagerFactory(String... names), PersistenceManager#getDataStoreConnection() & JDOConnection#getNativeConnection?)
[Eric Samson] IMHO, this is more for the sake of completion rather than a real need, but why not.
* configuration of JTA and the coordination of transactions across all data sources
[Eric Samson] Do you want to configure distributed transactions or do you want the implementation to decide how to (transparently ?) manage them? BTW: what kind of configuration do you have in mind? Is that JTA only? What about WS-*? Or a mix of them? Or something else?
* this would slow down work on 2.1 -- can we add in another maintenance release?
[Eric Samson] Yes, should be later in time.
-matthew
On Oct 29, 2007, at 10:05 AM, Eric Samson wrote:
Hello Erik,
Once again you start an important topic here! :-)
We also are working on a multi-data sources PMF.
I think the name "resource" could be confusing (I tend to prefer "data source").
Maybe the data source properties should be defined elsewhere (as you can have quite complex configurations when you want to access non-relational data stores)?
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 15:49
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : multiple databases one PM/TX
In JPOX we are implementing the access to multiple datastores within a single
PM/TX. If not too late, I'm wonder if you like to hear a proposal to
standardize the configuration of the "jdoconfig" and jdo metadata to be able to
handle this scenario. It may sound overkill, but IMO is a major advance over
JPA.
To introduce the subject, the goal is to handle persistence in multiple
databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
transaction/ single PM. From the user point of view, there are two items that
must be configured, jdo metadata, jdo configuration, in which would be part of
this proposal, so I show below an example of the configurations:
/jdoconfig/ sequence unbounded PMF
/jdoconfig/ sequence unbounded Resource
/PMF/
/PMF/@Class
/PMF/@TransactionTimeout
/PMF/@...
/Resource/
/Resource/@Name
/Resource/Connection Settings/
/Resource/Connection Settings/@ConnectionFactoryName
/Resource/Connection Settings/@ConnectionClientID
/Resource/Connection Settings/@ReadOnly
/Resource/Connection Settings/@...
/Resource/Transaction/
/Resource/Transaction/@TwoPhaseCommit
/Resource/Transaction/@Timeout
ConnectionClientID
----------------------------
ConnectionClientID is the identifier for the connection. Some databases such as
Oracle use this to identify the end user (not the connection user).
ConnectionClientID would accept the values:
1 - CredentialMapping - the CredentialMapping takes the principal of the running
application and sets it as client id - eg. ConnectionClientID=CredentialMapping
2 - Identity - the client id is taken from the id right after the Identity word
- eg. ConnectionClientID=Identity:MyUser
ReadOnly
----------------------------
ReadOnly (accepts true, false) will block write operations to this connection
TwoPhaseCommit
--------------------------
Two options:
1 - LastLoggingResource - If the resource is non XA, push down this resource in
commit order.
2 - Emulated - Emulates non XA protocol. Heuristics errors could happen
Example:
<jdoconfig>
<pmf name="snowdog" default-resource="Oracle">
</pmf>
<resource name="ERP">
<connection connectionfactoryname="BSCS_Hot"/>
</resource>
<resource name="PeopleSoft">
<connection connectionfactoryname="PS_Onyx"/>
</resource>
<resource name="Oracle">
<connection connectionfactoryname="ORA_Vinci"
connection-client-id="CredentialMapping"/>
<transaction two-phase-commit="LLR" timeout="30"/>
</resource>
<resource name="Xml">
<connection readonly="true"/>
<extension>
<jpox:xml file="file:/usr/home/myxml.xml <file:///\\usr\home\myxml.xml> "/>
</extension>
</resource>
</jdoconfig>
<jdo>
<package>
<class name="Invoice" resource="ERP"/>
<class name="ClassData"/> <!-- uses default-resource -->
<class name="Person" resource="PeopleSoft"/>
<class name="ReferenceData" resource="Xml"/>
</package>
</jdo>
Quoting Michelle Caisse <Mi...@sun.com>:
> Hi,
>
> We will have our regular meeting Friday, October 26 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Subquery spec update
> 2. Other issues
>
> Action Items from weeks past:
>
> [Oct 12 2007] AI Michael take a look at subquery tck tests.
> https://issues.apache.org/jira/browse/JDO-446
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
> attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
> >
>
Re: multiple databases one PM/TX
Posted by Matthew Adams <ma...@matthewadams.org>.
Hi all,
I like that JDO allows implementations to support this, and I do feel
that this could be a differentiator from JPA. The things that come
to my mind are the following:
* this should be an optional feature so that we don't slow down
implementations from being compliant
* we should examine the proposed JDO 2.1 metadata formats to ensure
that it can support but not require multiple data sources
* we need to examine the impact of configuring multiple data sources
on the API (i.e., new method JDOHelper.getPersistenceManagerFactory
(String... names), PersistenceManager#getDataStoreConnection() &
JDOConnection#getNativeConnection?)
* configuration of JTA and the coordination of transactions across
all data sources
* this would slow down work on 2.1 -- can we add in another
maintenance release?
-matthew
On Oct 29, 2007, at 10:05 AM, Eric Samson wrote:
> Hello Erik,
>
>
>
> Once again you start an important topic here! :-)
>
>
>
> We also are working on a multi-data sources PMF.
>
>
>
> I think the name "resource" could be confusing (I tend to prefer
> "data source").
>
>
>
> Maybe the data source properties should be defined elsewhere (as
> you can have quite complex configurations when you want to access
> non-relational data stores)?
>
>
>
> Best Regards,
>
> ....: Eric Samson, Founder & CTO, Xcalia
>
> Service your Data!
>
>
>
> -----Message d'origine-----
> De : Erik Bengtson [mailto:erik@jpox.org]
> Envoyé : vendredi 26 octobre 2007 15:49
> À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
> Objet : multiple databases one PM/TX
>
>
>
> In JPOX we are implementing the access to multiple datastores
> within a single
>
> PM/TX. If not too late, I’m wonder if you like to hear a proposal to
>
> standardize the configuration of the “jdoconfig” and jdo metadata
> to be able to
>
> handle this scenario. It may sound overkill, but IMO is a major
> advance over
>
> JPA.
>
>
>
> To introduce the subject, the goal is to handle persistence in
> multiple
>
> databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
>
> transaction/ single PM. From the user point of view, there are two
> items that
>
> must be configured, jdo metadata, jdo configuration, in which would
> be part of
>
> this proposal, so I show below an example of the configurations:
>
>
>
> /jdoconfig/ sequence unbounded PMF
>
> /jdoconfig/ sequence unbounded Resource
>
>
>
> /PMF/
>
> /PMF/@Class
>
> /PMF/@TransactionTimeout
>
> /PMF/@...
>
> /Resource/
>
> /Resource/@Name
>
> /Resource/Connection Settings/
>
> /Resource/Connection Settings/@ConnectionFactoryName
>
> /Resource/Connection Settings/@ConnectionClientID
>
> /Resource/Connection Settings/@ReadOnly
>
> /Resource/Connection Settings/@...
>
> /Resource/Transaction/
>
> /Resource/Transaction/@TwoPhaseCommit
>
> /Resource/Transaction/@Timeout
>
>
>
> ConnectionClientID
>
> ----------------------------
>
> ConnectionClientID is the identifier for the connection. Some
> databases such as
>
> Oracle use this to identify the end user (not the connection user).
>
> ConnectionClientID would accept the values:
>
>
>
> 1 - CredentialMapping - the CredentialMapping takes the principal
> of the running
>
> application and sets it as client id - eg.
> ConnectionClientID=CredentialMapping
>
> 2 - Identity – the client id is taken from the id right after the
> Identity word
>
> - eg. ConnectionClientID=Identity:MyUser
>
>
>
> ReadOnly
>
> ----------------------------
>
> ReadOnly (accepts true, false) will block write operations to this
> connection
>
>
>
> TwoPhaseCommit
>
> --------------------------
>
> Two options:
>
>
>
> 1 – LastLoggingResource - If the resource is non XA, push down this
> resource in
>
> commit order.
>
> 2 – Emulated – Emulates non XA protocol. Heuristics errors could
> happen
>
>
>
> Example:
>
>
>
> <jdoconfig>
>
>
>
> <pmf name=”snowdog” default-resource=”Oracle”>
>
> </pmf>
>
>
>
> <resource name=”ERP”>
>
> <connection connectionfactoryname=”BSCS_Hot”/>
>
> </resource>
>
>
>
> <resource name=”PeopleSoft”>
>
> <connection connectionfactoryname=”PS_Onyx”/>
>
> </resource>
>
>
>
> <resource name=”Oracle”>
>
> <connection connectionfactoryname=”ORA_Vinci”
>
> connection-client-id=”CredentialMapping”/>
>
> <transaction two-phase-commit=”LLR” timeout=”30”/>
>
> </resource>
>
>
>
> <resource name=”Xml”>
>
> <connection readonly=”true”/>
>
> <extension>
>
> <jpox:xml file=”file:/usr/home/myxml.xml”/>
>
> </extension>
>
> </resource>
>
>
>
>
>
> </jdoconfig>
>
>
>
> <jdo>
>
> <package>
>
> <class name=”Invoice” resource=”ERP”/>
>
> <class name=”ClassData”/> <!-- uses default-resource -->
>
> <class name=”Person” resource=”PeopleSoft”/>
>
> <class name=”ReferenceData” resource=”Xml”/>
>
> </package>
>
> </jdo>
>
>
>
>
>
>
>
>
>
> Quoting Michelle Caisse <Mi...@sun.com>:
>
>
>
> > Hi,
>
> >
>
> > We will have our regular meeting Friday, October 26 at 9 am PDT to
>
> > discuss JDO TCK issues and status.
>
> >
>
> > Dial-in numbers are:
>
> > 866 230-6968 294-0479#
>
> > International: +1 865 544-7856
>
> >
>
> > Agenda:
>
> >
>
> > 1. Subquery spec update
>
> > 2. Other issues
>
> >
>
> > Action Items from weeks past:
>
> >
>
> > [Oct 12 2007] AI Michael take a look at subquery tck tests.
>
> > https://issues.apache.org/jira/browse/JDO-446
>
> >
>
> > [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> >
>
> > [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> >
>
> > [June 22 2007] AI Craig write a proposal on annotation overrides for
>
> > the expert group.
>
> >
>
> > [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.
>
> >
>
> > [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
>
> > CurrentDevelopment wiki page
>
> >
>
> > [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> >
>
> > [Apr 27 2007] AI Erik file a JIRA regarding JPA style
> transactions and
>
> > attach his discussion document to it.
>
> >
>
> > [Mar 9 2007] AI Craig: Update the spec to require that the key of
> the
>
> > listener is the class name of the listener, for consistency with
>
> > proposed xml..
>
> >
>
> > [Mar 2 2007] AI Craig: update the JDOHelper class to include a
> string
>
> > constant "META-INF/jdo.xml" and a new method
>
> > getPersistenceManagerFactory taking no arguments.
>
> >
>
> > [Aug 11 2006] AI Craig propose some semantics for behavior if user
>
> > tries to add to a list where the ordering element is incorrect.
>
> >
>
> > [Jul 14 2006] AI: Erik document 220 annotations that don't have a
>
> > corresponding JDO concept.
>
> >
>
> > [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
>
> > for Enum types. In progress.
>
> >
>
> > [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> >
>
> > [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of
> JDK 1.5
>
> > issues. In progress
>
> >
>
> > [Sep 2 2005] AI: To recruit members, update the web site.
> Articles on
>
> > TheServerSide directing attention to the site. T-shirts, logo.
> AI:
>
> > Craig write a ServerSide article.
>
> >
>
> > -- Michelle
>
> >
>
> > >
>
> >
>
>
>
>
>
>
>
>
RE: multiple databases one PM/TX
Posted by Eric Samson <er...@xcalia.com>.
Hello Erik,
Once again you start an important topic here! :-)
We also are working on a multi-data sources PMF.
I think the name "resource" could be confusing (I tend to prefer "data source").
Maybe the data source properties should be defined elsewhere (as you can have quite complex configurations when you want to access non-relational data stores)?
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 15:49
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : multiple databases one PM/TX
In JPOX we are implementing the access to multiple datastores within a single
PM/TX. If not too late, I'm wonder if you like to hear a proposal to
standardize the configuration of the "jdoconfig" and jdo metadata to be able to
handle this scenario. It may sound overkill, but IMO is a major advance over
JPA.
To introduce the subject, the goal is to handle persistence in multiple
databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
transaction/ single PM. From the user point of view, there are two items that
must be configured, jdo metadata, jdo configuration, in which would be part of
this proposal, so I show below an example of the configurations:
/jdoconfig/ sequence unbounded PMF
/jdoconfig/ sequence unbounded Resource
/PMF/
/PMF/@Class
/PMF/@TransactionTimeout
/PMF/@...
/Resource/
/Resource/@Name
/Resource/Connection Settings/
/Resource/Connection Settings/@ConnectionFactoryName
/Resource/Connection Settings/@ConnectionClientID
/Resource/Connection Settings/@ReadOnly
/Resource/Connection Settings/@...
/Resource/Transaction/
/Resource/Transaction/@TwoPhaseCommit
/Resource/Transaction/@Timeout
ConnectionClientID
----------------------------
ConnectionClientID is the identifier for the connection. Some databases such as
Oracle use this to identify the end user (not the connection user).
ConnectionClientID would accept the values:
1 - CredentialMapping - the CredentialMapping takes the principal of the running
application and sets it as client id - eg. ConnectionClientID=CredentialMapping
2 - Identity - the client id is taken from the id right after the Identity word
- eg. ConnectionClientID=Identity:MyUser
ReadOnly
----------------------------
ReadOnly (accepts true, false) will block write operations to this connection
TwoPhaseCommit
--------------------------
Two options:
1 - LastLoggingResource - If the resource is non XA, push down this resource in
commit order.
2 - Emulated - Emulates non XA protocol. Heuristics errors could happen
Example:
<jdoconfig>
<pmf name="snowdog" default-resource="Oracle">
</pmf>
<resource name="ERP">
<connection connectionfactoryname="BSCS_Hot"/>
</resource>
<resource name="PeopleSoft">
<connection connectionfactoryname="PS_Onyx"/>
</resource>
<resource name="Oracle">
<connection connectionfactoryname="ORA_Vinci"
connection-client-id="CredentialMapping"/>
<transaction two-phase-commit="LLR" timeout="30"/>
</resource>
<resource name="Xml">
<connection readonly="true"/>
<extension>
<jpox:xml file="file:/usr/home/myxml.xml"/>
</extension>
</resource>
</jdoconfig>
<jdo>
<package>
<class name="Invoice" resource="ERP"/>
<class name="ClassData"/> <!-- uses default-resource -->
<class name="Person" resource="PeopleSoft"/>
<class name="ReferenceData" resource="Xml"/>
</package>
</jdo>
Quoting Michelle Caisse <Mi...@sun.com>:
> Hi,
>
> We will have our regular meeting Friday, October 26 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Subquery spec update
> 2. Other issues
>
> Action Items from weeks past:
>
> [Oct 12 2007] AI Michael take a look at subquery tck tests.
> https://issues.apache.org/jira/browse/JDO-446
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
> attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
> >
>
Re: securing data in JDO
Posted by Matthew Adams <ma...@matthewadams.org>.
Two things:
1. Spring has never been an all-or-nothing proposition. It goes to
great lengths to ensure that only those portions of Spring that
provide you value can be used. See http://www.acegisecurity.org/
standalone.html.
2. I don't really think that domain object security is something that
should be addressed by JDO. This is a classic example of AOP and I
don't think we need to do anything in JDO to explicitly address
this. Spring Security (formerly called "Acegi") provides facilities
for domain object security (see http://www.acegisecurity.org/guide/
springsecurity.html#domain-acls).
If JDO, an SE spec, is to consider domain object security at all,
which I don't think it should, it should wait to see what the JCP
proposes for this kind of security. Is it time for a new JSR on
security? Maybe. Since I tend to favor lagging specs and the only
mature domain object security implementation out there is Spring
Security, I don't think that it's quite time for it.
My $0.02,
Matthew
On Oct 30, 2007, at 5:28 AM, Eric Samson wrote:
> Before we reinvent the wheel, is there any reasonably correct
> framework available out there we can look at as a starting basis?
>
> Some often mention ACEGI, but I’m not sure it is really usable
> outside Spring. Matthew: any comment on this?
>
>
>
> Best Regards,
>
> ....: Eric Samson, Founder & CTO, xcalia
>
> Service your Data!
>
> De : Erik Bengtson [mailto:erik@jpox.org]
> Envoyé : lundi 29 octobre 2007 20:00
> À : Eric Samson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
> Objet : RE: securing data in JDO
>
>
>
> Eric,
>
>
>
> Thanks for your feedback. Perhaps I should put down my requirements
> to fuel the discussion.
>
>
>
> The JDO implementation should be capable of performing security
> checks on data access based on context credentials.
>
>
>
> JDO needs authorization of data access. Authentication is done
> externally.
>
>
>
> Security Credentials:
>
> - principals
>
> - roles
>
> - etc
>
>
>
> Permissions:
>
> - read
>
> - write
>
> - delete
>
> - create
>
>
>
> Data Permissions
>
> - defined sets of data with access denied/granted
>
>
>
> Decision points:
>
> - instance access
>
> - field access
>
> - data access
>
>
>
> Configurable Actions:
>
> - java exceptions
>
> - no ops (so no state transitions)
>
>
>
> Queries:
>
> - The access denied to data would make results invisible to user –
> either the data is not retrieved from database, or discarded upon
> retrieval – implementation choice.
>
>
>
> Detached:
>
> - detached objects also need security checks. It’s possible that
> security context changes over time during the lifecycle of the
> detached objects.
>
>
>
> I agree with the independent standard for general security, and the
> best would be a standard meta framework to perform the decision of
> granting/denying access to data based on its policies.
>
>
>
> However we need a framework to cope with data access and I don’t
> see any light of that coming from a std committee.
>
>
>
> Regards
>
>
>
>
>
> De : Eric Samson [mailto:eric@xcalia.com]
> Envoyé : lundi 29 octobre 2007 17:13
> À : Erik Bengtson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
> Objet : RE: securing data in JDO
>
>
>
> Hello Erik,
>
>
>
> You are starting a very important debate here.
>
>
>
> My first opinion is that, ideally, security should not be defined
> as part of a persistence standard, as it is a general need in the
> Java world.
>
> IMHO, it should be specified as a complete and independent standard
> within the JCP, but I don’t know what’s Sun’s vision about that
> question.
>
>
>
> That said, I fully agree a persistence layer needs a security
> mechanism.
>
> Maybe it is even more important to be able to plug a security
> mechanism into JDO than defining a new security model…
>
>
>
> I don't really like having the security policies and ACLs defined
> in the mapping or JDO metadata.
>
>
>
> About raising exceptions: I think users want to configure that.
>
> For instance, instead of raising Exceptions we could define a new
> state in the StateManager indicating that a value has not be loaded
> due to active security policies.
>
>
>
> Thank you Erik for having started the debate and let’s see where it
> will go.
>
>
>
> Best Regards,
>
> ....: Eric Samson, Founder & CTO, Xcalia
>
> Service your Data!
>
>
>
> -----Message d'origine-----
> De : Erik Bengtson [mailto:erik@jpox.org]
> Envoyé : vendredi 26 octobre 2007 18:04
> À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
> Objet : securing data in JDO
>
>
>
> I would like also to get some feedback about controlling access to
> data in a
>
> standard JDO:
>
>
>
> - Users should be able to specify fine grained access control
> to persistent
>
> objects.
>
> - JDO implementations raise exceptions if the authenticated
> user does not fit
>
> into the role specified in the metadata
>
>
>
> e.g.
>
>
>
> <jdo>
>
> <package>
>
> <class name=”Person”>
>
> <security principal=”adminuser”/>
>
> </class>
>
> </package>
>
> </jdo>
>
>
>
> Or
>
>
>
> <jdo>
>
> <package>
>
> <class name=”Person”>
>
> <field name=”controlCode”>
>
> <security principal=”superuser”/>
>
> </field>
>
> </class>
>
> </package>
>
> </jdo>
>
>
>
>
>
> The user code:
>
>
>
> Person.getControlCode(); //If the principal is not valid, a
> JDOSecurityException
>
> is raised.
>
>
>
> A JDOQL:
>
>
>
> SELECT controlCode FROM Person //If the principal is not valid
> when evaluating
>
> the query (not when compiling), a JDOSecurityException is raised.
>
>
>
>
RE: securing data in JDO
Posted by Eric Samson <er...@xcalia.com>.
Before we reinvent the wheel, is there any reasonably correct framework available out there we can look at as a starting basis?
Some often mention ACEGI, but I'm not sure it is really usable outside Spring. Matthew: any comment on this?
Best Regards,
....: Eric Samson, Founder & CTO, xcalia
Service your Data!
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : lundi 29 octobre 2007 20:00
À : Eric Samson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : RE: securing data in JDO
Eric,
Thanks for your feedback. Perhaps I should put down my requirements to fuel the discussion.
The JDO implementation should be capable of performing security checks on data access based on context credentials.
JDO needs authorization of data access. Authentication is done externally.
Security Credentials:
- principals
- roles
- etc
Permissions:
- read
- write
- delete
- create
Data Permissions
- defined sets of data with access denied/granted
Decision points:
- instance access
- field access
- data access
Configurable Actions:
- java exceptions
- no ops (so no state transitions)
Queries:
- The access denied to data would make results invisible to user - either the data is not retrieved from database, or discarded upon retrieval - implementation choice.
Detached:
- detached objects also need security checks. It's possible that security context changes over time during the lifecycle of the detached objects.
I agree with the independent standard for general security, and the best would be a standard meta framework to perform the decision of granting/denying access to data based on its policies.
However we need a framework to cope with data access and I don't see any light of that coming from a std committee.
Regards
De : Eric Samson [mailto:eric@xcalia.com]
Envoyé : lundi 29 octobre 2007 17:13
À : Erik Bengtson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : RE: securing data in JDO
Hello Erik,
You are starting a very important debate here.
My first opinion is that, ideally, security should not be defined as part of a persistence standard, as it is a general need in the Java world.
IMHO, it should be specified as a complete and independent standard within the JCP, but I don't know what's Sun's vision about that question.
That said, I fully agree a persistence layer needs a security mechanism.
Maybe it is even more important to be able to plug a security mechanism into JDO than defining a new security model...
I don't really like having the security policies and ACLs defined in the mapping or JDO metadata.
About raising exceptions: I think users want to configure that.
For instance, instead of raising Exceptions we could define a new state in the StateManager indicating that a value has not be loaded due to active security policies.
Thank you Erik for having started the debate and let's see where it will go.
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 18:04
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : securing data in JDO
I would like also to get some feedback about controlling access to data in a
standard JDO:
- Users should be able to specify fine grained access control to persistent
objects.
- JDO implementations raise exceptions if the authenticated user does not fit
into the role specified in the metadata
e.g.
<jdo>
<package>
<class name="Person">
<security principal="adminuser"/>
</class>
</package>
</jdo>
Or
<jdo>
<package>
<class name="Person">
<field name="controlCode">
<security principal="superuser"/>
</field>
</class>
</package>
</jdo>
The user code:
Person.getControlCode(); //If the principal is not valid, a JDOSecurityException
is raised.
A JDOQL:
SELECT controlCode FROM Person //If the principal is not valid when evaluating
the query (not when compiling), a JDOSecurityException is raised.
RE: securing data in JDO
Posted by Erik Bengtson <er...@jpox.org>.
Eric,
Thanks for your feedback. Perhaps I should put down my requirements to fuel
the discussion.
The JDO implementation should be capable of performing security checks on
data access based on context credentials.
JDO needs authorization of data access. Authentication is done externally.
Security Credentials:
- principals
- roles
- etc
Permissions:
- read
- write
- delete
- create
Data Permissions
- defined sets of data with access denied/granted
Decision points:
- instance access
- field access
- data access
Configurable Actions:
- java exceptions
- no ops (so no state transitions)
Queries:
- The access denied to data would make results invisible to user either
the data is not retrieved from database, or discarded upon retrieval
implementation choice.
Detached:
- detached objects also need security checks. Its possible that security
context changes over time during the lifecycle of the detached objects.
I agree with the independent standard for general security, and the best
would be a standard meta framework to perform the decision of
granting/denying access to data based on its policies.
However we need a framework to cope with data access and I dont see any
light of that coming from a std committee.
Regards
De : Eric Samson [mailto:eric@xcalia.com]
Envoyé : lundi 29 octobre 2007 17:13
À : Erik Bengtson; jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : RE: securing data in JDO
Hello Erik,
You are starting a very important debate here.
My first opinion is that, ideally, security should not be defined as part of
a persistence standard, as it is a general need in the Java world.
IMHO, it should be specified as a complete and independent standard within
the JCP, but I dont know whats Suns vision about that question.
That said, I fully agree a persistence layer needs a security mechanism.
Maybe it is even more important to be able to plug a security mechanism into
JDO than defining a new security model
I don't really like having the security policies and ACLs defined in the
mapping or JDO metadata.
About raising exceptions: I think users want to configure that.
For instance, instead of raising Exceptions we could define a new state in
the StateManager indicating that a value has not be loaded due to active
security policies.
Thank you Erik for having started the debate and lets see where it will go.
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 18:04
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : securing data in JDO
I would like also to get some feedback about controlling access to data in a
standard JDO:
- Users should be able to specify fine grained access control to
persistent
objects.
- JDO implementations raise exceptions if the authenticated user does
not fit
into the role specified in the metadata
e.g.
<jdo>
<package>
<class name=Person>
<security principal=adminuser/>
</class>
</package>
</jdo>
Or
<jdo>
<package>
<class name=Person>
<field name=controlCode>
<security principal=superuser/>
</field>
</class>
</package>
</jdo>
The user code:
Person.getControlCode(); //If the principal is not valid, a
JDOSecurityException
is raised.
A JDOQL:
SELECT controlCode FROM Person //If the principal is not valid when
evaluating
the query (not when compiling), a JDOSecurityException is raised.
RE: securing data in JDO
Posted by Eric Samson <er...@xcalia.com>.
Hello Erik,
You are starting a very important debate here.
My first opinion is that, ideally, security should not be defined as part of a persistence standard, as it is a general need in the Java world.
IMHO, it should be specified as a complete and independent standard within the JCP, but I don't know what's Sun's vision about that question.
That said, I fully agree a persistence layer needs a security mechanism.
Maybe it is even more important to be able to plug a security mechanism into JDO than defining a new security model...
I don't really like having the security policies and ACLs defined in the mapping or JDO metadata.
About raising exceptions: I think users want to configure that.
For instance, instead of raising Exceptions we could define a new state in the StateManager indicating that a value has not be loaded due to active security policies.
Thank you Erik for having started the debate and let's see where it will go.
Best Regards,
....: Eric Samson, Founder & CTO, Xcalia
Service your Data!
-----Message d'origine-----
De : Erik Bengtson [mailto:erik@jpox.org]
Envoyé : vendredi 26 octobre 2007 18:04
À : jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Objet : securing data in JDO
I would like also to get some feedback about controlling access to data in a
standard JDO:
- Users should be able to specify fine grained access control to persistent
objects.
- JDO implementations raise exceptions if the authenticated user does not fit
into the role specified in the metadata
e.g.
<jdo>
<package>
<class name="Person">
<security principal="adminuser"/>
</class>
</package>
</jdo>
Or
<jdo>
<package>
<class name="Person">
<field name="controlCode">
<security principal="superuser"/>
</field>
</class>
</package>
</jdo>
The user code:
Person.getControlCode(); //If the principal is not valid, a JDOSecurityException
is raised.
A JDOQL:
SELECT controlCode FROM Person //If the principal is not valid when evaluating
the query (not when compiling), a JDOSecurityException is raised.
securing data in JDO
Posted by Erik Bengtson <er...@jpox.org>.
I would like also to get some feedback about controlling access to data in a
standard JDO:
- Users should be able to specify fine grained access control to persistent
objects.
- JDO implementations raise exceptions if the authenticated user does not fit
into the role specified in the metadata
e.g.
<jdo>
<package>
<class name=Person>
<security principal=adminuser/>
</class>
</package>
</jdo>
Or
<jdo>
<package>
<class name=Person>
<field name=controlCode>
<security principal=superuser/>
</field>
</class>
</package>
</jdo>
The user code:
Person.getControlCode(); //If the principal is not valid, a JDOSecurityException
is raised.
A JDOQL:
SELECT controlCode FROM Person //If the principal is not valid when evaluating
the query (not when compiling), a JDOSecurityException is raised.
multiple databases one PM/TX
Posted by Erik Bengtson <er...@jpox.org>.
In JPOX we are implementing the access to multiple datastores within a single
PM/TX. If not too late, Im wonder if you like to hear a proposal to
standardize the configuration of the jdoconfig and jdo metadata to be able to
handle this scenario. It may sound overkill, but IMO is a major advance over
JPA.
To introduce the subject, the goal is to handle persistence in multiple
databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO
transaction/ single PM. From the user point of view, there are two items that
must be configured, jdo metadata, jdo configuration, in which would be part of
this proposal, so I show below an example of the configurations:
/jdoconfig/ sequence unbounded PMF
/jdoconfig/ sequence unbounded Resource
/PMF/
/PMF/@Class
/PMF/@TransactionTimeout
/PMF/@...
/Resource/
/Resource/@Name
/Resource/Connection Settings/
/Resource/Connection Settings/@ConnectionFactoryName
/Resource/Connection Settings/@ConnectionClientID
/Resource/Connection Settings/@ReadOnly
/Resource/Connection Settings/@...
/Resource/Transaction/
/Resource/Transaction/@TwoPhaseCommit
/Resource/Transaction/@Timeout
ConnectionClientID
----------------------------
ConnectionClientID is the identifier for the connection. Some databases such as
Oracle use this to identify the end user (not the connection user).
ConnectionClientID would accept the values:
1 - CredentialMapping - the CredentialMapping takes the principal of the running
application and sets it as client id - eg. ConnectionClientID=CredentialMapping
2 - Identity the client id is taken from the id right after the Identity word
- eg. ConnectionClientID=Identity:MyUser
ReadOnly
----------------------------
ReadOnly (accepts true, false) will block write operations to this connection
TwoPhaseCommit
--------------------------
Two options:
1 LastLoggingResource - If the resource is non XA, push down this resource in
commit order.
2 Emulated Emulates non XA protocol. Heuristics errors could happen
Example:
<jdoconfig>
<pmf name=snowdog default-resource=Oracle>
</pmf>
<resource name=ERP>
<connection connectionfactoryname=BSCS_Hot/>
</resource>
<resource name=PeopleSoft>
<connection connectionfactoryname=PS_Onyx/>
</resource>
<resource name=Oracle>
<connection connectionfactoryname=ORA_Vinci
connection-client-id=CredentialMapping/>
<transaction two-phase-commit=LLR timeout=30/>
</resource>
<resource name=Xml>
<connection readonly=true/>
<extension>
<jpox:xml file=file:/usr/home/myxml.xml/>
</extension>
</resource>
</jdoconfig>
<jdo>
<package>
<class name=Invoice resource=ERP/>
<class name=ClassData/> <!-- uses default-resource -->
<class name=Person resource=PeopleSoft/>
<class name=ReferenceData resource=Xml/>
</package>
</jdo>
Quoting Michelle Caisse <Mi...@sun.com>:
> Hi,
>
> We will have our regular meeting Friday, October 26 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Subquery spec update
> 2. Other issues
>
> Action Items from weeks past:
>
> [Oct 12 2007] AI Michael take a look at subquery tck tests.
> https://issues.apache.org/jira/browse/JDO-446
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
> attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
> issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles on
> TheServerSide directing attention to the site. T-shirts, logo. AI:
> Craig write a ServerSide article.
>
> -- Michelle
>
> >
>
JDO TCK Conference Call Friday, Oct 26 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 26 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Subquery spec update
2. Other issues
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests.
https://issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
>
JDO TCK Conference Call Friday, Oct 19 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 12 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. 2.1 spec and TCK status
2. Other issues
Action Items from weeks past:
[Oct 12 2007] AI Michael take a look at subquery tck tests.
https://issues.apache.org/jira/browse/JDO-446
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
>
Re: If Oracle buys BEA...
Posted by Erik Bengtson <er...@jpox.org>.
No comments about buyout, but patrick would be welcome to our team in setting up a data access platform in heterogeneous data stores for soa, data analysis, mining and ofcourse operational usage. Doh!
-- BlackBerry® from Mobistar ---
-----Original Message-----
From: David Jordan <da...@bellsouth.net>
Date: Fri, 12 Oct 2007 07:37:33
To:JDO Expert Group <jd...@sun.com>
Cc:jdo-dev@db.apache.org
Subject: If Oracle buys BEA...
that very likely signals the death of Kodo JDO...
and also Oracle Application Server...
In my personal view, it would be real nice if Patrick Linskey joined
the JPOX team.
If Oracle buys BEA...
Posted by David Jordan <da...@bellsouth.net>.
that very likely signals the death of Kodo JDO...
and also Oracle Application Server...
In my personal view, it would be real nice if Patrick Linskey joined
the JPOX team.
Re: JDO TCK Conference Call Friday, Oct 12 , 9 am PDT
Posted by Matthew Adams <ma...@matthewadams.org>.
I won't be able to make tomorrow's meeting, or the two after that.
Out of town on each of these days...
-matthew
On Oct 11, 2007, at 4:03 PM, Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, October 12 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Make more JDO APIs generic: https://issues.apache.org/jira/
> browse/JDO-538
> 2. Other issues
>
> Action Items from weeks past:
>
> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides
> for the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> and attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of
> the listener is the class name of the listener, for consistency
> with proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a
> string constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink
> support for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of
> JDK 1.5 issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles
> on TheServerSide directing attention to the site. T-shirts,
> logo. AI: Craig write a ServerSide article.
>
> -- Michelle
>
>
Minutes: JDO TCK Conference Call Friday, Oct 12 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Chris Beams, Michael Bouschen, Craig Russell
Agenda:
1. Make more JDO APIs generic: https://issues.apache.org/jira/browse/
JDO-538
AI Craig discuss the query execute methods on the expert group alias.
https://issues.apache.org/jira/browse/JDO-542 Looks very good.
Closing the implied iterator (e.g. for (Person person : pm.getExtent
(Person.class)) seems to be the only issue. AI discuss how the spec
needs to be updated to discuss what happens if the iterator is
exhausted (automatically closed) versus stopped in the middle of
iteration (closeAll is needed to clean it up, or use a weak reference
algorithm).
2. Other issues
Michael volunteered to start work on the subquery tck tests. https://
issues.apache.org/jira/browse/JDO-446
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 12 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 12 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Make more JDO APIs generic:
https://issues.apache.org/jira/browse/JDO-538
2. Other issues
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Oct 5 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Chris Beams, Matthew
Adams, Craig Russell
Agenda:
1. Make more JDO APIs generic: https://issues.apache.org/jira/browse/
JDO-538
query.execute(Object... )
doesn't work because it limits the ability to pass Object[] as a
single parameter to a Query, for example to compare a field in an
instance to an array.
<T> T[] makePersistentAll (T... pcs);
seems like a good idea since it only requires a change to the
implementation's signature; no change to the logic is needed.
void makeTransientAll (boolean useFetchPlan, Object... pcs);
seems good to add these new methods, and since we would now have two
methods with different signatures but identical semantics, deprecate
the old methods so users would know that the new shiny was the
preferred method but applications would still compile and execute the
same as they once did.
2. Proposed PMF changes (JDOHelper.getPersistenceManagerFactory
section" email from Craig 10/1/2007) No comments yet; AI Matthew
compare spec with existing implementation.
3. Other issues
Final field persistence. Seems like a good thing to fully support
this, but has some implementation issues. AI Chris Beams look into
implementation issues.
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Oct 5 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 5 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Make more JDO APIs generic: https://issues.apache.org/jira/browse/JDO-538
2. Proposed PMF changes (JDOHelper.getPersistenceManagerFactory section"
email from Craig 10/1/2007)
3. Other issues
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by Ilan Kirsh <ki...@objectdb.com>.
Hi Craig,
Thank you for the clarification and the support.
I was hoping it is just a misunderstanding.
Of course, patch is better than exclude (if time permits).
I am looking forward to the fixed 2.0.1 branch.
Regards, Ilan
----- Original Message -----
From: "Craig L Russell" <Cr...@Sun.COM>
Cc: <jd...@db.apache.org>; <jd...@Sun.COM>
Sent: Saturday, September 29, 2007 7:37 PM
Subject: Re: Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
> Hi Ilan,
>
> I was afraid I didn't spend quite enough time on this writeup to be
> completely clear.
>
> The intent is to update the 2.0.1 branch such that a compliant
> implementation can pass the tck with this branch. This means that
> tests that are in violation of the 2.0 specification should either be
> patched to avoid the violation or be excluded. As you have correctly
> pointed out, several issues remain in the 2.0.1 branch and we'd like
> to fix this branch.
>
> Where it is not desirable to exclude the incorrect test, it needs to
> be patched. That's the approach we are trying to take, to avoid
> excluding tests. So for your example for JDO-529, the update needs to
> be merged from the 2.1 trunk to the 2.0.1 test case challenge branch.
> That's the action item that Michelle took: to review the errors and
> merge the fixes to the branch.
>
> Thanks for working with us on this.
>
> Craig
>
> On Sep 29, 2007, at 10:11 AM, Ilan Kirsh wrote:
>
>> Hi Craig,
>>
>>> 2. Test challenges. Some challenges have been filed by Ilan. Most
>>> have been fixed in 2.1 maintenance (trunk) and one of them is
>>> unresolved but can be fixed in the challenge resolution branch
>>> 2.0.1 interim to a final fix in 2.1 maintenance.
>>> Clarification: The 2.1 maintenance work is being done on the
>>> trunk. We created a 2.0.1 branch that has no API changes from 2.0
>>> but has fixes for the tck where a specification clarification or
>>> API change would be needed to pass the tck. A compliant JDO 2.0
>>> implementation should be able to pass the latest tck test in the
>>> 2.0.1 branch.
>>
>> I am not sure I understand this. Currently it is impossible for a
>> compliant
>> JDO implementation to pass the latest tck tests in the 2.0.1 branch.
>>
>> For instance, look at:
>> http://issues.apache.org/jira/browse/JDO-529
>> As you explained very well in a comment to this issue on 16 Sep 2007,
>> an implementation should return 4 result objects rather than 3.
>>
>> I suggest adding these 5 tests to the exclude list of branch 2.0.1.
>>
>> Otherwise, until the release of JDO 2.1 no implementation can be
>> JDO compliance (unfortunately including the reference implementation),
>> because you can only pass the tests by violating the specification.
>>
>> Regards, Ilan
>>
>>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Ilan,
I was afraid I didn't spend quite enough time on this writeup to be
completely clear.
The intent is to update the 2.0.1 branch such that a compliant
implementation can pass the tck with this branch. This means that
tests that are in violation of the 2.0 specification should either be
patched to avoid the violation or be excluded. As you have correctly
pointed out, several issues remain in the 2.0.1 branch and we'd like
to fix this branch.
Where it is not desirable to exclude the incorrect test, it needs to
be patched. That's the approach we are trying to take, to avoid
excluding tests. So for your example for JDO-529, the update needs to
be merged from the 2.1 trunk to the 2.0.1 test case challenge branch.
That's the action item that Michelle took: to review the errors and
merge the fixes to the branch.
Thanks for working with us on this.
Craig
On Sep 29, 2007, at 10:11 AM, Ilan Kirsh wrote:
> Hi Craig,
>
>> 2. Test challenges. Some challenges have been filed by Ilan. Most
>> have been fixed in 2.1 maintenance (trunk) and one of them is
>> unresolved but can be fixed in the challenge resolution branch
>> 2.0.1 interim to a final fix in 2.1 maintenance.
>> Clarification: The 2.1 maintenance work is being done on the
>> trunk. We created a 2.0.1 branch that has no API changes from 2.0
>> but has fixes for the tck where a specification clarification or
>> API change would be needed to pass the tck. A compliant JDO 2.0
>> implementation should be able to pass the latest tck test in the
>> 2.0.1 branch.
>
> I am not sure I understand this. Currently it is impossible for a
> compliant
> JDO implementation to pass the latest tck tests in the 2.0.1 branch.
>
> For instance, look at:
> http://issues.apache.org/jira/browse/JDO-529
> As you explained very well in a comment to this issue on 16 Sep 2007,
> an implementation should return 4 result objects rather than 3.
>
> I suggest adding these 5 tests to the exclude list of branch 2.0.1.
>
> Otherwise, until the release of JDO 2.1 no implementation can be
> JDO compliance (unfortunately including the reference implementation),
> because you can only pass the tests by violating the specification.
>
> Regards, Ilan
>
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by Ilan Kirsh <ki...@objectdb.com>.
Hi Craig,
> 2. Test challenges. Some challenges have been filed by Ilan. Most
> have been fixed in 2.1 maintenance (trunk) and one of them is
> unresolved but can be fixed in the challenge resolution branch 2.0.1
> interim to a final fix in 2.1 maintenance.
>
> Clarification: The 2.1 maintenance work is being done on the trunk.
> We created a 2.0.1 branch that has no API changes from 2.0 but has
> fixes for the tck where a specification clarification or API change
> would be needed to pass the tck. A compliant JDO 2.0 implementation
> should be able to pass the latest tck test in the 2.0.1 branch.
I am not sure I understand this. Currently it is impossible for a compliant
JDO implementation to pass the latest tck tests in the 2.0.1 branch.
For instance, look at:
http://issues.apache.org/jira/browse/JDO-529
As you explained very well in a comment to this issue on 16 Sep 2007,
an implementation should return 4 result objects rather than 3.
I suggest adding these 5 tests to the exclude list of branch 2.0.1.
Otherwise, until the release of JDO 2.1 no implementation can be
JDO compliance (unfortunately including the reference implementation),
because you can only pass the tests by violating the specification.
Regards, Ilan
Minutes: JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Support for final modifier on fields. There are a few issues with
making final fields persistent. First, the only difference between
final and private is that final protects the class writer from
accidentally changing the value of a final field; private protects
the class writer from external code. Except in both cases, using
reflection invalidates the protection. Second, the point at which the
final field is modified by the jdo implementation would need to be
carefully thought through. The final fields' values would have to be
changed during specific life cycle events, such as retrieval from the
datastore, flush, commit, rollback, etc. When exactly would the final
fields be set? And how does this affect the memory model guarantees?
Bottom line: We'd like to see some more justification and discussion
on the open questions raised above.
2. Test challenges. Some challenges have been filed by Ilan. Most
have been fixed in 2.1 maintenance (trunk) and one of them is
unresolved but can be fixed in the challenge resolution branch 2.0.1
interim to a final fix in 2.1 maintenance.
Clarification: The 2.1 maintenance work is being done on the trunk.
We created a 2.0.1 branch that has no API changes from 2.0 but has
fixes for the tck where a specification clarification or API change
would be needed to pass the tck. A compliant JDO 2.0 implementation
should be able to pass the latest tck test in the 2.0.1 branch.
3. Other issues
http://issues.apache.org/jira/browse/JDO-534 Signature test doesn't
work with JDK 6. Looks like the mechanism we use to check signatures
has changed in an incompatible way from Java 5 to Java 6. Volunteer
needed to check into this issue. It looks like the issue is running
Java 5 jar files with Java 6 runtime. The signature test works fine
if the api2 project is compiled with Java 6.
EvictAll: Michael created an issue http://issues.apache.org/jira/
browse/JDO-535 and updated the ChangeLog.
The tck2 currently fails due to database cleanup issues. Teardown
fails. AI Michelle see if recently added tests have affected the
teardown.
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 28 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 28 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Support for final modifier on fields
2. Test challenges
3. Other issues
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Sep 21 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Chris Beams, Matthew Adams, Michael Bouschen, Michelle Caisse, Craig
Russell
Agenda:
1. Should non ORM implementations support bidirectional relationship?
The biggest concern is what to call the "mapped-by" attribute of the
metadata. AI Matthew try to think of a better term than mapped-by for
this concept. Perhaps "related-to" or "reciprocates" works? This
would be a synonym for "mapped-by" for backward compatibility.
2. (JDO-529) ChangeQuery - DISTINCT is expected even though it is not
specified. Michael checked in a fix.
3. Configurable persistence by reachability in JDO 2.1? Seems to be
not really needed or useful in JDO.
4. Other issues
AI Michael update the ChangeLog, file a jira for evictAll(Class) and
propose a fix.
Christiaan's mail discussing large inserts cache behavior has merit.
AI Craig propose an update to the spec to require that the
implementation not hold a strong reference to dirty instances after
flush.
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 21 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 21 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Should non ORM implementations support bidirectional relationship?
2. (JDO-529) ChangeQuery - DISTINCT is expected even though it is not
specified
3. Configurable persistence by reachability in JDO 2.1?
4. Other issues
Action Items from weeks past:
[Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml.
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
RE: Minutes: JDO TCK Conference Call Friday, Sep 14, 9 am PDT
Posted by Erik Bengtson <er...@jpox.org>.
>2. Review PMF bootstrap process for JDO specification. Feedback was
>received from Matthew. Other issues are whether there is a need for
>getPMF(Map, ClassLoader, ClassLoader) and whether you can use a Map
>plus a String pmf name. AI Matthew provide examples for 8.6.1.1
>jdoconfig.xml.
I have an use case to fuel the classloading discussion...
An app running in OSGI environment:
The application runs in a thread which classpath is isolated from other
resources such as PC classes, bootstrap configuration file (.properties,
jdoconfig.xml or persistence.xml), jdo implementation and jdbc drivers.
So the classpath is organized as:
System classpath
jdo.jar (CP 0)
Application classes (CP 1) - jdo classes loading delegated to CP 0
bootstrap configuration file in (CP 2)
jdo implementation in (CP 3) - jdo classes loading delegated to CP 0
jdbc drivers in (CP 4)
Pseudo code:
//current thread classloader is CP1
Map props = CP2.load bootstrap file();
props.put("org.jpox.primaryClassLoader",CP4);
PersistenceManagerFactory pmf =
JDOHelper.getPersistenceManagerFactory(props,CP2);
Minutes: JDO TCK Conference Call Friday, Sep 14, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Chris Beams, Matthew
Adams, Erik Bengtson, Craig Russell
Agenda:
1. Discussion: Add void evictAll (Class pcClass, boolean
subclasses). This allows to evict instances for a particluar class.
This cannot be implemented by the user. There do not seem to be any
negative effects of doing this. AI Craig update ChangeLog and
CurrentDevelopment. Clarify behavior of persistent classes if the
parameter is a persistent interface. This comment also applies to the
DataStoreCache interface method evictAll(Class).
2. Review PMF bootstrap process for JDO specification. Feedback was
received from Matthew. Other issues are whether there is a need for
getPMF(Map, ClassLoader, ClassLoader) and whether you can use a Map
plus a String pmf name. AI Matthew provide examples for 8.6.1.1
jdoconfig.xml.
3. Other issues
The CopyOnAttach proposal by Chris Beams was sent around and was
reviewed. Items include adding the CopyOnAttach property to the
PersistenceManager and write a bit of text describing the behavior at
a high level. AI Chris update the proposal.
Spring support for JDO 2.1 needs definition. AI Chris send discussion
to dev email alias.
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of
the listener is the class name of the listener, for consistency
with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a
string constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Sep 14, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 14 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Discussion: Add void evictAll (Class pcClass, boolean subclasses);
2. Review PMF bootstrap process for JDO specification
3. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Sep 7, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 7 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Restriction on <unique> subelements
2. Negative test in
org.apache.jdo.tck.query.result.ResultClassRequirements (JDO-524)
3. Spec status update
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Aug 31, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 31 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Draft proposal for CopyOnAttach property
2. Update on managed relationship classes
3. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Aug 24, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Matthew Adams, Chris Beams, Michael Bouschen, Michelle Caisse
Chris will have proposal for CopyOnAttach property (JDO-522) prepared by
next meeting for discussion. Matthew suggests that the proposal consider
effects on second level cache.
Matthew will investigate JSO-523 misleading error message. Code path is
operating correctly, but only the last step in the search is reflected
in the error message. Message should cumulate over the different
attempts to find the resource.
Michelle attached patch for first tests for managed relationships
(JDO-521). Two cases are failing such that the other side of the
relationship is not set by the implementation, though it is after commit
when fetched with a new pm. A third case fails in both cases. Three
cases pass.
-- Michelle
>
>
> Agenda:
>
> 1. Draft proposal for CopyOnAttach property
> 2. Other issues
>
> Action Items from weeks past:
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> and attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
> 1.5 issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles
> on TheServerSide directing attention to the site. T-shirts, logo.
> AI: Craig write a ServerSide article.
>
> -- Michelle
JDO TCK Conference Call Friday, Aug 24, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 24 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Draft proposal for CopyOnAttach property
2. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: jdo 2.1 - 18.14 property
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Erik,
The 18.14 section is incomplete; it doesn't address the several use
cases that we discussed a couple of months ago. I'm going to update
the section as soon as I review the discussion.
Thanks,
Craig
On Aug 17, 2007, at 3:04 AM, Erik Bengtson wrote:
> Hi,
>
> §18.14
> "When contained in a class element:
> - The field-name attribute is required; it associates a persistent
> field with
> the named property."
>
> AFAIR field-name attribute is used for generated classes. It should
> be optional
> when contained in class or interface elements.
>
> e.g.
>
> //user given interface
> interface Animal
> {
> @Persistent(fieldname="kind2")
> int getKind();
> }
>
> //jdo implementation generated class
> class GeneratedAnimal
> {
> int kind2;
> int getKind()
> {
> return kind2;
> }
> }
>
> or
> ---
>
> //user given abstract class
> abstract Jedi
> {
> int jedilevel;
> @Persistent(fieldname="jedilevel")
> int getLevel();
> }
>
> //jdo implementation generated class
> class GeneratedJedi
> {
> int jedilevel;
> int getLevel()
> {
> return jedilevel;
> }
> }
>
>
> The new wording could be:
> "When contained in a class or interface element:
> - The field-name attribute is optional; it associates a persistent
> property with
> a named field."
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
jdo 2.1 - 18.14 property
Posted by Erik Bengtson <er...@jpox.org>.
Hi,
§18.14
"When contained in a class element:
- The field-name attribute is required; it associates a persistent field with
the named property."
AFAIR field-name attribute is used for generated classes. It should be optional
when contained in class or interface elements.
e.g.
//user given interface
interface Animal
{
@Persistent(fieldname="kind2")
int getKind();
}
//jdo implementation generated class
class GeneratedAnimal
{
int kind2;
int getKind()
{
return kind2;
}
}
or
---
//user given abstract class
abstract Jedi
{
int jedilevel;
@Persistent(fieldname="jedilevel")
int getLevel();
}
//jdo implementation generated class
class GeneratedJedi
{
int jedilevel;
int getLevel()
{
return jedilevel;
}
}
The new wording could be:
"When contained in a class or interface element:
- The field-name attribute is optional; it associates a persistent property with
a named field."
Re: Misleading error message
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Erik,
Please file a JIRA issue on this so we can track it.
Thanks,
Craig
On Aug 23, 2007, at 3:44 PM, Erik Bengtson wrote:
> Hi,
>
> Running the following code, and if the jpox.properties cannot be
> found, a
> misleading message is raised that indicates a missing a EntityManager
> persistence provider, but should actually tell me that my resource
> jpox.properties cannot be found.
>
> PersistenceManagerFactory pmf =
> JDOHelper.getPersistenceManagerFactory("jpox.properties");
>
> ------------------
> Exception in thread "main" javax.jdo.JDOFatalUserException: Unable
> to invoke
> javax.persistence.Persistence.createEntityManagerFactory(String)
> at javax.jdo.JDOHelper.getPMFFromEMF(JDOHelper.java:1210)
> at javax.jdo.JDOHelper.getPersistenceUnit(JDOHelper.java:952)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 894)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 836)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 814)
> at org.jpox.persistence.Main.main(Main.java:10)
> NestedThrowablesStackTrace:
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at javax.jdo.JDOHelper.getPMFFromEMF(JDOHelper.java:1194)
> at javax.jdo.JDOHelper.getPersistenceUnit(JDOHelper.java:952)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 894)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 836)
> at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:
> 814)
> at org.jpox.persistence.Main.main(Main.java:10)
> Caused by: javax.persistence.PersistenceException: No Persistence
> provider for
> EntityManager named jpox.properties
> at
> javax.persistence.Persistence.createEntityManagerFactory
> (Persistence.java:89)
> at
> javax.persistence.Persistence.createEntityManagerFactory
> (Persistence.java:60)
> ... 10 moreg
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Misleading error message
Posted by Erik Bengtson <er...@jpox.org>.
Hi,
Running the following code, and if the jpox.properties cannot be found, a
misleading message is raised that indicates a missing a EntityManager
persistence provider, but should actually tell me that my resource
jpox.properties cannot be found.
PersistenceManagerFactory pmf =
JDOHelper.getPersistenceManagerFactory("jpox.properties");
------------------
Exception in thread "main" javax.jdo.JDOFatalUserException: Unable to invoke
javax.persistence.Persistence.createEntityManagerFactory(String)
at javax.jdo.JDOHelper.getPMFFromEMF(JDOHelper.java:1210)
at javax.jdo.JDOHelper.getPersistenceUnit(JDOHelper.java:952)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:894)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:836)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:814)
at org.jpox.persistence.Main.main(Main.java:10)
NestedThrowablesStackTrace:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.jdo.JDOHelper.getPMFFromEMF(JDOHelper.java:1194)
at javax.jdo.JDOHelper.getPersistenceUnit(JDOHelper.java:952)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:894)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:836)
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:814)
at org.jpox.persistence.Main.main(Main.java:10)
Caused by: javax.persistence.PersistenceException: No Persistence provider for
EntityManager named jpox.properties
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:89)
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60)
... 10 moreg
RE: Minutes: JDO TCK Conference Call Friday, Aug 17, 9 am PDT
Posted by "Matthew T. Adams" <ma...@matthewadams.org>.
Thanks, and this will be included in the standard enhancement contract.
-----Original Message-----
From: Erik Bengtson [mailto:erik@jpox.org]
Sent: Saturday, August 18, 2007 6:57 AM
To: jdo-dev@db.apache.org; jdo-experts-ext@sun.com
Subject: Re: Minutes: JDO TCK Conference Call Friday, Aug 17, 9 am PDT
Matthew and All,
Do you also have ClassFileTransformer for transparent runtime enhancement
with
JRE 5 ?
usage example:
------------------
java -javaagent:jdo-2.1.jar -Djavax.jdo.enhancer.class=acme.EnhancerImpl
<MAIN>
alternative command line:
java -javaagent:jdo-2.1.jar=enhancer.class=acme.EnhancerImpl <MAIN>
Implementation
-------------------------------------
package acme;
public class Enhancer
{
public Enhancer() {}
public byte[] enhance(final String className, byte[] classdefinition,
ClassLoader loader)
{
return bytecodemodified;
}
}
--------------------------------------
package javax.jdo.enhancer;
public JDOClassFileTransformer implements ClassFileTransformer
{
public static void premain(String agentArguments, Instrumentation
instrumentation)
{
instrumentation.addTransformer(new JDOClassFileTransformer());
}
public byte[] transform(ClassLoader loader, String className, Class
classBeingRedefined, ProtectionDomain protectionDomain, byte[]
classfileBuffer)
{
Enhancer enhancer = new instance of class defined at
System.getProperty("javax.jdo.enhancer.class")
return enhancer.enhance(className,classfileBuffer,loader);
}
}
--------------------------------------------------
Quoting Michelle Caisse <Mi...@sun.com>:
> Attendees: Matthew Adams, Michelle Caisse
>
> Matthew is working on standard enhancer and schema management classes
> and the associated SPI.
> His patch dealing with PMF properties "name" and "persistenceUnitName"
> have been checked in (JDO-496). Seems to work.
>
> Michelle is working on tests for relationship integrity on flush() when
> the application changes one side of the relationship (spec 15.3).
>
> Craig is working on spec updates for persistent properties.
>
> -- Michelle
>
> Michelle Caisse wrote:
>
> > Hi,
> >
> > We will have our regular meeting Friday, August 17 at 9 am PDT to
> > discuss JDO TCK issues and status.
> >
> > Dial-in numbers are:
> > 866 230-6968 294-0479#
> > International: +1 865 544-7856
> >
> > Agenda:
> >
> > 1. Relationship mapping tests update
> > 2. Annotations on properties
> > 3. Other issues
> >
> > Action Items from weeks past:
> >
> > [June 22 2007] AI Craig discuss svn:eol-style on email.
> >
> > [June 22 2007] AI Craig write a proposal on annotation overrides for
> > the expert group.
> >
> > [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.
> >
> > [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> > CurrentDevelopment wiki page
> >
> > [Apr 27 2007] AI Craig review Query API and send email to experts.
> >
> > [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> > and attach his discussion document to it.
> >
> > [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> > listener is the class name of the listener, for consistency with
> > proposed xml..
> >
> > [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> > constant "META-INF/jdo.xml" and a new method
> > getPersistenceManagerFactory taking no arguments.
> >
> > [Aug 11 2006] AI Craig propose some semantics for behavior if user
> > tries to add to a list where the ordering element is incorrect.
> >
> > [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> > corresponding JDO concept.
> >
> > [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> > for Enum types. In progress.
> >
> > [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
> >
> > [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
> > 1.5 issues. In progress
> >
> > [Sep 2 2005] AI: To recruit members, update the web site. Articles
> > on TheServerSide directing attention to the site. T-shirts, logo.
> > AI: Craig write a ServerSide article.
> >
> > -- Michelle
>
>
>
Re: Minutes: JDO TCK Conference Call Friday, Aug 17, 9 am PDT
Posted by Erik Bengtson <er...@jpox.org>.
Matthew and All,
Do you also have ClassFileTransformer for transparent runtime enhancement with
JRE 5 ?
usage example:
------------------
java -javaagent:jdo-2.1.jar -Djavax.jdo.enhancer.class=acme.EnhancerImpl <MAIN>
alternative command line:
java -javaagent:jdo-2.1.jar=enhancer.class=acme.EnhancerImpl <MAIN>
Implementation
-------------------------------------
package acme;
public class Enhancer
{
public Enhancer() {}
public byte[] enhance(final String className, byte[] classdefinition,
ClassLoader loader)
{
return bytecodemodified;
}
}
--------------------------------------
package javax.jdo.enhancer;
public JDOClassFileTransformer implements ClassFileTransformer
{
public static void premain(String agentArguments, Instrumentation
instrumentation)
{
instrumentation.addTransformer(new JDOClassFileTransformer());
}
public byte[] transform(ClassLoader loader, String className, Class
classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer)
{
Enhancer enhancer = new instance of class defined at
System.getProperty("javax.jdo.enhancer.class")
return enhancer.enhance(className,classfileBuffer,loader);
}
}
--------------------------------------------------
Quoting Michelle Caisse <Mi...@sun.com>:
> Attendees: Matthew Adams, Michelle Caisse
>
> Matthew is working on standard enhancer and schema management classes
> and the associated SPI.
> His patch dealing with PMF properties "name" and "persistenceUnitName"
> have been checked in (JDO-496). Seems to work.
>
> Michelle is working on tests for relationship integrity on flush() when
> the application changes one side of the relationship (spec 15.3).
>
> Craig is working on spec updates for persistent properties.
>
> -- Michelle
>
> Michelle Caisse wrote:
>
> > Hi,
> >
> > We will have our regular meeting Friday, August 17 at 9 am PDT to
> > discuss JDO TCK issues and status.
> >
> > Dial-in numbers are:
> > 866 230-6968 294-0479#
> > International: +1 865 544-7856
> >
> > Agenda:
> >
> > 1. Relationship mapping tests update
> > 2. Annotations on properties
> > 3. Other issues
> >
> > Action Items from weeks past:
> >
> > [June 22 2007] AI Craig discuss svn:eol-style on email.
> >
> > [June 22 2007] AI Craig write a proposal on annotation overrides for
> > the expert group.
> >
> > [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.
> >
> > [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> > CurrentDevelopment wiki page
> >
> > [Apr 27 2007] AI Craig review Query API and send email to experts.
> >
> > [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> > and attach his discussion document to it.
> >
> > [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> > listener is the class name of the listener, for consistency with
> > proposed xml..
> >
> > [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> > constant "META-INF/jdo.xml" and a new method
> > getPersistenceManagerFactory taking no arguments.
> >
> > [Aug 11 2006] AI Craig propose some semantics for behavior if user
> > tries to add to a list where the ordering element is incorrect.
> >
> > [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> > corresponding JDO concept.
> >
> > [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> > for Enum types. In progress.
> >
> > [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
> >
> > [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
> > 1.5 issues. In progress
> >
> > [Sep 2 2005] AI: To recruit members, update the web site. Articles
> > on TheServerSide directing attention to the site. T-shirts, logo.
> > AI: Craig write a ServerSide article.
> >
> > -- Michelle
>
>
>
Minutes: JDO TCK Conference Call Friday, Aug 17, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse
Matthew is working on standard enhancer and schema management classes
and the associated SPI.
His patch dealing with PMF properties "name" and "persistenceUnitName"
have been checked in (JDO-496). Seems to work.
Michelle is working on tests for relationship integrity on flush() when
the application changes one side of the relationship (spec 15.3).
Craig is working on spec updates for persistent properties.
-- Michelle
Michelle Caisse wrote:
> Hi,
>
> We will have our regular meeting Friday, August 17 at 9 am PDT to
> discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> 866 230-6968 294-0479#
> International: +1 865 544-7856
>
> Agenda:
>
> 1. Relationship mapping tests update
> 2. Annotations on properties
> 3. Other issues
>
> Action Items from weeks past:
>
> [June 22 2007] AI Craig discuss svn:eol-style on email.
>
> [June 22 2007] AI Craig write a proposal on annotation overrides for
> the expert group.
>
> [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.
>
> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/
> CurrentDevelopment wiki page
>
> [Apr 27 2007] AI Craig review Query API and send email to experts.
>
> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
> and attach his discussion document to it.
>
> [Mar 9 2007] AI Craig: Update the spec to require that the key of the
> listener is the class name of the listener, for consistency with
> proposed xml..
>
> [Mar 2 2007] AI Craig: update the JDOHelper class to include a string
> constant "META-INF/jdo.xml" and a new method
> getPersistenceManagerFactory taking no arguments.
>
> [Aug 11 2006] AI Craig propose some semantics for behavior if user
> tries to add to a list where the ordering element is incorrect.
>
> [Jul 14 2006] AI: Erik document 220 annotations that don't have a
> corresponding JDO concept.
>
> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support
> for Enum types. In progress.
>
> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
>
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
> 1.5 issues. In progress
>
> [Sep 2 2005] AI: To recruit members, update the web site. Articles
> on TheServerSide directing attention to the site. T-shirts, logo.
> AI: Craig write a ServerSide article.
>
> -- Michelle
JDO TCK Conference Call Friday, Aug 17, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 17 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Relationship mapping tests update
2. Annotations on properties
3. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Aug 10, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Agenda:
1. Changes to build script. SNAPSHOT vs. 2.1-SNAPSHOT
2. Annotations: discuss custom settings for enum-valued elements.
3. Attach (makePersistent) a detached instance always merges changes
into the cache. Can this behavior be changed to always make the
parameter instance change its state, throwing an exception if there
already is an instance in the cache?
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Aug 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Thanks. Have a good vacation.
Craig
On Aug 3, 2007, at 11:25 AM, Michael Bouschen wrote:
> Hi Craig,
>
> [...]
>> 3. TCK signature test: The signatures of the api2 and api2-legacy
>> are different even thought the code is the same. Michael Bouschen
>> has volunteered to fix it and has sent a patch in email. It will
>> be checked in today.
> Done. See revision 562539.
>
> Regards Michael
>
> [...]
>
> --
> Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
> Buelowstr. 66 Fax.: +49/(0)30/217 520-12
> 10783 Berlin mailto:mbo.tech@spree.de
> Geschaeftsfuehrung: Anna-Kristin Proefrock
> Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Aug 3, 9 am PDT
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
[...]
> 3. TCK signature test: The signatures of the api2 and api2-legacy are
> different even thought the code is the same. Michael Bouschen has
> volunteered to fix it and has sent a patch in email. It will be
> checked in today.
Done. See revision 562539.
Regards Michael
[...]
--
Tech@Spree Engineering GmbH Tel.: +49/(0)30/235 520-33
Buelowstr. 66 Fax.: +49/(0)30/217 520-12
10783 Berlin mailto:mbo.tech@spree.de
Geschaeftsfuehrung: Anna-Kristin Proefrock
Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
Re: JDO TCK Conference Call Friday, Aug 3, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
The draft spec has been published on the JDO web site. Please see
http://db.apache.org/jdo/documentation.html
1. Annotations update: Annotations are now stable. All the issues
have been resolved. Annotations are intended to be exactly as
expressive as xml. Please review and comment if there are any
differences.
2. Abstract Class persistence: JPOX doesn't currently support
pm.newInstance(AbstractClass). There's a wiki discussion here http://
www.jpox.org/servlet/wiki/en/Persistent_Abstract_Class_Design
3. TCK signature test: The signatures of the api2 and api2-legacy are
different even thought the code is the same. Michael Bouschen has
volunteered to fix it and has sent a patch in email. It will be
checked in today.
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Aug 3, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 3 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Annotations update
2. Abstract Class persistence
3. TCK signature test
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for the
expert group.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, July 27, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 27 at 9 am PDT to discuss
JDO TCK issues and status.
Apologies for the late notice.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Annotations update
2. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for the
expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
On Jul 21, 2007, at 10:48 AM, Andy Jefferson wrote:
> Hi Craig,
>
>> This brings up a question. In JPOX, if you enhance a class with a
>> field that is NotPersistent, can you then in an embedded use case
>> mark the same field as Persistent?
>
> The only situation I'd currently thought of (but never tried) would
> be of
> not persisting a field that had been defined as persistent (not the
> other
> way around). The JPOX Enhancer doesn't do anything special in this
> situation so if the user enhanced it as non-persistent and tried
> that it
> would likely fail.
>
> I've certainly seen some situations where a particular class is
> defined
> with a full persistence definition, but when stored embedded only a
> subset
> of the fields are wanted to be persisted.
>
>> More questions than answers. Are we sure that it's a good idea to
>> allow overriding the PersistenceModifier in embedded usages?
>
> I'd like to allow the "downgrade" option (not persist a persistable
> field)
> since it should be common enough when embedding. As you pointed
> out, the
> "upgrade" option creates problems and would require special
> treatment to
> allow it so I've no problem ruling it out.
Ok, I've restored PersistenceModifier and I'll put in some javadoc to
indicate where it might productively be used.
Thanks,
Craig
> --
> Andy
> Java Persistent Objects (JPOX)
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
Hi Craig,
> This brings up a question. In JPOX, if you enhance a class with a
> field that is NotPersistent, can you then in an embedded use case
> mark the same field as Persistent?
The only situation I'd currently thought of (but never tried) would be of
not persisting a field that had been defined as persistent (not the other
way around). The JPOX Enhancer doesn't do anything special in this
situation so if the user enhanced it as non-persistent and tried that it
would likely fail.
I've certainly seen some situations where a particular class is defined
with a full persistence definition, but when stored embedded only a subset
of the fields are wanted to be persisted.
> More questions than answers. Are we sure that it's a good idea to
> allow overriding the PersistenceModifier in embedded usages?
I'd like to allow the "downgrade" option (not persist a persistable field)
since it should be common enough when embedding. As you pointed out, the
"upgrade" option creates problems and would require special treatment to
allow it so I've no problem ruling it out.
--
Andy
Java Persistent Objects (JPOX)
Re: JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Andy,
Good catch.
This brings up a question. In JPOX, if you enhance a class with a
field that is NotPersistent, can you then in an embedded use case
mark the same field as Persistent? The spec doesn't really address
this issue. The implication is that the enhancer would need to
enhance every field as if it were Persistent, even if it's marked
NotPersistent, just in case it's overridden in the embedded case. And
then each field access to a NotPersistent field would need to check
to see if it's still NotPersistent for this particular case.
More questions than answers. Are we sure that it's a good idea to
allow overriding the PersistenceModifier in embedded usages?
Craig
On Jul 21, 2007, at 12:43 AM, Andy Jefferson wrote:
>> The only reason to have PersistenceModifier at all is to make it
>> possible to say @Persistent
>> (persistenceModifier=PersistenceModifier.NONE) or @Persistent
>> (persistenceModifier=PersistenceModifier.TRANSACTIONAL). It can be
>> removed without loss of functionality.
>
> It *cannot* be removed with no loss of functionality. If I need to
> specify
> the fields of an embedded instance and I want to override the
> persistence-modifier setting of a field how would I do that? I
> don't see
> it since I cant specify @NotPersistent in the "fields" of @Embedded
> since
> it takes an array of @Persistent.
>
>
> --
> Andy
> Java Persistent Objects (JPOX)
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Andy Jefferson <an...@jpox.org>.
> The only reason to have PersistenceModifier at all is to make it
> possible to say @Persistent
> (persistenceModifier=PersistenceModifier.NONE) or @Persistent
> (persistenceModifier=PersistenceModifier.TRANSACTIONAL). It can be
> removed without loss of functionality.
It *cannot* be removed with no loss of functionality. If I need to specify
the fields of an embedded instance and I want to override the
persistence-modifier setting of a field how would I do that? I don't see
it since I cant specify @NotPersistent in the "fields" of @Embedded since
it takes an array of @Persistent.
--
Andy
Java Persistent Objects (JPOX)
Re: JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Annotations update Craig checked in some changes to annotations
that included changing String[ ] embedded to Embedded[ ] embedded.
This caused the enhancer to fail. Other changes pending will also
make the enhancer fail: removing @Field and @Property, replacing them
by @Persistent. These changes were outlined in the message from Craig
http://mail-archives.apache.org/mod_mbox/db-jdo-dev/200707.mbox/%
3c705B9F42-DC2E-45D9-9F65-EFF7594C9BBE@SUN.com%3e
The only reason to have PersistenceModifier at all is to make it
possible to say @Persistent
(persistenceModifier=PersistenceModifier.NONE) or @Persistent
(persistenceModifier=PersistenceModifier.TRANSACTIONAL). It can be
removed without loss of functionality.
The spec should note that @NotPersistent maps to persistence-
modifier="none"
recursionDepth needs to be added to @Persistent so it can be used
instead of @FetchField in @FetchGroup.
Maybe we should remove @Persistence type() because types() covers it.
Perhaps we should rename the element to allowedTypes, or
requiredTypes or boundedTypes, permittedTypes(), subTypes(),
extendedTypes()
AI Craig update the proposal; attach a patch to a new JIRA; call for
a vote
2. Other issues
Interesting application that might apply to JDO. Domain Driven
Design, Eric Evans. Persistent objects that have collaboration logic
for relationship handling but also have some business logic. Content
management application. Planned vs. actual pattern. Detached object
launches a thread and notifies a listener of a state change. The
listener attaches the object to the database and updates the database.
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 20, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 20 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Annotations update
2. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for the
expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, July 13, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Review of "JDO Spec clarifications for mapping metadata" (10 July)
Looking at the additions needed (at the bottom of the document) it
appears that we need just a few more for completeness. AI Craig write
up the newest additions for email discussion.
2. PMF Name issues Matthew is nearly done with the integration of PMF
Name into the bootstrap process. AI Matthew write up latest
algorithm. AI All review writeup, as it's going into the specification.
3. Other issues
None.
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for
the expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 13, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 13 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Review of "JDO Spec clarifications for mapping metadata" (10 July)
2. PMF Name issues
3. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for the
expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
No JDO TCK Conference Call
Posted by Michelle Caisse <Mi...@Sun.COM>.
As mentioned in last week's minutes, this week's meeting is cancelled.
We will meet again on Friday, July 13.
-- Michelle
JDO TCK Conference Call Friday, June 29, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 29 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Put all annotations on class, name field within annotation?
2. Nested embedded annotations
3. Primary key, foreign key annotations
4. Other issues
Action Items from weeks past:
[June 22 2007] AI Craig discuss svn:eol-style on email.
[June 22 2007] AI Craig write a proposal on annotation overrides for the
expert group.
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, June 22, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 22 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. svn repository: add svn:eol-style property for file with suffix
.java, .jdo, .orm etc.
2. Annotation overrides - what does override mean?
3. Annotations for embedded fields
4. Branching tck20
5. What about defining an enum like TriStateBoolean with TRUE, FALSE,
UNDEFINED?
6. Other issues
Action Items from weeks past:
[June 15 2007] AI Craig put spec somewhere for review.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, June 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 15 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Annotations update
2. Feedback on JDO 2.1 draft spec
3. Update TCK to use 2.1 xsd
4. Other issues
Action Items from weeks past:
[Jun 7 2007] AI Craig file a JIRA to improve javadoc for the test classes.
[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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, June 8, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Martin Zaun, Matthew Adams, Craig Russell
Agenda:
1. Branching for legacy/Java 1.5 Done. All you need to do is to svn
update from the trunk and the old api20 directory will be removed and
replaced by the new api2 and api2-legacy. That's all that's been
done. Artifact ids and java version dependencies have been changed.
2. PersistenceUnitName/Name Find the resource. Find a named PMF via
the property name. If not found, delegate to the
Persistence.createEntityManagerFactory with the PersistenceUnitName.
AI Matthew Create a JIRA issue. AI Craig: Write up how to use the
different properties with some use cases.
3. "[Fatal Error]" messages on api2 build. Register an error handler
that simply eats the exceptions. A JDO implementation should be able
to register a document builder factory and/or an error handler. New
APIs are needed for the spi.JDOImplHelper. AI Matthew file a JIRA.
4. Other issues.
Need to use an own class loader in the jdoconfig.xml tests. Might
need better documentation on what is happening. AI Craig file a JIRA
to improve javadoc for the test classes.
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.
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, June 8, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 8 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Branching for legacy/Java 1.5
2. PersistenceUnitName/Name
3. "[Fatal Error]" messages on api20 build
4. 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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, June 1, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michael Bouschen, Michelle Caisse, Martin Zaun
JDO-472 New xsd files
Patch checked in and issue is resolved. The version number of the fixed
files is 2.1. The API 2.0 test files now link to the new xsd's. We
should also change the TCK20 metadata files to refer to the 2.1 version
of the xsd when JPOX is ready to handle this. It would be good to do
this before the TCK project is branched for legacy vs. JDK 5 support.
JDO-482 Service lookup
Matthew was not present to speak to this.
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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, June 1, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 1 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO-472 New xsd files - Any remaining issues?
2. JDO-472 Service lookup
3. 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.
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, May 25, 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell
Agenda:
1. Are we ready to branch for JDK 1.5 vs legacy?
Still one more checkin that is waiting for the xsd resolution. AI
Michael: Update the xsd for jdoquery and orm.
2. Standard JDO enhancer interface. No action. Deferred until next week.
3. Other issues
Schema management API: AI Matthew Adams prepare a proposal with just
the basics of schema synchronization with jdo and orm metadata.
Grails looks really interesting. Based on GORM (Groovy Object
Relational Mapping). Currently only uses Hibernate but might be
extended to use other persistence providers like JPA and JDO. 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.
Action Items from weeks past:
[May 18 2007] AI Michael resolve 472
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 25, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 25 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Are we ready to branch for JDK 1.5 vs legacy?
2. Standard JDO enhancer interface
3. Other issues
Action Items from weeks past:
[May 18 2007] AI Michael resolve 472
[May 18 2007] AI Craig update
http://wiki.apache.org/jdo/CurrentDevelopment wiki page
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, May 18 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Review steps toward releasing JDO 2.1
Looks like we're ready to branch after http://issues.apache.org/jira/
browse/JDO-472 is checked in. This will split the api20 project into
api2-legacy and api2 (with JDK 1.5 changes); and tck20 project into
tck2-legacy and tck2.
AI Michael resolve 472. AI Craig update http://wiki.apache.org/jdo/
CurrentDevelopment wiki page.
2. Other issues
Propose to add an enhancer interface to make life easier on users.
Use the services concept to define a class that implements the
enhancer interface.
How about relaxing the requirement that classes be enhanced? This
project was proposed a while ago but there were no volunteers.
Assertion spreadsheet: it's out of date with regard to the spec. If
we get rid of the spreadsheet we will need to publish a version of
the spec with the assertions.
Action Items from weeks past:
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions
and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, May 18 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 18 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Review steps toward releasing JDO 2.1
2. Other issues
Action Items from weeks past:
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, May 4 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, May 4 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JPA style transactions
2. Other issues
Action Items from weeks past:
[Apr 27 2007] AI Craig reply to JDO-403 discussion.
[Apr 27 2007] AI Craig review Query API and send email to experts.
[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and
attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Apr 27 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 27 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO metadata: XSD changes
2. Support specification of ForeignKey, PrimaryKey within @Join and
@Element annotations (JDO-486)
3. Other issues
Action Items from weeks past:
[Mar 30 2007] AI Eric: Post a number of scenarios regarding JDO2/JPA
transaction types for discussion.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Apr 20 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Eric Bengtson, Michael Bouschen, Martin
Zaun, Matthew Adams
1. JDOHelper.isLoaded proposal (JDO-483)
The following solution was suggested: User can check
javax.jdo.option.BinaryCompatibility before calling the boolean method
isLoaded(Instance, fieldName). The method will throw
JDOUnsupportedOperationException only if the object is detached, the
value of field is null, 0, or false, and the implementation does not
support binary compatibility.. Add method to StateInterrogation
interface boolean isLoaded(Instance, fieldName). TBD: Add
jdoIsLoaded(fieldName) to PersistenceCapable?
2. Eric asked whether JOD2 transaction types will mirror JPA;
specifically, do we add joinTransaction() to PersistenceManager?
Requires getting a reference to the transaction manager. If a user mixes
JDO and JPA transaction apis, throw JDOUserException. Need to consider
a number of scenarios. AI: Eric wll post a number of scenarios for
discussion.
3. Michael provided an update on the XML story. The fix for API20 test
checked in. It works now except when run from the top level directory.
AI: Michael will propose changes for naming and schema to experts.
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20 (done)
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Apr 20 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 20 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDOHelper.isLoaded proposal (JDO-483)
2. enlistment of native connections for optimistic txs -- further
discussion?
3. Other issues
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Apr 13 , 9 am PDT
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Erik Bengtson,Craig Russell
Agenda:
1. xsd issues Two things: update xsd schema file in order to make it
valid. Michael sent around an update that loosened the restrictions
on the placement of extension elements, meaning that the jdo
implementation needs to do more checking.
There seems to be consensus in the expert group that we should make
the change that Michael proposed. We also need to update the DTD with
the new version number. AI Michael send updated proposal and commit
changes.
2. Enlistment of native connections for optimistic txs: Comments were
received on the proposed new API getDataStoreConnection(boolean
enlist). AI Craig reply to message.
3. Other issues
It seems that we don't need to distinguish the PU by PUName, maybe we
should change this to Name property. AI Craig send a proposal to the
experts.
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Apr 13 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 13 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. xsd issues
2. Enlistment of native connections for optimistic txs
3. Other issues
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Apr 6 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, April 6 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Challenge of org.apache.jdo.tck.lifecycle.StateTransitionsReturnedObjects
2. xml library error on api20
3. Other issues
Action Items from weeks past:
[Mar 30 2007] AI Michael: Change xml test in api20
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 30 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michael Bouschen, Martin Zaun, Matthew Adams, Michelle
Caisse, Eric Bengtson
1. XSD
An xsd expert confirmed that our xsd files are not valid. A sequence of
elements where two are identical, as with <extension>, where the
intervening elements are all optional, is not permitted. We intend,
then, to use a choice for the elements, which will not impose an order,
but cannot express a limit on the maximum number of occurrences.
Therefore, JDO implementations must verify that certain elements are not
found more than once.
Michael will change xml test in api20 to test this case using the JDK5
xml schema parser, which would have caught this problem.
2. Named PMF proposal
Matthew is uploading a new patch which adds some new tests. He will
discuss some XML issues with Michael. The code is close to completion
and Matthew is waiting for feedback. The code has not been tested on
1.3 and would require separate download of JAXP to run.
-- Michelle
JDO TCK Conference Call Friday, Mar 30 , 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 30 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. XSD woes
2. Named PMF -- comments on JDO-467
3. Other issues
Action Items from weeks past:
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Mar 23,
9 am PDT [NOTE CHANGE TO DAYLIGHT SAVING TIME]
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 23 at 9 am PDT to discuss
JDO TCK issues and status.
NOTE: The U.S. has changed to Daylight Saving Time, while Europe remains
on Standard Time for another week, so the time of tomorrow's meeting
will be an hour earlier for some of you.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Other issues
Action Items from weeks past:
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Mar 9,
9 am PDT [NOTE CHANGE TO DAYLIGHT SAVING TIME]
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 16 at 9 am PDT to discuss
JDO TCK issues and status.
NOTE: The U.S. has changed to Daylight Saving Time, while Europe remains
on Standard Time for another two weeks, so the time of tomorrow's
meeting will be an hour earlier for some of you.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Delete by object id
2. Persistent properties for classes questions
3. Problem with JDO 2 xsd
4. Other issues
Action Items from weeks past:
[Mar 9 2007] AI Craig: Update the spec to require that the key of the
listener is the class name of the listener, for consistency with
proposed xml..
[Mar 9 2007] AI Michelle: Get rid of old beta and rc1 releases using
disk space on Apache.
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Mar 9, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 9 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Named PMF proposal
2. Delete by object id
3. Other issues
Action Items from weeks past:
[Mar 2 2007] AI: All review issue
http://issues.apache.org/jira/browse/JDO-467
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string
constant "META-INF/jdo.xml" and a new method
getPersistenceManagerFactory taking no arguments.
[Mar 2 2007] AI: Craig and Michelle - TOI on updating Sun web site for
JDO-379
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Mar 2, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Matthew Adams, Michael Bouschen, Martin Zaun, Michelle
Caisse, Craig Russell
Agenda:
1. Named PMF proposal. Good feedback on the proposal.
Why not just use JPA? Because we need other stuff that's JDO specific.
Why not support META-INF to find services? Good idea. See Erik's
proposal, which will end up in the spec.
Should there be another way to find metadata? Maybe not. We already
know how to find .jdo, .orm, and .jdoquery files.
Do we need to add a bunch of stuff to the JDOHelper and
PersistenceManagerFactory APIs? Just JDOHelper: a string constant
"META-INF/jdo.xml" and a new method getPersistenceManagerFactory
taking no arguments. AI Craig: update the JDOHelper class to include
the new constant and method.
AI: All review issue http://issues.apache.org/jira/browse/JDO-467
2. Other issues
Who is going to update the xsd on the Sun web site?
I propose Michelle. Mind meld will be scheduled with Craig.
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Mar 2, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, March 2 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Named PMF proposal
2. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Feb 23, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 23 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Persistent interface specification clarification
2. Forking codeline for JDK 1.5 support
3. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Feb 16, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 16 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. getPersistenceManagerProxy discussion
2. JDO-460 StateTransitions test - different transitions expected for
hollow vs. persistent nontransactional instance
3. Other issues
Action Items from weeks past:
[Feb 9 2006] AI Craig send Server TimeZone proposal to the expert group
for a vote.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Feb 9, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Martin Zaun, Erik Bengtson, Michael Bouschen, Matthew
Adams, Craig Russell
Agenda:
1. Server TimeZone: One issue is using multiple databases with a
single PMF. Which time is acquired? This will have to be configured
using some proprietary API. The time zone might not be known by the
application, so it might have to be configured in the PMF. AI Craig
send proposal to the expert group for a vote.
2. Other issues
Proxy proposal: Currently, JPOX supports JTA outside the Java EE
container via lightweight frameworks; does the proposal address this
use case? Yes. Any environment in which the implementation can get
access to the JTA transaction can support the proxy API. AI Craig put
to gether a proposal to be formally proposed to the expert group.
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 9, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 9 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Server TimeZone
2. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Feb 2, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Craig Russell
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO-378 SQL query : executeWithMap test. In the spirit of having
fun doing code reviews, we decided to review this patch during the
call. The new patch will reflect the results of the call.
http://video.google.com/videoplay?
docid=-8502904076440714866&q=mondrian+code+review
2. Other issues
none
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Feb 2, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, February 2 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO-378 SQL query : executeWithMap test
2. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Jan 26, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 26 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Proposal for Service Discovery
2. JDO2 Annotations
3. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Proposal for Service Discovery
Posted by Erik Bengtson <er...@jpox.org>.
> For OSGi containers, in addition to having the JDO jar compliant,
> some additional infrastructure is needed, for example the
> implementation jar should also contain a service definition for JDO.
> AI Erik write up proposal for the group.
>
Proposal for J2SE Service Discovery and OSGi Service Discovery for JDO
Provide transparent and less development time (in terms of pmf properties)
dependencies to JDO vendors, enabling runtime discovery.
J2SE Service Discovery
-------------------------------
The goal is provide more transparent replacement of implementation for
operations/deployment or easier bootstrap mechanism for creating JDO instances.
For awareness this proposal uses a similar mechanism to JPA.
An Use Case is an application deployed to production environment which uses JDO
implementation A and is not performing well. It was identified the problem was
within the JDO implementation A, and to fix the issue it was decided to replace
the implementation with a different vendor. The procedure consists in replacing
the JDO vendor jar in the classpath and update the PMF properties pointing to
the new vendor PMF class.
With a service discovery this procedure would be reduced down to replacing only
the JDO vendor jar.
To implement such thing we can use the standard jar specification.
How does it work for the jdo user :
As before, by using the JDOHelper.getPMF(properties). However there is no need
to set the property javax.jdo.PersistenceManagerFactoryClass if there is only
one JDO vendor jar in the classpath.
How does it work for the implementation :
In the JDO jar file, add the file
/META-INF/services/javax.jdo.PersistenceManagerFactory, and inside the
file set the fully qualified class name for the PMF implementation.
The JDOHelper.getPMF(properties) will do the service discovery, by using the
standard jar spec.
This service discovery is very likely to be used in J2SE environments.
See:
jar spec
jpa spec (for an example of this service)
OSGi Service Discovery for JDO
-------------------------------
The idea here is make better integration between JDO and OSGi, and the ultimate
goal is to provide an OSGi service that can instantiates JDO PMFs.
In OSGi containers, the service discovery uses similar concepts, but has
different implementations, plut the way classloaders are handled is much more
complex.
>From points 1 to 6 I expose the problems that occurs with OSGi development and
JDO.
1)
An OSGi application is usually split into several jars, something like:
mycomponent1.jar (OSGi bundle)
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle)
2)
Each OSGi bundle is loaded by a different classloader, java runtime classloader
is parent for the bundle classlaoders.
Each component can include libraries inside, for instance JDO. So:
mycomponent1.jar (OSGi bundle)
- jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle)
3)
For the moment only component1 uses the Persistent classes, but if mycomponent3
needs to read Company instances, you will
also need the Persistent classes + jdo.jar in the classpath. Then you decide to
duplicate the classes to both OSGi bundles
mycomponent1.jar (OSGi bundle)
- jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle)
- jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
4)
Easy?? No, actually it will fail with ClassCastException at runtime, since
Person of component1 is not castable
to Person of component3. Solution:
mycomponent1.jar (OSGi bundle) - depends on mydomainclasses.jar and jdo.jar OSGi
bundles
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle) - depends on mydomainclasses.jar and jdo.jar OSGi
bundles
jdo.jar (OSGi bundle)
- jdo.jar
mydomainclasses.jar (OSGi bundle) - depends on jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
So this fixes the issue of ClassCastException.
5)
Problem: Where to put the jdo vendor implementation?
Actually it can be put anywhere, unless you also want to share instances of the
JDO vendor classes at runtime between
OSGi bundles. The best choice is this:
mycomponent1.jar (OSGi bundle) - depends on mydomainclasses.jar, jdo.jar and
VENDOR_X.jar OSGi bundles
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle) - depends on mydomainclasses.jar, jdo.jar and
VENDOR_X.jar OSGi bundles
jdo.jar (OSGi bundle)
- jdo.jar
mydomainclasses.jar (OSGi bundle) - depends on jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
VENDOR_X.jar (OSGi bundle)
6)
Problem: How to remove the dependency to the JDO vendor jar at build time?
Have an OSGi Service that discovers the implementation in the OSGi container and
permits to create a PMF instance.
mycomponent1.jar (OSGi bundle) - depends on mydomainclasses.jar and jdo.jar OSGi
bundles
mycomponent2.jar (OSGi bundle)
mycomponent3.jar (OSGi bundle) - depends on mydomainclasses.jar and jdo.jar OSGi
bundles
jdo.jar (OSGi bundle) - provides Service JDOPMF
- jdo.jar
mydomainclasses.jar (OSGi bundle) - depends on jdo.jar
- Person.class (PersistenceCapable)
- Company.class (PersistenceCapable)
VENDOR_X.jar (OSGi bundle) - implements Service JDOPMF
See
osgi spec for more details on osgi services (osgi.org)
Finally, how is this service implemented in OSGi?
A sample will come soon. As soon as I have time to pack something, but I must
say the implementation is very stupid.
Minutes: JDO TCK Conference Call Friday, Jan 19, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Michelle Caisse, Erik
Bengtson, Martin Zaun, Craig Russell
Agenda:
1. Maven repo issues. The repo that contains the artifact for jta was
down all day yesterday. We will monitor the situation and take action
if it happens again.
2. State Transitions spec changes - https://issues.apache.org/jira/
browse/JDO-456 and https://issues.apache.org/jira/browse/JDO-460
track this issue. When detaching a hollow instance with an active
datastore transaction, the new specification requires that the
instance transition to persistent-clean. JPOX currently fails this test.
3. Other issues
For OSGi containers, in addition to having the JDO jar compliant,
some additional infrastructure is needed, for example the
implementation jar should also contain a service definition for JDO.
AI Erik write up proposal for the group.
There was an email posted to jdo-users regarding persistent
interfaces. Can anyone reply to it?
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink
support for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 19, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 19 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Maven repo issues
2. State Transitions spec changes - Comments?
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more work
in the annotation handler and doesn't provide for compile-time checking
of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 12, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Martin Zaun, Craig Russell
Agenda:
1. State transitions: Michelle updated the two tck tests with the
changes that were made to the specification. The changed tck tests
pass on the JPOX version in the dependencies (SNAPSHOT). Still need
updates for the spec for detached dirty and nontransactional dirty
life cycle changes. http://issues.apache.org/jira/browse/JDO-456
2. PersistenceCapable.jdoIsDetached There is a bug in the spec that
Andy Jefferson noticed. This will be fixed in the maintenance
release. http://issues.apache.org/jira/browse/JDO-459
3. Other issues
The maven repository is broken. A workaround for some of the
artifacts is available but not for all. AI: Craig complain bitterly
to Apache infrastructure about how every project using maven 1 got
the shaft.
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more
work in the annotation handler and doesn't provide for compile-time
checking of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink
support for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Jan 12, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 12 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. State transitions
2. PersistenceCapable.jdoIsDetached
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more work
in the annotation handler and doesn't provide for compile-time checking
of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Jan 5, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams, Craig
Russell, Martin Zaun
1. api2-legacy.jar
Michael hecked in updates for license headers. Craig is working on
non-JDK1.5 changes in API, close to finished. Then api2-legacy and
(maybe) tck2-legacy workspaces can be branched off and will continue to
work in a Java 1.3 or 1.4 environment.
2. Current DB time feature
This is still under discussion. Craig suggested adding a method to
PersistenceManager using a Calendar. How this would be implemented is
unclear. Feedback from experts is required on whether it is possible in
all cases to get timezone information from the server. Insufficient
feedback on the need for a query language syntax to handle dates. If
someone needs this feature they should provide some input for the
specification.
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more work
in the annotation handler and doesn't provide for compile-time checking
of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Jan 5, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, January 5 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. api2-legacy.jar
2. Current DB time feature
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int.
This allows "default" to be a valid value, but requires a bit more work
in the annotation handler and doesn't provide for compile-time checking
of the values.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Dec 22, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 22 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Moving forward with JDO maintenance release
2. Other issues
Action Items from weeks past:
[Dec 15 2006] AI Michelle ask Bill Shannon if fscontext and
providerutil will be available for automatic download from maven
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, Dec 15, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Michael Bouschen, Martin Zaun, Craig Russell
Agenda:
1. Moving forward with JDO maintenance release. Some progress has
been made on updating the specification. Tracking on the wiki page
http://wiki.apache.org/jdo/CurrentDevelopment
Focus now on the changes that need updated interfaces so we can give
JPOX advance notice of the change. Looking in particular at the Query
Chapter 14 and BNF.
2. Updates to license information. Michael has taken ownership of the
JIRA issue http://issues.apache.org/jira/browse/JDO-441
3. Other issues
The TCK still depends on fscontext and providerutil which must be
downloaded by the user. It would be nice if they were available to
maven directly. AI Michelle ask Bill Shannon if this might be possible.
What about JDK6? We can see if there are any issues with the release.
Don't expect any issues. Even our exposure to JDBC is minimal.
We plan to meet next week, December 22, and skip the following week,
December 29.
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, Dec 15, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 15 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Moving forward with JDO maintenance release
2. Updates to license information
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Dec 8, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 8 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Moving forward with JDO maintenance release
2. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Dec 1, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, December 1 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Moving forward with JDO maintenance release
2. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Nov 16, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 16 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Moving forward with JDO maintenance release
2. Follow-up on suggestion for new PMF setting javax.jdo.ClassLoader
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Nov 10, 9 am PST
Posted by Erik Bengtson <er...@jpox.org>.
> 2. Suggestion for new PMF setting javax.jdo.ClassLoader
>
> From Erik: When a JDBC driver is not loaded by the classloader ruled
> by JDO, there is no standard trick to make it work besides
> implementing the object factory (DriverManager is not designed for
> complex classpath). In JPOX, we have implemented a PMF setting where
> users can specify a ClassLoader for general use (it is the last one
> in search order). Do you think we could make this in the standard?
>
> javax.jdo.ClassLoader which takes a java.lang.ClassLoader as value.
>
> We assume that the intended use is for applications that specify the
> property javax.jdo.javax.jdo.option.ConnectionDriverName and
> class.forName on this property value results in class not found. So
> the jdbc driver is never registered with DriverManager.
>
This is the most common case I remember that needs to lookup to the user defined
classloader.
> Questions: Why doesn't the ContextClassLoader work?
Here is the scenario:
ClassLoader A loads libraries like JDBC drivers.
ClassLoader B loads persistent classes.
ClassLoader C loads persistent code. (delegates to B, C and D) (has a reference
to A)
ClassLoader D loads libraries like JDO.
ClassLoader E loads JPOX. (delegates to D)
ClassLoader F is used by GUI .
App starts with Thread 1 that uses classloader F, it switch to class loader C
(creates the pmf), but quickly falls back to F. After that, the current context
loader is F. The only workaround is giving the reference of A to the PMF when
created.
> usage in a managed environment?
No, this is not the main case. Here people should use the datasource provided by
the app servers
Minutes: JDO TCK Conference Call Friday, Nov 10, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig
Russell
Agenda:
1. Logistics for JDO maintenance release. Michael has proposed
splitting the api20 and tck20 projects into two: one for 1.5 and the
other for legacy (1.3). This will be the plan going forward unless
objections are raised on the jdo-dev alias. We should probably do the
split after most of the common work has been done. Craig has already
renamed the JIRA categories to correspond to the new project names.
2. Suggestion for new PMF setting javax.jdo.ClassLoader
From Erik: When a JDBC driver is not loaded by the classloader ruled
by JDO, there is no standard trick to make it work besides
implementing the object factory (DriverManager is not designed for
complex classpath). In JPOX, we have implemented a PMF setting where
users can specify a ClassLoader for general use (it is the last one
in search order). Do you think we could make this in the standard?
javax.jdo.ClassLoader which takes a java.lang.ClassLoader as value.
We assume that the intended use is for applications that specify the
property javax.jdo.javax.jdo.option.ConnectionDriverName and
class.forName on this property value results in class not found. So
the jdbc driver is never registered with DriverManager.
Questions: Why doesn't the ContextClassLoader work? Is the intended
usage in a managed environment? This method would need to be
protected via a security permission, e.g. a JDOPermission
("configurePersistenceManagerFactory") or a standard permission.
3. JDOHelper.getVersion(Object): Behaviour of jdo versioning. It
seems that this is an underspecified part of the specification, as
Marco points out.
Questions: For unmodified objects, should this always return an equal
instance? For modified objects, should getVersion force a flush? If a
flush has already happened, should a new Version always return a not-
equal instance (compared to the Version at the beginning of the
transaction)? If executed outside a transaction, is there any
required behavior?
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, Nov 10, 9 am PST
Posted by Erik Bengtson <er...@jpox.org>.
> 2. Suggestion for new PMF setting javax.jdo.ClassLoader
Sorry, I forgot my mobile at home and wont be able to join the meeting today.
Hopefully, the requirements I described were clear enough for discussion...
JDO TCK Conference Call Friday, Nov 10, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 10 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Logistics for JDO maintenance release
2. Suggestion for new PMF setting javax.jdo.ClassLoader
3. JDOHelper.getVersion(Object): Behaviour of jdo versioning
4. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, Nov 2, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, November 2 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Date arithmetic in queries
2. New subprojects for JDK 1.5 support
3. Other issues
Action Items from weeks past:
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split
between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate
different defaults for annotations (?) based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Oct 27, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 23 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO 2.1 maintenance release: current DB time
2. JDO annotations - split between JDO and ORM
3. Other issues
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context. In progress.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for
Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, Oct 13, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 13 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Test challenge status
2. Proposal for new method
3. Proposal for alignment with JPA
4. Other issues
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases. Done. No one opposed it;
Ilan Kirsch liked it. No one volunteered to help with the work.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context. In progress.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review. In progress. Wes Biggs proposed a new
API that allows both single-string and API versions of subqueries that
looks good.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
JDO TCK Conference Call Friday, Oct 6, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, October 6 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Test challenge issues and status
2. Reflection based implementations
3. JDOQL subquery proposal
4. Other issues
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, September 29, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Martin Zaun
1. JDOQL subqueries
Discussion on jdo-dev is converging on a proposal. Michael will
summarize in a new email.
2. Handling test challenges
A number of email challenges have come to the jdo-dev alias. Michael
has created a wiki page summarizing the challenges
http://wiki.apache.org/jdo/TCKChallenges and the team is currently
evaluating them. We need to determine how and when to provide a patch
for sustained challenges. There are questions on some of the challenges
with respect to class names and JIRA issues mentioned. Michael will
send an email asking for clarification on the wiki with respect to
challenges submitted.
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, September 29, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 29 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDOQL subqueries
2. Handling test challenges
3. Other issues
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, September 22, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 15 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDOQL subqueries
2. Other issues
Action Items from weeks past:
[Sep 15 2006] AI Craig discuss a request for enhancement of the TCK to
permit reflective implementations on aliases.
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, September 15, 9 am PDT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 15 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Relationships mapped with mapped-by
2. JDO annotations
3. JDOQL subqueries
4. Other issues
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio
(JDO-406). (In progress)
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, September 8, 9 am PT
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 8 at 9 am PT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Relationships mapped with mapped-by
2. JDO annotations
3. JDOQL subqueries
4. Other issues
Action Items from weeks past:
[Sep 1 2006] AI Matthew: look into a cleaner separation for object model
vs. mapping annotations. AI Craig check into default handling to
accommodate different defaults based on context.
[Sep 1 2006] AI Michael and Craig: propose spec updates for JDOQL
subqueries for community review.
[Sep 1 2006] AI Michelle update download page to refer to ibiblio (JDO-406).
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Re: JDO TCK Conference Call Friday, September 1, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Erik
Bangston, Martin Zaun, Craig Russell
Agenda:
1. JDO annotations.
Matthew comments that some of the object model annotations include
references to mapping annotations. He'd like to see more isolation of
the two models. AI Matthew: look into a cleaner separation. AI Craig
check into default handling to accommodate different defaults based
on context.
2. JDOQL subqueries. The document that Michael sent out seems to be
agreeable. AI Michael and Craig: propose spec updates for community
review.
3. Apache JDO downloads no longer at http://www.apache.org/dyn/
closer.cgi/java-repository/javax.jdo/jars. AI Michelle update
download page to refer to ibiblio (JDO-406).
4. Maven 2 repo for JDO 2 is wrong. The POM was created by Apache
infrastructure and refers to incorrect dependent jar version numbers.
AI Matthew file a JDO JIRA and fix it.
This just in. Vanatec GMBH has started a project to take Versant
OpenAccess and convert it to C# in .NET.
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user
tries to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning
a copy. Approved.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached
to JDO-403 as a straw proposal for JDO2 annotations..
[Jul 21 2006] Deletion of objects when foreign-key is present
(JDO-392) Craig thinks that we need to add metadata to specify the
behavior of the JDO implementation. AI: Craig propose wording and new
metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept. In progress.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: JDO TCK Conference Call Friday, September 1, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, September 1 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO annotations
2. JDOQL subqueries
3. Apache JDO downloads no longer at
http://www.apache.org/dyn/closer.cgi/java-repository/javax.jdo/jars (JDO
406)
4. Other issues
Action Items from weeks past:
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries
to add to a list where the ordering element is incorrect.
[Aug 4 2006] AI everyone: review Michael's proposal for subqueries in
JDOQL in an email dated 26-Jul 2:41 PM PDT Subject Re: JDOQL Subquery
proposals and provide feedback.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached to
JDO-403 as a straw proposal for JDO2 annotations..
[Jul 21 2006] Deletion of objects when foreign-key is present (JDO-392)
Craig thinks that we need to add metadata to specify the behavior of the
JDO implementation. AI: Craig propose wording and new metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, August 11, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 11 at 9 am PST to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO annotations proposal
2. JDOQL subqueries proposal
3. Apache JDO downloads no longer at
http://www.apache.org/dyn/closer.cgi/java-repository/javax.jdo/jars
4. Other issues
Action Items from weeks past:
[Aug 4 2006] AI everyone: review Michael's proposal for subqueries in
JDOQL in an email dated 26-Jul 2:41 PM PDT Subject Re: JDOQL Subquery
proposals and provide feedback.
[Aug 4 2006] AI: Craig call for a negative vote to approve returning a
copy.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached to
JDO-403 as a straw proposal for JDO2 annotations..
[Jul 21 2006] Deletion of objects when foreign-key is present (JDO-392)
Craig thinks that we need to add metadata to specify the behavior of the
JDO implementation. AI: Craig propose wording and new metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, August 4, 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michael Bouschen, Matthew Adams, Erik Bengtson, Craig Russell
Agenda:
1. Subqueries in JDOQL. Michael has summarized the current proposal
in an email dated 26-Jul 2:41 PM PDT Subject Re: JDOQL Subquery
proposals. The proposal includes several example queries. AI
everyone: review and provide feedback.
2. [VOTE]: Should FetchPlan.getGroups return a copy or a reference?
There were only three votes. Two in favor of returning a copy; one in
favor of returning a reference. AI: Craig call for a negative vote to
approve returning a copy.
3. JDO2 Annotations: AI everyone review what Andy has documented as
a straw proposal. While it is not close to final, it is a good basis
for discussion.
4 Other issues
Michael provided a patch for JDO-394, which needs review. AI Craig:
review the patch.
Action Items from weeks past:
[Jul 28 2006] AI Craig: Proceed with detailed planning for JDO2
Annotations.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached
to JDO-403.
[Jul 21 2006] Deletion of objects when foreign-key is present
(JDO-392) Craig thinks that we need to add metadata to specify the
behavior of the JDO implementation. AI: Craig propose wording and new
metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, August 4, 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, August 3 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Subqueries in JDOQL
2. [VOTE]: Should FetchPlan.getGroups return a copy or a reference?
3. JDO2 Annotations: next steps?
4 Other issues
Action Items from weeks past:
[Jul 28 2006] AI Craig: Proceed with detailed planning for JDO2
Annotations.
[Jul 28 2006] AI all: review the JPOX .jar file of sources attached to
JDO-403.
[Jul 21 2006] Deletion of objects when foreign-key is present (JDO-392)
Craig thinks that we need to add metadata to specify the behavior of the
JDO implementation. AI: Craig propose wording and new metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, July 28 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Attendees: Michelle Caisse, Martin Zaun, Michael Bouschen, Matthew Adams
1. Subqueries in JDOQL - response to Michael's analysis (Re: JDOQL
Subquery proposals, 7/26/2006)
No issues seen with Michael's proposal. Allowing more time for response
from the community.
2. JDO2 Annotations - further comments?
Matthew responded to Martin's suggestion to put all annotations in one
package. He explained that non-relational vendors don't want relational
mappings in the same namespace as the logical annotations. AI Craig:
Proceed with detailed planning for JDO2 Annotations. AI all: review the
JPOX .jar file of sources attached to JDO-403.
3. Clarification : sequences and catalog/schema - response to Andy's
question
No answer from the attendees on this. Currently explicitly using
schema/catalog.sequence is probably the only answer.
Action Items from weeks past:
[Jul 21 2006] Deletion of objects when foreign-key is present (JDO-392)
Craig thinks that we need to add metadata to specify the behavior of the
JDO implementation. AI: Craig propose wording and new metadata.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types. In progress
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5
issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo. AI:
Craig write a ServerSide article. .
JDO TCK Conference Call Friday, July 28 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 28 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Subqueries in JDOQL - response to Michael's analysis
2. JDO2 Annotations - further comments?
3. Clarification : sequences and catalog/schema - response to Andy's
question
4 Other issues
Action Items from weeks past:
[Jul 21 2006] Deletion of objects when foreign-key is present (JDO-392)
Craig thinks that we need to add metadata to specify the behavior of the
JDO implementation. AI Craig propose wording and new metadata.
[Jul 14 2006] AI: everyone respond to the annotations discussion on the
expert group alias.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 30 2006] Craig sent around some more example queries. AI:
Michael will propose a JDOQL query that will handle them. AI: Matthew
will send follow-up email on his proposal.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts,
logo. AI: Craig write a ServerSide article. .
-- Michelle
Re: JDO TCK Conference Call Friday, July 21 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Martin
Zaun, Craig Russell
Hi,
Agenda:
1. Locale instances are shared by different PMs (when in use as FCO)
(JDO-397) (Craig)
The spec says that portable applications must not depend on whether
String, Locale, etc. are treated as FCO or SCO. But this was not
meant to impose the requirement that field instances must be cloned.
The spec needs to be updated. AI Craig respond to the issue. AI
others pile on with opinions.
2. Deletion of objects when foreign-key is present (JDO-392) (Craig,
others) Craig thinks that we need to add metadata to specify the
behavior of the JDO implementation. We need to be careful not to
confuse the delete-action metadata with this new specification. AI
Craig propose wording and new metadata.
3. Subqueries in JDOQL (any and all) AI Michael summarize the current
proposal.
4 JDO2 Annotations: 1, 2, or 3 (any and all) The latest proposal is
a refinement to put object model annotations into their own name
space and orm annotations into their own name space. e.g.
javax.jdo.annotations.jdo and javax.jdo.annotations.orm.
Action Items from weeks past:
[Jul 14 2006] AI: everyone respond to the annotations discussion on
the expert group alias.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 30 2006] Craig sent around some more example queries. AI:
Michael will propose a JDOQL query that will handle them. AI:
Matthew will send follow-up email on his proposal.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts,
logo. AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 21 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 21 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Locale instances are shared by different PMs (when in use as FCO)
(JDO-397) (Craig)
2. Deletion of objects when foreign-key is present (JDO-392) (Craig,
others)
3. Subqueries in JDOQL (any and all)
4 JDO2 Annotations: 1, 2, or 3 (any and all)
5. Other issues (any and all)
Action Items from weeks past:
[Jul 14 2006] AI: everyone respond to the annotations discussion on the
expert group alias.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a
corresponding JDO concept.
[Jul 14 2006] AI Craig write up the proposal for deletion of objects
when foreign-key is present (JDO-392)
[Jul 14 2006] AI Erik write up JPOX behavior for deletion of objects
when foreign-key is present .
[Jun 30 2006] Craig sent around some more example queries. AI:
Michael will propose a JDOQL query that will handle them. AI: Matthew
will send follow-up email on his proposal.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Bin Sun <su...@yahoo.com>.
--- Jörg von Frantzius
<jo...@artnology.com> wrote:
> To me this means losing an important data security
> feature when using
> JDO over other access paths to the DB. FK
> constraints can prevent you
> from inadvertently deleting data, and by silently
> removing any dangling
> references on the object level (and so circumventing
> any FK constraints)
> you are entirely losing this kind of "safety belt"!
> JDO would never tell
> you about these dangling references, but instead
> would silently go and
> delete that information.
>
I strongly agree on this point. This may not be a JDO
responsibility, but it's very important.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Michael Watzek <mw...@spree.de>.
Hi Craig, Joerg,
I agree that FK constraints are an important and powerful feature of
relational databases. They provide for referential integrity, and, as a
side effect, prevent people/applications from deleting rows unless FKs
are nullified first.
My impression is that below you are talking of different delete
semantics in the object domain:
1) Deleting an object means that all references to that object are
nullify implicitly.
2) Deleting an object is only successful if there are no references to
that object.
I think it would make sense to support both semantics in JDO.
Regards,
Michael
Jörg von Frantzius wrote:
> Hi Craig,
>
> Craig L Russell schrieb:
>> Hi Jörg,
>>
>> On Jul 17, 2006, at 10:27 AM, Jörg von Frantzius wrote:
>>
>>> Craig L Russell schrieb:
>>>>> If that's the case, then I wonder why a user would want to have FK
>>>>> constraints in his schema at all? They wouldn't be of much use then.
>>>> If only using JDO, I agree. What matters is the consistency of the
>>>> object model, which is managed by the JDO implementation without
>>>> help from the database. But seldom is JDO the only access path to
>>>> the database.
>>> To me this means losing an important data security feature when using
>>> JDO over other access paths to the DB. FK constraints can prevent you
>>> from inadvertently deleting data, and by silently removing any
>>> dangling references on the object level (and so circumventing any FK
>>> constraints) you are entirely losing this kind of "safety belt"! JDO
>>> would never tell you about these dangling references, but instead
>>> would silently go and delete that information.
>> I'm not sure I understand your concern. Is it ok for the application
>> to explicitly nullify references to instances that it deletes? It's
>> not clear to me how a nullable database constraint improves the
>> reliability of your user's code.
> Yes exactly, I find it good if the application programmer must
> explicitly nullify any references before deleting. That way he'll know
> what relationships exactly he is going to remove the object from. If it
> happens transparently and without notice, he might not realize the
> consequences. I find it adequate that code for deleting objects must be
> written with care.
>
> So in my opinion, and from my experience, FK constraints help to prevent
> programming mistakes from creating serious data loss.
>> On the other hand, if it is a requirement of the object model that
>> there must be a non-null reference to an instance, then would a
>> not-null foreign key satisfy the requirement? In this case, JPOX's
>> automatic nullification of the reference would cause a (null)
>> constraint violation. Or JPOX would throw an exception if it knew
>> about the not-null constraint. Or defer the delete until commit, by
>> which time the other side would have to have been set to a valid
>> not-deleted instance. And the application would have to be careful to
>> set the other side of the relationship.
> That's interesting, but I wasn't thinking about FKs with an additional
> NOT-NULL constraint here. I was thinking of simply not allowing the
> deletion to happen at all, as it turned out to our own surprise, please
> see below.
>> As you know, there are no TCK tests for these cases. I'd like to
>> formalize the specification and add some tests once we all agree on
>> the semantics.
>>> As I wrote in an earlier mail, we had a case here where we were
>>> really lucky that the FK constraint would fire upon deletion, because
>>> we didn't think of all the relationships that an object would be
>>> removed from, and for which we really didn't want to lose the
>>> information. That was for users that are logged as creators and
>>> modifiers of other objects: if you can delete a user, you'll lose the
>>> information about who created or edited an object, something that
>>> would have gone lost silently forever if it wasn't for the FK
>>> constraints firing.
>> So is it the case that explicitly nullifying the relationship is
>> illegal for the user? I'm trying to picture the security domain model
>> where a user is authorized to delete from a table but is not
>> authorized to set the column of a related table to null. How is this
>> supposed to work?
> What I meant to say is that the "delete user" functionality of the
> application turned out to not having been thought out well enough. It
> was only when an end-user clicked the "delete"-button on another user
> that had already created or modified other objects, that we realized we
> don't want to allow a deletion in this case at all. And we realized it
> only because luckily an SQLException was thrown due to the constraint
> violation.
>
> In this case, it would have been a serious mistake if the programmer had
> nullified the relationships explicitly, but in doing so he is forced to
> think twice about it, hopefully, and you can't prevent people from
> creating damage on purpose ;)
>>
>>>>> I may also add that, as far as I know, JPOX nulls out only for
>>>>> one-one bidirectional, not for one-many, so there would be some
>>>>> inconsistency of behaviour here.
>>>> Interesting point, but without another level of detail, it's hard to
>>>> evaluate this statement.
>>> If you look at the code in DeleteRequest, you'll see that in
>>> execute() it'll null out FKs for any fields obained using
>>> getFildsWithRelatedObjects(). The latter's javadoc says
>>>
>>> /**
>>> * All fields that have related objects and where we use the
>>> related object to
>>> * maintain a relationship. These are used where we have 1-1
>>> bidirectional
>>> * relationships with a single FK (in the other object).
>>> * @return The fields with related objects
>>> */
>>> public FieldMetaData[] getFieldsWithRelatedObjects()
>>>
>>> That's the case for 1-1 relationships with "mapped-by" on the side
>>> where the object is deleted. From what I saw in my tests, that's
>>> where the nulling out happens, and it doesn't happen for one-many
>>> relationships with "mapped-by", so you'll see FK constraints
>>> violations there.
>>
>> For one-many relationships there is no additional foreign key. Take
>> the case of deleting an Employee for which there is a
>> Department-Employee relationship. There is no explicit database action
>> needed when deleting the Employee because there is no explicit
>> reference from the DEPARTMENT table to the key values in the EMPLOYEE
>> table. The primary key in EMPLOYEE defines the relationship.
> What I was thinking of would in this example be a deletion of a
> Department that has Employees. I had understood you that you want to
> transparently have the Employees be removed from the Department when it
> is deleted. Currently JPOX doesn't do that, and an FK violation occurs.
>
> Let's take this a step further. Let's assume that Department has an
> "employees" Collection field annotated with "mapped-by". That means we
> have two Java object references that are represented by one FK on the
> database level. From an object-oriented perspective, I shouldn't need to
> know that there is only a single FK, and where it is exactly. However, I
> can delete an Employee without further action, while I cannot delete a
> Department without further action. There is an asymmetry here that is
> rooted in the relational nature of the database, and, for the sake of
> transparency, it should be hidden. For the sake of data security, I'd
> prefer to hide the asymmetry by throwing exceptions in both cases
>
> So I'd even say that it should not be possible to delete an Employee
> before removing it from its Department's employees collection, because
> there won't be any FK violation notifying of the dangling object
> reference. However, if you find that a little over the top, I won't
> insist too long as our code generator already causes exceptions to be
> thrown in these cases...
>> Regards,
>>
>> Craig
>>
>>>>
>>>> Regards,
>>>>
>>>> Craig
>>>>>
>>>>> Regards,
>>>>> Jörg
>>>>>
>>>>> Craig L Russell schrieb:
>>>>>>
>>>>>> 2. Deletion of objects when foreign-key is present (JDO-392) (any
>>>>>> and all) It seems that there are two different issues: managing
>>>>>> the memory model and managing the database. Craig opines that the
>>>>>> general case of consistency is already covered in the chapter on
>>>>>> mapping, requiring that the object model be consistent after a
>>>>>> flush. Object model consistency would disallow a reference to a
>>>>>> deleted object, so the natural behavior would be to nullify the
>>>>>> reference to the deleted object. For to-many relationships mapped
>>>>>> to a foreign key on the other side, the consistency rule would
>>>>>> delete the reference from the collection on the one- side of the
>>>>>> relationship. So it seems that the JPOX behavior as originally
>>>>>> reported is consistent and we might simply document it in the
>>>>>> specification.
>>>>> Why does object model consistency disallow a reference to a deleted
>>>>> object?
>>>>> <joerg.von.frantzius.vcf>
>>>>
>>>> Craig Russell
>>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>>>>
>>>
>>> <joerg.von.frantzius.vcf>
>>
>> Craig Russell
>>
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>
>> 408 276-5638 mailto:Craig.Russell@sun.com
>>
>> P.S. A good JDO? O, Gasp!
>>
>>
>
--
-------------------------------------------------------------------
Michael Watzek Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
-------------------------------------------------------------------
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Jörg von Frantzius <jo...@artnology.com>.
Hi Craig,
Craig L Russell schrieb:
> Hi Jörg,
>
> On Jul 17, 2006, at 10:27 AM, Jörg von Frantzius wrote:
>
>> Craig L Russell schrieb:
>>>> If that's the case, then I wonder why a user would want to have FK
>>>> constraints in his schema at all? They wouldn't be of much use then.
>>> If only using JDO, I agree. What matters is the consistency of the
>>> object model, which is managed by the JDO implementation without
>>> help from the database. But seldom is JDO the only access path to
>>> the database.
>> To me this means losing an important data security feature when using
>> JDO over other access paths to the DB. FK constraints can prevent you
>> from inadvertently deleting data, and by silently removing any
>> dangling references on the object level (and so circumventing any FK
>> constraints) you are entirely losing this kind of "safety belt"! JDO
>> would never tell you about these dangling references, but instead
>> would silently go and delete that information.
> I'm not sure I understand your concern. Is it ok for the application
> to explicitly nullify references to instances that it deletes? It's
> not clear to me how a nullable database constraint improves the
> reliability of your user's code.
Yes exactly, I find it good if the application programmer must
explicitly nullify any references before deleting. That way he'll know
what relationships exactly he is going to remove the object from. If it
happens transparently and without notice, he might not realize the
consequences. I find it adequate that code for deleting objects must be
written with care.
So in my opinion, and from my experience, FK constraints help to prevent
programming mistakes from creating serious data loss.
> On the other hand, if it is a requirement of the object model that
> there must be a non-null reference to an instance, then would a
> not-null foreign key satisfy the requirement? In this case, JPOX's
> automatic nullification of the reference would cause a (null)
> constraint violation. Or JPOX would throw an exception if it knew
> about the not-null constraint. Or defer the delete until commit, by
> which time the other side would have to have been set to a valid
> not-deleted instance. And the application would have to be careful to
> set the other side of the relationship.
That's interesting, but I wasn't thinking about FKs with an additional
NOT-NULL constraint here. I was thinking of simply not allowing the
deletion to happen at all, as it turned out to our own surprise, please
see below.
> As you know, there are no TCK tests for these cases. I'd like to
> formalize the specification and add some tests once we all agree on
> the semantics.
>> As I wrote in an earlier mail, we had a case here where we were
>> really lucky that the FK constraint would fire upon deletion, because
>> we didn't think of all the relationships that an object would be
>> removed from, and for which we really didn't want to lose the
>> information. That was for users that are logged as creators and
>> modifiers of other objects: if you can delete a user, you'll lose the
>> information about who created or edited an object, something that
>> would have gone lost silently forever if it wasn't for the FK
>> constraints firing.
> So is it the case that explicitly nullifying the relationship is
> illegal for the user? I'm trying to picture the security domain model
> where a user is authorized to delete from a table but is not
> authorized to set the column of a related table to null. How is this
> supposed to work?
What I meant to say is that the "delete user" functionality of the
application turned out to not having been thought out well enough. It
was only when an end-user clicked the "delete"-button on another user
that had already created or modified other objects, that we realized we
don't want to allow a deletion in this case at all. And we realized it
only because luckily an SQLException was thrown due to the constraint
violation.
In this case, it would have been a serious mistake if the programmer had
nullified the relationships explicitly, but in doing so he is forced to
think twice about it, hopefully, and you can't prevent people from
creating damage on purpose ;)
>
>>>> I may also add that, as far as I know, JPOX nulls out only for
>>>> one-one bidirectional, not for one-many, so there would be some
>>>> inconsistency of behaviour here.
>>> Interesting point, but without another level of detail, it's hard to
>>> evaluate this statement.
>> If you look at the code in DeleteRequest, you'll see that in
>> execute() it'll null out FKs for any fields obained using
>> getFildsWithRelatedObjects(). The latter's javadoc says
>>
>> /**
>> * All fields that have related objects and where we use the
>> related object to
>> * maintain a relationship. These are used where we have 1-1
>> bidirectional
>> * relationships with a single FK (in the other object).
>> * @return The fields with related objects
>> */
>> public FieldMetaData[] getFieldsWithRelatedObjects()
>>
>> That's the case for 1-1 relationships with "mapped-by" on the side
>> where the object is deleted. From what I saw in my tests, that's
>> where the nulling out happens, and it doesn't happen for one-many
>> relationships with "mapped-by", so you'll see FK constraints
>> violations there.
>
> For one-many relationships there is no additional foreign key. Take
> the case of deleting an Employee for which there is a
> Department-Employee relationship. There is no explicit database action
> needed when deleting the Employee because there is no explicit
> reference from the DEPARTMENT table to the key values in the EMPLOYEE
> table. The primary key in EMPLOYEE defines the relationship.
What I was thinking of would in this example be a deletion of a
Department that has Employees. I had understood you that you want to
transparently have the Employees be removed from the Department when it
is deleted. Currently JPOX doesn't do that, and an FK violation occurs.
Let's take this a step further. Let's assume that Department has an
"employees" Collection field annotated with "mapped-by". That means we
have two Java object references that are represented by one FK on the
database level. From an object-oriented perspective, I shouldn't need to
know that there is only a single FK, and where it is exactly. However, I
can delete an Employee without further action, while I cannot delete a
Department without further action. There is an asymmetry here that is
rooted in the relational nature of the database, and, for the sake of
transparency, it should be hidden. For the sake of data security, I'd
prefer to hide the asymmetry by throwing exceptions in both cases
So I'd even say that it should not be possible to delete an Employee
before removing it from its Department's employees collection, because
there won't be any FK violation notifying of the dangling object
reference. However, if you find that a little over the top, I won't
insist too long as our code generator already causes exceptions to be
thrown in these cases...
> Regards,
>
> Craig
>
>>>
>>> Regards,
>>>
>>> Craig
>>>>
>>>> Regards,
>>>> Jörg
>>>>
>>>> Craig L Russell schrieb:
>>>>>
>>>>> 2. Deletion of objects when foreign-key is present (JDO-392) (any
>>>>> and all) It seems that there are two different issues: managing
>>>>> the memory model and managing the database. Craig opines that the
>>>>> general case of consistency is already covered in the chapter on
>>>>> mapping, requiring that the object model be consistent after a
>>>>> flush. Object model consistency would disallow a reference to a
>>>>> deleted object, so the natural behavior would be to nullify the
>>>>> reference to the deleted object. For to-many relationships mapped
>>>>> to a foreign key on the other side, the consistency rule would
>>>>> delete the reference from the collection on the one- side of the
>>>>> relationship. So it seems that the JPOX behavior as originally
>>>>> reported is consistent and we might simply document it in the
>>>>> specification.
>>>> Why does object model consistency disallow a reference to a deleted
>>>> object?
>>>> <joerg.von.frantzius.vcf>
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> <joerg.von.frantzius.vcf>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Jörg,
On Jul 17, 2006, at 10:27 AM, Jörg von Frantzius wrote:
> Craig L Russell schrieb:
>>> If that's the case, then I wonder why a user would want to have
>>> FK constraints in his schema at all? They wouldn't be of much use
>>> then.
>> If only using JDO, I agree. What matters is the consistency of the
>> object model, which is managed by the JDO implementation without
>> help from the database. But seldom is JDO the only access path to
>> the database.
> To me this means losing an important data security feature when
> using JDO over other access paths to the DB. FK constraints can
> prevent you from inadvertently deleting data, and by silently
> removing any dangling references on the object level (and so
> circumventing any FK constraints) you are entirely losing this kind
> of "safety belt"! JDO would never tell you about these dangling
> references, but instead would silently go and delete that information.
I'm not sure I understand your concern. Is it ok for the application
to explicitly nullify references to instances that it deletes? It's
not clear to me how a nullable database constraint improves the
reliability of your user's code.
On the other hand, if it is a requirement of the object model that
there must be a non-null reference to an instance, then would a not-
null foreign key satisfy the requirement? In this case, JPOX's
automatic nullification of the reference would cause a (null)
constraint violation. Or JPOX would throw an exception if it knew
about the not-null constraint. Or defer the delete until commit, by
which time the other side would have to have been set to a valid not-
deleted instance. And the application would have to be careful to set
the other side of the relationship.
As you know, there are no TCK tests for these cases. I'd like to
formalize the specification and add some tests once we all agree on
the semantics.
>
> As I wrote in an earlier mail, we had a case here where we were
> really lucky that the FK constraint would fire upon deletion,
> because we didn't think of all the relationships that an object
> would be removed from, and for which we really didn't want to lose
> the information. That was for users that are logged as creators and
> modifiers of other objects: if you can delete a user, you'll lose
> the information about who created or edited an object, something
> that would have gone lost silently forever if it wasn't for the FK
> constraints firing.
So is it the case that explicitly nullifying the relationship is
illegal for the user? I'm trying to picture the security domain model
where a user is authorized to delete from a table but is not
authorized to set the column of a related table to null. How is this
supposed to work?
>>> I may also add that, as far as I know, JPOX nulls out only for
>>> one-one bidirectional, not for one-many, so there would be some
>>> inconsistency of behaviour here.
>> Interesting point, but without another level of detail, it's hard
>> to evaluate this statement.
> If you look at the code in DeleteRequest, you'll see that in execute
> () it'll null out FKs for any fields obained using
> getFildsWithRelatedObjects(). The latter's javadoc says
>
> /**
> * All fields that have related objects and where we use
> the related object to
> * maintain a relationship. These are used where we have
> 1-1 bidirectional
> * relationships with a single FK (in the other object).
> * @return The fields with related objects
> */
> public FieldMetaData[] getFieldsWithRelatedObjects()
>
> That's the case for 1-1 relationships with "mapped-by" on the side
> where the object is deleted. From what I saw in my tests, that's
> where the nulling out happens, and it doesn't happen for one-many
> relationships with "mapped-by", so you'll see FK constraints
> violations there.
For one-many relationships there is no additional foreign key. Take
the case of deleting an Employee for which there is a Department-
Employee relationship. There is no explicit database action needed
when deleting the Employee because there is no explicit reference
from the DEPARTMENT table to the key values in the EMPLOYEE table.
The primary key in EMPLOYEE defines the relationship.
Regards,
Craig
>>
>> Regards,
>>
>> Craig
>>>
>>> Regards,
>>> Jörg
>>>
>>> Craig L Russell schrieb:
>>>>
>>>> 2. Deletion of objects when foreign-key is present (JDO-392)
>>>> (any and all) It seems that there are two different issues:
>>>> managing the memory model and managing the database. Craig
>>>> opines that the general case of consistency is already covered
>>>> in the chapter on mapping, requiring that the object model be
>>>> consistent after a flush. Object model consistency would
>>>> disallow a reference to a deleted object, so the natural
>>>> behavior would be to nullify the reference to the deleted
>>>> object. For to-many relationships mapped to a foreign key on the
>>>> other side, the consistency rule would delete the reference from
>>>> the collection on the one- side of the relationship. So it seems
>>>> that the JPOX behavior as originally reported is consistent and
>>>> we might simply document it in the specification.
>>> Why does object model consistency disallow a reference to a
>>> deleted object?
>>> <joerg.von.frantzius.vcf>
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> <joerg.von.frantzius.vcf>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Jörg von Frantzius <jo...@artnology.com>.
Craig L Russell schrieb:
>> If that's the case, then I wonder why a user would want to have FK
>> constraints in his schema at all? They wouldn't be of much use then.
> If only using JDO, I agree. What matters is the consistency of the
> object model, which is managed by the JDO implementation without help
> from the database. But seldom is JDO the only access path to the database.
To me this means losing an important data security feature when using
JDO over other access paths to the DB. FK constraints can prevent you
from inadvertently deleting data, and by silently removing any dangling
references on the object level (and so circumventing any FK constraints)
you are entirely losing this kind of "safety belt"! JDO would never tell
you about these dangling references, but instead would silently go and
delete that information.
As I wrote in an earlier mail, we had a case here where we were really
lucky that the FK constraint would fire upon deletion, because we didn't
think of all the relationships that an object would be removed from, and
for which we really didn't want to lose the information. That was for
users that are logged as creators and modifiers of other objects: if you
can delete a user, you'll lose the information about who created or
edited an object, something that would have gone lost silently forever
if it wasn't for the FK constraints firing.
>> I may also add that, as far as I know, JPOX nulls out only for
>> one-one bidirectional, not for one-many, so there would be some
>> inconsistency of behaviour here.
> Interesting point, but without another level of detail, it's hard to
> evaluate this statement.
If you look at the code in DeleteRequest, you'll see that in execute()
it'll null out FKs for any fields obained using
getFildsWithRelatedObjects(). The latter's javadoc says
/**
* All fields that have related objects and where we use the
related object to
* maintain a relationship. These are used where we have 1-1
bidirectional
* relationships with a single FK (in the other object).
* @return The fields with related objects
*/
public FieldMetaData[] getFieldsWithRelatedObjects()
That's the case for 1-1 relationships with "mapped-by" on the side where
the object is deleted. From what I saw in my tests, that's where the
nulling out happens, and it doesn't happen for one-many relationships
with "mapped-by", so you'll see FK constraints violations there.
>
> Regards,
>
> Craig
>>
>> Regards,
>> Jörg
>>
>> Craig L Russell schrieb:
>>>
>>> 2. Deletion of objects when foreign-key is present (JDO-392) (any
>>> and all) It seems that there are two different issues: managing the
>>> memory model and managing the database. Craig opines that the
>>> general case of consistency is already covered in the chapter on
>>> mapping, requiring that the object model be consistent after a
>>> flush. Object model consistency would disallow a reference to a
>>> deleted object, so the natural behavior would be to nullify the
>>> reference to the deleted object. For to-many relationships mapped to
>>> a foreign key on the other side, the consistency rule would delete
>>> the reference from the collection on the one- side of the
>>> relationship. So it seems that the JPOX behavior as originally
>>> reported is consistent and we might simply document it in the
>>> specification.
>> Why does object model consistency disallow a reference to a deleted
>> object?
>> <joerg.von.frantzius.vcf>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Jörg,
On Jul 17, 2006, at 9:26 AM, Jörg von Frantzius wrote:
> Hello Craig,
>
> if I understand things right, you changed your mind and now you
> don't see a any problem with JPOX's automatic nulling out of FKs?
Yes, I have changed my mind on this issue.
> If that's the case, then I wonder why a user would want to have FK
> constraints in his schema at all? They wouldn't be of much use then.
If only using JDO, I agree. What matters is the consistency of the
object model, which is managed by the JDO implementation without help
from the database. But seldom is JDO the only access path to the
database.
>
> I may also add that, as far as I know, JPOX nulls out only for one-
> one bidirectional, not for one-many, so there would be some
> inconsistency of behaviour here.
Interesting point, but without another level of detail, it's hard to
evaluate this statement.
Regards,
Craig
>
> Regards,
> Jörg
>
> Craig L Russell schrieb:
>>
>> 2. Deletion of objects when foreign-key is present (JDO-392) (any
>> and all) It seems that there are two different issues: managing
>> the memory model and managing the database. Craig opines that the
>> general case of consistency is already covered in the chapter on
>> mapping, requiring that the object model be consistent after a
>> flush. Object model consistency would disallow a reference to a
>> deleted object, so the natural behavior would be to nullify the
>> reference to the deleted object. For to-many relationships mapped
>> to a foreign key on the other side, the consistency rule would
>> delete the reference from the collection on the one- side of the
>> relationship. So it seems that the JPOX behavior as originally
>> reported is consistent and we might simply document it in the
>> specification.
> Why does object model consistency disallow a reference to a deleted
> object?
> <joerg.von.frantzius.vcf>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Jörg von Frantzius <jo...@artnology.com>.
Hello Craig,
if I understand things right, you changed your mind and now you don't
see a any problem with JPOX's automatic nulling out of FKs? If that's
the case, then I wonder why a user would want to have FK constraints in
his schema at all? They wouldn't be of much use then.
I may also add that, as far as I know, JPOX nulls out only for one-one
bidirectional, not for one-many, so there would be some inconsistency of
behaviour here.
Regards,
Jörg
Craig L Russell schrieb:
>
> 2. Deletion of objects when foreign-key is present (JDO-392) (any and
> all) It seems that there are two different issues: managing the memory
> model and managing the database. Craig opines that the general case of
> consistency is already covered in the chapter on mapping, requiring
> that the object model be consistent after a flush. Object model
> consistency would disallow a reference to a deleted object, so the
> natural behavior would be to nullify the reference to the deleted
> object. For to-many relationships mapped to a foreign key on the other
> side, the consistency rule would delete the reference from the
> collection on the one- side of the relationship. So it seems that the
> JPOX behavior as originally reported is consistent and we might simply
> document it in the specification.
Why does object model consistency disallow a reference to a deleted object?
Minutes: JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Kristian
Ernst, Erik Bengtson, Craig Russell
Agenda:
1. JDO2 Annotations: 1, 2, or 3 (any and all) Technically, we might
be better off having JDO annotations. But since 220 has already
defined annotations, it might be better to use them. On the other
side, Versant customers don't want to include 220 annotation
libraries in their code just to annotate classes as persistence-
capable. Perhaps a way around this is to define JDO annotations
completely, but allow JDO implementations to accept 220 annotations.
This might require that the JDO specification define the mapping from
220 to JDO annotations, to avoid portability issues where there is
ambiguous mapping. Overriding rules (metadata specified in
annotations plus xml) need to be defined as well.
AI: everyone respond to the discussion on the expert group alias.
AI: Erik document 220 annotations that don't have a corresponding JDO
concept.
2. Deletion of objects when foreign-key is present (JDO-392) (any and
all) It seems that there are two different issues: managing the
memory model and managing the database. Craig opines that the general
case of consistency is already covered in the chapter on mapping,
requiring that the object model be consistent after a flush. Object
model consistency would disallow a reference to a deleted object, so
the natural behavior would be to nullify the reference to the deleted
object. For to-many relationships mapped to a foreign key on the
other side, the consistency rule would delete the reference from the
collection on the one- side of the relationship. So it seems that the
JPOX behavior as originally reported is consistent and we might
simply document it in the specification.
AI Craig write up the proposal.
AI Erik write up JPOX behavior.
3. Subqueries in JDOQL (any and all) Michael still has the action
item to follow up on Craig's queries using the proposed update to the
query. Proposal is to define subqueries using the variable definition.
Action Items from weeks past:
[Jun 30 2006] AI everyone: Look at the link JPOX sent out for their
annotations.
[Jun 30 2006] Craig sent around some more example queries. AI:
Michael will propose a JDOQL query that will handle them. AI:
Matthew will send follow-up email on his proposal.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and
ask for review by EG. AI Martin look at what Hibernate and TopLink
support for Enum types.
[Jun 23 2006] AI everyone look at and respond to the JDOQL
subqueries thread.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts,
logo. AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
JDO TCK Conference Call Friday, July 14 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, July 14 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO2 Annotations: 1, 2, or 3 (any and all)
2. Deletion of objects when foreign-key is present (JDO-392) (any and all)
3. Subqueries in JDOQL (any and all)
4. Other issues (any and all)
Action Items from weeks past:
[Jun 30 2006] AI everyone: Look at the link JPOX sent out for their
annotations.
[Jun 30 2006] Craig sent around some more example queries. AI:
Michael will propose a JDOQL query that will handle them. AI: Matthew
will send follow-up email on his proposal.
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types.
[Jun 23 2006] JDO2 Annotations AI everyone respond to the email thread.
[Jun 23 2006] AI everyone look at and respond to the JDOQL subqueries
thread.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Minutes: JDO TCK Conference Call Friday, June 30 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
NOTE: Next week's JDO TCK Conference (July 7) is CANCELLED! The next
meeting will be on Friday, July 14.
_________________________________________________
Attendees: Matthew Adams, Michael Bouschen, Michelle Caisse
1. JDO2 Annotations - Discussion on approaches. AI everyone: Look at the
link JPOX sent out for their annotations. More analysis required.
2. Subqueries in JDOQL - Craig sent around some more example queries.
AI: Michael will propose a JDOQL query that will handle them. AI:
Matthew will send follow-up email on his proposal.
3. Other issues
Michael has heard no objections on splitting up core subproject. Will
begin unless he receives an objection.
Matthew learned that Excalia plans JDO2 compliance in September.
Action Items from weeks past:
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types.
[Jun 23 2006] JDO2 Annotations AI everyone respond to the email thread.
[Jun 23 2006] AI everyone look at and respond to the JDOQL subqueries
thread.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
JDO TCK Conference Call Friday, June 30 9 am PST
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
We will have our regular meeting Friday, June 23 at 9 am PST to discuss
JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. JDO2 Annotations (any and all)
2. Subqueries in JDOQL (any and all)
3. Other issues (any and all)
Action Items from weeks past:
[Jun 23 2006] AI Craig update ChangeLog and ChangeLog15 pages and ask
for review by EG. AI Martin look at what Hibernate and TopLink support
for Enum types.
[Jun 23 2006] JDO2 Annotations AI everyone respond to the email thread.
[Jun 23 2006] AI everyone look at and respond to the JDOQL subqueries
thread.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on
TheServerSide directing attention to the site. T-shirts, logo.
AI: Craig write a ServerSide article.
-- Michelle
Re: Minutes: JDO TCK Conference Call Friday, June 23 9 am PST [UPDATED]
Posted by Erik Bengtson <er...@jpox.org>.
> AI
> Martin look at what Hibernate and TopLink support for Enum types.
FYI, JPOX also supports Enums. adapted from docs:
A java.lang.Enum field is by default serialized into one column. It can also be
stored in VARCHAR or INTEGER data types via the "Java5" plugin. It's queryable
if stored in VARCHAR or INTEGER columns.
Minutes: JDO TCK Conference Call Friday, June 23 9 am PST [UPDATED]
Posted by Craig L Russell <Cr...@Sun.COM>.
Attendees: Michelle Caisse, Matthew Adams, Martin Zaun, Michael
Bouschen, Craig Russell
Agenda:
1. JDO maintenance release content (Craig) There are currently two
wiki pages on the maintenance release: ChangeLog and ChangeLog15. The
JDK15 issues were split into a separate page to more easily track
them. Issue on changing Query interface to use the builder pattern.
In JDO 2, the FetchPlan interface uses the builder pattern but no
other interfaces. We could change these but at the cost of binary
compatibility (a program using Query compiled under JDO 2.0 would not
execute against the JDO 2.0.1 jar file). AI Craig call for a vote on
EG for changing Query setters to return Query instance. AI Craig
update ChangeLog and ChangeLog15 pages and ask for review by EG. AI
Martin look at what Hibernate and TopLink support for Enum types.
2. JDO2 Annotations (Craig) AI everyone respond to the email thread.
3. Subqueries in JDOQL, further comments? (Matthew, Craig) There is
an email thread on how to specify subqueries. A new proposal by
Michael adds an alias to the FROM clause defining an alias that can
be used in either the outer or inner query; adds an initialization
phrase to the VARIABLES clause; defines the FROM clause as being a
collection of instances; and defines that an inner FROM clause can
have a variable as a parameter. AI everyone look at and respond to
the thread.
4. Updates to embedded field, date field relected in owning object,
JIRA 382 (Michelle) Michelle has written a test case and uploaded a
patch to the JIRA. AI Michelle split out the tests for SCO
projections to a new test class in the query.result package; AI
Michael review the test case.
5. Other issues (any and all)
Action Items from weeks past:
[Jun 16 2006] AI: Everyone respond to Matthew's email dated June 9.
Done.
[Jun 2 2006] Additional query tests for projecting variables are in
Craig's workspace. AI Craig: file a JIRA with patches to be reviewed.
[Jun 2 2006] AI team: go through the open issues and assign relevant
issues to the maintenance release.
[May 26 2006] The spec describes handling of oid fields (application
identity) where the field is a persistence capable type. The
description says that the type of the oid field must be the same
type as the persistence capable class, but actually the type of the
oid field must be the type of the oid of the referenced class. AI
Craig: update the spec and the wiki change log. Done.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK
1.5 issues. In progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles
on TheServerSide directing attention to the site. T-shirts,
logo. AI: Craig write a ServerSide article.
-- Michelle
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!