Re: [hibernate-dev] Using Hibernate ORM as automatic JPMS modules

Thanks for investigating this Gunnar. Some thoughts inline... On Wed, Dec 20, 2017 at 3:54 PM Gunnar Morling wrote: > * JDK 9 comes with an incomplete JTA module (java.transaction), so a > complete one must be provided via --upgrade-module-path (I'm using the >

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

this thread was "CDI integration in Hibernate ORM and the > Application scope". > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > On 21 December 2017 at 16:36, Steve Ebersole <st...@hibernate.org> wrote: > >> Awesome! Glad it worked out. >&

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

bernate > Search pass. > Here is a PR with the fixes: > https://github.com/hibernate/hibernate-orm/pull/2092 > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > On 14 December 2017 at 18:42, Steve Ebersole <st...@hibernate.org> wrote: > >> Here is

[hibernate-dev] HHH-12172 - Bintray v. OSSRH

HHH-12172 is about moving away from the JBoss Nexus repo for publishing our artifacts. There is an open question about which service to use instead - Sonatype's OSSRH (Nexus) or JFrog's Bintray (Artifactory). Personally I think Artifactory is far superior of a UI/platform. We all know Nexus

Re: [hibernate-dev] HHH-9440 - full instantiation of composites

he users having to know about > such aspects. > > Not least it would simply HHH-9440 as people wouldn't need to > understand where this can be done or not: another usability win. > > Thanks, > Sanne > > > On 18 December 2017 at 21:12, Steve Ebersole <st...@hibernate

Re: [hibernate-dev] HHH-9440 - full instantiation of composites

associations because that still injects a reference for that attribute Thoughts? On Mon, Dec 18, 2017 at 3:06 PM Steve Ebersole <st...@hibernate.org> wrote: > HHH-9440 is re > ___ hibernate-dev mailing list hibernate-dev@lists.jbo

[hibernate-dev] HHH-9440 - full instantiation of composites

HHH-9440 is re ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Keeping CI from being confusing.

Perhaps I am just dense here, but I still have no idea what you are expecting me to use as the label for my ORM jobs On Sat, Dec 16, 2017 at 12:53 PM Sanne Grinovero <sa...@hibernate.org> wrote: > On 16 December 2017 at 16:44, Steve Ebersole <st...@hibernate.org> wrote: > >

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

the javax.enterprise.inject.spi.InjectionTarget stuff Christian, I ended up going to "beans" as the package name because this supports non-CDI environments (direct instantiation) too. Not overly a fan of "beans" (overloaded term) but it was a lesser of evils. On Thu, Dec 14, 2017 at 10:57 A

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

to travel in about 3 hours, though. > > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > On 14 December 2017 at 14:46, Steve Ebersole <st...@hibernate.org> wrote: > >> I'll be on HipChat later after I get back from taking my son and daughter

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

sically the one I gave in my email. > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > On 14 December 2017 at 14:38, Steve Ebersole <st...@hibernate.org> wrote: > >> WRT to named beans, I asked Guillaume on HipChat what that is supposed to >> l

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

Steve Ebersole <st...@hibernate.org> wrote: > Its easier to cleanup > > On Thu, Dec 14, 2017 at 6:52 AM Steve Ebersole <st...@hibernate.org> > wrote: > >> There are a lot of changes to digest here, but if anyone wanted to take a >> look at this so far... >>

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

Its easier to cleanup On Thu, Dec 14, 2017 at 6:52 AM Steve Ebersole <st...@hibernate.org> wrote: > There are a lot of changes to digest here, but if anyone wanted to take a > look at this so far... > > > https://github.com/hibernate/hibernate-orm/commit/564ec55ca10c0d5d2af

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

Actually my fault. Apparently renaming the package was way too aggressive and renamed the artifact On Thu, Dec 14, 2017 at 6:40 AM Steve Ebersole <st...@hibernate.org> wrote: > Ah, nm. They change the artifact name. Boo! > > On Thu, Dec 14, 2017 at 6:39 AM Steve Ebersole <s

Re: [hibernate-dev] Interceptors and dependency injection

https://hibernate.atlassian.net/browse/HHH-11259 lists some other possibilities for things we might consider for accessing through ManagedBeanRegistry. We discussed Interceptor in Paris - I can definitely see that with some caveats/restrictions. Add it to that list or create a new sub-task. As

Re: [hibernate-dev] ManagedBeanRegistry - dependency injection support

r the > > package name `org.hibernate.resource.di` since CDI seems to be just one > > of the possible "integrations". > > > > > > Mit freundlichen Grüßen, > > > > *Christian Beikov* > > Am 13.12.2017 um 21:04 schrieb Steve Ebersole: > > >

[hibernate-dev] ManagedBeanRegistry - dependency injection support

https://hibernate.atlassian.net/browse/HHH-11259 and friends are mainly about back porting the work I did on 6.0 for the ManagedBeanRegistry abstraction over dependency injection containers. We will ship support for CDI as well as non-managed beans (things we directly instantiate). Of course

Re: [hibernate-dev] Killing hibernate-jpa-api ?

On Wed, Dec 13, 2017 at 7:05 AM Sanne Grinovero wrote: > Not really. Think of it as Deprecation: it will trigger some warnings > for end users, especially those who didn't get the "news" of moving to > the new API, and keep things working for a little longer for those >

Re: [hibernate-dev] Killing hibernate-jpa-api ?

Considering the spec contracts are defined by the EG under the JCP, I'm not sure where we ever stood legally with publishing this under any other license. Either way, I am not concerned about the license aspect - I think it is a reasonable expectation that if I am using a jar produced by a spec

Re: [hibernate-dev] HHH-12146 - subclass-specific caching

I just went ahead and did the same we do for the other modules. On Tue, Dec 12, 2017 at 9:47 PM Steve Ebersole <st...@hibernate.org> wrote: > Vlad, these changes cause some failures in the userguide tests[1]. This > is not completely unexpected since they seem to do cach

Re: [hibernate-dev] HHH-12146 - subclass-specific caching

t;JPA static metamodel" classes. They either do not get generated, or at the very least the build is not adding them to the project in a way that IntelliJ import picks them up. [1] http://ci.hibernate.org/job/hibernate-orm-5.3-steve/28/testReport/ On Tue, Dec 12, 2017 at 9:27 PM Steve Eb

Re: [hibernate-dev] HHH-12146 - subclass-specific caching

e > regions yet be able to exclude specific types from the (shared) region > of a type hierarchy. > > Sounds great. > > On 12 December 2017 at 18:45, Steve Ebersole <st...@hibernate.org> wrote: > > And btw, this *has* to happen. JPA requires it and the 2.2 TCK tests for &

Re: [hibernate-dev] Including Hibernate Spatial & dependencies in the WildFly modules

I think that's a great idea. Was just an oversight on my part. On Tue, Dec 12, 2017 at 7:19 PM Sanne Grinovero wrote: > Hi all, > > there's a feature request about including the (currently missing) bits > to be able to use the Spatial queries in WildFly: > -

Re: [hibernate-dev] HHH-12146 - subclass-specific caching

And btw, this *has* to happen. JPA requires it and the 2.2 TCK tests for it. So there is no "keep allowing caching at the root-level" option here On Tue, Dec 12, 2017 at 12:44 PM Steve Ebersole <st...@hibernate.org> wrote: > Its not any different than `#get( Leg

Re: [hibernate-dev] HHH-12146 - subclass-specific caching

Incidentally while writing this example I realize that such a mapping > could trigger issues even with existing caching options. > > Thanks, > Sanne > > > > On 12 December 2017 at 14:49, Steve Ebersole <st...@hibernate.org> wrote: > > HHH-12146 is about being able

[hibernate-dev] HHH-12146 - subclass-specific caching

HHH-12146 is about being able to enable/disable caching at various levels in an entity hierarchy. E.g., given a hierarchy such as `Person` and `Company` both extending `LegalEntity`, this would allow users to say that only `Company` should be cached but not `Person` nor any other `LegalEntity`

Re: [hibernate-dev] Realising the JavaDoc jars as well

Because we decided it is generally not useful to release jars of javadocs that do not inter-link, which is why we spent so much effort producing the aggregated javadocs. On Mon, Dec 11, 2017 at 1:12 PM Vlad Mihalcea wrote: > Hi, > > I've noticed this Pull Request which

Re: [hibernate-dev] Getting rid of our specific JavaDoc CSS?

Now that I've looked more, I agree. That standard one is much closer to the feel of the new website/blogs On Thu, Nov 30, 2017 at 12:35 PM Davide D'Alto wrote: > Sounds good to me. > > > On Thu, Nov 30, 2017 at 3:11 PM, Guillaume Smet > wrote:

Re: [hibernate-dev] Getting rid of our specific JavaDoc CSS?

In general I agree. This was a big hassle when Oracle re-did the JavaDoc generation a few releases ago (was it 6?). IMO though its still a nice touch to "skin" the coloring in the nav bars, main header, footer etc. I have not looked into how much work just those limited changes would be

Re: [hibernate-dev] JPA Compliance

n 28 November 2017 at 05:44, Vlad Mihalcea <mihalcea.v...@gmail.com> >> wrote: >> >>> I don't understand what is the requirement for the @Bag annotation and >>> the `hibernate.jpa.compliance=list` setting. >>> >>> From the JPA spec, only if we pr

Re: [hibernate-dev] JPA Compliance

2017 at 4:54 AM andrea boriero <and...@hibernate.org> wrote: > On 24 November 2017 at 17:39, Steve Ebersole <st...@hibernate.org> wrote: > >> Andrea, SF is a EMF. Unwrapping simply returns the same instance. >> > > yes but has you pointed out due to the bo

Re: [hibernate-dev] HHH-12125 - @GeneratedValue & 5.3

you suggested. > > +1 > > Vlad > > On Sat, Nov 25, 2017 at 6:18 PM, Steve Ebersole <st...@hibernate.org> > wrote: > >> The background is all in the Jira, but the crux is this... it is better to >> allow a user to do this: >> >>

Re: [hibernate-dev] HHH-12125 - @GeneratedValue & 5.3

Actually I just realized I was a little smarter than this back then :D `IdGeneratorStrategyInterpreter#determineGeneratorName` is actually passed the GenerationType and a "parameter object". I can add access to the generator name to the parameter object. On Sat, Nov 25, 2017 at 10:1

[hibernate-dev] HHH-12125 - @GeneratedValue & 5.3

The background is all in the Jira, but the crux is this... it is better to allow a user to do this: @GeneratedValue( strategy=SEQUENCE, generator="my_seq") rather than: @GeneratedValue( strategy=SEQUENCE, generator="my_seq") @SequenceGenerator( name="my_seq", sequenceName="my_seq" )

Re: [hibernate-dev] JPA Compliance

se compatibility methods according to their needs. >> >> E.g. Maybe someone wants the Strict JPA mode but with just 2 differences; >> >> - don't throw exception when closing the ENG twice >> - use the native Hibernate FlushMode.AUTO instead of the JPA one. >>

Re: [hibernate-dev] JPA Compliance

tions according the JPA spec" as opposed to "here is a class I will provide that will tell will treat transactions according to the JPA spec". ***Or have multiple settings following how I started with `hibernate.query.jpaql_strict_compliance`*** On Fri, Nov 24, 2017 at 11:39 A

[hibernate-dev] Auto run CI job

I am trying to set up a CI job against my personal ORM fork to automatically trigger on push. I follow the configuration from jobs against the main ORM repo which work, but mine does not. I assume it has something to do with it being a personal branch. Is there something I need to do on my repo

Re: [hibernate-dev] Relaxing JIRA assignment restrictions

to fully research. I looked quickly but Jira's permissions are not easy to sift through imo On Tue, Nov 21, 2017 at 9:39 AM Sanne Grinovero <sa...@hibernate.org> wrote: > On 21 November 2017 at 15:33, Steve Ebersole <st...@hibernate.org> wrote: > > Because we allow certai

Re: [hibernate-dev] Relaxing JIRA assignment restrictions

Because we allow certain elevated privileges to people who can be assigned issues. On Tue, Nov 21, 2017, 6:57 AM Sanne Grinovero wrote: > 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

Re: [hibernate-dev] Legacy positional params and JPA "positional" params

inted out this for users will be > another upgrade concer , so may be for a 5.3 it is better to mantain the > zero-based style. > > On 18 November 2017 at 19:18, Steve Ebersole <st...@hibernate.org> wrote: > >> Another thing that comes up is parameters and native queries. In nati

Re: [hibernate-dev] Legacy positional params and JPA "positional" params

( 1, "Steve" ); session.createNativeQuery( "... where a.name = ?1" ).setParameter( 1, "Steve" ); The only down side to this is yet another upgrade concern for users. Thoughts? On Fri, Nov 17, 2017 at 12:15 PM Sanne Grinovero <sa...@hibernate.org> wrote: >

[hibernate-dev] Legacy positional params and JPA "positional" params

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

Re: [hibernate-dev] HHH-10418 and Infinispan

.issuetabpanels:comment-tabpanel#comment-83441 >> >> On Thu, Nov 16, 2017 at 6:28 PM, Steve Ebersole <st...@hibernate.org> >> wrote: >> >>> No that is currently broken. See >>> https://hibernate.atlassian.net/browse/HHH-11356 >>> >>&g

Re: [hibernate-dev] HHH-10418 and Infinispan

No that is currently broken. See https://hibernate.atlassian.net/browse/HHH-11356 This won't be fixed in 5.x as fixing it required significant changes to the caching SPIs to resolve. On Thu, Nov 16, 2017 at 8:10 PM Gail Badner wrote: > Steve/Radim, > > Is it OK if an

Re: [hibernate-dev] JPA Compliance

n trying to close the EMF twice > - native: we bend the rule where we don't agree with the standard > > Maybe we should expose all those cases and group them in some interface to > allow the user to customize the level of compliance they need. > > Vlad > > On Thu, Nov 16, 2017 at

Re: [hibernate-dev] JPA Compliance

t; I noticed that the isJpaBootstrap method is deprecated. Was it intended > to be removed in 6.0? > > Vlad > > On Thu, Nov 16, 2017 at 6:21 PM, Steve Ebersole <st...@hibernate.org> > wrote: > >> Part of 5.2 was merging the JPA contracts into the corresponding H

[hibernate-dev] JPA Compliance

Part of 5.2 was merging the JPA contracts into the corresponding Hibernate ones. So, e.g., we no longer "wrap" a SessionFactory in an impl of EntityManagerFactory - instead, SessionFactory now extends EntityManagerFactory. This caused a few problems that we handled as they came up. In working

Re: [hibernate-dev] HHH-12007

I'll assume you mean AbstractEntityTuplizer#persistTransientEntity, as called from IncrediblySillyJpaMapsIdMappedIdentifierValueMarshaller via org.hibernate.tuple.entity.AbstractEntityTuplizer#determineEntityIdPersistIfNecessary[1] - if that's not correct let us know. With that assumption... It

Re: [hibernate-dev] Natural IDs and inheritance (HHH-12085)

Sorry, I misunderstood what you were asking. TBH I'm not sure what to think of this yet. On Fri, Nov 10, 2017 at 3:08 PM Steve Ebersole <st...@hibernate.org> wrote: > https://hibernate.atlassian.net/browse/HHH-7129 > > > On Fri, Nov 10, 2017 at 2:37 PM Gail Badner <gbad

Re: [hibernate-dev] Natural IDs and inheritance (HHH-12085)

https://hibernate.atlassian.net/browse/HHH-7129 On Fri, Nov 10, 2017 at 2:37 PM Gail Badner wrote: > 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

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

rcanoonline.com> > wrote: > > > On 10/26/2017 03:40 PM, Steve Ebersole wrote: > > > I can understand that. > > > > > > There is a room in our HipChat that we allow anonymous/guest access, no > > > need for an account. The only thing yo

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

On Thu, Oct 26, 2017 at 1:25 PM Robert Marcano <rob...@marcanoonline.com> wrote: > On 10/26/2017 12:03 PM, Steve Ebersole wrote: > > Why would we? What's the benefit over what we have? > > > > > > As someone that jumps from forums to forums when need to discuss b

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

at team? > > Just out of curiosity from someone that has just 2 weeks subscribed to > this mailing list. Why not try Riot/Matrix http://riot.im/ ? > > > > > That way we *could* all try it out, on the other hand since we have no > > choice we don't really need to evalua

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

Again, for the EAP no. For the real migration (~6 months) yes On Thu, Oct 26, 2017 at 9:54 AM Sanne Grinovero wrote: > On 26 October 2017 at 15:52, Gunnar Morling wrote: > > Does anyone know whether our chat histories will be transferred? > > Their

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

nths. HTH On Thu, Oct 26, 2017 at 8:56 AM Sanne Grinovero <sa...@hibernate.org> wrote: > On 26 October 2017 at 14:45, Steve Ebersole <st...@hibernate.org> wrote: > > Right, ultimately we won't have a choice.. they will simply be moving all > > HipChat cloud instances

Re: [hibernate-dev] Fwd: You're on the Stride waitlist!

On 24 October 2017 at 19:34, Steve Ebersole <st...@hibernate.org> wrote: > > I've signed up for a "test drive" account on Atlassian's Stride server. > > Stride is their replacement for HipChat. > > > > -- Forwarded message - > > From: S

Re: [hibernate-dev] SynchronizationRegistry: expose read (lookup) operations?

e the JTA one is, so it may not make much difference which object > carries the functionality for your case? > > Jonathan. > > On 25/10/17 16:25, Steve Ebersole wrote: > > Also, unless I am mistaken `TransactionSynchronizationRegistry#put` > > works on the

Re: [hibernate-dev] SynchronizationRegistry: expose read (lookup) operations?

ed, Oct 25, 2017 at 10:24 AM Steve Ebersole <st...@hibernate.org> wrote: > Jonathan, we aren't going to be exposing this or using this > via TransactionSynchronizationRegistry. Your comment about a "dummy" in > the JDBC txn case is exactly why. We already have such an abst

Re: [hibernate-dev] SynchronizationRegistry: expose read (lookup) operations?

Jonathan, we aren't going to be exposing this or using this via TransactionSynchronizationRegistry. Your comment about a "dummy" in the JDBC txn case is exactly why. We already have such an abstraction : SynchronizationRegistry On Wed, Oct 25, 2017 at 10:22 AM Steve Eb

Re: [hibernate-dev] SynchronizationRegistry: expose read (lookup) operations?

> Yes that would work for me, but thinking about the implementation it > implies you'd need to hold on to both a Set and a Map, and then we'd > be exposed to silly usage like people adding the same synchronization > twice in two different ways? > Does it? Nothing in the SPI requires us to store

Re: [hibernate-dev] SynchronizationRegistry: expose read (lookup) operations?

Yes, but that is only available in JTA environments. Ours is available no matter what kind of transaction environment we are executing in. Sanne, how about instead a separate registration method accepting a "registration key"? E.g.: public interface SynchronizationRegistry extends Serializable

[hibernate-dev] Fwd: You're on the Stride waitlist!

I've signed up for a "test drive" account on Atlassian's Stride server. Stride is their replacement for HipChat. -- Forwarded message - From: Stride by Atlassian Date: Tue, Oct 24, 2017, 1:32 PM Subject: You're on the Stride waitlist! To:

Re: [hibernate-dev] Programmatic entity mapping API

On Tue, Oct 24, 2017 at 8:38 AM Gunnar Morling wrote: > Sure. But it's great to know that you'd find it useful and can imagine > adding it. Thanks! > In fact we have similar requirement in ORM itself for hibernate-envers, but again the initial expectation is supporting

Re: [hibernate-dev] Programmatic entity mapping API

Of course you pick the easy case to illustrate :) A single entity with nothing but basic attributes or self-referential associations is going to be relatively simple. The trickier stuff is adding 2 entities with association between them, "property-ref" FKs, etc. Then your fluent API is not so

