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

[Emmanuel Bernard]

Hey all,

I was trying to answer the following question, what is roughly new between 5.6, 
5.7 and 5.8 (minor releases)?

My first reflex was to go to http://hibernate.org/search/downloads/ 
 to read about the onliner per release. 
Except it’s a onliner per micro release and “minor adjustments” for 5.6.3.Final 
gave me literally no info whatsoever.

My second reflex was to go to http://hibernate.org/search/roadmap/ 
 to find a historical entry about older 
versions and the main changes in bullet points. No luck. It only talks about 
the future.

My third reflex was to go to http://in.relation.to/hibernate-search/ 
 I ended up giving up midway page 2 of 
the list of blog entries. It’s a mix of simultaneous parallel releases with 
what’s new since the last CR or the last micro kind of reports and gave up in 
dismay at the energy I would have to spend to extract what’s new for a full 
minor release.

I did exaggerate a bit the third point but I did give up. We need somewhere a 
summary page of what’s new per minor releases. I think the roadmap page could 
be the host.
Likewise, we might need a oneliner entry in the download section (per release) 
that points to this minor release summary.

Thoughts?

Speaking of roadmap:
- HV roadmap is massively out of date
- OGM is lying a bit on the future but at least has the past summary I was 
talking about
- Search has a good future roadmap but no past

Emmanuek
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Yoann Rodiere]

Hey,

About Search, true, the information is somewhat hidden in many blog posts.
I'm not sure the roadmap is the right place, though, since we probably want
the format to be different for past and future releases: information for
past releases is typically more precise and more verbose, with code
examples and so on. See for instance this blog post: http://in.relation.to/
2017/06/13/hibernate-search-5-8-0-Beta3/ . I'm afraid the future roadmap
would be drowned in the past releases.

I was thinking about another problem: we don't have a compatibility matrix.
We only have a few dependencies (mainly ORM and Lucene), but it's really
hard to know which versions of the dependencies to use with which version
of Search, and users frequently use the wrong versions.
With that in mind, I would rather see a "Versions" page, with a summary at
the top (including a one-liner for each minor and the compatibilty matrix),
and one section for each minor (with anchors, so that we can link to them
from other pages such as the downloads). Or maybe even one page for the
detail of each minor, if there's too much text.
I think it would make sense to have all that information gathered in a
single place, because all of that is needed for users to pick the version
they want: they need to know the benefits of upgrading (features) but also
the constraints (compatibility matrix).
Maybe I can give it a try at the end of the week?


Yoann Rodière
Hibernate NoORM Team
yo...@hibernate.org

On 6 September 2017 at 09:21, Emmanuel Bernard 
wrote:

> Hey all,
>
> I was trying to answer the following question, what is roughly new between
> 5.6, 5.7 and 5.8 (minor releases)?
>
> My first reflex was to go to http://hibernate.org/search/downloads/ <
> http://hibernate.org/search/downloads/> to read about the onliner per
> release. Except it’s a onliner per micro release and “minor adjustments”
> for 5.6.3.Final gave me literally no info whatsoever.
>
> My second reflex was to go to http://hibernate.org/search/roadmap/ <
> http://hibernate.org/search/roadmap/> to find a historical entry about
> older versions and the main changes in bullet points. No luck. It only
> talks about the future.
>
> My third reflex was to go to http://in.relation.to/hibernate-search/ <
> http://in.relation.to/hibernate-search/> I ended up giving up midway page
> 2 of the list of blog entries. It’s a mix of simultaneous parallel releases
> with what’s new since the last CR or the last micro kind of reports and
> gave up in dismay at the energy I would have to spend to extract what’s new
> for a full minor release.
>
> I did exaggerate a bit the third point but I did give up. We need
> somewhere a summary page of what’s new per minor releases. I think the
> roadmap page could be the host.
> Likewise, we might need a oneliner entry in the download section (per
> release) that points to this minor release summary.
>
> Thoughts?
>
> Speaking of roadmap:
> - HV roadmap is massively out of date
> - OGM is lying a bit on the future but at least has the past summary I was
> talking about
> - Search has a good future roadmap but no past
>
> Emmanuek
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Marko Bekhta]

