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 Michael Bouschen <mi...@akquinet.de> on 2016/01/28 21:40:57 UTC

JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)

Hi,

We will have our regular meeting Friday, January 29 at 9 AM Pacific Time (PST) to discuss JDO TCK issues and status. 

Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt +49 69 222 216 106
Germany Munich: +49 89 1430 2323
Germany Toll free: 08006648515
Switzerland Geneva: +41 445804003
Switzerland Toll free: 0800650026
Oracle Conferencing - Operator-Free Global Access Num(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#

We use the conference call for audio and use Google Hangouts for screen sharing and video.
The Google Hangouts URL for the meeting: http://goo.gl/sCKJaS

Agenda:
1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log
2. Spec updates JDO-749 "Support for java.time types, and querying using associated methods" https://issues.apache.org/jira/browse/JDO-749
3. JIRA JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747 
4. Other issues

Action Items from weeks past:
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[May 15 2015] AI Craig Spec change for roll back an active transaction when closing a persistence manager (JDO-735)  
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process.

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 Web:   www.akquinet.de
<http://www.akquinet.de> akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht
Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680

Re: JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)

Posted by Matthew Adams <ma...@matthewadams.me>.
Please add to the agenda a discussion of who, if anyone, would like to take
over the (fairly inactive) JDO social media properties.

Here was my email to Craig, which may have fallen through the cracks:

Hi Craig,

As I haven't been participating hardly at all for some time now, I'd like
to hand over the various JDO social media accounts to you or a designee.
We have Facebook & Google+ "Pages", a Twitter account, and a Gmail account,
javadataobjects@gmail.com.  Here are available stats:

Facebook:  https://facebook.com/JavaDataObjects, 40 likes
Twitter:  @JavaDataObjects, 22 followers
Gmail:  javadataobjects@gmail.com
G+:  https://plus.google.com/106584233526334524963, 12 followers

Alternatively, I could delete these accounts.

To hand over each property, I need the following.

Facebook:  designated Facebook account to be page admin
Twitter:  person to give account password to
Gmail:  person to give account password to
G+:  designated Google/Google+ account to be page manager

It is pretty easy to spray messages to all of these accounts at once using
Hootsuite.  Please advise what you want me to do.

I hope you the rest of the JavaDOgs are doing well!



On Thu, Jan 28, 2016 at 2:40 PM, Michael Bouschen <
michael.bouschen@akquinet.de> wrote:

