JDO TCK Conference Call Thursday June 10 11:00 AM Pacific Daylight Time (PDT)

2021-06-09 Thread Michael Bouschen 
Hi,

We will have our regular meeting Thursday June 10 11:00 AM Pacific Daylight 
Time (PDT) to discuss JDO TCK issues and status.

We use the following dial-in for audio and video. You need a Skype account to 
join.
https://join.skype.com/lKWOxZDu2O5U

Agenda:
1. Spec Updates JDO-709  
"Standardize field/property converters"
2. Issues with Fix Version JDO-3.2 

3. Open Issues w/o Fix Version 

4. Release Policy Updates
5. JDO 3.1: Need to go through change lists in JIRA for 3.1 RC1 and 3.1 to 
prepare JCP Change Log
6. Other issues

Action Items from weeks past:
[May 27 2021] AI Tobias clarify GitHub action for direct pushes. 
[May 13 2021] AI Craig update specification terminology to "database type" 
instead of "converted type"
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Feb 04 2021] AI Craig ask Oracle for license for the specification.
[Jan 07 2021] AI Craig update to add workflow for contributions and preview of 
changes.
[Oct 30 2015] AI Craig: File a maintenance review with JCP
[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?
[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.

Regards Michael

[jira] [Commented] (JDO-709) Standardize field/property converters

2021-06-09 Thread Andy Jefferson (Jira) 


[ 
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360014#comment-17360014
 ] 

Andy Jefferson commented on JDO-709:


Good. Ignore the last comment on attributeName, of course I put "converter" on 
the Key, Value and Element annotations, so we don't need that anyway.

> Standardize field/property converters
> -
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Matthew T. Adams
>Assignee: Craig L Russell
>Priority: Minor
>  Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of 
> fields or properties of persistence-capable classes.  Currently, this is left 
> to vendor extensions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JDO-709) Standardize field/property converters

2021-06-09 Thread Michael Bouschen (Jira) 


[ 
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360008#comment-17360008
 ] 

Michael Bouschen commented on JDO-709:
--

I removed the Converts annotations (and the @Repeatable(Converts.class) in 
Covert) and could successfully run the TCK.

> Standardize field/property converters
> -
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Matthew T. Adams
>Assignee: Craig L Russell
>Priority: Minor
>  Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of 
> fields or properties of persistence-capable classes.  Currently, this is left 
> to vendor extensions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (JDO-709) Standardize field/property converters

2021-06-09 Thread Andy Jefferson (Jira) 


[ 
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359994#comment-17359994
 ] 

Andy Jefferson edited comment on JDO-709 at 6/9/21, 11:44 AM:
--

The other use of the "attributeName" was when wanting to define a converter for 
the key/value of a Map (attributeName="key", or attributeName="value"), or when 
we have a Collection of some non-persistable element and wanting to define a 
converter for the element type. That could be of use, and DataNucleus has the 
code for it ... but it *would* require the Converts annotation if the user is 
providing "key" *and* "value" converters. So we could add the attributeName to 
the Convert annotation just for those 3 specific cases, but ignore the embedded 
field converter override. Whether it's worth the effort at this point is 
arguable, not so highly used


was (Author: andy):
The other use of the "attributeName" was when wanting to define a converter for 
the key/value of a Map (attributeName="key", or attributeName="value"), or when 
we have a Collection of some non-persistable element and wanting to define a 
converter for the element type. That could be of use, and DataNucleus has the 
code for it ... but it does not require the Converts annotation though.

So we could add the attributeName to the Convert annotation just for those 3 
specific cases, but ignore the embedded field converter override.

> Standardize field/property converters
> -
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Matthew T. Adams
>Assignee: Craig L Russell
>Priority: Minor
>  Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of 
> fields or properties of persistence-capable classes.  Currently, this is left 
> to vendor extensions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JDO-709) Standardize field/property converters

2021-06-09 Thread Andy Jefferson (Jira) 


[ 
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359994#comment-17359994
 ] 

Andy Jefferson commented on JDO-709:


The other use of the "attributeName" was when wanting to define a converter for 
the key/value of a Map (attributeName="key", or attributeName="value"), or when 
we have a Collection of some non-persistable element and wanting to define a 
converter for the element type. That could be of use, and DataNucleus has the 
code for it ... but it does not require the Converts annotation though.

So we could add the attributeName to the Convert annotation just for those 3 
specific cases, but ignore the embedded field converter override.

> Standardize field/property converters
> -
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Matthew T. Adams
>Assignee: Craig L Russell
>Priority: Minor
>  Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of 
> fields or properties of persistence-capable classes.  Currently, this is left 
> to vendor extensions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JDO-709) Standardize field/property converters

2021-06-09 Thread Andy Jefferson (Jira) 


[ 
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359853#comment-17359853
 ] 

Andy Jefferson commented on JDO-709:


[~clr] Yes, the "attributeName" was omitted when it was added in 2015; can't 
remember why. Easiest option is just to remove "Converts" and move forward, and 
maybe add a javadoc comment (to the Convert annotation that an attribute could 
be added if wanting to support overriding the specification of converters for 
fields of embedded objects) or just add a Jira issue for a future release. But 
then I'm not exactly so much in favour of using annotations for such things; 
I've never had a need to override a default converter for a field, defined on 
the embedded class; the JDO XML definition is way more expressive to achieve 
that (IMHO)

> Standardize field/property converters
> -
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
>  Issue Type: New Feature
>  Components: api, specification, tck
>Reporter: Matthew T. Adams
>Assignee: Craig L Russell
>Priority: Minor
>  Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of 
> fields or properties of persistence-capable classes.  Currently, this is left 
> to vendor extensions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)