Hi Emmanuel,

I did some updates to HV roadmap with this PR [1]. There's also some
updates to
HV contribute page. Maybe somebody could check those changes and if needed
add
more to what is present, if what is already there is fine.

Have a nice day,
Marko

[1] https://github.com/hibernate/hibernate.org/pull/123.

2017-09-06 9:37 GMT+02:00 Yoann Rodiere :

> Hey,
>
> About Search, true, the information is somewhat hidden in many blog posts.
> I'm not sure the roadmap is the right place, though, since we probably want
> the format to be different for past and future releases: information for
> past releases is typically more precise and more verbose, with code
> examples and so on. See for instance this blog post:
> http://in.relation.to/
> 2017/06/13/hibernate-search-5-8-0-Beta3/ . I'm afraid the future roadmap
> would be drowned in the past releases.
>
> I was thinking about another problem: we don't have a compatibility matrix.
> We only have a few dependencies (mainly ORM and Lucene), but it's really
> hard to know which versions of the dependencies to use with which version
> of Search, and users frequently use the wrong versions.
> With that in mind, I would rather see a "Versions" page, with a summary at
> the top (including a one-liner for each minor and the compatibilty matrix),
> and one section for each minor (with anchors, so that we can link to them
> from other pages such as the downloads). Or maybe even one page for the
> detail of each minor, if there's too much text.
> I think it would make sense to have all that information gathered in a
> single place, because all of that is needed for users to pick the version
> they want: they need to know the benefits of upgrading (features) but also
> the constraints (compatibility matrix).
> Maybe I can give it a try at the end of the week?
>
>
> Yoann Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
> On 6 September 2017 at 09:21, Emmanuel Bernard 
> wrote:
>
> > Hey all,
> >
> > I was trying to answer the following question, what is roughly new
> between
> > 5.6, 5.7 and 5.8 (minor releases)?
> >
> > My first reflex was to go to http://hibernate.org/search/downloads/ <
> > http://hibernate.org/search/downloads/> to read about the onliner per
> > release. Except it’s a onliner per micro release and “minor adjustments”
> > for 5.6.3.Final gave me literally no info whatsoever.
> >
> > My second reflex was to go to http://hibernate.org/search/roadmap/ <
> > http://hibernate.org/search/roadmap/> to find a historical entry about
> > older versions and the main changes in bullet points. No luck. It only
> > talks about the future.
> >
> > My third reflex was to go to http://in.relation.to/hibernate-search/ <
> > http://in.relation.to/hibernate-search/> I ended up giving up midway
> page
> > 2 of the list of blog entries. It’s a mix of simultaneous parallel
> releases
> > with what’s new since the last CR or the last micro kind of reports and
> > gave up in dismay at the energy I would have to spend to extract what’s
> new
> > for a full minor release.
> >
> > I did exaggerate a bit the third point but I did give up. We need
> > somewhere a summary page of what’s new per minor releases. I think the
> > roadmap page could be the host.
> > Likewise, we might need a oneliner entry in the download section (per
> > release) that points to this minor release summary.
> >
> > Thoughts?
> >
> > Speaking of roadmap:
> > - HV roadmap is massively out of date
> > - OGM is lying a bit on the future but at least has the past summary I
> was
> > talking about
> > - Search has a good future roadmap but no past
> >
> > Emmanuek
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Guillaume Smet]

@Marko,

Yes, I plan to review them this week and add additional things to it!

On Wed, Sep 6, 2017 at 9:55 AM, Marko Bekhta 
wrote:

