Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell

Next meeting: Tuesday August 27 1100 PDT 2000 CEST

Agenda:

1. JIRA JDO-842 "Q class specification of candidate() method" 
https://issues.apache.org/jira/browse/JDO-842

The specification probably belongs in 10.2 Metamodel.
The JDO implementation creates a metamodel class for each persistence capable 
class. The base name of the metamodel class starts with a “Q” (Employee → 
QEmployee) and it has the same package as the persistence capable class.
The metamodel class provides a public static field for each persistent 
field/property and relationship of the persistence capable class. These static 
fields are used to represent field access in a query. 

Additionally, the metamodel class has the following methods:
public static QClass candidate()
The behavior of this method is identical to candidate("this").

public static QClass candidate(String name)
This method returns a new instance of QClass with the specified name. The name 
may be used in the JDO implementation when executing queries. Thus instances of 
the candidate returned by this method must not be reused. And the name must be 
unique in the execution of a query.

public static QClass variable(String name)
This method returns a new instance of QClass with the specified name. The name 
may be used by the implementation when implementing queries. Thus instances of 
the candidate returned by this method must not be reused. And the name must be 
unique among objects returned by candidate and variable in the execution of a 
query.

public static QClass parameter(String name)
This method is an internal implementation method; not for use by applications.

Action requested: Please review the above for inclusion in the Specification.

NOTE: Most examples in the specification have a typo
QEmployee cand = Qemployee.candidate();
should be:
QEmployee cand = QEmployee.candidate();

2. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" 
https://issues.apache.org/jira/browse/JDO-812

3. sonarcloud issues

 * JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
 * JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https://issues.apache.org/jira/browse/JDO-823
 * Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo
 * Cognitive Complexity of methods should not be too high:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo
 
 * Raw types should not be used:
https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo
 

4. Other issues

Action Items from weeks past:

[Jan 02 2024] AI everyone: see if anyone can see a problem with the parallel 
execution of tests Cast.java and SupportedOptionalMethods.java
[Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API 
disallows use with Android
[Jun 08 2023] AI All make a JIRA: JDO support for Java Records 
https://openjdk.org/jeps/395
[Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO 
development and see if and how they want to be recognized on the JDO and DB web 
sites.https://db.apache.org/whoweare.html
[Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group 
members asking if they wish to continue.
[Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts
[Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL 
datastores "https://issues.apache.org/jira/browse/JDO-651


Craig L Russell
c...@apache.org

Reply via email to