Apache JDO Project - JDO TCK Conference Call Friday, Aug 26, 9 am PDT

Author

JDO TCK Conference Call Friday, Aug 26, 9 am PDT

Michelle Caisse

2005-08-26, 2:45 am

Hi,

We will have our regular meeting Friday, August 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:

Test status (Michael W, Michelle)
Cleanup in setup or teardown? (Michael B)
JPOX fixes/issues (Erik)
Detached objects (Matthew)
Other issues and status (any and all)

Action Items from weeks past:

[Aug 12 2005] AI: Craig to propose release of API20 and the entire 11
release (API, RI, TCK). This generated a large response on the incubator
alias.

[Aug 5 2005] AI Brian McCallister can send info on the instructions how
to sync Apache and ibiblio. Re: Brian Topping needs info on creating a
maven package.

[Aug 5 2005] AI: Karan: Issue with maven: renaming JPOX releases to
SNAPSHOT. Need to update the README file and project.xml file.
[Aug 5 2005] AI: Geoff look into alternative ways to get this project.
Re: Maven needs to checkout files from netbeans, not documented well.

[July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated to
include all JDO metadata elements and attributes. [not done]

[July 29 2005] Inheritance proposal sent around by Michael. Needs to be
reviewed. 5 inheritance strategies. AI: Craig forward proposal to expert
group.

[July 29 2005] Is there any way to indicate from maven whether a set of
configurations was successful? Not the way it's set up. AI: Michael file
a JIRA on this.

[July 29 2005] (Craig, Brian T.) Need some permissions that Brian is
working on.

[July 22 2005] ? We need to enhance the DeepEquality class to allow
reporting of the difference reported. This will allow easier debugging
of mapping issues. Craig filed JIRA issue 109 on this.

[Jul 8] Double-check locking in the PMF (Martin) Martin has implemented
and will check in.

[April 22 2005] AI JDO API release on ibiblio (Brian T)

[May 20 2005] AI: Craig file JIRA bug and fix this. Can test cases rely
on JDOHelper for state interrogation of non-binary-compatibility
classes? Yes, but the JDO 2.0 JDOImplHelper class has not implemented
the functionality yet.

[April 15 2005] AI Brian Topping will update the wiki to tell how to
access our releases area.

[April 15 2005] AI Brian Topping will do the maven goal for creating and
uploading the snapshots. He will create a directory parallel to trunk
called "releases" and put the snapshots there.

[April 15 2005] AI Matthew will create a directory in the
tck.api.persistencemanager called detach in which he will have complete
freedom to implement the assertions in the detach section of the
specification.

[May 13 2005] AI Brian Topping will implement pushing SNAPSHOT builds of
the project to ibiblio.

[May 13 2005] AI Brian Topping will arrange for automated nightly builds.

[May 13 2005] AI Martin Zaun will investigate JSR 294 (Java 5) to see
impact on enhancer.

[May 20 2005] AI Craig to define the JCP distributions and see if maven
can help.

-- Michelle

Craig Russell

2005-08-26, 5:45 pm

Andy Jefferson

2005-08-26, 5:45 pm

> Michael W has sent patches for the logging changes, including a summary o=
f=20
> the test runs and putting all of the log files into one directory per mav=
en=20
> test run. The patch was well received and wildly successful.=20

Agreed. Much better!=20
One thing I do see with the new logging is that the jpox enhancer log is st=
ill=20
being generated in ${TCK_HOME}/target/enhanced/jdori/{datastore|
application}identity/
rather than under ${TCK_HOME}/target/logs/

> 3. JPOX fixes/issues (Erik) no change.

In response to Craig's mail earlier about specification of the PK of the jo=
in=20
table in the cases where you have embedded SimpleClass objects, I mentioned=
=20
that specification of the PK columns needed implementing in JPOX. This is n=
ow=20
in JPOX CVS, so you should (from tomorrow mornings build) be able to define=
=20
your PK for the join table in the ORM file like this
<join>
=A0 =A0 <primary-key name=3D"COLL_OBJ1_PK">
=A0 =A0 =A0 =A0 <column name=3D"IDENTIFIER"/>
=A0 =A0 =A0 =A0 <column name=3D"ID"/>
=A0 =A0 </primary-key>
</join>

=46YI. JPOX IssueLog has been changed, and can now be seen here
http://www.jpox.org/servlet/jira/se...=3D10000&subse=
t=3D-1
so you're aware of progress of implementing JDO2 features.

=2D-=20
Andy

Michael Watzek

2005-08-29, 5:45 pm

Hi Andy,

>
>
> Agreed. Much better!
> One thing I do see with the new logging is that the jpox enhancer log is still
> being generated in ${TCK_HOME}/target/enhanced/jdori/{datastore|
> application}identity/
> rather than under ${TCK_HOME}/target/logs/
I agree: All log files should be generated in subdirectories of
${TCK_HOME}/target/logs/, e.g. ${TCK_HOME}/target/logs/enhancer. Maybe
you did not enhance when ran TCK? In this case, you would still see the
"old" enhancer log files (generated by a previous run) in
${TCK_HOME}/target/enhanced/jdori/{datastore|application}identity/.

Regards,
Michael
>
>
>
>
> In response to Craig's mail earlier about specification of the PK of the join
> table in the cases where you have embedded SimpleClass objects, I mentioned
> that specification of the PK columns needed implementing in JPOX. This is now
> in JPOX CVS, so you should (from tomorrow mornings build) be able to define
> your PK for the join table in the ORM file like this
> <join>
> <primary-key name="COLL_OBJ1_PK">
> <column name="IDENTIFIER"/>
> <column name="ID"/>
> </primary-key>
> </join>
>
>
> FYI. JPOX IssueLog has been changed, and can now be seen here
> http://www.jpox.org/servlet/jira/se...10000&subset=-1
> so you're aware of progress of implementing JDO2 features.
>
>

--
-------------------------------------------------------------------
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/
-------------------------------------------------------------------