> Hi Emmanuel,
>
> I did some updates to HV roadmap with this PR [1]. There's also some
> updates to
> HV contribute page. Maybe somebody could check those changes and if needed
> add
> more to what is present, if what is already there is fine.
>
> Have a nice day,
> Marko
>
> [1] https://github.com/hibernate/hibernate.org/pull/123.
>
> 2017-09-06 9:37 GMT+02:00 Yoann Rodiere :
>
> > Hey,
> >
> > About Search, true, the information is somewhat hidden in many blog
> posts.
> > I'm not sure the roadmap is the right place, though, since we probably
> want
> > the format to be different for past and future releases: information for
> > past releases is typically more precise and more verbose, with code
> > examples and so on. See for instance this blog post:
> > http://in.relation.to/
> > 2017/06/13/hibernate-search-5-8-0-Beta3/ . I'm afraid the future roadmap
> > would be drowned in the past releases.
> >
> > I was thinking about another problem: we don't have a compatibility
> matrix.
> > We only have a few dependencies (mainly ORM and Lucene), but it's really
> > hard to know which versions of the dependencies to use with which version
> > of Search, and users frequently use the wrong versions.
> > With that in mind, I would rather see a "Versions" page, with a summary
> at
> > the top (including a one-liner for each minor and the compatibilty
> matrix),
> > and one section for each minor (with anchors, so that we can link to them
> > from other pages such as the downloads). Or maybe even one page for the
> > detail of each minor, if there's too much text.
> > I think it would make sense to have all that information gathered in a
> > single place, because all of that is needed for users to pick the version
> > they want: they need to know the benefits of upgrading (features) but
> also
> > the constraints (compatibility matrix).
> > Maybe I can give it a try at the end of the week?
> >
> >
> > Yoann Rodière
> > Hibernate NoORM Team
> > yo...@hibernate.org
> >
> > On 6 September 2017 at 09:21, Emmanuel Bernard 
> > wrote:
> >
> > > Hey all,
> > >
> > > I was trying to answer the following question, what is roughly new
> > between
> > > 5.6, 5.7 and 5.8 (minor releases)?
> > >
> > > My first reflex was to go to http://hibernate.org/search/downloads/ <
> > > http://hibernate.org/search/downloads/> to read about the onliner per
> > > release. Except it’s a onliner per micro release and “minor
> adjustments”
> > > for 5.6.3.Final gave me literally no info whatsoever.
> > >
> > > My second reflex was to go to http://hibernate.org/search/roadmap/ <
> > > http://hibernate.org/search/roadmap/> to find a historical entry about
> > > older versions and the main changes in bullet points. No luck. It only
> > > talks about the future.
> > >
> > > My third reflex was to go to http://in.relation.to/hibernate-search/ <
> > > http://in.relation.to/hibernate-search/> I ended up giving up midway
> > page
> > > 2 of the list of blog entries. It’s a mix of simultaneous parallel
> > releases
> > > with what’s new since the last CR or the last micro kind of reports and
> > > gave up in dismay at the energy I would have to spend to extract what’s
> > new
> > > for a full minor release.
> > >
> > > I did exaggerate a bit the third point but I did give up. We need
> > > somewhere a summary page of what’s new per minor releases. I think the
> > > roadmap page could be the host.
> > > Likewise, we might need a oneliner entry in the download section (per
> > > release) that points to this minor release summary.
> > >
> > > Thoughts?
> > >
> > > Speaking of roadmap:
> > > - HV roadmap is massively out of date
> > > - OGM is lying a bit on the future but at least has the past summary I
> > was
> > > talking about
> > > - Search has a good future roadmap but no past
> > >
> > > Emmanuek
> > > ___
> > > hibernate-dev mailing list
> > > hibernate-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Sanne Grinovero]

Thanks for that Emmanuel.

I'll fix the one-liner describing the release, I believe we had
already noticed this in the past: they need to describe the whole
minor not the micro update.
The Search roadmap actually also needs a little re-touch, I'll propose
a PR for that too.

Regarding past roadmaps: I don't like to clutter the roadmap page with
the previous copies, especially as they should have a different nature
of not being a plan but being a record of what was actually done.
Also, we did agree in past meetings to remove all the old ones. e.g.
we never ported the release notes for version 3.x and 4.x as back then
we decided this was no place for that. Happy to revisit this decision
but let's separate them:

What about a "past releases" page at the same level of roadmap, and
linking to it both from the main Search menu and the roadmap?

+1 for Yoann's proposal to re-introduce the compatibility matrix
(there was one ~6 years ago). I also had proposed to reintroduce it
more recently, and was not done on the grounds that it gets out of
date quickly.
Still users badly need it so unless someone has a better idea, let's
agree on trying to keep it up to date manually. Let's try structure it
in such a way that it won't need to be updated for every single
release.

