[GitHub] [cayenne] mrg commented on a change in pull request #371: New BeanAccessor constructor, allowing custom accessor method names
mrg commented on a change in pull request #371: New BeanAccessor constructor,
allowing custom accessor method names
URL: https://github.com/apache/cayenne/pull/371#discussion_r267550157
##
File path:
cayenne-server/src/main/java/org/apache/cayenne/reflect/BeanAccessor.java
##
@@ -152,4 +163,19 @@ public void setValue(Object object, Object newValue)
throws PropertyException {
throw new PropertyException("Error writing property: "
+ propertyName, this, object, th);
}
}
+
Review comment:
Won't these methods generate an NPE if the property name is a single
character?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [cayenne] hugith opened a new pull request #371: New BeanAccessor constructor, allowing custom accessor method names
hugith opened a new pull request #371: New BeanAccessor constructor, allowing custom accessor method names URL: https://github.com/apache/cayenne/pull/371 Simplifies creation of BeanAccessor subclasses made solely to modify accessor method names. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (CAY-2554) Redesign dbRelationship's and join's structure
[ https://issues.apache.org/jira/browse/CAY-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2554: - Summary: Redesign dbRelationship's and join's structure (was: Rebuild dbRelationship's and join's structure) > Redesign dbRelationship's and join's structure > -- > > Key: CAY-2554 > URL: https://issues.apache.org/jira/browse/CAY-2554 > Project: Cayenne > Issue Type: Task > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > Need to create DbJoin in order to represent relation between entities. > DbJoin will hold relationship's condition(usual join with pairs of attributes > or expression join) and two dbRelationships, one at a time for each entities. > This change will better represent relation from database view and will help > to implement some new features. > Structure: > DbJoin > * DbJoinCondition > * DbRelationship[] > Condition for pairs of attributes: > ColumnPairsCondition > * List > or ExpressionCondition(in future) > * Expression > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAY-2554) Redesign dbRelationship's and join's structure
[ https://issues.apache.org/jira/browse/CAY-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arseni Bulatski updated CAY-2554: - Description: Need to redesign DbRelationship and DbJoin in order to represent relation between entities. DbJoin will hold relationship's condition(usual join with pairs of attributes or expression join) and two dbRelationships, one at a time for each entities. This change will better represent relation from database view and will help to implement some new features. Structure: DbJoin * DbJoinCondition * DbRelationship[] Condition for pairs of attributes: ColumnPairsCondition * List or ExpressionCondition(in future) * Expression was: Need to create DbJoin in order to represent relation between entities. DbJoin will hold relationship's condition(usual join with pairs of attributes or expression join) and two dbRelationships, one at a time for each entities. This change will better represent relation from database view and will help to implement some new features. Structure: DbJoin * DbJoinCondition * DbRelationship[] Condition for pairs of attributes: ColumnPairsCondition * List or ExpressionCondition(in future) * Expression > Redesign dbRelationship's and join's structure > -- > > Key: CAY-2554 > URL: https://issues.apache.org/jira/browse/CAY-2554 > Project: Cayenne > Issue Type: Task > Components: Core Library >Affects Versions: 4.2.M1 >Reporter: Arseni Bulatski >Priority: Major > Fix For: 4.2.M1 > > > Need to redesign DbRelationship and DbJoin in order to represent relation > between entities. > DbJoin will hold relationship's condition(usual join with pairs of attributes > or expression join) and two dbRelationships, one at a time for each entities. > This change will better represent relation from database view and will help > to implement some new features. > Structure: > DbJoin > * DbJoinCondition > * DbRelationship[] > Condition for pairs of attributes: > ColumnPairsCondition > * List > or ExpressionCondition(in future) > * Expression > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAY-2554) Rebuild dbRelationship's and join's structure
Arseni Bulatski created CAY-2554: Summary: Rebuild dbRelationship's and join's structure Key: CAY-2554 URL: https://issues.apache.org/jira/browse/CAY-2554 Project: Cayenne Issue Type: Task Components: Core Library Affects Versions: 4.2.M1 Reporter: Arseni Bulatski Fix For: 4.2.M1 Need to create DbJoin in order to represent relation between entities. DbJoin will hold relationship's condition(usual join with pairs of attributes or expression join) and two dbRelationships, one at a time for each entities. This change will better represent relation from database view and will help to implement some new features. Structure: DbJoin * DbJoinCondition * DbRelationship[] Condition for pairs of attributes: ColumnPairsCondition * List or ExpressionCondition(in future) * Expression -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAY-2092) Exception for query that uses pagination and sorting on to-many
[ https://issues.apache.org/jira/browse/CAY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797008#comment-16797008 ] Guðmundur Stefán Þorvaldsson edited comment on CAY-2092 at 3/20/19 10:19 AM: - > That is my case also, ordering on a to-many relationship. > This seems valid, but not very useful, no? The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. was (Author: gummis): > This seems valid, but not very useful, no? That is my case also, ordering on a to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. > Exception for query that uses pagination and sorting on to-many > --- > > Key: CAY-2092 > URL: https://issues.apache.org/jira/browse/CAY-2092 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.0.M3 >Reporter: Andrus Adamchik >Priority: Minor > > Somehow we haven't seen this reported before, perhaps because the combination > makes no practical sense. I was able to find it during regression testing of > a LinkRest app that translates REST calls to Cayenne SelectQueries. Anyways, > a query that uses pagination and also ordering on a property of a to-many > relationship (the ordering part doesn't make sense) ends up generating the > following exception, even though all the data is there: > org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] > Some ObjectIds are missing from the database. Expected 62, fetched 31 > at > org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(IncrementalFaultList.java:323) > at > org.apache.cayenne.access.IncrementalFaultList.resolveInterval(IncrementalFaultList.java:262) > at > org.apache.cayenne.access.IncrementalFaultList.get(IncrementalFaultList.java:507) > at com.nhl.link.rest.encoder.ListEncoder.visit(ListEncoder.java:168) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAY-2092) Exception for query that uses pagination and sorting on to-many
[ https://issues.apache.org/jira/browse/CAY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797008#comment-16797008 ] Guðmundur Stefán Þorvaldsson edited comment on CAY-2092 at 3/20/19 10:18 AM: - > This seems valid, but not very useful, no? That is my case also, ordering on a to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. was (Author: gummis): >This seems valid, but not very useful, no? That is my case also, ordering on a to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. > Exception for query that uses pagination and sorting on to-many > --- > > Key: CAY-2092 > URL: https://issues.apache.org/jira/browse/CAY-2092 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.0.M3 >Reporter: Andrus Adamchik >Priority: Minor > > Somehow we haven't seen this reported before, perhaps because the combination > makes no practical sense. I was able to find it during regression testing of > a LinkRest app that translates REST calls to Cayenne SelectQueries. Anyways, > a query that uses pagination and also ordering on a property of a to-many > relationship (the ordering part doesn't make sense) ends up generating the > following exception, even though all the data is there: > org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] > Some ObjectIds are missing from the database. Expected 62, fetched 31 > at > org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(IncrementalFaultList.java:323) > at > org.apache.cayenne.access.IncrementalFaultList.resolveInterval(IncrementalFaultList.java:262) > at > org.apache.cayenne.access.IncrementalFaultList.get(IncrementalFaultList.java:507) > at com.nhl.link.rest.encoder.ListEncoder.visit(ListEncoder.java:168) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAY-2092) Exception for query that uses pagination and sorting on to-many
[ https://issues.apache.org/jira/browse/CAY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797008#comment-16797008 ] Guðmundur Stefán Þorvaldsson edited comment on CAY-2092 at 3/20/19 10:19 AM: - > Here I was talking about a very specific case - ordering on a to-many >relationship That is my case also, ordering on a to-many relationship. > This seems valid, but not very useful, no? The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. was (Author: gummis): > That is my case also, ordering on a to-many relationship. > This seems valid, but not very useful, no? The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. > Exception for query that uses pagination and sorting on to-many > --- > > Key: CAY-2092 > URL: https://issues.apache.org/jira/browse/CAY-2092 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.0.M3 >Reporter: Andrus Adamchik >Priority: Minor > > Somehow we haven't seen this reported before, perhaps because the combination > makes no practical sense. I was able to find it during regression testing of > a LinkRest app that translates REST calls to Cayenne SelectQueries. Anyways, > a query that uses pagination and also ordering on a property of a to-many > relationship (the ordering part doesn't make sense) ends up generating the > following exception, even though all the data is there: > org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] > Some ObjectIds are missing from the database. Expected 62, fetched 31 > at > org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(IncrementalFaultList.java:323) > at > org.apache.cayenne.access.IncrementalFaultList.resolveInterval(IncrementalFaultList.java:262) > at > org.apache.cayenne.access.IncrementalFaultList.get(IncrementalFaultList.java:507) > at com.nhl.link.rest.encoder.ListEncoder.visit(ListEncoder.java:168) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAY-2092) Exception for query that uses pagination and sorting on to-many
[ https://issues.apache.org/jira/browse/CAY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797008#comment-16797008 ] Guðmundur Stefán Þorvaldsson edited comment on CAY-2092 at 3/20/19 10:18 AM: - >This seems valid, but not very useful, no? That is my case also, ordering on a to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. was (Author: gummis): >This seems valid, but not very useful, no?That is my case also, ordering on a >to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. > Exception for query that uses pagination and sorting on to-many > --- > > Key: CAY-2092 > URL: https://issues.apache.org/jira/browse/CAY-2092 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.0.M3 >Reporter: Andrus Adamchik >Priority: Minor > > Somehow we haven't seen this reported before, perhaps because the combination > makes no practical sense. I was able to find it during regression testing of > a LinkRest app that translates REST calls to Cayenne SelectQueries. Anyways, > a query that uses pagination and also ordering on a property of a to-many > relationship (the ordering part doesn't make sense) ends up generating the > following exception, even though all the data is there: > org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] > Some ObjectIds are missing from the database. Expected 62, fetched 31 > at > org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(IncrementalFaultList.java:323) > at > org.apache.cayenne.access.IncrementalFaultList.resolveInterval(IncrementalFaultList.java:262) > at > org.apache.cayenne.access.IncrementalFaultList.get(IncrementalFaultList.java:507) > at com.nhl.link.rest.encoder.ListEncoder.visit(ListEncoder.java:168) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAY-2092) Exception for query that uses pagination and sorting on to-many
[ https://issues.apache.org/jira/browse/CAY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797008#comment-16797008 ] Guðmundur Stefán Þorvaldsson commented on CAY-2092: --- >This seems valid, but not very useful, no?That is my case also, ordering on a >to-many relationship. The way i see it, the result set will contain a completely different set of Artists if ordered by "artist.painting.name" *asc* vs. *desc* for example. > Exception for query that uses pagination and sorting on to-many > --- > > Key: CAY-2092 > URL: https://issues.apache.org/jira/browse/CAY-2092 > Project: Cayenne > Issue Type: Bug >Affects Versions: 4.0.M3 >Reporter: Andrus Adamchik >Priority: Minor > > Somehow we haven't seen this reported before, perhaps because the combination > makes no practical sense. I was able to find it during regression testing of > a LinkRest app that translates REST calls to Cayenne SelectQueries. Anyways, > a query that uses pagination and also ordering on a property of a to-many > relationship (the ordering part doesn't make sense) ends up generating the > following exception, even though all the data is there: > org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] > Some ObjectIds are missing from the database. Expected 62, fetched 31 > at > org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(IncrementalFaultList.java:323) > at > org.apache.cayenne.access.IncrementalFaultList.resolveInterval(IncrementalFaultList.java:262) > at > org.apache.cayenne.access.IncrementalFaultList.get(IncrementalFaultList.java:507) > at com.nhl.link.rest.encoder.ListEncoder.visit(ListEncoder.java:168) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[cayenne-website] branch asf-site updated: release highlights - fixing typos
This is an automated email from the ASF dual-hosted git repository. aadamchik pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/cayenne-website.git The following commit(s) were added to refs/heads/asf-site by this push: new 192c137 release highlights - fixing typos 192c137 is described below commit 192c1372c9462df87faf540376a5c731c5034d2e Author: Andrus Adamchik AuthorDate: Wed Mar 20 10:46:38 2019 +0300 release highlights - fixing typos --- 2019/03/cayenne-41b1-released.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2019/03/cayenne-41b1-released.html b/2019/03/cayenne-41b1-released.html index 9377836..10f51bc 100644 --- a/2019/03/cayenne-41b1-released.html +++ b/2019/03/cayenne-41b1-released.html @@ -96,7 +96,7 @@ The API is frozen now and it is safe to try it out. From now on the 4.1 branch w The highlights of this release are: -Cross-context synchronization to turned off by default. This should improve commit performance and cluster consistency. It can be turned back on via cayenne.server.contexts_sync_strategy property (aka Constants.SERVER_CONTEXTS_SYNC_PROPERTY) +Cross-context synchronization is turned off by default. This should improve commit performance and data consistency in app clustering scenarios. It can be turned back on via cayenne.server.contexts_sync_strategy property (aka Constants.SERVER_CONTEXTS_SYNC_PROPERTY). Improved DB Import tab for DataMaps
[cayenne-website] branch master updated: release highlights - fixing typos
This is an automated email from the ASF dual-hosted git repository. aadamchik pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cayenne-website.git The following commit(s) were added to refs/heads/master by this push: new 16415a7 release highlights - fixing typos 16415a7 is described below commit 16415a7499f879f436f7e90049a2552c84bf669f Author: Andrus Adamchik AuthorDate: Wed Mar 20 10:40:35 2019 +0300 release highlights - fixing typos --- src/main/site/content/news/cayenne-41b1-released.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/site/content/news/cayenne-41b1-released.md b/src/main/site/content/news/cayenne-41b1-released.md index 8553607..832fe41 100644 --- a/src/main/site/content/news/cayenne-41b1-released.md +++ b/src/main/site/content/news/cayenne-41b1-released.md @@ -8,7 +8,7 @@ Apache Cayenne team is glad to announce the first beta release of Cayenne 4.1. The API is frozen now and it is safe to try it out. From now on the 4.1 branch will concentrate on bug fixes. The highlights of this release are: -* Cross-context synchronization to turned off by default. This should improve commit performance and cluster consistency. It can be turned back on via `cayenne.server.contexts_sync_strategy` property (aka `Constants.SERVER_CONTEXTS_SYNC_PROPERTY`) +* Cross-context synchronization is turned off by default. This should improve commit performance and data consistency in app clustering scenarios. It can be turned back on via `cayenne.server.contexts_sync_strategy` property (aka `Constants.SERVER_CONTEXTS_SYNC_PROPERTY`). * Improved "DB Import" tab for DataMaps
[cayenne-website] branch asf-site updated: release highlights
This is an automated email from the ASF dual-hosted git repository. aadamchik pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/cayenne-website.git The following commit(s) were added to refs/heads/asf-site by this push: new 659740a release highlights 659740a is described below commit 659740a4b8608e950cad85042412531a6002e125 Author: Andrus Adamchik AuthorDate: Wed Mar 20 10:42:29 2019 +0300 release highlights --- .DS_Store | Bin 6148 -> 0 bytes 2019/03/cayenne-41b1-released.html| 15 +-- img/cayenne-modeler-40rc1-a464d37d53.png | Bin 54843 -> 0 bytes img/favicon/android-chrome-192x192-c8e800d2b0.png | Bin 1118 -> 0 bytes img/favicon/android-chrome-512x512-f4a2f5a020.png | Bin 3391 -> 0 bytes img/favicon/mstile-144x144-5f1d044e49.png | Bin 1144 -> 0 bytes img/favicon/mstile-144x144-a94ba73eaf.png | Bin 1047 -> 0 bytes img/favicon/mstile-150x150-0fe674a907.png | Bin 869 -> 0 bytes img/favicon/mstile-150x150-13e731f590.png | Bin 1043 -> 0 bytes img/favicon/mstile-310x150-0d0c5a17af.png | Bin 1141 -> 0 bytes img/favicon/mstile-310x150-ff5e1a04ff.png | Bin 861 -> 0 bytes img/favicon/mstile-310x310-a40d63b59e.png | Bin 1781 -> 0 bytes img/favicon/mstile-310x310-b51c330c59.png | Bin 2371 -> 0 bytes img/favicon/mstile-70x70-6e391d6d5c.png | Bin 650 -> 0 bytes img/favicon/mstile-70x70-c524897489.png | Bin 724 -> 0 bytes img/logo_mono_full-b893724c6c.svg.png | Bin 1468 -> 0 bytes img/modeler-4-24b0368dc2.0-screen.png | Bin 52711 -> 0 bytes img/modeler-dbimport-58df3bd3e6.png | Bin 74222 -> 0 bytes img/modeler-screen-368bbb5de6.png | Bin 52415 -> 0 bytes schema/.DS_Store | Bin 6148 -> 0 bytes 20 files changed, 13 insertions(+), 2 deletions(-) diff --git a/.DS_Store b/.DS_Store deleted file mode 100644 index cff8ab3..000 Binary files a/.DS_Store and /dev/null differ diff --git a/2019/03/cayenne-41b1-released.html b/2019/03/cayenne-41b1-released.html index 5225c33..9377836 100644 --- a/2019/03/cayenne-41b1-released.html +++ b/2019/03/cayenne-41b1-released.html @@ -91,8 +91,19 @@ -Apache Cayenne team is glad to announce first beta release of Cayenne 4.1. -The API is frozen now and it is safe to try it out. From now on the 4.1 branch will concentrate on bug fixes. +Apache Cayenne team is glad to announce the first beta release of Cayenne 4.1. +The API is frozen now and it is safe to try it out. From now on the 4.1 branch will concentrate on bug fixes. +The highlights of this release are: + + +Cross-context synchronization to turned off by default. This should improve commit performance and cluster consistency. It can be turned back on via cayenne.server.contexts_sync_strategy property (aka Constants.SERVER_CONTEXTS_SYNC_PROPERTY) + +Improved DB Import tab for DataMaps + +Class Generation dialog is now implemented as a DataMap tab. Class generation user selections are preserved in the project and can be reused from Maven/Gradle/Ant cgen. + +General Modeler cleanup and bugfixes; framework bugfixes. + Cayenne can be downloaded from here. diff --git a/img/cayenne-modeler-40rc1-a464d37d53.png b/img/cayenne-modeler-40rc1-a464d37d53.png deleted file mode 100644 index 155d77c..000 Binary files a/img/cayenne-modeler-40rc1-a464d37d53.png and /dev/null differ diff --git a/img/favicon/android-chrome-192x192-c8e800d2b0.png b/img/favicon/android-chrome-192x192-c8e800d2b0.png deleted file mode 100644 index 2d7a971..000 Binary files a/img/favicon/android-chrome-192x192-c8e800d2b0.png and /dev/null differ diff --git a/img/favicon/android-chrome-512x512-f4a2f5a020.png b/img/favicon/android-chrome-512x512-f4a2f5a020.png deleted file mode 100644 index 53eaf3a..000 Binary files a/img/favicon/android-chrome-512x512-f4a2f5a020.png and /dev/null differ diff --git a/img/favicon/mstile-144x144-5f1d044e49.png b/img/favicon/mstile-144x144-5f1d044e49.png deleted file mode 100644 index e9ad16c..000 Binary files a/img/favicon/mstile-144x144-5f1d044e49.png and /dev/null differ diff --git a/img/favicon/mstile-144x144-a94ba73eaf.png b/img/favicon/mstile-144x144-a94ba73eaf.png deleted file mode 100644 index b0c413a..000 Binary files a/img/favicon/mstile-144x144-a94ba73eaf.png and /dev/null differ diff --git a/img/favicon/mstile-150x150-0fe674a907.png b/img/favicon/mstile-150x150-0fe674a907.png deleted file mode 100644 index c7e2f37..000 Binary files a/img/favicon/mstile-150x150-0fe674a907.png and /dev/null differ diff --git a/img/favicon/mstile-150x150-13e731f590.png b/img/favicon/mstile-150x150-13e731f590.png deleted file mode 100644 index 2a23695..000 Binary files a/img/favicon/mstile-150x150-13e731f590.png and /dev/null differ
[cayenne-website] branch master updated: release highlights
This is an automated email from the ASF dual-hosted git repository. aadamchik pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cayenne-website.git The following commit(s) were added to refs/heads/master by this push: new d310f92 release highlights d310f92 is described below commit d310f92ea0720ad43003d43b050542fa8a745803 Author: Andrus Adamchik AuthorDate: Wed Mar 20 10:40:35 2019 +0300 release highlights --- src/main/site/content/news/cayenne-41b1-released.md | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/src/main/site/content/news/cayenne-41b1-released.md b/src/main/site/content/news/cayenne-41b1-released.md index 580a044..8553607 100644 --- a/src/main/site/content/news/cayenne-41b1-released.md +++ b/src/main/site/content/news/cayenne-41b1-released.md @@ -4,8 +4,17 @@ date: 2019-03-18T12:00:00+03:00 url: /2019/03/cayenne-41b1-released.html --- -Apache Cayenne team is glad to announce first beta release of Cayenne 4.1. +Apache Cayenne team is glad to announce the first beta release of Cayenne 4.1. The API is frozen now and it is safe to try it out. From now on the 4.1 branch will concentrate on bug fixes. +The highlights of this release are: + +* Cross-context synchronization to turned off by default. This should improve commit performance and cluster consistency. It can be turned back on via `cayenne.server.contexts_sync_strategy` property (aka `Constants.SERVER_CONTEXTS_SYNC_PROPERTY`) + +* Improved "DB Import" tab for DataMaps + +* "Class Generation" dialog is now implemented as a DataMap tab. Class generation user selections are preserved in the project and can be reused from Maven/Gradle/Ant cgen. + +* General Modeler cleanup and bugfixes; framework bugfixes. Cayenne can be downloaded from [here](/download.html).