Re: [hibernate-dev] Question..

different empty-creation decisions for each embedded usage of that embeddable. On Tue, Oct 17, 2017, 9:42 AM Steve Ebersole <st...@hibernate.org> wrote: > On Tue, Oct 17, 2017 at 12:55 AM Gail Badner <gbad...@redhat.com> wrote: > >> > >> > WRT to the condition check,

Re: [hibernate-dev] Question..

On Tue, Oct 17, 2017 at 12:55 AM Gail Badner wrote: > > > > WRT to the condition check, you suggest to "compare a primitive value in > a > > composite with the default for the primitive type (e.g, comparing an int > > value with 0 instead of null)". That's not the best

Re: [hibernate-dev] Statements leaks when using JPA StoredProcedureQuery API

If only. I seriously doubt we can get that approach as the solution through the EG, but we'll see On Mon, Oct 16, 2017, 1:12 PM Robert Marcano <rob...@marcanoonline.com> wrote: > On 10/16/2017 10:13 AM, Steve Ebersole wrote: > > On Mon, Oct 16, 2017 at 9:00 AM Robe

Re: [hibernate-dev] Statements leaks when using JPA StoredProcedureQuery API

Sweet, thanks On Mon, Oct 16, 2017 at 10:59 AM Robert Marcano wrote: > On 10/11/2017 03:15 PM, Vlad Mihalcea wrote: > > You can open a GitHub issue for JPA. Meanwhile, you can work around it > > as you suggested. > > Opened an issue on JPA spec