Thanks,
Sanne


On 6 September 2017 at 08:37, Yoann Rodiere  wrote:
> Hey,
>
> About Search, true, the information is somewhat hidden in many blog posts.
> I'm not sure the roadmap is the right place, though, since we probably want
> the format to be different for past and future releases: information for
> past releases is typically more precise and more verbose, with code
> examples and so on. See for instance this blog post: http://in.relation.to/
> 2017/06/13/hibernate-search-5-8-0-Beta3/ . I'm afraid the future roadmap
> would be drowned in the past releases.
>
> I was thinking about another problem: we don't have a compatibility matrix.
> We only have a few dependencies (mainly ORM and Lucene), but it's really
> hard to know which versions of the dependencies to use with which version
> of Search, and users frequently use the wrong versions.
> With that in mind, I would rather see a "Versions" page, with a summary at
> the top (including a one-liner for each minor and the compatibilty matrix),
> and one section for each minor (with anchors, so that we can link to them
> from other pages such as the downloads). Or maybe even one page for the
> detail of each minor, if there's too much text.
> I think it would make sense to have all that information gathered in a
> single place, because all of that is needed for users to pick the version
> they want: they need to know the benefits of upgrading (features) but also
> the constraints (compatibility matrix).
> Maybe I can give it a try at the end of the week?
>
>
> Yoann Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
> On 6 September 2017 at 09:21, Emmanuel Bernard 
> wrote:
>
>> Hey all,
>>
>> I was trying to answer the following question, what is roughly new between
>> 5.6, 5.7 and 5.8 (minor releases)?
>>
>> My first reflex was to go to http://hibernate.org/search/downloads/ <
>> http://hibernate.org/search/downloads/> to read about the onliner per
>> release. Except it’s a onliner per micro release and “minor adjustments”
>> for 5.6.3.Final gave me literally no info whatsoever.
>>
>> My second reflex was to go to http://hibernate.org/search/roadmap/ <
>> http://hibernate.org/search/roadmap/> to find a historical entry about
>> older versions and the main changes in bullet points. No luck. It only
>> talks about the future.
>>
>> My third reflex was to go to http://in.relation.to/hibernate-search/ <
>> http://in.relation.to/hibernate-search/> I ended up giving up midway page
>> 2 of the list of blog entries. It’s a mix of simultaneous parallel releases
>> with what’s new since the last CR or the last micro kind of reports and
>> gave up in dismay at the energy I would have to spend to extract what’s new
>> for a full minor release.
>>
>> I did exaggerate a bit the third point but I did give up. We need
>> somewhere a summary page of what’s new per minor releases. I think the
>> roadmap page could be the host.
>> Likewise, we might need a oneliner entry in the download section (per
>> release) that points to this minor release summary.
>>
>> Thoughts?
>>
>> Speaking of roadmap:
>> - HV roadmap is massively out of date
>> - OGM is lying a bit on the future but at least has the past summary I was
>> talking about
>> - Search has a good future roadmap but no past
>>
>> Emmanuek
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

___
hibernate-dev mailing list
hibernate

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

[Steve Ebersole]

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:


   - https://github.com/hibernate/hibernate-orm/wiki/Roadmap5.2
   - https://github.com/hibernate/hibernate-orm/wiki/Migration-Guide---5.2
   - https://github.com/hibernate/hibernate-orm/wiki/ReleaseNotes5.2


The format could be better and some of this information could be combined
(release notes and migration guide e.g.).  But bear in mind that this was
just what I put together to illustrate what I was wanted to do, generally
speaking - so its a bit "rough"


On Wed, Sep 6, 2017 at 4:17 AM Sanne Grinovero  wrote:

