Good news, this is not happening in the master. I will close the ticket and
wait for the release.
On Wed, Jan 23, 2019 at 11:16 AM Ivan Junckes Filho
wrote:
> This is the ticket:
> https://issues.apache.org/jira/browse/TOMEE-2457
>
> This looks like a release blocker in my opinion. I will check
This is the ticket:
https://issues.apache.org/jira/browse/TOMEE-2457
This looks like a release blocker in my opinion. I will check the master
and see how it behaves.
On Tue, Jan 22, 2019 at 3:53 PM Roberto Cortez wrote:
> Hi Ivan,
>
> Can you please provide a test case that reproduces the
Hi Ivan,
Can you please provide a test case that reproduces the issue? Thank you!
Cheers,
Roberto
> On 22 Jan 2019, at 16:07, Romain Manni-Bucau wrote:
>
> Long story short, the MP impl assume CDI is active, if not then tomee but
> disable the MP impl.
> For us it means disabling also the
Long story short, the MP impl assume CDI is active, if not then tomee but
disable the MP impl.
For us it means disabling also the servlet container initializers. It can
be done in OpenEJBContextConfig or - likely good - implementing a
contextual ConfigSource (reading AppContext#properties for
When you say it is a bug in CDI support of TomEE, could you please be more
specific? Of course if you are aware of what it could be·
On Tue, Jan 22, 2019 at 12:50 PM Romain Manni-Bucau
wrote:
> Hmm, we can add a check in the filter and fail the deployment but at the
> end it is a bug in CDI