Re: [hibernate-dev] Statements leaks when using JPA StoredProcedureQuery API

On Mon, Oct 16, 2017 at 9:00 AM Robert Marcano wrote: > No, I know implicitly closing the JDBC statement is not possible with > only the current CallableStatement API. There is no way to know if the > client code needs or read all possible outputs from the stored >

Re: [hibernate-dev] Question..

On Fri, Oct 13, 2017, 3:35 PM Gail Badner <gbad...@redhat.com> wrote: > Hi Steve, > > I'm circling back to this. Please see below... > > On Sat, Sep 2, 2017 at 8:47 AM, Steve Ebersole <st...@hibernate.org> > wrote: > > I don't have the original em

Re: [hibernate-dev]

ot related to your question? > > Thanks, > Sanne > > > > On 13 October 2017 at 14:31, Steve Ebersole <st...@hibernate.org> wrote: > > Hibernate mappings define a feature to allow a secondary table (`` > > in hbm terms) to be defined as not joined via : ` &g

Re: [hibernate-dev] Statements leaks when using JPA StoredProcedureQuery API

The conceptualization of a Query for both Hibernate and JPA is that you execute it and get back the result of that execution: a List, a single result, a ScrollableResult, a Stream, etc. Yet then JPA throws in StoredProcedureQuery which is completely different conceptually. Here you execute and

[hibernate-dev]

Hibernate mappings define a feature to allow a secondary table (`` in hbm terms) to be defined as not joined via : ``. This actually creates a subsequent select to load the data from the secondary table. I am trying to figure out how to best incorporate this into the paradigm for JDBC statement

[hibernate-dev] @db.dialect@ - yet again

I just upgraded to IntelliJ 2017.3 EAP and am back to this frustrating "Dialect class not found: @db.dialect@" problem. I run the `processTestResources` (or `compile`, does not matter) and then when I try to run a test in the IDE I get this error. What is the magic incantation I am missing?

Re: [hibernate-dev] New layout for in.relation.to

+1 Great job (again) On Fri, Sep 29, 2017 at 3:36 PM Chris Cranford wrote: > Was curious if we would carry the new style to in.relation.to. > It looks superb. > > Chris > > On 09/29/2017 01:57 PM, Guillaume Smet wrote: > > Hi! > > > > I converted in.relation.to to the new

Re: [hibernate-dev] ORM release process

To be honest, I think that is perfect process Guillaume. I can now define all that content and information in one place, which is a huge win. Which make me think of a future nice-to-have we could consider... to drive the release announcements (blog, emails, twitter, etc) from the content of a

Re: [hibernate-dev] New layout for the website

That was a rich joke Sanne... On Thu, Sep 28, 2017 at 9:27 AM Sanne Grinovero <sa...@hibernate.org> wrote: > On 28 September 2017 at 15:10, Steve Ebersole <st...@hibernate.org> wrote: > > If you really like the gold, why not try making that whole banner gol

Re: [hibernate-dev] New layout for the website

; >> On 09/28/2017 09:32 AM, Guillaume Smet wrote: >> > On Thu, Sep 28, 2017 at 3:23 PM, Guillaume Smet < >> guillaume.s...@gmail.com> >> > wrote: >> > >> >> On Thu, Sep 28, 2017 at 2:11 PM, Steve Ebersole <st...@hibernate.org> >>

Re: [hibernate-dev] New layout for the website

P.S. Sorry, I would TIAS but my CSS skills are slight better than those of an ocelot. On Thu, Sep 28, 2017 at 8:55 AM Steve Ebersole <st...@hibernate.org> wrote: > Ah, so its retro-modern ;) > > So what happens if you remove the gold/light-gray completely and just use

Re: [hibernate-dev] New layout for the website

u, Sep 28, 2017 at 3:23 PM, Guillaume Smet <guillaume.s...@gmail.com> > wrote: > >> On Thu, Sep 28, 2017 at 2:11 PM, Steve Ebersole <st...@hibernate.org> >> wrote: >> >>> Overall the new design looks amazing. I do agree with Andrea about the >>

Re: [hibernate-dev] [Search and more] What is new in a give release

The question is not about whether to have that information. The question is whether a one row table spanning horizontally across the screen is the best presentation for that info. On Thu, Sep 28, 2017 at 8:01 AM Sanne Grinovero <sa...@hibernate.org> wrote: > On 28 September 2017 at 13:

Re: [hibernate-dev] [Search and more] What is new in a give release

Do y'all really think it makes sense to have JPA versions in this ORM "compatibility matrix"? My concern is that it is more involved (as we then try to convey in the section below that matrix) than a cell in a matrix/table with just a version number. If we end up treating JPA compatibility

Re: [hibernate-dev] "Hibernate Types" project

I'm not so sure a single "extras" artifact/module makes the most sense though. Since some involve pulling in driver jars - I think (if we do this) we ought to have `hibernate-extras-base` as well as db-specific extensions (`hibernate-extras-pgsql`, ...). We had a similar discussion recently on

Re: [hibernate-dev] New layout for the website

Overall the new design looks amazing. I do agree with Andrea about the gold backgrounds - that looks anything but modern and does not match the rest of the site design imo. For another iteration... "Getting started" is another group of information that is version specific. A minor thing that I

Re: [hibernate-dev] JVM metadata costs vs the use of inheritance across Logger interfaces

mber 2017 at 12:47, Steve Ebersole <st...@hibernate.org> wrote: > > I'm missing something. IIUC the discovery was that, e.g., having > something > > like `BaseHibernateSearchLogger` in module-A and then something like > > `RealLogger` in module-B that extends `BaseHibernate

