[jira] [Commented] (MEECROWAVE-338) move Oauth2Test from sun.security to Bouncycastle
[ https://issues.apache.org/jira/browse/MEECROWAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854131#comment-17854131 ] Romain Manni-Bucau commented on MEECROWAVE-338: --- well the CVE will still pop up by external scanners and on maven repository so still > move Oauth2Test from sun.security to Bouncycastle > - > > Key: MEECROWAVE-338 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-338 > Project: Meecrowave > Issue Type: Improvement >Affects Versions: 1.2.15 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.2.16, 2.0.0 > > > We still use sun.security to generate our key files. We should use > bouncycastle instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827810#comment-17827810 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~arne] cxf just released 4.0.4, if it does not work we should clearly request them to fix it since there are solution for the dropped API. +1 to not fork now > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822296#comment-17822296 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- Sure, while needed no issue but no reordering for ex. Idea is in the diff only required changes when possible...after we are not PR extremists ;). > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822255#comment-17822255 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~shaikezam] we move to the min of cxf/owb for java version, yes. No strong guidelines, idea is to limit the changes to the minimum, avoid wildcard imports or full style refactoring and ensure tests still pass and add tests if you add something new. Nothing crazy normally. > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822158#comment-17822158 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~rzo1] this is the kind of thing I was thinking about, we can just override `public void injectBus` and restore an override of the extension (just needs to register an openwebbeans loaderservice filtering cxf extension and replacing it by ours which is disabled if cxf is not in the cp, nothing crazy IMHO if there is some will to do it early). > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822140#comment-17822140 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~rzo1] which issue ? We worked around multiple times cxf limitations so can be done yet another time depending what it is. > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821404#comment-17821404 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- Hi [~shaikezam] , # I guess we upgrade transitive deps in project forcing the versions so we don't release meecrowave that often but there is no real blocker to do it # We had the jakarta bundle ([https://repo1.maven.org/maven2/org/apache/meecrowave/meecrowave-core/1.2.15/meecrowave-core-1.2.15-jakarta.jar)] which was covering it until the full stack migrates to jakarta, now openwebbeans, tomcat and cxf migrated and some years passed we can likely do it # probably check 1. which enables to be CVE free with last release feel free to do a PR to work on 2 if you are interested? > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1438) Synthetic InjectionPoint for CDI.current() and similar usages
[ https://issues.apache.org/jira/browse/OWB-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820041#comment-17820041 ] Romain Manni-Bucau commented on OWB-1438: - -1, this goes against the spec (see CDI/Instance doc) plus it keeps the same exact bug with a producer using getMember or getAnnotated so no good reason to pollute our code IMHO until you find a way to fix other methods. > Synthetic InjectionPoint for CDI.current() and similar usages > - > > Key: OWB-1438 > URL: https://issues.apache.org/jira/browse/OWB-1438 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 4.0.2 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 4.0.3 > > > Right now using CDI.current().select(...).get() does not create an > InjectionPoint. Thus it's not possible to use a Dependent Scoped producer. We > could create a synthetic InjectionPoint with the qualifiers and type which > got selected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1434) upgrade various dependencies to more recent versions
[ https://issues.apache.org/jira/browse/OWB-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811767#comment-17811767 ] Romain Manni-Bucau commented on OWB-1434: - We should list the impacting one explicitly (others are not very important for end user) to ensure it surfaces in release notes otherwise this kind of ticket is pretty useless for everybody - as dependabot commits. > upgrade various dependencies to more recent versions > > > Key: OWB-1434 > URL: https://issues.apache.org/jira/browse/OWB-1434 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 4.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 4.0.2 > > > While preparing a 4.0.1 release we should also go through various > dependencies and upgrade to more recent versions. E.g. fixed jakarta spec api > jars. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1429) Java 21 not supported?
[ https://issues.apache.org/jira/browse/OWB-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779575#comment-17779575 ] Romain Manni-Bucau commented on OWB-1429: - Hi, it needs a new xbean-asm release, you can use a snapshot, build it yourself or ensure your bytecode uses java 17 (even if it runs on java21). > Java 21 not supported? > -- > > Key: OWB-1429 > URL: https://issues.apache.org/jira/browse/OWB-1429 > Project: OpenWebBeans > Issue Type: Bug > Components: Core >Affects Versions: 2.0.27 >Reporter: Torsten Stolpmann >Priority: Major > > I am porting our application from Java 11 to Java 21. > During initialization, I get the following exception from OpenWebBeans 2.0.27: > Caused by: java.lang.RuntimeException: Unable to read class definition for > com.sun.faces.context.FacesFileNotFoundException > at > org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1180) > at > org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:153) > at > org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:166) > at > org.apache.webbeans.corespi.scanner.xbean.OwbAnnotationFinder.(OwbAnnotationFinder.java:41) > at > org.apache.webbeans.corespi.scanner.AbstractMetaDataDiscovery.initFinder(AbstractMetaDataDiscovery.java:138) > at > org.apache.webbeans.corespi.scanner.AbstractMetaDataDiscovery.scan(AbstractMetaDataDiscovery.java:177) > ... 33 more > Caused by: java.lang.IllegalArgumentException: Unsupported class file major > version 65 > at org.apache.xbean.asm9.ClassReader.(ClassReader.java:199) > at org.apache.xbean.asm9.ClassReader.(ClassReader.java:180) > at org.apache.xbean.asm9.ClassReader.(ClassReader.java:166) > at org.apache.xbean.asm9.ClassReader.(ClassReader.java:287) > at > org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1176) > I already updated the org.apache.xbean:xbean-asm9-shaded dependency to the > latest version 4.24. > Is OpenWebBeans 2.0.27 not supposed to work with Java 21? > What else can I try? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1423) openwebbeans-impl-jakarta is using old javax namespace
[
https://issues.apache.org/jira/browse/OWB-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687894#comment-17687894
]
Romain Manni-Bucau commented on OWB-1423:
-
[~Tsakumagos] guess you need to put a project on github reproducing the issue
since this setup is known working. can come from something else.
> openwebbeans-impl-jakarta is using old javax namespace
> --
>
> Key: OWB-1423
> URL: https://issues.apache.org/jira/browse/OWB-1423
> Project: OpenWebBeans
> Issue Type: Bug
>Affects Versions: 2.0.26, 2.0.27
>Reporter: Georg Tsakumagos
>Priority: Major
>
> h3. Description
> Openwebbeans with jakarta qualifier should use the jakarta namespace. I try
> to use openejb 9.0.0 for testing but run into a no NoSuchMethodError.
> The class
> *_org.apache.webbeans.portable.events.discovery.BeforeBeanDiscoveryImpl_* is
> using the old namespace.
> h3. Stacktrace
> {code:java}
> Caused by: org.apache.webbeans.exception.WebBeansException:
> java.lang.NoSuchMethodError: 'void
> jakarta.enterprise.inject.spi.BeforeBeanDiscovery.addAnnotatedType(jakarta.enterprise.inject.spi.AnnotatedType)'
> at
> org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:377)
> at
> org.apache.webbeans.event.NotificationManager.invokeObserverMethod(NotificationManager.java:1146)
> at
> org.apache.webbeans.event.NotificationManager.doFireSync(NotificationManager.java:1009)
> ... 61 more
> Caused by: java.lang.NoSuchMethodError: 'void
> jakarta.enterprise.inject.spi.BeforeBeanDiscovery.addAnnotatedType(jakarta.enterprise.inject.spi.AnnotatedType)'
> at
> org.apache.bval.cdi.BValExtension.addBvalBinding(BValExtension.java:112)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> {code}
> h3. GAV Coordinates
> {code:xml}
>
> org.apache.openwebbeans
> openwebbeans-impl
> jakarta
> 2.0.27
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OWB-1423) openwebbeans-impl-jakarta is using old javax namespace
[
https://issues.apache.org/jira/browse/OWB-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687883#comment-17687883
]
Romain Manni-Bucau commented on OWB-1423:
-
Hi [~Tsakumagos] ,
Think you didn't use the jakarta stack but just one artifact leading to this
error, either define the owb artifacts to use jakarta or reuse this dependency
which already does it:
```
io.yupiik.uship
backbone-owb
1.0.16
pom
```
> openwebbeans-impl-jakarta is using old javax namespace
> --
>
> Key: OWB-1423
> URL: https://issues.apache.org/jira/browse/OWB-1423
> Project: OpenWebBeans
> Issue Type: Bug
>Affects Versions: 2.0.26, 2.0.27
>Reporter: Georg Tsakumagos
>Priority: Major
>
> h3. Description
> Openwebbeans with jakarta qualifier should use the jakarta namespace. I try
> to use openejb 9.0.0 for testing but run into a no NoSuchMethodError.
> The class
> *_org.apache.webbeans.portable.events.discovery.BeforeBeanDiscoveryImpl_* is
> using the old namespace.
> h3. Stacktrace
> {code:java}
> Caused by: org.apache.webbeans.exception.WebBeansException:
> java.lang.NoSuchMethodError: 'void
> jakarta.enterprise.inject.spi.BeforeBeanDiscovery.addAnnotatedType(jakarta.enterprise.inject.spi.AnnotatedType)'
> at
> org.apache.webbeans.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:377)
> at
> org.apache.webbeans.event.NotificationManager.invokeObserverMethod(NotificationManager.java:1146)
> at
> org.apache.webbeans.event.NotificationManager.doFireSync(NotificationManager.java:1009)
> ... 61 more
> Caused by: java.lang.NoSuchMethodError: 'void
> jakarta.enterprise.inject.spi.BeforeBeanDiscovery.addAnnotatedType(jakarta.enterprise.inject.spi.AnnotatedType)'
> at
> org.apache.bval.cdi.BValExtension.addBvalBinding(BValExtension.java:112)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> {code}
> h3. GAV Coordinates
> {code:xml}
>
> org.apache.openwebbeans
> openwebbeans-impl
> jakarta
> 2.0.27
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OWB-1417) Implement CDI-4.0 spec
[ https://issues.apache.org/jira/browse/OWB-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682218#comment-17682218 ] Romain Manni-Bucau commented on OWB-1417: - For future readers: core minus lite part as of today. > Implement CDI-4.0 spec > -- > > Key: OWB-1417 > URL: https://issues.apache.org/jira/browse/OWB-1417 > Project: OpenWebBeans > Issue Type: Epic >Affects Versions: 4.0.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 4.0.0 > > > All tickets to implement CDI-4.0 > > We likely will just implement the core parts in the first go. The rest > (especially 'cdi-light') might be implemented in a portable way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1416) Possible misintepretation of spec regarding Unproxyable bean types
[ https://issues.apache.org/jira/browse/OWB-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627686#comment-17627686 ] Romain Manni-Bucau commented on OWB-1416: - What about doing a pr to fix it? If not too intrusive a toggle can be a good compromise no? > Possible misintepretation of spec regarding Unproxyable bean types > -- > > Key: OWB-1416 > URL: https://issues.apache.org/jira/browse/OWB-1416 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Alexander Larsen >Priority: Major > > OWB seems to throw an exception for all unproxyable normal scoped beans. I > think that this might be incorrect. > The > [specification|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#unproxyable] > says the "A bean type must be proxyable if an injection point resolves to a > bean", not that all the types of the bean must be proxyable. In other words, > as long as the bean is a legal bean, and all injection point resolving to > this bean is a proxyable type - no exception should be thrown. > In the part about [contextual > references|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#contextual_reference], > there is further indications that unproxyable types should be allowed in the > set of types for the bean. It's only when you try to get a reference(injected > or by bean manager) to an unproxyable type, and the bean must be proxied > (normal scoped, intercepted or decorated) an exception should thrown. > Also, the [Weld user guide suggests introducing an interface as a solution to > having an unproxyable > bean|https://docs.jboss.org/weld/reference/latest/en-US/html_single/#_client_proxies]. > The current OWB implementation makes a pattern of having an interface and > (one or more) implementation class with final fields/methods somewhat > difficult :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1416) Possible misintepretation of spec regarding Unproxyable bean types
[ https://issues.apache.org/jira/browse/OWB-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627658#comment-17627658 ] Romain Manni-Bucau commented on OWB-1416: - Maybe but this quote also does not bring any requirements (compared to other parts) so sounds like an useless sentence in current form, I agree. Both options have pitfalls - not the same indeed ;) - so think our current state is likely the safer whereas relaxing it can be convenient in some cases it will break others so not sure it is worth the effort being said there are solution to handle the case you reference cleanly already, so quite mitigated for now. > Possible misintepretation of spec regarding Unproxyable bean types > -- > > Key: OWB-1416 > URL: https://issues.apache.org/jira/browse/OWB-1416 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Alexander Larsen >Priority: Major > > OWB seems to throw an exception for all unproxyable normal scoped beans. I > think that this might be incorrect. > The > [specification|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#unproxyable] > says the "A bean type must be proxyable if an injection point resolves to a > bean", not that all the types of the bean must be proxyable. In other words, > as long as the bean is a legal bean, and all injection point resolving to > this bean is a proxyable type - no exception should be thrown. > In the part about [contextual > references|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#contextual_reference], > there is further indications that unproxyable types should be allowed in the > set of types for the bean. It's only when you try to get a reference(injected > or by bean manager) to an unproxyable type, and the bean must be proxied > (normal scoped, intercepted or decorated) an exception should thrown. > Also, the [Weld user guide suggests introducing an interface as a solution to > having an unproxyable > bean|https://docs.jboss.org/weld/reference/latest/en-US/html_single/#_client_proxies]. > The current OWB implementation makes a pattern of having an interface and > (one or more) implementation class with final fields/methods somewhat > difficult :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1416) Possible misintepretation of spec regarding Unproxyable bean types
[ https://issues.apache.org/jira/browse/OWB-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627615#comment-17627615 ] Romain Manni-Bucau commented on OWB-1416: - Well yes and no, `getReference` is a good example of the previous point: "by any client proxy that is returned" so it must impl any bean type cause you don't know with which value it will be called - keep in mind it can be dynamic using reflection too - so to respect the spec (tck+pdf+javadoc) you must impl it as OWB did. Agree it can not be the most convenient but weld ecosystem is also know to not respect the spec everywhere (bypassing proxies for app scoped injections in some cases for ex - it is a good optimization by itself but which breaks other parts of the spec for ex) so not sure it is a good reference for this particular point. > Possible misintepretation of spec regarding Unproxyable bean types > -- > > Key: OWB-1416 > URL: https://issues.apache.org/jira/browse/OWB-1416 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Alexander Larsen >Priority: Major > > OWB seems to throw an exception for all unproxyable normal scoped beans. I > think that this might be incorrect. > The > [specification|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#unproxyable] > says the "A bean type must be proxyable if an injection point resolves to a > bean", not that all the types of the bean must be proxyable. In other words, > as long as the bean is a legal bean, and all injection point resolving to > this bean is a proxyable type - no exception should be thrown. > In the part about [contextual > references|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#contextual_reference], > there is further indications that unproxyable types should be allowed in the > set of types for the bean. It's only when you try to get a reference(injected > or by bean manager) to an unproxyable type, and the bean must be proxied > (normal scoped, intercepted or decorated) an exception should thrown. > Also, the [Weld user guide suggests introducing an interface as a solution to > having an unproxyable > bean|https://docs.jboss.org/weld/reference/latest/en-US/html_single/#_client_proxies]. > The current OWB implementation makes a pattern of having an interface and > (one or more) implementation class with final fields/methods somewhat > difficult :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1416) Possible misintepretation of spec regarding Unproxyable bean types
[ https://issues.apache.org/jira/browse/OWB-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627582#comment-17627582 ] Romain Manni-Bucau commented on OWB-1416: - Hmm, for a managed bean (= plain class, not a producer) it is an issue since the proxy must be a subclass of the impl, not the typed so this must fail by spec AFAIK. I know weld worked it around but it is not 100% spec compliant IIRC. The solution would be to use a producer for the bean, this should work (use @Vetoed on the class and replace it by a producer which type it accordingly). > Possible misintepretation of spec regarding Unproxyable bean types > -- > > Key: OWB-1416 > URL: https://issues.apache.org/jira/browse/OWB-1416 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Alexander Larsen >Priority: Major > > OWB seems to throw an exception for all unproxyable normal scoped beans. I > think that this might be incorrect. > The > [specification|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#unproxyable] > says the "A bean type must be proxyable if an injection point resolves to a > bean", not that all the types of the bean must be proxyable. In other words, > as long as the bean is a legal bean, and all injection point resolving to > this bean is a proxyable type - no exception should be thrown. > In the part about [contextual > references|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#contextual_reference], > there is further indications that unproxyable types should be allowed in the > set of types for the bean. It's only when you try to get a reference(injected > or by bean manager) to an unproxyable type, and the bean must be proxied > (normal scoped, intercepted or decorated) an exception should thrown. > Also, the [Weld user guide suggests introducing an interface as a solution to > having an unproxyable > bean|https://docs.jboss.org/weld/reference/latest/en-US/html_single/#_client_proxies]. > The current OWB implementation makes a pattern of having an interface and > (one or more) implementation class with final fields/methods somewhat > difficult :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1416) Possible misintepretation of spec regarding Unproxyable bean types
[ https://issues.apache.org/jira/browse/OWB-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17627487#comment-17627487 ] Romain Manni-Bucau commented on OWB-1416: - Hi, since spec requires subclassing, interface usage is not a solution until you use `@Typed` or hide the impl class I think. > Possible misintepretation of spec regarding Unproxyable bean types > -- > > Key: OWB-1416 > URL: https://issues.apache.org/jira/browse/OWB-1416 > Project: OpenWebBeans > Issue Type: Bug >Reporter: Alexander Larsen >Priority: Major > > OWB seems to throw an exception for all unproxyable normal scoped beans. I > think that this might be incorrect. > The > [specification|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#unproxyable] > says the "A bean type must be proxyable if an injection point resolves to a > bean", not that all the types of the bean must be proxyable. In other words, > as long as the bean is a legal bean, and all injection point resolving to > this bean is a proxyable type - no exception should be thrown. > In the part about [contextual > references|https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#contextual_reference], > there is further indications that unproxyable types should be allowed in the > set of types for the bean. It's only when you try to get a reference(injected > or by bean manager) to an unproxyable type, and the bean must be proxied > (normal scoped, intercepted or decorated) an exception should thrown. > Also, the [Weld user guide suggests introducing an interface as a solution to > having an unproxyable > bean|https://docs.jboss.org/weld/reference/latest/en-US/html_single/#_client_proxies]. > The current OWB implementation makes a pattern of having an interface and > (one or more) implementation class with final fields/methods somewhat > difficult :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-323) Incorrect filename for annotation processor
[
https://issues.apache.org/jira/browse/MEECROWAVE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17617183#comment-17617183
]
Romain Manni-Bucau commented on MEECROWAVE-323:
---
Hi [~vbychkov] , do you want to submit a PR on github
(@apache/openwebbeans-meecrowave project) - guess we can exclude the file since
it is log4j related and we don't intend to enable to build custom log4j plugins
with this fatjar?
Side note: for people blocked, maven-compiler supports to configure the
annotation processors explicitly which enables to bypass this error.
> Incorrect filename for annotation processor
> ---
>
> Key: MEECROWAVE-323
> URL: https://issues.apache.org/jira/browse/MEECROWAVE-323
> Project: Meecrowave
> Issue Type: Bug
>Affects Versions: 1.2.14
> Environment: Java 17
>Reporter: Vladimir V. Bychkov
>Priority: Blocker
>
> Dependency artifact
> [meecrowave-core:1.2.14:jakarta|https://repo1.maven.org/maven2/org/apache/meecrowave/meecrowave-core/1.2.14/meecrowave-core-1.2.14-jakarta.jar]
> contains file /META-INF/services/*jakarta*.annotation.processing.Processor.
> The name of file si incorrect: this file is not a part of Jakarta EE, but
> part of Java EE. His name since JDK 6 was und stays
> *javax*.annotation.processing.Processor.
> This error is name is a blocker: when build with maven-compiler it produces
> error
> {code}
> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException:
> Compilation failure error: Bad service configuration file, or exception
> thrown while constructing Processor object:
> jakarta/annotation/processing/AbstractProcessor
> at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1310)
> at
> org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:183)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (MEECROWAVE-321) Upgrade to Johnzon 1.2.19
[ https://issues.apache.org/jira/browse/MEECROWAVE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-321. --- Resolution: Fixed > Upgrade to Johnzon 1.2.19 > - > > Key: MEECROWAVE-321 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-321 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.15 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MEECROWAVE-322) Upgrade to OpenWebBeans 2.0.27
[ https://issues.apache.org/jira/browse/MEECROWAVE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-322. --- Resolution: Fixed > Upgrade to OpenWebBeans 2.0.27 > -- > > Key: MEECROWAVE-322 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-322 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.15 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEECROWAVE-321) Upgrade to Johnzon 1.2.19
Romain Manni-Bucau created MEECROWAVE-321: - Summary: Upgrade to Johnzon 1.2.19 Key: MEECROWAVE-321 URL: https://issues.apache.org/jira/browse/MEECROWAVE-321 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEECROWAVE-322) Upgrade to OpenWebBeans 2.0.27
Romain Manni-Bucau created MEECROWAVE-322: - Summary: Upgrade to OpenWebBeans 2.0.27 Key: MEECROWAVE-322 URL: https://issues.apache.org/jira/browse/MEECROWAVE-322 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OWB-1404) Cannot build
[ https://issues.apache.org/jira/browse/OWB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536552#comment-17536552 ] Romain Manni-Bucau commented on OWB-1404: - here https://repository.apache.org/content/repositories/snapshots/org/apache/openwebbeans/openwebbeans-distribution/2.0.27-SNAPSHOT/openwebbeans-distribution-2.0.27-20220513.102740-5-binary.zip > Cannot build > > > Key: OWB-1404 > URL: https://issues.apache.org/jira/browse/OWB-1404 > Project: OpenWebBeans > Issue Type: Bug > Components: XML Configuration >Affects Versions: 2.0.26 >Reporter: Hugo >Priority: Major > > Cannot build. > [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not > transfer artifact > org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to > central (http://repo.maven.apache.org/maven2): Failed to transfer file: > http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.5/maven-remote-resources-plugin-1.5.pom. > Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (OWB-1404) Cannot build
[ https://issues.apache.org/jira/browse/OWB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536449#comment-17536449 ] Romain Manni-Bucau edited comment on OWB-1404 at 5/13/22 6:38 AM: -- Hi [~hugol] , not sure what's your issue is (tested with success mvn 3.6 and 3.8+previous config) is but I deployed the snapshot at [https://repository.apache.org/content/repositories/snapshots] FYI I fixed the http repository issue on master was (Author: romain.manni-bucau): Hi [~hugol] , not sure what's your issue is (tested with success mvn 3.6 and 3.8+previous config) is but I deployed the snapshot at https://repository.apache.org/content/repositories/snapshots > Cannot build > > > Key: OWB-1404 > URL: https://issues.apache.org/jira/browse/OWB-1404 > Project: OpenWebBeans > Issue Type: Bug > Components: XML Configuration >Affects Versions: 2.0.26 >Reporter: Hugo >Priority: Major > > Cannot build. > [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not > transfer artifact > org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to > central (http://repo.maven.apache.org/maven2): Failed to transfer file: > http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.5/maven-remote-resources-plugin-1.5.pom. > Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (OWB-1404) Cannot build
[ https://issues.apache.org/jira/browse/OWB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536449#comment-17536449 ] Romain Manni-Bucau commented on OWB-1404: - Hi [~hugol] , not sure what's your issue is (tested with success mvn 3.6 and 3.8+previous config) is but I deployed the snapshot at https://repository.apache.org/content/repositories/snapshots > Cannot build > > > Key: OWB-1404 > URL: https://issues.apache.org/jira/browse/OWB-1404 > Project: OpenWebBeans > Issue Type: Bug > Components: XML Configuration >Affects Versions: 2.0.26 >Reporter: Hugo >Priority: Major > > Cannot build. > [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not > transfer artifact > org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to > central (http://repo.maven.apache.org/maven2): Failed to transfer file: > http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.5/maven-remote-resources-plugin-1.5.pom. > Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (OWB-1404) Cannot build
[
https://issues.apache.org/jira/browse/OWB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536295#comment-17536295
]
Romain Manni-Bucau commented on OWB-1404:
-
[~hugol] you need to enable http repositories in your .m2/settings.xml:
{code:java}
maven-default-http-blocker
external:dont-match-anything-mate:*
Pseudo repository to mirror external repositories initially
using HTTP.
http://0.0.0.0/
false
{code}
(we don't reference this repository directly, it is due to a transitive
dependency so we can't help much, if you care about the related security you
can refine the whitelisted repo)
> Cannot build
>
>
> Key: OWB-1404
> URL: https://issues.apache.org/jira/browse/OWB-1404
> Project: OpenWebBeans
> Issue Type: Bug
> Components: XML Configuration
>Affects Versions: 2.0.26
>Reporter: Hugo
>Priority: Major
>
> Cannot build.
> [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or
> one of its dependencies could not be resolved: Failed to read artifact
> descriptor for
> org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not
> transfer artifact
> org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to
> central (http://repo.maven.apache.org/maven2): Failed to transfer file:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.5/maven-remote-resources-plugin-1.5.pom.
> Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (OWB-1404) Cannot build
[ https://issues.apache.org/jira/browse/OWB-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536229#comment-17536229 ] Romain Manni-Bucau commented on OWB-1404: - [~hugol] did you use maven 3.3, 3.6, 3.8? > Cannot build > > > Key: OWB-1404 > URL: https://issues.apache.org/jira/browse/OWB-1404 > Project: OpenWebBeans > Issue Type: Bug > Components: XML Configuration >Affects Versions: 2.0.26 >Reporter: Hugo >Priority: Major > > Cannot build. > [ERROR] Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for > org.apache.maven.plugins:maven-remote-resources-plugin:jar:1.5: Could not > transfer artifact > org.apache.maven.plugins:maven-remote-resources-plugin:pom:1.5 from/to > central (http://repo.maven.apache.org/maven2): Failed to transfer file: > http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.5/maven-remote-resources-plugin-1.5.pom. > Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (OWB-1403) Observed frequent logs - Could NOT lazily initialize session context because NO active request context
[
https://issues.apache.org/jira/browse/OWB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534202#comment-17534202
]
Romain Manni-Bucau commented on OWB-1403:
-
Hi [~rameshchatty] , I see, it could be worked around by disabling the session
listener (overriding the methods with a no-op in WebBeansConfigurationListener)
but I guess you can just configure TomEE to not log this warning, would be
easier and since you don't use session/conversation scopes it will not hurt.
Can also be worth to debug to check when the session context is created cause
your description tend to mention it shouldn't enter into this block (go in
WebContextService#getCurrentContext and check when SessionScoped.class is
initialized). It can help to refine a better solution.
> Observed frequent logs - Could NOT lazily initialize session context because
> NO active request context
> --
>
> Key: OWB-1403
> URL: https://issues.apache.org/jira/browse/OWB-1403
> Project: OpenWebBeans
> Issue Type: Bug
>Reporter: Ramesh Chatty
>Priority: Major
>
> After upgrading TomEE version from {*}8.0.6 -> 8.0.10{*}, frequently getting
> warnings logged as below whenever session timeout occurs:
>
> {code:java}
> org.apache.webbeans.web.context.WebContextsService lazyStartSessionContext
> WARNING: Could NOT lazily initialize session context because NO active
> request context
> {code}
>
> I have noticed one change in the *WebContextsService >>
> lazyStartSessionContext* method, where the parameter is sending as *false*
> for *getRequestContext(false)* method in *openwebbeans-web-2.0.26.jar* with
> in *TomEE-8.0.10* , where as this value is sent as *true* in
> *openwebbeans-web-2.0.12.jar* with in *TomEE-8.0.6*
>
> _Can you please suggest how to handle this scenario? Also are there any other
> impact scenarios we may be missing due to this change?_
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (OWB-1403) Observed frequent logs - Could NOT lazily initialize session context because NO active request context
[
https://issues.apache.org/jira/browse/OWB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532143#comment-17532143
]
Romain Manni-Bucau commented on OWB-1403:
-
Hi,
It is due to the fact we don't create request context upfront as before
([https://github.com/apache/openwebbeans/commit/91edc6f3fda6f7b8d65102e9200e331eb1491ceb)]
so depending your threading model, you can end up not having the request when
you start using a session scoped bean and therefore the creation does not work
as expected.
The impact an be that you don't use the session you think and that your bean
instances are not scoped as expected.
First thing to check is whether you use the servlet container thread or another
thread pool when it happens.
Romain
> Observed frequent logs - Could NOT lazily initialize session context because
> NO active request context
> --
>
> Key: OWB-1403
> URL: https://issues.apache.org/jira/browse/OWB-1403
> Project: OpenWebBeans
> Issue Type: Bug
>Reporter: Ramesh Chatty
>Priority: Major
>
> After upgrading TomEE version from {*}8.0.6 -> 8.0.10{*}, frequently getting
> warnings logged as below whenever session timeout occurs:
>
> {code:java}
> org.apache.webbeans.web.context.WebContextsService lazyStartSessionContext
> WARNING: Could NOT lazily initialize session context because NO active
> request context
> {code}
>
> I have noticed one change in the *WebContextsService >>
> lazyStartSessionContext* method, where the parameter is sending as *false*
> for *getRequestContext(false)* method in *openwebbeans-web-2.0.26.jar* with
> in *TomEE-8.0.10* , where as this value is sent as *true* in
> *openwebbeans-web-2.0.12.jar* with in *TomEE-8.0.6*
>
> _Can you please suggest how to handle this scenario? Also are there any other
> impact scenarios we may be missing due to this change?_
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (MEECROWAVE-320) Upgrade to johnzon 1.2.17
Romain Manni-Bucau created MEECROWAVE-320: - Summary: Upgrade to johnzon 1.2.17 Key: MEECROWAVE-320 URL: https://issues.apache.org/jira/browse/MEECROWAVE-320 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (MEECROWAVE-320) Upgrade to johnzon 1.2.17
[ https://issues.apache.org/jira/browse/MEECROWAVE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-320. --- Resolution: Fixed > Upgrade to johnzon 1.2.17 > - > > Key: MEECROWAVE-320 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-320 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (MEECROWAVE-319) Log4j 2.17.2
[ https://issues.apache.org/jira/browse/MEECROWAVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-319. --- Resolution: Fixed > Log4j 2.17.2 > > > Key: MEECROWAVE-319 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-319 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-319) Log4j 2.17.2
Romain Manni-Bucau created MEECROWAVE-319: - Summary: Log4j 2.17.2 Key: MEECROWAVE-319 URL: https://issues.apache.org/jira/browse/MEECROWAVE-319 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-318) CXF 3.5.2
[ https://issues.apache.org/jira/browse/MEECROWAVE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-318. --- Resolution: Fixed > CXF 3.5.2 > - > > Key: MEECROWAVE-318 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-318 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-318) CXF 3.5.2
Romain Manni-Bucau created MEECROWAVE-318: - Summary: CXF 3.5.2 Key: MEECROWAVE-318 URL: https://issues.apache.org/jira/browse/MEECROWAVE-318 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-317) Tomcat 9.0.62
[ https://issues.apache.org/jira/browse/MEECROWAVE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-317. --- Resolution: Fixed > Tomcat 9.0.62 > - > > Key: MEECROWAVE-317 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-317 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-317) Tomcat 9.0.62
Romain Manni-Bucau created MEECROWAVE-317: - Summary: Tomcat 9.0.62 Key: MEECROWAVE-317 URL: https://issues.apache.org/jira/browse/MEECROWAVE-317 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-316) Upgrade to tomcat 9.0.60
[ https://issues.apache.org/jira/browse/MEECROWAVE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-316. --- Resolution: Fixed > Upgrade to tomcat 9.0.60 > > > Key: MEECROWAVE-316 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-316 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-316) Upgrade to tomcat 9.0.60
Romain Manni-Bucau created MEECROWAVE-316: - Summary: Upgrade to tomcat 9.0.60 Key: MEECROWAVE-316 URL: https://issues.apache.org/jira/browse/MEECROWAVE-316 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-314) Upgrade to CXF 3.5.1
[ https://issues.apache.org/jira/browse/MEECROWAVE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-314. --- Resolution: Fixed > Upgrade to CXF 3.5.1 > > > Key: MEECROWAVE-314 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-314 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-312) Upgrade to Tomcat 9.0.59
[ https://issues.apache.org/jira/browse/MEECROWAVE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-312. --- Resolution: Fixed > Upgrade to Tomcat 9.0.59 > > > Key: MEECROWAVE-312 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-312 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-315) Upgrade to Johnzon 1.2.16
[ https://issues.apache.org/jira/browse/MEECROWAVE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-315. --- Resolution: Fixed > Upgrade to Johnzon 1.2.16 > - > > Key: MEECROWAVE-315 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-315 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-313) Upgrade to OpenWebBeans 2.0.26
[ https://issues.apache.org/jira/browse/MEECROWAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-313. --- Resolution: Fixed > Upgrade to OpenWebBeans 2.0.26 > -- > > Key: MEECROWAVE-313 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-313 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-315) Upgrade to Johnzon 1.2.16
Romain Manni-Bucau created MEECROWAVE-315: - Summary: Upgrade to Johnzon 1.2.16 Key: MEECROWAVE-315 URL: https://issues.apache.org/jira/browse/MEECROWAVE-315 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-313) Upgrade to OpenWebBeans 2.0.26
Romain Manni-Bucau created MEECROWAVE-313: - Summary: Upgrade to OpenWebBeans 2.0.26 Key: MEECROWAVE-313 URL: https://issues.apache.org/jira/browse/MEECROWAVE-313 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-314) Upgrade to CXF 3.5.1
Romain Manni-Bucau created MEECROWAVE-314: - Summary: Upgrade to CXF 3.5.1 Key: MEECROWAVE-314 URL: https://issues.apache.org/jira/browse/MEECROWAVE-314 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MEECROWAVE-312) Upgrade to Tomcat 9.0.59
[ https://issues.apache.org/jira/browse/MEECROWAVE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated MEECROWAVE-312: -- Fix Version/s: 1.2.14 (was: 1.2.15) > Upgrade to Tomcat 9.0.59 > > > Key: MEECROWAVE-312 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-312 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-312) Upgrade to Tomcat 9.0.59
Romain Manni-Bucau created MEECROWAVE-312: - Summary: Upgrade to Tomcat 9.0.59 Key: MEECROWAVE-312 URL: https://issues.apache.org/jira/browse/MEECROWAVE-312 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.15 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OWB-1088) fix samples with java 8 and update to tomcat7/8
[ https://issues.apache.org/jira/browse/OWB-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1088: Fix Version/s: 2.0.27 (was: 2.0.26) > fix samples with java 8 and update to tomcat7/8 > --- > > Key: OWB-1088 > URL: https://issues.apache.org/jira/browse/OWB-1088 > Project: OpenWebBeans > Issue Type: Task > Components: Samples Documentation >Affects Versions: 2.0.0 >Reporter: Reinhard Sandtner >Assignee: Reinhard Sandtner >Priority: Major > Fix For: 2.0.27 > > > some of our samples are currently broken under java 8 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[
https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated OWB-1074:
Fix Version/s: 2.0.27
(was: 2.0.26)
> implement automatic supportsConversation() detection
>
>
> Key: OWB-1074
> URL: https://issues.apache.org/jira/browse/OWB-1074
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
>Affects Versions: 1.5.0
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 2.0.27
>
>
> Currently we rely on the user to define the configuration option in
> OpenWebBeansConfiguration
> {code}
> APPLICATION_SUPPORTS_CONVERSATION =
> "org.apache.webbeans.application.supportsConversation";
> {code}
> This is by default disabled in owb-impl (core) and gets enabled by adding the
> web or jsf plugins.
> We could improve this by not only allowing {{true}} or {{false}} but also
> with an {{auto}} mode.
> In this mode the BeanManager can walk through all registered beans and check
> whether there is a single @ConversationScoped bean. In that case we will
> automagically enable CDI conversations, otherwise OWB will dynamically
> disable conversation support and don't need to do all kinds of work in
> WebContextsService for example.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OWB-1078) create Dockerfiles for installing OpenWebBeans as Docker Image based on Tomcat8
[ https://issues.apache.org/jira/browse/OWB-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1078: Fix Version/s: 2.0.27 (was: 2.0.26) > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 > --- > > Key: OWB-1078 > URL: https://issues.apache.org/jira/browse/OWB-1078 > Project: OpenWebBeans > Issue Type: New Feature > Components: Samples Documentation >Affects Versions: 1.5.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.27 > > > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OWB-1282) Reduce reflection usage for default services in WebBeansContext
[ https://issues.apache.org/jira/browse/OWB-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1282: Fix Version/s: 2.0.27 (was: 2.0.26) > Reduce reflection usage for default services in WebBeansContext > --- > > Key: OWB-1282 > URL: https://issues.apache.org/jira/browse/OWB-1282 > Project: OpenWebBeans > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.27 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (OWB-1402) CDI iterated Instance#select broken
[
https://issues.apache.org/jira/browse/OWB-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau resolved OWB-1402.
-
Fix Version/s: 2.0.26
Assignee: Romain Manni-Bucau
Resolution: Fixed
Didn't find the exact reference in the spec where it should behave like that
but "additionalQualifiers" is more than sufficient for me to behave this way
even if implicit @Default or/and @Any are treated specifically (this is the bit
blurry part for me). should be fixed on master
> CDI iterated Instance#select broken
> ---
>
> Key: OWB-1402
> URL: https://issues.apache.org/jira/browse/OWB-1402
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Injection and Lookup
>Affects Versions: 2.0.25
> Environment: linux, openjdk 11
>Reporter: Roland Bergler
>Assignee: Romain Manni-Bucau
>Priority: Major
> Fix For: 2.0.26
>
>
> I found the following bug within an openejb server (version 8.0.9), but can
> be reproduced with owb arquillian container, but not with weld.
> I have Managed Beans annotated with two qualifiers each (Examples from my
> test project, URL below):
> {noformat}
> @FoodQualifier(FoodType.FRUIT)
> @TasteQualifier(TasteType.YUMMY)
> public class Strawberry extends Food {
> ... {noformat}
> I got an injected Instance object, on which I want to select beans in a
> two-step process:
> {noformat}
> @Inject @Any private Instance allTypesOfFood;
> ...
> Instance vegetables = allTypesOfFood.select(new
> LiteralFoodType(FoodType.VEGETABLE));
> Instance yummyVegetables = vegetables.select(new
> LiteralTasteType(TasteType.YUMMY));
> {noformat}
> The second call to "select" seems to completely ignore the fact it is meant
> to be working on a restricted set, it yields all YUMMY foots, not just the
> vegetables.
> Find code here: [https://github.com/montanero/openejb-bug,
> |https://github.com/montanero/openejb-bug]type
> {{mvn install -P owb}}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (OWB-1401) Make interceptor injected method array sorted to be deterministic in proxy classes
[ https://issues.apache.org/jira/browse/OWB-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved OWB-1401. - Resolution: Fixed > Make interceptor injected method array sorted to be deterministic in proxy > classes > -- > > Key: OWB-1401 > URL: https://issues.apache.org/jira/browse/OWB-1401 > Project: OpenWebBeans > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 2.0.26 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OWB-1401) Make interceptor injected method array sorted to be deterministic in proxy classes
Romain Manni-Bucau created OWB-1401: --- Summary: Make interceptor injected method array sorted to be deterministic in proxy classes Key: OWB-1401 URL: https://issues.apache.org/jira/browse/OWB-1401 Project: OpenWebBeans Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 2.0.26 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-310) Upgrade to Tomcat 9.0.58
[ https://issues.apache.org/jira/browse/MEECROWAVE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-310. --- Resolution: Fixed > Upgrade to Tomcat 9.0.58 > > > Key: MEECROWAVE-310 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-310 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-309) Upgrade to Johnzon 1.2.15
[ https://issues.apache.org/jira/browse/MEECROWAVE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-309. --- Resolution: Fixed > Upgrade to Johnzon 1.2.15 > - > > Key: MEECROWAVE-309 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-309 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-311) Upgrade to Log4j 2.17.1
[ https://issues.apache.org/jira/browse/MEECROWAVE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-311. --- Resolution: Fixed > Upgrade to Log4j 2.17.1 > --- > > Key: MEECROWAVE-311 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-311 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-311) Upgrade to Log4j 2.17.1
Romain Manni-Bucau created MEECROWAVE-311: - Summary: Upgrade to Log4j 2.17.1 Key: MEECROWAVE-311 URL: https://issues.apache.org/jira/browse/MEECROWAVE-311 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-309) Upgrade to Johnzon 1.2.15
Romain Manni-Bucau created MEECROWAVE-309: - Summary: Upgrade to Johnzon 1.2.15 Key: MEECROWAVE-309 URL: https://issues.apache.org/jira/browse/MEECROWAVE-309 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-310) Upgrade to Tomcat 9.0.58
Romain Manni-Bucau created MEECROWAVE-310: - Summary: Upgrade to Tomcat 9.0.58 Key: MEECROWAVE-310 URL: https://issues.apache.org/jira/browse/MEECROWAVE-310 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OWB-1400) "/tomcat" entry in "org.apache.webbeans.scanExclusionPaths" disables scanning on official tomcat docker image
[ https://issues.apache.org/jira/browse/OWB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478792#comment-17478792 ] Romain Manni-Bucau commented on OWB-1400: - [~jfreire] there is a single rule, the rule about file is that you will get the class name in general (MyService.class for ex) so you must go up using the class name and you will end in WEB-INF/classes so either we consider we scan blindly or we go up of 2 more level to check if we exclude the full war, was my point. > "/tomcat" entry in "org.apache.webbeans.scanExclusionPaths" disables scanning > on official tomcat docker image > - > > Key: OWB-1400 > URL: https://issues.apache.org/jira/browse/OWB-1400 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.23 > Environment: docker image tomcat:8.5-jdk17-corretto >Reporter: Jose Luis Freire >Priority: Major > > When deploying an application in a tomcat docker image, the application is > typically installed in "/usr/local/tomcat/webapps". > > The application libs will typically be located in > "/usr/local/tomcat/webapps/ROOT/WEB-INF/lib". > The "/tomcat" entry in the exclusion path results in all the application > beans getting ignored if the jar files don't have the "META-INF/beans.xml" > (which isn't required in the default setup). > > I propose changing "/tomcat" to "/tomcat/lib" to avoid this overreaching > optimization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OWB-1400) "/tomcat" entry in "org.apache.webbeans.scanExclusionPaths" disables scanning on official tomcat docker image
[ https://issues.apache.org/jira/browse/OWB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478614#comment-17478614 ] Romain Manni-Bucau commented on OWB-1400: - Hi We can't change to `/tomcat/lib` since the intent is more to exclude `tomcat-.jar`. We have a way to get the jar/folder name so we can exclude from there (we do it in last version - [https://github.com/apache/openwebbeans/blob/master/webbeans-impl/src/main/java/org/apache/webbeans/corespi/scanner/AbstractMetaDataDiscovery.java#L239)] so we can maybe more match the jar name (or parent when class, web-inf, meta-inf) rather than anything else. Wdyt? > "/tomcat" entry in "org.apache.webbeans.scanExclusionPaths" disables scanning > on official tomcat docker image > - > > Key: OWB-1400 > URL: https://issues.apache.org/jira/browse/OWB-1400 > Project: OpenWebBeans > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.23 > Environment: docker image tomcat:8.5-jdk17-corretto >Reporter: Jose Luis Freire >Priority: Major > > When deploying an application in a tomcat docker image, the application is > typically installed in "/usr/local/tomcat/webapps". > > The application libs will typically be located in > "/usr/local/tomcat/webapps/ROOT/WEB-INF/lib". > The "/tomcat" entry in the exclusion path results in all the application > beans getting ignored if the jar files don't have the "META-INF/beans.xml" > (which isn't required in the default setup). > > I propose changing "/tomcat" to "/tomcat/lib" to avoid this overreaching > optimization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-308) Upgrade to log4j 2.17.0
[ https://issues.apache.org/jira/browse/MEECROWAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-308. --- Resolution: Fixed > Upgrade to log4j 2.17.0 > --- > > Key: MEECROWAVE-308 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-308 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-308) Upgrade to log4j 2.17.0
Romain Manni-Bucau created MEECROWAVE-308: - Summary: Upgrade to log4j 2.17.0 Key: MEECROWAVE-308 URL: https://issues.apache.org/jira/browse/MEECROWAVE-308 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MEECROWAVE-307) Upgrade to cxf 3.5.0
[ https://issues.apache.org/jira/browse/MEECROWAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated MEECROWAVE-307: -- Issue Type: Improvement (was: Bug) > Upgrade to cxf 3.5.0 > > > Key: MEECROWAVE-307 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-307 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-307) Upgrade to cxf 3.5.0
[ https://issues.apache.org/jira/browse/MEECROWAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-307. --- Resolution: Fixed > Upgrade to cxf 3.5.0 > > > Key: MEECROWAVE-307 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-307 > Project: Meecrowave > Issue Type: Bug >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.14 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MEECROWAVE-307) Upgrade to cxf 3.5.0
Romain Manni-Bucau created MEECROWAVE-307: - Summary: Upgrade to cxf 3.5.0 Key: MEECROWAVE-307 URL: https://issues.apache.org/jira/browse/MEECROWAVE-307 Project: Meecrowave Issue Type: Bug Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (OWB-1395) Jar not scanned after 2.0.24 upgrade
[ https://issues.apache.org/jira/browse/OWB-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved OWB-1395. - Resolution: Fixed > Jar not scanned after 2.0.24 upgrade > > > Key: OWB-1395 > URL: https://issues.apache.org/jira/browse/OWB-1395 > Project: OpenWebBeans > Issue Type: Bug >Affects Versions: 2.0.24 >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Blocker > Fix For: 2.0.25 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OWB-1395) Jar not scanned after 2.0.24 upgrade
Romain Manni-Bucau created OWB-1395: --- Summary: Jar not scanned after 2.0.24 upgrade Key: OWB-1395 URL: https://issues.apache.org/jira/browse/OWB-1395 Project: OpenWebBeans Issue Type: Bug Affects Versions: 2.0.24 Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 2.0.25 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (MEECROWAVE-303) [jpa] extension can leak closed entity managers
[ https://issues.apache.org/jira/browse/MEECROWAVE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-303. --- Resolution: Fixed > [jpa] extension can leak closed entity managers > --- > > Key: MEECROWAVE-303 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-303 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.13 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-303) [jpa] extension can leak closed entity managers
Romain Manni-Bucau created MEECROWAVE-303: - Summary: [jpa] extension can leak closed entity managers Key: MEECROWAVE-303 URL: https://issues.apache.org/jira/browse/MEECROWAVE-303 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-302) Upgrade to cxf 3.4.5
[ https://issues.apache.org/jira/browse/MEECROWAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-302. --- Resolution: Fixed > Upgrade to cxf 3.4.5 > > > Key: MEECROWAVE-302 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-302 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.13 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-302) Upgrade to cxf 3.4.5
Romain Manni-Bucau created MEECROWAVE-302: - Summary: Upgrade to cxf 3.4.5 Key: MEECROWAVE-302 URL: https://issues.apache.org/jira/browse/MEECROWAVE-302 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-301) Upgrade to tomcat 9.0.54
[ https://issues.apache.org/jira/browse/MEECROWAVE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-301. --- Resolution: Fixed > Upgrade to tomcat 9.0.54 > > > Key: MEECROWAVE-301 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-301 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.13 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-300) Upgrade to johnzon 1.2.14
[ https://issues.apache.org/jira/browse/MEECROWAVE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-300. --- Resolution: Fixed > Upgrade to johnzon 1.2.14 > - > > Key: MEECROWAVE-300 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-300 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.13 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-301) Upgrade to tomcat 9.0.54
Romain Manni-Bucau created MEECROWAVE-301: - Summary: Upgrade to tomcat 9.0.54 Key: MEECROWAVE-301 URL: https://issues.apache.org/jira/browse/MEECROWAVE-301 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-300) Upgrade to johnzon 1.2.14
Romain Manni-Bucau created MEECROWAVE-300: - Summary: Upgrade to johnzon 1.2.14 Key: MEECROWAVE-300 URL: https://issues.apache.org/jira/browse/MEECROWAVE-300 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OWB-1391) AbstractMetaDataDiscovery ignores classpath entries starting with a common path
Romain Manni-Bucau created OWB-1391: --- Summary: AbstractMetaDataDiscovery ignores classpath entries starting with a common path Key: OWB-1391 URL: https://issues.apache.org/jira/browse/OWB-1391 Project: OpenWebBeans Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 2.0.24 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OWB-1391) AbstractMetaDataDiscovery ignores classpath entries starting with a common path
[ https://issues.apache.org/jira/browse/OWB-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved OWB-1391. - Resolution: Fixed > AbstractMetaDataDiscovery ignores classpath entries starting with a common > path > --- > > Key: OWB-1391 > URL: https://issues.apache.org/jira/browse/OWB-1391 > Project: OpenWebBeans > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 2.0.24 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OWB-1390) support javax.enterprise.inject.scan.implicit property
[ https://issues.apache.org/jira/browse/OWB-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved OWB-1390. - Resolution: Fixed > support javax.enterprise.inject.scan.implicit property > -- > > Key: OWB-1390 > URL: https://issues.apache.org/jira/browse/OWB-1390 > Project: OpenWebBeans > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 2.0.24 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OWB-1390) support javax.enterprise.inject.scan.implicit property
Romain Manni-Bucau created OWB-1390: --- Summary: support javax.enterprise.inject.scan.implicit property Key: OWB-1390 URL: https://issues.apache.org/jira/browse/OWB-1390 Project: OpenWebBeans Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 2.0.24 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-299) Upgrade OpenJPA to 3.2.0
[ https://issues.apache.org/jira/browse/MEECROWAVE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-299. --- Resolution: Fixed > Upgrade OpenJPA to 3.2.0 > > > Key: MEECROWAVE-299 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-299 > Project: Meecrowave > Issue Type: Task >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-299) Upgrade OpenJPA to 3.2.0
Romain Manni-Bucau created MEECROWAVE-299: - Summary: Upgrade OpenJPA to 3.2.0 Key: MEECROWAVE-299 URL: https://issues.apache.org/jira/browse/MEECROWAVE-299 Project: Meecrowave Issue Type: Task Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.12 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OWB-1388) ViolationMessageBuilder has System.getProperty call as instance variable rather than static variable
[
https://issues.apache.org/jira/browse/OWB-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382516#comment-17382516
]
Romain Manni-Bucau commented on OWB-1388:
-
Best is likely to use
https://docs.oracle.com/javase/8/docs/api/java/lang/System.html#lineSeparator--
. Since it is about violations, it is always better to not keep it allocated
until needed IMHO and it is not a big deal to hit synchronized there since it
is not a highly concurrent point nor an expected codepath except in dev (it
stays a deployment error code path).
> ViolationMessageBuilder has System.getProperty call as instance variable
> rather than static variable
>
>
> Key: OWB-1388
> URL: https://issues.apache.org/jira/browse/OWB-1388
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Enterprise Web Beans, Simple Web Beans
>Reporter: Raghunandan
>Priority: Major
>
> *Problem*: Repeated instantiation of
> [ViolationMessageBuilder.java|https://github.com/apache/openwebbeans/blob/master/webbeans-impl/src/main/java/org/apache/webbeans/exception/helper/ViolationMessageBuilder.java]
> causes thread to block at java.util.Hashtable.
> Class :
> [https://github.com/apache/openwebbeans/blob/master/webbeans-impl/src/main/java/org/apache/webbeans/exception/helper/ViolationMessageBuilder.java]
> Current field :
> _private_ _final String lineSeparator =
> System.getProperty("line.separator");_
> _Currently it is getting instantiated every time
> *{color:#FF}ViolationMessageBuilder{color}* is instantiated by the code._
>
> *_Fix :_*
> Change it to static variable :
> _private {color:#FF}static{color} final String lineSeparator =
> System.getProperty("line.separator");_
> This will prevent java.util.HashTable
> (_System.getProperty("line.separator")_ being called every time
> {color:#FF}ViolationMessageBuilder{color} instantiated.
>
> *Sample thread block noticed at high concurrency*
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> java.util.Hashtable.get(Ljava/lang/Object;)Ljava/lang/Object;(Hashtable.java:363)
> - waiting to lock <0x00069a4fc6e0> (a java.util.Properties)
> at
> java.util.Properties.getProperty(Ljava/lang/String;)Ljava/lang/String;(Properties.java:1093)
> at
> java.lang.System.getProperty(Ljava/lang/String;)Ljava/lang/String;(System.java:732)
> at
> org.apache.webbeans.exception.helper.*{color:#FF}ViolationMessageBuilder{color}*{color:#FF}.{color}()V(ViolationMessageBuilder.java:25)
> at
> org.apache.webbeans.exception.helper.ViolationMessageBuilder.newViolation([Ljava/lang/String;)Lorg/apache/webbeans/exception/helper/ViolationMessageBuilder;(ViolationMessageBuilder.java:34)
> at
> org.apache.webbeans.util.InjectionExceptionUtil.*throwUnsatisfiedResolutionException*(Ljava/lang/Class;Ljavax/enterprise/inject/spi/InjectionPoint;[Ljava/lang/annotation/Annotation;)V(InjectionExceptionUtil.java:51)
> at
> org.apache.webbeans.container.InjectionResolver.getInjectionPointBean(Ljavax/enterprise/inject/spi/InjectionPoint;)Ljavax/enterprise/inject/spi/Bean;(InjectionResolver.java:293)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-298) Upgrade to Tomcat 9.0.50
[ https://issues.apache.org/jira/browse/MEECROWAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-298. --- Resolution: Fixed > Upgrade to Tomcat 9.0.50 > > > Key: MEECROWAVE-298 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-298 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-298) Upgrade to Tomcat 9.0.50
Romain Manni-Bucau created MEECROWAVE-298: - Summary: Upgrade to Tomcat 9.0.50 Key: MEECROWAVE-298 URL: https://issues.apache.org/jira/browse/MEECROWAVE-298 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.12 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OWB-1078) create Dockerfiles for installing OpenWebBeans as Docker Image based on Tomcat8
[ https://issues.apache.org/jira/browse/OWB-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1078: Fix Version/s: (was: 2.0.23) 2.0.24 > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 > --- > > Key: OWB-1078 > URL: https://issues.apache.org/jira/browse/OWB-1078 > Project: OpenWebBeans > Issue Type: New Feature > Components: Samples Documentation >Affects Versions: 1.5.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.24 > > > create Dockerfiles for installing OpenWebBeans as Docker Image based on > Tomcat8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OWB-1088) fix samples with java 8 and update to tomcat7/8
[ https://issues.apache.org/jira/browse/OWB-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1088: Fix Version/s: (was: 2.0.23) 2.0.24 > fix samples with java 8 and update to tomcat7/8 > --- > > Key: OWB-1088 > URL: https://issues.apache.org/jira/browse/OWB-1088 > Project: OpenWebBeans > Issue Type: Task > Components: Samples Documentation >Affects Versions: 2.0.0 >Reporter: Reinhard Sandtner >Assignee: Reinhard Sandtner >Priority: Major > Fix For: 2.0.24 > > > some of our samples are currently broken under java 8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[
https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated OWB-1074:
Fix Version/s: (was: 2.0.23)
2.0.24
> implement automatic supportsConversation() detection
>
>
> Key: OWB-1074
> URL: https://issues.apache.org/jira/browse/OWB-1074
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
>Affects Versions: 1.5.0
>Reporter: Mark Struberg
>Priority: Major
> Fix For: 2.0.24
>
>
> Currently we rely on the user to define the configuration option in
> OpenWebBeansConfiguration
> {code}
> APPLICATION_SUPPORTS_CONVERSATION =
> "org.apache.webbeans.application.supportsConversation";
> {code}
> This is by default disabled in owb-impl (core) and gets enabled by adding the
> web or jsf plugins.
> We could improve this by not only allowing {{true}} or {{false}} but also
> with an {{auto}} mode.
> In this mode the BeanManager can walk through all registered beans and check
> whether there is a single @ConversationScoped bean. In that case we will
> automagically enable CDI conversations, otherwise OWB will dynamically
> disable conversation support and don't need to do all kinds of work in
> WebContextsService for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OWB-1282) Reduce reflection usage for default services in WebBeansContext
[ https://issues.apache.org/jira/browse/OWB-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1282: Fix Version/s: (was: 2.0.23) 2.0.24 > Reduce reflection usage for default services in WebBeansContext > --- > > Key: OWB-1282 > URL: https://issues.apache.org/jira/browse/OWB-1282 > Project: OpenWebBeans > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.24 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-295) Upgrade to OWB 2.0.23
[ https://issues.apache.org/jira/browse/MEECROWAVE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-295. --- Resolution: Fixed > Upgrade to OWB 2.0.23 > - > > Key: MEECROWAVE-295 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-295 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-296) Upgrade to Johnzon 1.2.12
[ https://issues.apache.org/jira/browse/MEECROWAVE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-296. --- Resolution: Fixed > Upgrade to Johnzon 1.2.12 > - > > Key: MEECROWAVE-296 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-296 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MEECROWAVE-297) Upgrade to CXF 3.4.4
[ https://issues.apache.org/jira/browse/MEECROWAVE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved MEECROWAVE-297. --- Resolution: Fixed > Upgrade to CXF 3.4.4 > > > Key: MEECROWAVE-297 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-297 > Project: Meecrowave > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau >Priority: Major > Fix For: 1.2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-295) Upgrade to OWB 2.0.23
Romain Manni-Bucau created MEECROWAVE-295: - Summary: Upgrade to OWB 2.0.23 Key: MEECROWAVE-295 URL: https://issues.apache.org/jira/browse/MEECROWAVE-295 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.12 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-296) Upgrade to Johnzon 1.2.12
Romain Manni-Bucau created MEECROWAVE-296: - Summary: Upgrade to Johnzon 1.2.12 Key: MEECROWAVE-296 URL: https://issues.apache.org/jira/browse/MEECROWAVE-296 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.12 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MEECROWAVE-297) Upgrade to CXF 3.4.4
Romain Manni-Bucau created MEECROWAVE-297: - Summary: Upgrade to CXF 3.4.4 Key: MEECROWAVE-297 URL: https://issues.apache.org/jira/browse/MEECROWAVE-297 Project: Meecrowave Issue Type: Improvement Reporter: Romain Manni-Bucau Assignee: Romain Manni-Bucau Fix For: 1.2.12 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MEECROWAVE-261) upgrde to java16 ready versions
[ https://issues.apache.org/jira/browse/MEECROWAVE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355574#comment-17355574 ] Romain Manni-Bucau commented on MEECROWAVE-261: --- [~struberg] AFAIK it is the test utility to create the keystore only so think this issue is fixed (in terms of user consumption). > upgrde to java16 ready versions > --- > > Key: MEECROWAVE-261 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-261 > Project: Meecrowave > Issue Type: Task >Affects Versions: 1.2.9 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.2.12 > > > We've got some fixes in the chain which makes it possible to also run MW > under the upcoming Java16 release. This includes CXF, OpenWebBeans and > OpenJPA plus a few spec updates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OWB-1386) Print the exception's message when ERROR_0013 occurs
[
https://issues.apache.org/jira/browse/OWB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350532#comment-17350532
]
Romain Manni-Bucau commented on OWB-1386:
-
[~cocorossello] hello, not sure what you had in mind for \{0} but I guess it is
a parenthesis error more than a parameter issue, exception stack should be
logged I think. Adding the exception message can be another enhancement but not
sure we need it - really neutral here.
> Print the exception's message when ERROR_0013 occurs
>
>
> Key: OWB-1386
> URL: https://issues.apache.org/jira/browse/OWB-1386
> Project: OpenWebBeans
> Issue Type: Bug
>Affects Versions: 2.0.22
>Reporter: Vicente Rossello Jaume
>Priority: Minor
>
> I just got this (very rare) message error:
> 2021/05/22 08:13:28.925 ERROR [http-25]
> org.apache.webbeans.web.context.WebContextsService - Caught an Exception
> while starting a fresh session!
> I think that the exception's message is missing.
> I was going to change the message to:
> ERROR_0013 = Caught an Exception while starting a fresh session!: [{0}]
> Is it ok?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