> Hi,
>
> We will have our regular meeting Friday, January 29 at 9 AM Pacific Time
> (PST) to discuss JDO TCK issues and status.
>
> Dial-in numbers are:
> US Toll free: 866 682-4770
> Germany Frankfurt +49 69 222 216 106
> Germany Munich: +49 89 1430 2323
> Germany Toll free: 08006648515
> Switzerland Geneva: +41 445804003
> Switzerland Toll free: 0800650026
> Oracle Conferencing - Operator-Free Global Access Num(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#
>
> We use the conference call for audio and use Google Hangouts for screen
> sharing and video.
> The Google Hangouts URL for the meeting: http://goo.gl/sCKJaS
>
> Agenda:
> 1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to
> prepare JCP Change Log
> 2. Spec updates JDO-749 "Support for java.time types, and querying using
> associated methods" https://issues.apache.org/jira/browse/JDO-749
> 3. JIRA JDO-747 "Behavior of delete() with multiple concurrent
> Transactions" https://issues.apache.org/jira/browse/JDO-747
> 4. Other issues
>
> Action Items from weeks past:
> [Oct 30 2015] AI Craig: File a maintenance review with JCP
> [May 15 2015] AI Craig Spec change for roll back an active transaction
> when closing a persistence manager (JDO-735)
> [Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once
> the JCP Maintenance Release for JDO 3.1 is published
> [Oct 17 2014] AI Matthew any updates for "Modify specification to address
> NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
> [Feb 28 2014] AI Everyone: take a look at
> https://issues.apache.org/jira/browse/JDO-712
> [Feb 28 2014] AI Everyone: take a look at
> https://issues.apache.org/jira/browse/JDO-625
> [Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as
> persistent field types
> [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about
> JDOHelper methods. In process.
>
> 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 Web:   www.akquinet.de
> <http://www.akquinet.de> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht
> Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
>



-- 
mailto:matthew@matthewadams.me <ma...@matthewadams.me>
skype:matthewadams12
googletalk:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

ViewVC problem

Posted by Tilmann <za...@gmx.de>.
Hi,

I realised that using Chrome instead of Firefox works, even though it 
hangs ~30 seconds before showing anything.
Also, the original issue (https://issues.apache.org/jira/browse/JDO-748) 
explains that the problem with ViewCVS occurred even with an http-link, 
because Firefox automatically changed that to https if the server 
supports it.
I suppose changing the link to http would probably not help.

My guess is that the issue may have to do with the security-certificates 
that Firefox is using, or with the certificate authorities it is trying 
to contact when browsing from Switzerland.

Considering that the problem appears to be limited to Switzerland and 
Firefox browsers, and that there is a good chance that changing to https 
won't help, I won't raise in issue just yet.

Let me know if you think the issue should still be raised. In that case 
it may make sense to vote on my commit rights, as suggested by Craig, so 
I could fix and verify the solution myself.

Cheers,
Tilmann

===============
Tilmann Zaeschke
http://www.zoodb.org




Re: Minutes: JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)

Posted by Andy Jefferson <an...@datanucleus.org>.
> 2. Spec updates JDO-749 "Support for java.time types, and querying using associated methods" https://issues.apache.org/jira/browse/JDO-749
> 
> Chapter 14: why are other supported time types not orderable? 

No reason, I simply added LocalDateTime, LocalDate, LocalTime where Date was previously mentioned - this could become supported java.time types. But then there are other types not mentioned in that section that are supported as persistable (Locale, Calendar, etc), so why were they excluded?. 
Same applies in Result Class Requirements section.

> Chapter 18: why don't other supported time types not have default JDBC types?

Because the default still needs defining. To give an example
java.time.YearMonth can be persisted (by DN) as
* String
* DATE (setting day to 0)
* (INT, INT) storing the year and month.


> There is special treatment for Local time, date, and date time. Are there implementation issues?

I see no implementation issue, and I also see no "special treatment" (in the spec). Where?


> 4. Other issues
> 
> There are several un-accepted changes in the specification noticed during review of changes in JIRA issues. 

Do you mean "Track Changes" is ON in the spec docs in SVN? clearly, because the tracked changes in those docs are what has changed since 3.1 (so that it is easier to compile a list of changes when 3.2/4.0 is ever released). Or maybe you mean something else



When is there confirmation of what this release is to be called? I'm assuming 3.2, but such a thing should be decided up front when the scope of changes is visible ... which it is.


Regards
-- 
Andy
DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)

Minutes: JDO TCK Conference Call Friday January 29, 9 AM Pacific Time (PST)

Posted by Craig Russell <cr...@oracle.com>.
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell

Agenda:

1. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to prepare JCP Change Log

no change

2. Spec updates JDO-749 "Support for java.time types, and querying using associated methods" https://issues.apache.org/jira/browse/JDO-749

Chapter 14: why are other supported time types not orderable? 
Chapter 18: why don't other supported time types not have default JDBC types?
Appendix D: changes look good

There is special treatment for Local time, date, and date time. Are there implementation issues?

3. JIRA JDO-747 "Behavior of delete() with multiple concurrent Transactions" https://issues.apache.org/jira/browse/JDO-747

Still waiting for feedback on the specification updates. Are there any implementation issues?

4. Other issues

There are several un-accepted changes in the specification noticed during review of changes in JIRA issues. 

Are there any current toll-free numbers for Germany and Switzerland?

The link to viewvc in page http://db.apache.org/jdo/svn.html uses https:// Can this use http:// instead? AI Tilmann file a JIRA.

Action Items from weeks past:
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[May 15 2015] AI Craig Spec change for roll back an active transaction when closing a persistence manager (JDO-735)  
[Apr 17 2015] AI Craig: Oracle spec page on JDO need to be updated once the JCP Maintenance Release for JDO 3.1 is published
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores": https://issues.apache.org/jira/browse/JDO-651?
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-712
[Feb 28 2014] AI Everyone: take a look at https://issues.apache.org/jira/browse/JDO-625
[Dec 13 2013] AI Craig file a JIRA for java.sql.Blob and java.sql.Clob as persistent field types
[Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process.