Re: [hibernate-dev] JVM metadata costs vs the use of inheritance across Logger interfaces

I'm missing something. IIUC the discovery was that, e.g., having something like `BaseHibernateSearchLogger` in module-A and then something like `RealLogger` in module-B that extends `BaseHibernateSearchLogger` causes extra space to be taken up within the VM memory space. Yet this is still

Re: [hibernate-dev] [Search and more] What is new in a give release

And again I just wanted to say thanks, great job. It works much better I think, no matter these nit-picky things On Fri, Sep 22, 2017 at 11:00 AM Steve Ebersole <st...@hibernate.org> wrote: > I think he is saying what I was saying... make the nav links point to the > la

Re: [hibernate-dev] [Search and more] What is new in a give release

I think he is saying what I was saying... make the nav links point to the latest version, but with easy nav from there to list of all series/family/whatever On Fri, Sep 22, 2017 at 10:25 AM Yoann Rodiere wrote: > Ok, this will never end... It was good to merge less than

Re: [hibernate-dev] Number of SQL statements

For such assertions in the Hibernate test suite we generally rely on Hibernate Statistics. I also really like Vlad's solution. On Fri, Sep 22, 2017 at 10:19 AM Sanne Grinovero wrote: > Hi Thomas, > > I can't answer your question - will leave that to the people working >