> Thanks for that Emmanuel.
>
> I'll fix the one-liner describing the release, I believe we had
> already noticed this in the past: they need to describe the whole
> minor not the micro update.
> The Search roadmap actually also needs a little re-touch, I'll propose
> a PR for that too.
>
> Regarding past roadmaps: I don't like to clutter the roadmap page with
> the previous copies, especially as they should have a different nature
> of not being a plan but being a record of what was actually done.
> Also, we did agree in past meetings to remove all the old ones. e.g.
> we never ported the release notes for version 3.x and 4.x as back then
> we decided this was no place for that. Happy to revisit this decision
> but let's separate them:
>
> What about a "past releases" page at the same level of roadmap, and
> linking to it both from the main Search menu and the roadmap?
>
> +1 for Yoann's proposal to re-introduce the compatibility matrix
> (there was one ~6 years ago). I also had proposed to reintroduce it
> more recently, and was not done on the grounds that it gets out of
> date quickly.
> Still users badly need it so unless someone has a better idea, let's
> agree on trying to keep it up to date manually. Let's try structure it
> in such a way that it won't need to be updated for every single
> release.
>
> Thanks,
> Sanne
>
>
> On 6 September 2017 at 08:37, Yoann Rodiere  wrote:
> > Hey,
> >
> > About Search, true, the information is somewhat hidden in many blog
> posts.
> > I'm not sure the roadmap is the right place, though, since we probably
> want
> > the format to be different for past and future releases: information for
> > past releases is typically more precise and more verbose, with code
> > examples and so on. See for instance this blog post:
> http://in.relation.to/
> > 2017/06/13/hibernate-search-5-8-0-Beta3/ . I'm afraid the future roadmap
> > would be drowned in the past releases.
> >
> > I was thinking about another problem: we don't have a compatibility
> matrix.
> > We only have a few dependencies (mainly ORM and Lucene), but it's really
> > hard to know which versions of the dependencies to use with which version
> > of Search, and users frequently use the wrong versions.
> > With that in mind, I would rather see a "Versions" page, with a summary
> at
> > the top (including a one-liner for each minor and the compatibilty
> matrix),
> > and one section for each minor (with anchors, so that we can link to them
> > from other pages such as the downloads). Or maybe even one page for the
> > detail of each minor, if there's too much text.
> > I think it would make sense to have all that information gathered in a
> > single place, because all of that is needed for users to pick the version
> > they want: they need to know the benefits of upgrading (features) but
> also
> > the constraints (compatibility matrix).
> > Maybe I can give it a try at the end of the week?
> >
> >
> > Yoann Rodière
> > Hibernate NoORM Team
> > yo...@hibernate.org
> >
> > On 6 September 2017 at 09:21, Emmanuel Bernard 
> > wrote:
> >
> >> Hey all,
> >>
> >> I was trying to answer the following question, what is roughly new
> between
> >> 5.6, 5.7 and 5.8 (minor releases)?
> >>
> >> My first reflex was to go to http://hibernate.org/search/downloads/ <
> >> http://hibernate.org/search/downloads/> to read about the onliner per
> >> release. Except it’s a onliner per micro release and “minor adjustments”
> >> for 5.6.3.Final gave me literally no info whatsoever.
> >>
> >> My second reflex was to go to http://hibernate.org/search/roadmap/ <
> >> http://hibernate.org/search/roadmap/> to find a historical entry about
> >> older versions and the main changes in bullet points. No luck. It only
> >> talks about the future.
> >>
> >> My third reflex was to go to http://in.relation.to/hibernate-search/ <
> >> http://in.relation.to/hibernate-search/> I ended up giving up midway
> page
> >> 2 of the list of blog entries. It’s a mix of simultaneous parallel
> releases
> >> with what’s new since the last CR or the last micro kind of reports and
> >> gave up in dismay at the energy I would have to spend to extract what’s
> new
> >> for a full minor release.
> >>
> >> I did exaggerate a bi

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

[Sanne Grinovero]

Hi Gail,

the failing test is CDIInjectionIT from my personal branch of
Hibernate Search called "WildFly11" :

https://github.com/Sanne/hibernate-search/blob/WildFly11/integrationtest/wildfly/src/test/java/org/hibernate/search/test/integration/wildfly/cdi/CDIInjectionIT.java

It is an Arquillian test and 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

Thanks,
Sanne


