Re: [db-jdo-site] branch main updated: update XSD/DTD to match the JDO 3.2.1 variant

2022-04-10 Thread Bouschen, Michael 
Hi Andy,

just fyi: we have not yet shipped JDO 3.2.1.

Regards Michael

This is an automated email from the ASF dual-hosted git repository.

andyj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git


The following commit(s) were added to refs/heads/main by this push:
 new b50fabf  update XSD/DTD to match the JDO 3.2.1 variant
b50fabf is described below

commit b50fabfe621a798fc24f2e180a3bcd21252b8905
Author: andyjefferson 
AuthorDate: Sun Apr 10 16:01:54 2022 +0100

update XSD/DTD to match the JDO 3.2.1 variant
---
 src/main/asciidoc/jdo_dtd.adoc   | 19 +++
 src/main/asciidoc/jdoconfig_dtd.adoc | 17 -
 src/main/asciidoc/metadata.adoc  |  7 +++
 src/main/asciidoc/orm_dtd.adoc   | 19 +++
 src/main/resources/downloads/xmlns/jdo_3_2.dtd   |  4 ++--
 src/main/resources/downloads/xmlns/jdo_3_2.xsd   |  4 ++--
 src/main/resources/downloads/xmlns/jdoconfig_3_2.dtd |  4 ++--
 src/main/resources/downloads/xmlns/jdoconfig_3_2.xsd |  6 +++---
 src/main/resources/downloads/xmlns/jdoquery_3_2.dtd  |  4 ++--
 src/main/resources/downloads/xmlns/jdoquery_3_2.xsd  |  4 ++--
 src/main/resources/downloads/xmlns/orm_3_2.dtd   |  4 ++--
 src/main/resources/downloads/xmlns/orm_3_2.xsd   |  4 ++--
 12 files changed, 50 insertions(+), 46 deletions(-)

diff --git a/src/main/asciidoc/jdo_dtd.adoc b/src/main/asciidoc/jdo_dtd.adoc
index 955a73a..1078cc9 100644
--- a/src/main/asciidoc/jdo_dtd.adoc
+++ b/src/main/asciidoc/jdo_dtd.adoc
@@ -20,9 +20,13 @@ Here are a few examples valid for *jdo* files with DTD 
specifications

 
 http://xmlns.jcp.org/dtd/jdo_3_0.dtd;>
+"-//The Apache Software Foundation//DTD Java Data Objects Metadata 3.2//EN"
+
"https://db.apache.org/jdo/xmlns/jdo_3_2.dtd;>
+
+
+or

+
 >
 

@@ -33,15 +37,14 @@ Here is an example valid for *jdo* files with XSD 
specification

 
 
-http://xmlns.jcp.org/xml/ns/jdo/jdo;
- 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
- xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdo
-
http://xmlns.jcp.org/xml/ns/jdo/jdo_3_0.xsd;>
+https://db.apache.org/jdo/xmlns/jdo;
+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+xsi:schemaLocation="https://db.apache.org/jdo/xmlns/jdo 
https://db.apache.org/jdo/xmlns/jdo_3_2.xsd;
 version="3.2">
 ...
 
 

 Your MetaData should match either the
-http://xmlns.jcp.org/dtd/jdo_3_0.dtd[DTD] or the
-http://xmlns.jcp.org/xml/ns/jdo/jdo_3_0.xsd[XSD] specification.
+http://db.apache.org/jdo/xmlns/jdo_3_2.dtd[DTD] or the
+http://db.apache.org/jdo/xmlns/jdo_3_2.xsd[XSD] specification.

diff --git a/src/main/asciidoc/jdoconfig_dtd.adoc 
b/src/main/asciidoc/jdoconfig_dtd.adoc
index 9115e3b..b2e862d 100644
--- a/src/main/asciidoc/jdoconfig_dtd.adoc
+++ b/src/main/asciidoc/jdoconfig_dtd.adoc
@@ -20,9 +20,9 @@ Here are a few examples valid for *jdoconfig* files with DTD
 specifications

 
-http://xmlns.jcp.org/dtd/jdoconfig_3_0.dtd;>
+https://db.apache.org/jdo/xmlns/jdoconfig_3_2.dtd;>

 >
 
@@ -34,15 +34,14 @@ Here is an example valid for *jdoconfig* files with XSD 
specification

 
 
-http://xmlns.jcp.org/xml/ns/jdo/jdoconfig;
- 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
- xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/jdo/jdoconfig
-
http://xmlns.jcp.org/xml/ns/jdo/jdoconfig_3_0.xsd;>
+https://db.apache.org/jdo/xmlns/jdoconfig;
+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
+xsi:schemaLocation="https://db.apache.org/jdo/xmlns/jdoconfig 
https://db.apache.org/jdo/xmlns/jdoconfig_3_2.xsd;
 version="3.2">
 ...
 
 

 Your MetaData should match either the
-http://xmlns.jcp.org/dtd/jdoconfig_3_0.dtd[DTD] or the
-http://xmlns.jcp.org/xml/ns/jdo/jdoconfig_3_0.xsd[XSD] specification.
+https://db.apache.org/jdo/xmlns/jdoconfig_3_2.dtd[DTD] or the
+https://db.apache.org/jdo/xmlns/jdoconfig_3_2.xsd[XSD] specification.

diff --git a/src/main/asciidoc/metadata.adoc

[jira] [Resolved] (JDO-809) Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly map embedded element fields

2022-04-10 Thread Andy Jefferson (Jira) 


 [ 
https://issues.apache.org/jira/browse/JDO-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Jefferson resolved JDO-809.

  Assignee: Andy Jefferson
Resolution: Fixed

Fixed by commit 
https://github.com/apache/db-jdo/commit/c2ae74ab0b393786962106961d291d2254ba531c

> Mapping info for ArrayListCollections/TreeSetCollections doesn't correctly 
> map embedded element fields
> --
>
> Key: JDO-809
> URL: https://issues.apache.org/jira/browse/JDO-809
> Project: JDO
>  Issue Type: Bug
>  Components: tck
>Affects Versions: JDO 2 final (2.0), JDO 3 (3.0), JDO 3.1, JDO 3.2
>Reporter: Andy Jefferson
>Assignee: Andy Jefferson
>Priority: Major
> Fix For: JDO 3.2.1
>
>
> The tests for the different java.util.Collection types all should follow the 
> same pattern, with the samples having a range of fields that cover the 
> primary field usages.
> Field XXXOfObject1 should represent a Collection of Object, where the Object 
> is a PersistenceCapable type, persisting embedded into a join table.
> Field XXXOfSimpleClass should represent a Collection of PersistenceCapable 
> type, persisting embedded into a join table.
> Field XXXOfSimpleInterface should represent a Collection of interface, where 
> the interface is a PersistenceCapable type, persisting embedded into a join 
> table.
>  
> In the case of the ArrayList and TreeSet cases the ORM files do not define 
> the  block for how the fields of the PersistenceCapable element 
> will map into the join table. The schema for those cases also do not map the 
> fields of the PersistenceCapable element, instead just having a FK to the 
> table of the element (so not embedded at all).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)