Re: [hibernate-dev] New `noorm-admins` team on Github & proposal for group restructuring

+1 On Fri, Sep 15, 2017, 9:10 AM Sanne Grinovero wrote: > I created a new team on Github and am giving it admin privileges to > Validator, Search, OGM, and the related support repositories (JPQL > parser, HCANN). > > This is to give some selected members admin privileges on

Re: [hibernate-dev] How is LogicalConnectionImplementor#makeShareableCopy intended to be used?

However, as it is part of the SPI its probably better to deprecate it and we can remove it in 6.0 On Thu, Sep 14, 2017 at 9:05 AM Steve Ebersole <st...@hibernate.org> wrote: > It was originally intended for "shared Session" handling, but we ended up > handling this d

Re: [hibernate-dev] How is LogicalConnectionImplementor#makeShareableCopy intended to be used?

It was originally intended for "shared Session" handling, but we ended up handling this differently. I believe this can go away. On Tue, Sep 12, 2017 at 2:42 PM Gail Badner wrote: > LogicalConnectionImplementor#makeShareableCopy [1] doesn't seem to be used > by anything. >

Re: [hibernate-dev] [Search and more] What is new in a give release

but when we copy the docs to JBoss, we also copy the > User Guide as index.html as well. This will allow our users to retain > bookmarks they've created since we published the new User Guide. > > Let me know which one do you prefer. > Vlad > > On Thu, Sep 14, 2017 at 3:34 PM,

