[jira] [Resolved] (TOMEE-1837) Old, bugged openwebbens library (1.2.7)

["Richard Zowalla (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TOMEE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Zowalla resolved TOMEE-1837.
------------------------------------
    Resolution: Auto Closed

Hi there!

We wanted to reach out and let you know that we're currently working on cleaning up open issues in Jira that specifically impact unsupported versions, including 1.7.x, 7.0.x, and 7.1.x.

If you had previously reported this issue on one of these unsupported versions, we kindly ask you to check if the problem still persists and can be reproduced on a supported version such as 8.0.x or 9.0.x. If you find that it is indeed reproducible on a supported version, you're more than welcome to re-open this issue.

Thanks!


> Old, bugged openwebbens library (1.2.7)
> ---------------------------------------
>
>                 Key: TOMEE-1837
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1837
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 1.7.3, 1.7.4
>            Reporter: Andrzej K
>            Priority: Major
>
> TomEE uses old openwebbeans version which generates errors when a situalion like this occurs:
> -bean A depends on bean B and C
> -bean A declares observer method with parameters @Observes Object event (which means, that observes all events)
> There is (sometimes, it depends on a classpath) a deployment error because A cannot be built if B and C were not analyzed from the classpath. A should be build, because a containter wants to fire an event ProcessObserverMethod. The problem is, that this event is a lifecycle event and it should be never fired to bean A which is not Extension specialization (however v. 1.2.7 does it -- incorrectly).
> An openwebbeans 1.2.7 implementation is broken, so it should be migrated (event in this 1.7.x TomEE version). Newer versions (from 1.6.x) do not have this bug



--
This message was sent by Atlassian Jira
(v8.20.10#820010)