July 2018 - hibernate-dev - Jboss List Archives

JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

by Rory O'Donnell

Hi Sanne, *JDK 11 is in Rampdown Phase one* * *The overall feature set is frozen. No further JEPs will be targeted to this release.* * *Rampdown Phase two is scheduled to start * *26th of July* **JDK 11 EA build 22 , *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. *** * Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes *FOSS fixes in recent builds.* * JBoss Netty (b17) - JDK-8203937 (b17) * JUnit5 & other Foss Projects (b22) -JDK-8206355 **Notable changes in JDK 11 EA *build 22* * New Collection.toArray(IntFunction) Default Method (JDK-8060192 <http://bugs.openjdk.java.net/browse/JDK-8060192>) * Make some system properties effectively readonly (JDK-8066709 <http://bugs.openjdk.java.net/browse/JDK-8066709>) * Obsolete Support for Commercial Features (JDK-8202331 <http://bugs.openjdk.java.net/browse/JDK-8202331>) * JFR start failure after AppCDS archive created with JFR StartFlightRecording (JDK-8203664 <http://bugs.openjdk.java.net/browse/JDK-8203664>) * Change to policy for the default set of modules resolved when compiling or running code on the class path (JDK-8197532 <http://bugs.openjdk.java.net/browse/JDK-8197532>) *JDK 12 Early Access Build 02 is available at **http://jdk.java.net/12/* * OpenJDK builds o These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in this build are listed here <http://hg.openjdk.java.net/jdk/jdk/log?revcount=10000&rev=reverse%28%22jd...> *The Quality Report for July 2018 is published **here <https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+for...>* * With the new six months release , we now publish the Quality report every three months. * Thanks to all the FOSS Projects for logging bugs against the JDK 11 EA Builds! Rgds,Rory [1] http://openjdk.java.net/projects/jdk/11/

7 years, 8 months

1
0
0 / 0

ORM - Asciidoclet

by Guillaume Smet

Hi, Are we using Asciidoc javadoc in the current tree (i.e. not 6)? With JDK 11, when ./gradlew :hibernate-core:javadoc is executed and this doclet is enabled, I have the following error: javadoc: error - invalid flag: -Xdoclint:none In the javadoc -X help, it says that doclint is "Provided by the Standard doclet". Removing the asciidoclet declaration fixes the issue. As asciidoclet is not enabled in the aggregateJavadocs task, I'm under the impression that it is not used. Could someone confirm this? Thanks! -- Guillaume

7 years, 8 months

2
7
0 / 0

[ORM] Javadoc errors fixing

by Guillaume Smet

Hi, So due to the issue with Asciidoclet I exposed in my previous email, I thought for some time that they had removed the -XDoclint flag in Java 11. Thus I started cleaning up all the Javadoc errors we have in the ORM source code... This led to the following changes: https://github.com/hibernate/hibernate-orm/compare/master...gsmet:HHH-128... . It's kinda huge and while it's only trivial changes, I'm a bit worried about what will happen when you will try to merge this in your 6 branch. All the errors are fixed except: - 3 reference not found errors for which I need advice - the errors in the generated sources that are thrown in the aggregateJavadocs task: the exclude rules are not taken into account by Gradle in this task, probably a Gradle bug, I saw an old forum post of Steve in the Gradle forum about this issue. Note: I don't have any issue if we consider it's not the right time to do that and we should only do that on 6. That's why I ask the question. I have no idea of what the 6 branch look like so I don't know how much of an issue it can be. Cherry-picking these changes on top of 6, once it's stabilized is a possibility. Thoughts? -- Guillaume

7 years, 8 months

2
2
0 / 0

ORM 6.0 Alpha1 release planning

by Steve Ebersole

I had a talk with Luis this morning with regard to the performance benchmarks for 6 versus 5. He is working from 2 different benchmarks - one simply compares parsing HQL (without executing it) and the other compares certain operations (save/persist, load, etc). Luis, correct me if I am wrong, but what I took away from the conversation is this: 1. For the operations benchmark the numbers for 6 were better than 5, but within the error margin - so 6 is better-than-or-equal-to 5 here. 2. 6 was generally faster at parsing queries except for when it came to interpreting paths. We need to address the paths problem, for sure, but honestly I was not expecting any performance improvements in query parsing - at least not initially and the primary focus of the work is in making the executions more performant. Any improvements on query parsing performance is cake at this point, though certainly something we want to look at. I asked Luis to compare the numbers specifically for load operations in that operations benchmark. That is really the only operations case where I would expect perf improvements at this time - it should piggy-back on the overall JDBC execution performance improvements. Luis, I'd also like to get some simple HQL queries into that operations benchmark if we could to verify that this ^^ happens there as well. I can help with that if you want - let me know. Barring any crazy outcomes from these new benchmark results, I feel comfortable starting to plan an initial Alpha release schedule. We currently have a fairly aggressive set of items to complete on our Alpha1 checklist[1][2]. I think we ought to consider paring that down in the interest of release early, release often - having releases would help OGM, etc integrate early and often as well. My proposal is to just implement basic support for plural attributes in Alpha1 and push the rest to later Alphas. E.g.: 1. Alpha1 1. plural attribute suppport 2. Alpha2 1. Any / ManyToAny support 2. Cascading 3. Alpha3 1. Metamodel fetching 2. JDBC batching 4. We'll see where we are... IMO each Alpha ought to be 2 weeks, though I could live with 3 or depending one everyone else's opinion. Thoughts? Opinions? [1] https://github.com/sebersole/hibernate-core/blob/wip/6.0/design/6.0-todo.... [2] That list is somewhat out of date anyway as quite a few things listed there are already implemented

7 years, 8 months

2
1
0 / 0

Delivery failed

by Mail Administrator

��b��c�l�6��"��ip��P��3# �U��:^�r�N>�`�25��$X��C� �1��U��#�)��Ek]�G��I��5��|�t��L��l}S��c�zu��/�19� !`$�u��{]��onC��I�0J��o��- ��bLFSz��A"� �a�iz��fA��f/�(��Z5.��kX��w74��*�l��a��!�W��s�\��p��<f�]X��u� �� .��m�\��S��k�J~`I��G�U��cw��A ��<��u��O��^�{��<�$7�?tQt��I��1�]O��HB�V��y�3��)�n��Z��Y�q��O<^&��D�� A&��Y6�q�F"��d�wLd��w�V>�F/b��&��q�F G�s_�$�!��Oq��GXQ��P�I`�9[��7z*��,C�bK�X?u��M)3��6��sza6#>U��D�� xz��I�$�W�O��N�l�b(��j��/�A�y��*y &i�#�U<Y��a��`H�p��i��/\Q�<!��[2��G�2��D�WSj��8�� en��6;�I��{1��k�P��-��x��Xa'��Z�/B� ��Yo��u�Y Z��|2��?4vx��i��ZX��2"�� `��9?�� S�'g��!��d(�#�0�Q�`1gx`��b�b��w3��l�� iymd<��6�l��|#-a}�Z�%a�#�"4��:�E��B7;��HKJ��c��'gs��p�A3��O�3��|��8Sg �8�i��A��/��J�Ze��)X�1i�b��$|-e�.8��j�Y��aP��Hs��f��[8��H��F�Bo�!��*� �U�`��/$��/�zK��?��~��$��_4V�J�j��Bjr��x%��z XR$2D��Go��[��H�\�}��M�Q� ��:c}� �9��>x ��c�z��j"c-lh��w"u��mu��}��J�e'�� ??/d��_vL��y��`O�F>��J��_Jk�xL0Tr�L�mKCC�Dx�c�i�){��'LU�D4��%��S�p;��]/��G��,��:��S�j��5!N9O��V9�I"�}��)�� 9��Z� R:��S�` ��]e��v8f��%��W��5�;N��"��{3��b��M��fe�N>oU_34vC[Mb��.W�khk��-O��NM?��8f[R�~��'t�>��-N�w�7� 8 O�3Z3X�$?i{��FE�mjIZk� � ��0X��_`�� a$w�?6$:��U�5��d �x��Pw��q-X#��A��M��I`��.QrX%�&��n��*'w��b��_�^9%�]��_!��*QAl4-�w��H��f5{�1�R]\�zr�T! 7�{��xe��10�*��bq��_��(�cP6��-��j��N��p)8�Q��i��).�O��z{)�8{��.6Sm^�Tx�n`�?y�2�� 0�L�\��/�?RW^�(��&#[�4Gu"J�� X��sdw��D�N�b�Kv��BO��N.��fo��qD .��l�*E� �{��n��s��9H��0�r�~��t8p��o�b�H6��17��z��T��U��hJX`2��G�!�uc��z��k�y��q��w��u�3�2��8��kh92��[7g�� hN$��_C�Jy��cH(�^ ��S-��HLmr��6�w��p� 9IRY�$��9mM/�W��H�5��y�o�F<v��8��d��Tl~h��VN�1��'W1r�U6\'��\ L8��jP��<#f��<��J�1R��6��uYqTjoA"d��X4��|�[�ZPj��&�B�K�$.rs\�d�{NHWVe�� }T�� :A(�y.��{83>��>b||��2��6�c�t�d�� 1V2T��Lun�D4p9��U5C��pJ��x�4��x�� z��[� ��CK��qs�_<�nD��!vbP��1��7�F��c��bE�_x��N�#��8r98�De��D��R�n|L��y��J��r|A�L�8�9��2 c9��nK��1�`� �d�H��K�1��P��W�;��K!� �-C-c�F�v��i.>��;p��uT�aJ$>xE��.0�3��?�U��p��[?�V5�j6�L��Q/i�6��\ ��< ��<_A�a*�Ro��F��I%��W�M�.J6|i��/� ��m��kFnd��!��J�K��7��t��S,O��BD�m��a,`DF��x��6�A�;��3��H� �'�kcKkIW��#e��2��YJ��qwbX��Ets�s��I��d�� "��l�)�z,][��QH��)��Q�;!o��w�h4��""�d�a��_O��91��jc��x��q��g:��>��nJ�4� � ��70�c��./�3��Cv<��\ ��_Fa-U>a�t��M(. �p:�C�w�e��R��Ebo��R��#a�W5m��#�]��x��5� gw�/a4`�N1�In��f�#��}�w�� 0H�.��'��U��xd?R��z/��"{b��!�Q*��_P�/��;��~��r��Y��~r�o��f-I��%�w��%ot#lj6��\��]}�_O`�z�X�p�h&��'��`h�ct�N�0Vxy/*��6��m!awh��o��l��uZ�dpC�s�(��6cd{V$��>��U[3��%�#c��:�1�D��$�

7 years, 8 months

1
0
0 / 0

Re: [hibernate-dev] Test

by Antônio Diego da Luz Silva

She held suggestions to turn better the Hibernate documentation. ________________________________ From: Antônio Diego da Luz Silva <diego-luz(a)live.com> Sent: Tuesday, July 10, 2018 5:33:20 PM To: Vlad Mihalcea Subject: Re: [hibernate-dev] Test Thanks for the answer. I sended one message before that and I haven't received answers. ________________________________ From: Vlad Mihalcea <mihalcea.vlad(a)gmail.com> Sent: Tuesday, July 10, 2018 5:28:53 PM To: Antônio Diego da Luz Silva Subject: Re: [hibernate-dev] Test Yes, we got your email. Vlad On Tue, 10 Jul 2018, 23:22 Antônio Diego da Luz Silva, <diego-luz(a)live.com<mailto:diego-luz@live.com>> wrote: Are someone receiving my messages? _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org<mailto:hibernate-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/hibernate-dev

7 years, 8 months

1
0
0 / 0

Test

by Antônio Diego da Luz Silva

Are someone receiving my messages?

7 years, 8 months

1
0
0 / 0

Javassist version alignment for Hibernate ORM 5.3 + WildFly 14...

by Scott Marlow

We would like to update WildFly (14) to Javassist 3.23.1, has anyone tried using Javassist 3.23.1 with Hibernate ORM 5.3? I'd like to know that we at least can pass the Javassist tests with the ORM testsuite, preferably on JDK11 (since that is why we want to upgrade Javassist on WildFly). Thanks, Scott

7 years, 8 months

3
6
0 / 0

AbstractStandardBasicType#getReplacement() prototype is incorrect since HHH-12054

by Guillaume Smet

Hi, When HHH-12054 was fixed (see https://github.com/hibernate/hibernate-orm/pull/2042/files), we took into account the fact that original and target could be set to LazyPropertyInitializer.UNFETCHED_PROPERTY in the AbstractStandardBasicType#getReplacement() method whereas we haven't changed the prototype of the method. Meaning we expect for instance LazyPropertyInitializer.UNFETCHED_PROPERTY to be a T, which is not the case. This led to ClassCastException such as in https://hibernate.atlassian.net/browse/HHH-12555 . To be honest, I'm wondering why we don't have more of them. We have 2 ways of fixing this issue: 1- change the getReplacement() prototype to take Object parameters and return an Object as the originating replace() method 2- move the LazyPropertyInitializer.UNFETCHED_PROPERTY logic up to replace() and make getReplacement() a "I'm sure everything is OK, now get me a clone of my original object" thing. 1- will obviously break compatibility with any user type extending AbstractStandardBasicType#getReplacement(). 2- will slightly change the meaning of replace() and getReplacement() and might lead to subtle behavior changes in user applications. 2- also means that we would have to override both replace() and getReplacement() in BlobType and allegates. I pushed a commit for 1- at https://github.com/gsmet/hibernate-orm/commit/73e66e40f3438794375451145af... so that you can fully grasp the issue. Not saying it's the path we should take. Thoughts? -- Guillaume

7 years, 8 months

2
3
0 / 0

Documentation: Cascade and orphanRemoval on associations and Inheritance

by Antônio Diego da Luz Silva

I think that will be good if it haves the advise of the need of put the cascade parameter on associations to cause the saving cascade effects on the child entitys. Also, I think that will be good if it haves too the advise of the need of maps the entities which are subclasses of entities to use them. Also, the orphanRemoval parameter not worked without the parent entity update operation with Hibernate native apis. This seems to be unlike that that is on Documentation.

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev July 2018