The problems are in the details.
an EL #{javax.enterprise.context.conversation.id}
will iterate over the EL loader chain a whooping 5 times!
First it will resolve „javax“. Then on that object it will resolve
„enterprise“, then …
And on the last (id) you will finally hit the OWB WebBeansELResolver.
The problem is that you have no way of knowing if after „java“ there will be a
„servlet“ or an „enterprise“…
So if you implement this for CDI, then there is no way any other spec can
implement it.
This would only be possible if there is a single instance for the whole EE
container. Which is perfectly doable in TomEE - but not in OWB.
LieGrue,
strub
> Am 29.09.2016 um 14:41 schrieb Romain Manni-Bucau <[email protected]>:
>
> yep, you can add a test on "enterprise" as well.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-09-29 14:38 GMT+02:00 Xavier Dury <[email protected]>:
>
>> something like this? https://gist.github.com/kalgon/
>> c1ccffff45540a629314f615b90f944f
>>
>>
>>