Re: [hibernate-dev] [Search and more] What is new in a give release

Yoann, First thanks for the work on this. I think it looks worlds better. A few minor things: 1. Not sure of the source for this, but can we fix these doc link for 5.2 from ` https://docs.jboss.org/hibernate/stable/orm/userguide/html_single/Hibernate_User_Guide.html` to

Re: [hibernate-dev] ORM 5.2 issue with getInterceptor() not being a true getter

I'm fine with that. That method really does not fit with the paradigm which needs that pulse. On Mon, Sep 11, 2017 at 1:36 PM Sanne Grinovero wrote: > On 11 September 2017 at 16:14, Guillaume Smet > wrote: > > Hi! > > > > Any comment on this? >

Re: [hibernate-dev] [Search and more] What is new in a give release

On Fri, Sep 8, 2017 at 9:45 AM Yoann Rodiere wrote: > Steve, > > If I understood correctly, the main difference between what I did and what > you want is you don't want a "hub" pointing to different versions, you want > to redirect to the page for the latest version, and

Re: [hibernate-dev] [Search and more] What is new in a give release

sted sections from various > > blog posts. > > A list of all releases in this series. > > > > What I didn't do, but could make sense: > > > > add a sub-menu element under "Releases" for each series > > link to the documentation for each of the lat

Re: [hibernate-dev] CDI / ORM / WildFly / Search integration plumbing

it requires you to build Hibernate ORM >> >> > master first, as I switched the dependencies to use Hibernate ORM >> >> > 5.2.11-SNAPSHOT (It otherwise won't work on WildFly 11 as it requires >> >> > HHH-11950 >> >> > >> >>

Re: [hibernate-dev] [Search and more] What is new in a give release

This is something I brought up ages ago wrt ORM. I wanted something (although ideally integrated with the "more version friendly" hibernate.org design) similar to what I did atm on the ORM GitHub wiki. For example, for 5.2 we have: -

Re: [hibernate-dev] Question..

;empty" composite issues". > > You can ignore the first message and just read the 2nd one. > > Thanks, > Gail > > On Fri, Sep 1, 2017 at 12:53 PM, Steve Ebersole <st...@hibernate.org> > wrote: > >> You asked me to comment on an email, I'm sorry but I

<    1   2   3   4   5   6   7   8   9   10   >