Relaxing JIRA assignment restrictions
by Sanne Grinovero
Hi all,
I'm being frequently asked to add new contributors to "the right
groups" on JIRA just for the sake of being able to assign issues to
them.
I'm not sure why it's useful to prevent this for anyone to do being
able to do this, and also I suspect some people might be more inclined
to "just do it" if they had a clearer, more welcoming approach to
signal that they're looking into the issue themselves.
Any objections to relax this requirement?
Thanks,
Sanne
8 years, 1 month
Legacy positional params and JPA "positional" params
by Steve Ebersole
I wont bore everyone with the history here, but long story short is that we
need to start treating JPA "positional" parameters as positional in the
`javax.persistence.Parameter#getPosition` sense. Even though there is
nothing positional about JPA's positional parameters, this has moved from a
philosophical discussion to a practical one as the JPA 2.2 TCK is testing
this, whereas older ones did not
To do that however, we need to drop our older positional parameter
support. That feature has been deprecated for quite some time now. Unless
there are objections, I will plan on dropping that in 5.3
8 years, 1 month
Re: [hibernate-dev] JDK 10 b29 Early Access is available on jdk.java.net
by Gunnar Morling
Hi Dalibor,
2017-11-20 10:24 GMT+01:00 dalibor topic <dalibor.topic(a)oracle.com>:
>
>
> On 19.11.2017 13:03, Gunnar Morling wrote:
>
>> Hi Rory,
>>
>> While updating my JDK API change report generator [1] for JDK 10, I
>> noticed that three modules aren't available in JDK 10 as of b32 which
>> existed in JDK 9:
>>
>> * jdk.management.cmm
>> * jdk.management.jfr
>> * jdk.management.resource
>>
>
> Hi Gunnar,
>
> the modules are there for (still) commercial features like the Java Flight
> Recorder. Commercial features not made available in JDK early access builds.
>
I see, thanks.
But why is then that other modules also marked as commercial in their
JavaDoc are part of the EA build (e.g. "jdk.jfr")? And why are the
non-available modules nevertheless parts of the API docs published at
http://download.java.net/java/jdk10/docs/api? It seems a bit inconsistent.
Really looking forward to the open-sourced JFR + MC btw., that's a
fantastic development!
>
> cheers,
> dalibor topic
>
>
>> Interestingly, these modules are contained in the published JDK 10
>> JavaDoc [3], but I couldn't find the jmod files in the "jmods" directory of
>> the preview build.
>>
>> Thanks,
>>
>> --Gunnar
>>
>> [1] https://github.com/gunnarmorling/jdkapidiff
>> [2] http://jdk.java.net/10/release-notes
>> [3] http://download.java.net/java/jdk10/docs/api/jdk.management.
>> cmm-summary.html
>>
>>
>>
>>
>> 2017-11-03 11:20 GMT+01:00 Rory O'Donnell <rory.odonnell(a)oracle.com
>> <mailto:rory.odonnell@oracle.com>>:
>>
>> Hi Sanne,
>>
>> JDK 10 Early Access build 29 is available at : - jdk.java.net/10/
>> <http://jdk.java.net/10/>
>>
>>
>> JDK 10 Early Access Release Notes are available [1]
>>
>> JDK 10 Schedule, Status & Features are available [2]
>>
>>
>> Notes
>>
>> * OpenJDK EA binaries will be available at a later date.
>> * Oracle has proposed: Newer version-string scheme for the Java SE
>> Platform and the JDK
>> o Please see Mark Reinhold's proposal [3] , feedback via the
>> mailing list to Mark please.
>>
>> <http://openjdk.java.net/projects/jdk8u/releases/8u162.html
>> <http://openjdk.java.net/projects/jdk8u/releases/8u162.html>>
>>
>> Feedback - If you have suggestions or encounter bugs, please submit
>> them
>> using the usual Java SE bug-reporting channel.
>> Be sure to include complete version information from the output of the
>> |java --version| command.
>>
>> Regards,
>> Rory
>>
>> [1] http://jdk.java.net/10/release-notes
>> <http://jdk.java.net/10/release-notes>
>> [2] http://openjdk.java.net/projects/jdk/10/
>> <http://openjdk.java.net/projects/jdk/10/>
>> [3]
>> http://mail.openjdk.java.net/pipermail/jdk-dev/2017-November
>> /000089.html
>> <http://mail.openjdk.java.net/pipermail/jdk-dev/2017-Novembe
>> r/000089.html>
>>
>> --
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> <https://lists.jboss.org/mailman/listinfo/hibernate-dev>
>>
>>
>>
> --
> <http://www.oracle.com> Dalibor Topic | Principal Product Manager
> Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
> <tel:+491737185961>
>
> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
>
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
>
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>
> <http://www.oracle.com/commitment> Oracle is committed to developing
> practices and products that help protect the environment
>
8 years, 1 month
HHH-10418 and Infinispan
by Gail Badner
Steve/Radim,
Is it OK if an entity and collection region have the same name, they will
use the same AdvancedCache? I realize that the key will be different (as
long as hibernate.cache.keys_factory != simple).
I'm assuming they use the same access strategies, etc. I know there would
be problems if they didn't (HHH-10707/HHH-11356).
I've been looking at how things are implemented in 5.2 to avoid the
ClassCacheException when an entity region and collection region has the
same name.
I see that org.hibernate.internal.CacheImpl has a separate map for each
type of cache (i.e., entity, collection, natural-id). [1]
I also see that org.hibernate.cache.infinispan.InfinispanRegionFactory#
buildEntityRegion and #buildCollectionRegion both call #getCache. [2]
#getCache checks to see if there is already a cache with the specified
regionName, but does not take the type (i.e., entity, collection,
natural-id) into account. If there is already a cache with that region
name, it will be used.
In other words, it seems that if an entity and collection region have the
same name, they will use the same AdvancedCache.
I just want to confirm that this is intended and there is no problem with
having different types of data in the same AdvancedCache.
Thanks,
Gail
[1]
https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src...
[2]
https://github.com/hibernate/hibernate-orm/blob/master/hibernate-infinisp...
8 years, 1 month
HHH-12007
by Gail Badner
Hi Steve,
The test case for HHH-12087 shows that executing a query that has a
transient entity bound to it will cause that transient entity to be
persisted.
Please take a look at the PR for HHH-12087:
https://github.com/hibernate/hibernate-orm/pull/2054
It removes IncrediblySillyJpaMapsIdMappedIdentifierValueMarshaller#persistTransientEntity
and, AFAICT, doesn't break anything.
Thanks,
Gail
8 years, 1 month
Natural IDs and inheritance (HHH-12085)
by Gail Badner
IIUC, a natural ID should apply to an entire entity hierarchy. Is that true?
HHH-12085 reports a "bug" when a natural ID is mapped on a non-root
entity. Is that expected? Is this something we may want to support in
the future?
Thanks,
Gail
8 years, 1 month
