Hi,
FYI, I posted the last PR of the OGM series today:
https://github.com/hibernate/hibernate-orm/pull/1997 .
I expect some discussion about it in the next few days as it's not that
straightforward.
--
Guillaume
On Fri, Aug 25, 2017 at 7:24 PM, Gail Badner wrote:
> That's fine. I can wait fo
Hi,
In OGM tests, we have a lot of warnings on this sort of constructs:
NativeQuery query = session.createNativeQuery( nativeQuery ).addEntity(
OscarWildePoem.class );
because addEntity() comes from SQLQuery and SQLQuery is deprecated.
I don't think it's a good thing for our users as they have a
Hi Gail,
no I haven't opened a WFLY issue as I'm not sure if this is an issue.
There seems to be some inconsistency and it certainly breaks some
Hibernate Search tests but we could of course adapt things to the new
reality.. if this is how it's meant to be.
The source code of the ExtendedBeanMa
On 29 August 2017 at 20:28, Steve Ebersole wrote:
> Then I think we should update 5.2 as well, but that creates an interesting
> concern in that the published artifact name would change if I understand
> correctly because it would change the artifact's classifier from
> `wildfly-10-dist` to `wildf
On Wed, Aug 30, 2017 at 10:38 AM Sanne Grinovero
wrote:
> On 29 August 2017 at 20:28, Steve Ebersole wrote:
> > Then I think we should update 5.2 as well, but that creates an
> interesting
> > concern in that the published artifact name would change if I understand
> > correctly because it would
On 30 August 2017 at 16:53, Steve Ebersole wrote:
>
> On Wed, Aug 30, 2017 at 10:38 AM Sanne Grinovero
> wrote:
>>
>> On 29 August 2017 at 20:28, Steve Ebersole wrote:
>> > Then I think we should update 5.2 as well, but that creates an
>> > interesting
>> > concern in that the published artifact
As I said initially, I agree that 5.2 should be updated. We just need to
be clear about the ramifications.
On Wed, Aug 30, 2017 at 11:14 AM Sanne Grinovero
wrote:
> On 30 August 2017 at 16:53, Steve Ebersole wrote:
> >
> > On Wed, Aug 30, 2017 at 10:38 AM Sanne Grinovero
> > wrote:
> >>
> >>
After WildFly 11 and EAP 7.1.0.GA is released, or shortly thereafter, ORM
5.1 will no longer be publicly released, so it really is not worthwhile to
backport this to 5.1.
Sorry for asking, I didn't think it through before sending.
On Wed, Aug 30, 2017 at 9:26 AM, Steve Ebersole wrote:
> As I sa
We have discussed this deprecation strategy ad nauseam. See any of the
previous discussion on the dev list (as recent as just a few weeks ago)
On Wed, Aug 30, 2017 at 11:39 AM Guillaume Smet
wrote:
> Hi,
>
> In OGM tests, we have a lot of warnings on this sort of constructs:
> NativeQuery query
On 08/30/2017 11:27 AM, Sanne Grinovero wrote:
> Hi Gail,
>
> no I haven't opened a WFLY issue as I'm not sure if this is an issue.
>
> There seems to be some inconsistency and it certainly breaks some
> Hibernate Search tests but we could of course adapt things to the new
> reality.. if this is
That's a good question.
There are some methods which don't have a replacement in JPA so we should
probably move to some subclass and remove the deprecated flag.
Vlad
On Wed, Aug 30, 2017 at 5:59 PM, Guillaume Smet
wrote:
> Hi,
>
> In OGM tests, we have a lot of warnings on this sort of constru
The whole purpose of ExtendedBeanManager is cases where the BeanManager is
not available when Hibernate boots (in other words when Hibernate is told
which to use) . This is a way to give Hibernate a callback when the
BeanManager is available. IMO this ExtendedBeanManager implementing
BeanManager
12 matches
Mail list logo