On 1 September 2017 at 19:11, Gail Badner  wrote:
> I have a better understanding after discussing further with Scott, so I
> agree with Steve now.
>
> I have some ideas about how to fix this.
>
> Sanne, you mentioned getting a failure using an integration test. Please
> provide details for reproducing this.
>
> On Wed, Aug 30, 2017 at 11:43 AM, Steve Ebersole 
> wrote:
>>
>> 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 is inaccurate.  But would certainly like to hear Scott's opinion
>> as well.
>>
>> Technically this situation is non-JPA compliant as JPA requires that the
>> BeanManager passed to be available at boot-time.
>>
>> On Wed, Aug 30, 2017 at 12:02 PM 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 how it's meant to be.
>>>
>>> The source code of the ExtendedBeanManager which you didn't find is
>>> located in the WildFly source code; it's part of JipiJapa:
>>>  -
>>> https://github.com/wildfly/wildfly/blob/master/jpa/hibernate5/src/main/java/org/jboss/as/jpa/hibernate5/HibernateExtendedBeanManager.java
>>>
>>> As you also noticed, it no longer implement the standard BeanManager
>>> interface. I agree with you that I'd expect it to still implement it,
>>> but clearly this was changed intentionally so I hope someone (Scott
>>> possibly?) can clarify - or revert.
>>>
>>> In case this is intentionally no longer implementing the standard
>>> interface we should at least clarify the javadocs if this
>>> configuration property.
>>>
>>> The missing  javax.el.ELResolver and javax.el.ExpressionFactory is
>>> unfortunate. I'd hope we could do better than just add them back,
>>> maybe it requires a dedicated module? Having too many dependencies -
>>> in this case half of Weld - slows down our bootstrap significantly and
>>> users have been complaining about that.
>>>
>>> Thanks,
>>> Sanne
>>>
>>> On 30 August 2017 at 06:58, Gail Badner  wrote:
>>> > Hi Sanne,
>>> >
>>> > Do you have a WFLY  issue for this?
>>> >
>>> > I've tentatively created a branch and pushed a commit to my fork that
>>> > reproduces this issue. [1]
>>> >
>>> > It reproduces using Hibernate 5.1.11-SNAPSHOT and 5.2.11-SNAPSHOT.
>>> >
>>> > In 5.1, org.hibernate.jpa.test.cdi.ExtendedBeanManagerCdiTest uses an
>>> > implementation, ExtendedBeanManagerImpl [2], that implements both
>>> > BeanManager, ExtendedBeanManager.
>>> >
>>> > I don't see this test in 5.2, and I don't see any implementation of
>>> > ExtendedBeanManager in 5.2. I do see tests in
>>> > org.hibernate.jpa.test.cdi.extended, but have not had a chance to look
>>> > at
>>> > those yet.
>>> >
>>> > I suspect that org.jboss.as.jpa.hibernate5.HibernateExtendedBeanManager
>>> > should implement javax.enterprise.inject.spi.BeanManager as well. I
>>> > tried
>>> > making this change, and having BeanManager methods delegate to
>>> > HibernateExtendedBeanManager#beanManager, but it looks like a
>>> > dependency is
>>> > missing, because javax.el.ELResolver and javax.el.ExpressionFactory are
>>> > unresolved.
>>> >
>>> > Please let me know if I'm on the right (or wrong) track. I'll pick this
>>> > up
>>> > tomorrow.
>>> >
>>> > Regards,
>>> > Gail
>>> >
>>> > [1] https://github.com/gbadner/wildfly/tree/WFLY-CCE-bug
>>> > [2]
>>> >
>>> > https://github.com/hibernate/hibernate-orm/blob/5.1/hibernate-entitymanager/src/test/java/org/hibernate/jpa/test/cdi/ExtendedBeanManagerCdiTest.java#L195
>>> >
>>> > On Tue, Aug 29, 2017 at 8:18 AM, Sanne Grinovero 
>>> > wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> In Hibernate Search we have a snippet of code doing:
>>> >>
>>> >> private static BeanManager getBeanManager(Map
>>> >> configurationValues) {
>>> >>return (BeanManager) configurationValues.get(
>>> >> AvailableSettings.CDI_BEAN_MANAGER );
>>> >> }
>>> >>
>>> >> This used to work on WildFly 10 - even if we were to override the
>>> >> Hibernate ORM version to 5.2.
>>> >>
>>> >> By runnning the same integration test on WildFly 11 I'm now getting a
>>> >> ClassCastException as the returned