[jira] [Commented] (ARIES-2106) Memory leak in SPI-Fly when bundle is unloaded.
[
https://issues.apache.org/jira/browse/ARIES-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783721#comment-17783721
]
ASF subversion and git services commented on ARIES-2106:
Commit 51becafa4df52ea5f644eb4bb2e1147e5d78774d in aries's branch
refs/heads/trunk from JB Onofré
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=51becafa4 ]
ARIES-2106: fix memory leak when bundle is unloaded
> Memory leak in SPI-Fly when bundle is unloaded.
> ---
>
> Key: ARIES-2106
> URL: https://issues.apache.org/jira/browse/ARIES-2106
> Project: Aries
> Issue Type: Bug
> Components: SPI Fly
>Affects Versions: spifly-1.3.6
>Reporter: Chris Rankin
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: MemoryLeak, memory-leak
> Fix For: spifly-1.3.7
>
>
> On unloading a bundle from the Felix framework, SPI-Fly correctly removes the
> {{{}WeavingData{}}}, but forgets also to remove the consumer restrictions:
> {code:java|title=org.apache.aries.spifly.BaseActivator}
> public void removeWeavingData(Bundle bundle) {
> bundleWeavingData.remove(bundle);
> + consumerRestrictions.remove(bundle);
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2128) Upgrade to ASM 9.6
[ https://issues.apache.org/jira/browse/ARIES-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783720#comment-17783720 ] ASF subversion and git services commented on ARIES-2128: Commit 137207cc95f0f04ec525757df2e7ff2ace2316c8 in aries's branch refs/heads/trunk from JB Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=137207cc9 ] ARIES-2128: Upgrade to ASM 9.6 > Upgrade to ASM 9.6 > -- > > Key: ARIES-2128 > URL: https://issues.apache.org/jira/browse/ARIES-2128 > Project: Aries > Issue Type: Dependency upgrade > Components: SPI Fly >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: spifly-1.3.7 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2126) Upgrade to ASM 9.6
[ https://issues.apache.org/jira/browse/ARIES-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783714#comment-17783714 ] ASF subversion and git services commented on ARIES-2126: Commit 9ef2263deee9b686c7921eff900ab769ee0aab61 in aries's branch refs/heads/trunk from JB Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=9ef2263de ] ARIES-2126: Upgrade to ASM 9.6 > Upgrade to ASM 9.6 > -- > > Key: ARIES-2126 > URL: https://issues.apache.org/jira/browse/ARIES-2126 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.14 > > > https://asm.ow2.io/versions.html#9.5 required for Java 21 support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2126) Upgrade to ASM 9.6
[ https://issues.apache.org/jira/browse/ARIES-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783712#comment-17783712 ] ASF subversion and git services commented on ARIES-2126: Commit 89058608bec923f500151f38633f661ece27e58a in aries's branch refs/heads/trunk from JB Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=89058608b ] ARIES-2126: Upgrade to ASM 9.6 > Upgrade to ASM 9.6 > -- > > Key: ARIES-2126 > URL: https://issues.apache.org/jira/browse/ARIES-2126 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.14 > > > https://asm.ow2.io/versions.html#9.5 required for Java 21 support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2126) Upgrade to ASM 9.5
[ https://issues.apache.org/jira/browse/ARIES-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772181#comment-17772181 ] ASF subversion and git services commented on ARIES-2126: Commit 1c66f6c90c87998e205d8789a9449d6cc22c73de in aries's branch refs/heads/trunk from Christian Schneider [ https://gitbox.apache.org/repos/asf?p=aries.git;h=1c66f6c90 ] Merge pull request #242 from rovarga/aries2126 ARIES-2126: Update ASM to 9.5 > Upgrade to ASM 9.5 > -- > > Key: ARIES-2126 > URL: https://issues.apache.org/jira/browse/ARIES-2126 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Robert Varga >Priority: Major > > https://asm.ow2.io/versions.html#9.5 required for Java 21 support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2126) Upgrade to ASM 9.5
[ https://issues.apache.org/jira/browse/ARIES-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772180#comment-17772180 ] ASF subversion and git services commented on ARIES-2126: Commit e49322620e128bb2eef438ee3e15ea9541cb1014 in aries's branch refs/heads/trunk from Robert Varga [ https://gitbox.apache.org/repos/asf?p=aries.git;h=e49322620 ] ARIES-2126: Update ASM to 9.5 Signed-off-by: Robert Varga > Upgrade to ASM 9.5 > -- > > Key: ARIES-2126 > URL: https://issues.apache.org/jira/browse/ARIES-2126 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Robert Varga >Priority: Major > > https://asm.ow2.io/versions.html#9.5 required for Java 21 support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2127) Add Java 21 support
[
https://issues.apache.org/jira/browse/ARIES-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772182#comment-17772182
]
ASF subversion and git services commented on ARIES-2127:
Commit fa62254951363bfa95872866d535898cde26430b in aries's branch
refs/heads/trunk from Robert Varga
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=fa6225495 ]
ARIES-2127: Add constants for Java 20/21
Signed-off-by: Robert Varga
> Add Java 21 support
> ---
>
> Key: ARIES-2127
> URL: https://issues.apache.org/jira/browse/ARIES-2127
> Project: Aries
> Issue Type: Improvement
> Components: Proxy
>Reporter: Robert Varga
>Priority: Major
>
> Latest release is failing on Java 21 with:
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Invalid Java version 65
> at
> org.apache.aries.proxy.impl.ProxyUtils.getWeavingJavaVersion(ProxyUtils.java:104)
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceCombiningClassAdapter.(InterfaceCombiningClassAdapter.java:79)
> at
> org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.createProxyClass(ProxyClassLoader.java:155)
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator.getProxyInstance(InterfaceProxyGenerator.java:97)
> at
> org.apache.aries.proxy.impl.AsmProxyManager.createNewProxy(AsmProxyManager.java:80)
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:77)
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingProxy(AbstractProxyManager.java:42)
> at
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.createProxy(AbstractServiceReferenceRecipe.java:332)
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:125)
> ... 46 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2127) Add Java 21 support
[
https://issues.apache.org/jira/browse/ARIES-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772183#comment-17772183
]
ASF subversion and git services commented on ARIES-2127:
Commit a5064f11658c3168863e632675d2eaeecebca5e1 in aries's branch
refs/heads/trunk from Christian Schneider
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=a5064f116 ]
Merge pull request #243 from rovarga/aries2127
ARIES-2127: Add constants for Java 20/21
> Add Java 21 support
> ---
>
> Key: ARIES-2127
> URL: https://issues.apache.org/jira/browse/ARIES-2127
> Project: Aries
> Issue Type: Improvement
> Components: Proxy
>Reporter: Robert Varga
>Priority: Major
>
> Latest release is failing on Java 21 with:
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Invalid Java version 65
> at
> org.apache.aries.proxy.impl.ProxyUtils.getWeavingJavaVersion(ProxyUtils.java:104)
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceCombiningClassAdapter.(InterfaceCombiningClassAdapter.java:79)
> at
> org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.createProxyClass(ProxyClassLoader.java:155)
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator.getProxyInstance(InterfaceProxyGenerator.java:97)
> at
> org.apache.aries.proxy.impl.AsmProxyManager.createNewProxy(AsmProxyManager.java:80)
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:77)
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingProxy(AbstractProxyManager.java:42)
> at
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.createProxy(AbstractServiceReferenceRecipe.java:332)
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:125)
> ... 46 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2108) Catch 'NoClassDefFoundError' when loading Service-Provider instances
[
https://issues.apache.org/jira/browse/ARIES-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770370#comment-17770370
]
ASF subversion and git services commented on ARIES-2108:
Commit 891b7318d7925f58303ff8314660085c74a6d2cf in aries's branch
refs/heads/trunk from Hannes Wellmann
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=891b7318d ]
[ARIES-2108] Catch NoClassDefFoundError when loading Service-Providers
Fixes https://issues.apache.org/jira/browse/ARIES-2108.
Loading ServiceProvider instances, which depend on classes absent at
runtime (e.g. because they are contained in an optional dependency)
throws a NoClassDefFoundError instead of a ClassNotFoundException,
which is propagated to the caller of
ProviderBundleTrackerCustomizer.addingBundle() and leads to an empty
list of providers.
Instead a NoClassDefFoundError should be handled like a
ClassNotFoundException.
The reason for this different exception in this case is that although
the service class is found it cannot be defined.
The javadoc of 'NoClassDefFoundError' states:
"Thrown if the Java Virtual Machine or a ClassLoader instance tries to
load in the definition of a class (as part of a normal method call or as
part of creating a new instance using the new expression) and no
definition of the class could be found."
The javadoc of 'ClassNotFoundException' states:
"Thrown when an application tries to load in a class through its string
name using:
- The forName method in class Class.
- The findSystemClass method in class ClassLoader .
- The loadClass method in class ClassLoader.
but no definition for the class with the specified name could be found."
> Catch 'NoClassDefFoundError' when loading Service-Provider instances
>
>
> Key: ARIES-2108
> URL: https://issues.apache.org/jira/browse/ARIES-2108
> Project: Aries
> Issue Type: Bug
> Components: SPI Fly
>Affects Versions: spifly-1.3.6
>Reporter: Hannes Wellmann
>Priority: Major
>
> Loading ServiceProvider instances which depend on classes absent at runtime
> (e.g. because they are contained in an optional dependency) throws a
> {{NoClassDefFoundError}} instead of a {{{}ClassNotFoundException{}}}, which
> is propagated to the caller of
> {{ProviderBundleTrackerCustomizer.addingBundle()}} and leads to an empty list
> of providers. Instead a {{NoClassDefFoundError}} should be handled like a
> {{{}ClassNotFoundException{}}}.
> The reason for this different exception in this case is that although the
> service class is found it cannot be defined.
> The javadoc of {{NoClassDefFoundError}} states:
> {code:java}
> Thrown if the Java Virtual Machine or a ClassLoader instance tries to load in
> the definition of a class
> (as part of a normal method call or as part of creating a new instance using
> the new expression)
> and no definition of the class could be found.{code}
> The javadoc of {{ClassNotFoundException}} states:
> {code:java}
> Thrown when an application tries to load in a class through its string name
> using:
> - The forName method in class Class.
> - The findSystemClass method in class ClassLoader .
> - The loadClass method in class ClassLoader.
> but no definition for the class with the specified name could be found.{code}
> One example where this scenario occurs is Logback for SLF4J-2. Besides the
> {{SLF4JServiceProvider}} service this bundle also provides a
> {{{}ServletContainerInitializer{}}}, which is only relevant/intended for
> server/web-app environments where an implementation of the
> {{jakarta./javax.servlet}} API is provided.
> Therefore the maven dependencies for {{jakarta./javax.servlet}} are in the
> provided scope and optional and correspondingly the
> {{jakarta./javax.servlet}} packages are only optionally imported in the
> MANIFEST.MF.
> [https://github.com/qos-ch/logback/blob/4e069d34d9422a43511ae7d6242a27caa8834e14/logback-classic/pom.xml#L335-L356]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2108) Catch 'NoClassDefFoundError' when loading Service-Provider instances
[
https://issues.apache.org/jira/browse/ARIES-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770371#comment-17770371
]
ASF subversion and git services commented on ARIES-2108:
Commit 09b2d7593e6dbd51b9b8735a7106781957f944e9 in aries's branch
refs/heads/trunk from Christian Schneider
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=09b2d7593 ]
Merge pull request #233 from HannesWell/noClassDefFoundError
[ARIES-2108] Catch 'NoClassDefFoundError' when loading Service-Provider
instances
> Catch 'NoClassDefFoundError' when loading Service-Provider instances
>
>
> Key: ARIES-2108
> URL: https://issues.apache.org/jira/browse/ARIES-2108
> Project: Aries
> Issue Type: Bug
> Components: SPI Fly
>Affects Versions: spifly-1.3.6
>Reporter: Hannes Wellmann
>Priority: Major
>
> Loading ServiceProvider instances which depend on classes absent at runtime
> (e.g. because they are contained in an optional dependency) throws a
> {{NoClassDefFoundError}} instead of a {{{}ClassNotFoundException{}}}, which
> is propagated to the caller of
> {{ProviderBundleTrackerCustomizer.addingBundle()}} and leads to an empty list
> of providers. Instead a {{NoClassDefFoundError}} should be handled like a
> {{{}ClassNotFoundException{}}}.
> The reason for this different exception in this case is that although the
> service class is found it cannot be defined.
> The javadoc of {{NoClassDefFoundError}} states:
> {code:java}
> Thrown if the Java Virtual Machine or a ClassLoader instance tries to load in
> the definition of a class
> (as part of a normal method call or as part of creating a new instance using
> the new expression)
> and no definition of the class could be found.{code}
> The javadoc of {{ClassNotFoundException}} states:
> {code:java}
> Thrown when an application tries to load in a class through its string name
> using:
> - The forName method in class Class.
> - The findSystemClass method in class ClassLoader .
> - The loadClass method in class ClassLoader.
> but no definition for the class with the specified name could be found.{code}
> One example where this scenario occurs is Logback for SLF4J-2. Besides the
> {{SLF4JServiceProvider}} service this bundle also provides a
> {{{}ServletContainerInitializer{}}}, which is only relevant/intended for
> server/web-app environments where an implementation of the
> {{jakarta./javax.servlet}} API is provided.
> Therefore the maven dependencies for {{jakarta./javax.servlet}} are in the
> provided scope and optional and correspondingly the
> {{jakarta./javax.servlet}} packages are only optionally imported in the
> MANIFEST.MF.
> [https://github.com/qos-ch/logback/blob/4e069d34d9422a43511ae7d6242a27caa8834e14/logback-classic/pom.xml#L335-L356]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2112) ClassCastException on JDK 9+
[ https://issues.apache.org/jira/browse/ARIES-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763684#comment-17763684 ] ASF subversion and git services commented on ARIES-2112: Commit 6a09c782bf708bbe1f9cffc57a404e0155900a88 in aries-rsa's branch refs/heads/master from Amichai Rothman [ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=6a09c782 ] ARIES-2112 - Fix ClassCastException on JDK9+ > ClassCastException on JDK 9+ > > > Key: ARIES-2112 > URL: https://issues.apache.org/jira/browse/ARIES-2112 > Project: Aries > Issue Type: Bug > Components: Remote Service Admin >Affects Versions: rsa-1.16.1 >Reporter: Amichai Rothman >Priority: Major > > Arrays.asList().toArray() returned type has changed from String[] to Object[] > due to [https://bugs.openjdk.org/browse/JDK-6260652,] causing > ClassCastException on JDK9+ (and caught by the unit tests :) ). > > java.lang.ClassCastException: class [Ljava.lang.Object; cannot be cast to > class [Ljava.lang.String; ([Ljava.lang.Object; and [Ljava.lang.String; are in > module java.base of loader 'bootstrap') > > at > org.apache.aries.rsa.eapub.EventAdminHelperTest$1.answer(EventAdminHelperTest.java:89) > at org.easymock.internal.Result.answer(Result.java:106) > at org.easymock.internal.ReplayState.invokeInner(ReplayState.java:60) > at org.easymock.internal.ReplayState.invoke(ReplayState.java:46) > at > org.easymock.internal.MockInvocationHandler.invoke(MockInvocationHandler.java:40) > at > org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:94) > at com.sun.proxy.$Proxy10.postEvent(Unknown Source) > at > org.apache.aries.rsa.eapub.EventAdminHelper.notifyEventAdmins(EventAdminHelper.java:103) > at > org.apache.aries.rsa.eapub.EventAdminHelper.remoteAdminEvent(EventAdminHelper.java:86) > at > org.apache.aries.rsa.eapub.EventAdminHelperTest.testPublishNotification(EventAdminHelperTest.java:122) > 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) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69) > at > com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38) > at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11) > at > com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35) > at > com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:232) > at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:55) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-1219) Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not supported with computeFrames option
[ https://issues.apache.org/jira/browse/ARIES-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709886#comment-17709886 ] ASF subversion and git services commented on ARIES-1219: Commit 55b2b3482d9a8eee30a04434bb7768bbec1daf43 in aries's branch refs/heads/trunk from Timothy James Ward [ https://gitbox.apache.org/repos/asf?p=aries.git;h=55b2b3482 ] Merge pull request #215 from stiemannkj1/ARIES-1219-support-jsr-ret-in-spi-fly ARIES-1219 Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not supported with computeFrames option > Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not > supported with computeFrames option > -- > > Key: ARIES-1219 > URL: https://issues.apache.org/jira/browse/ARIES-1219 > Project: Aries > Issue Type: Question > Environment: Apache Karaf 3.0.1 >Reporter: Eleni Giannakopoulou >Priority: Major > Labels: Fly, JSR/RET, Karaf, SPI > > Trying to integrate jBPM6 in Apache Karaf 3.0.1, we came across with > ServiceLoader.load() issues and for that reason we have used dynamic weaving > of Aries SPI Fly. > While some classloading of jBPM classes, we get the following exception: > java.lang.ClassFormatError: Weaving hook failed. > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2074) > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1501) > at > org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75) > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_45] > ... > Caused by: java.lang.RuntimeException: JSR/RET are not supported with > computeFrames option > at org.objectweb.asm.Frame.a(Unknown Source) > at org.objectweb.asm.MethodWriter.visitJumpInsn(Unknown Source) > at org.objectweb.asm.MethodVisitor.visitJumpInsn(Unknown Source) > at org.objectweb.asm.ClassReader.a(Unknown Source) > at org.objectweb.asm.ClassReader.b(Unknown Source) > at org.objectweb.asm.ClassReader.accept(Unknown Source) > at org.objectweb.asm.ClassReader.accept(Unknown Source) > at > org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61) > at > org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1127) > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2057) > It seems that there is a problem with StackMap tables used in jBPM6. jBPM6 > has been built using JDK 1.6.0_45 and the JVM runs 1.7.0_45. > Any suggestions would be appreciated as this is a blocking issue for us. > Thank you in advance, > Eleni. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-1219) Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not supported with computeFrames option
[ https://issues.apache.org/jira/browse/ARIES-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709885#comment-17709885 ] ASF subversion and git services commented on ARIES-1219: Commit 9df919f40ce6022b8a8d354d1d4273d9d91d876e in aries's branch refs/heads/trunk from Kyle Stiemann [ https://gitbox.apache.org/repos/asf?p=aries.git;h=9df919f40 ] Fix ARIES-1219 Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not supported with computeFrames option > Weaving of Aries SPI Fly bundle produces RuntimeException: JSR/RET are not > supported with computeFrames option > -- > > Key: ARIES-1219 > URL: https://issues.apache.org/jira/browse/ARIES-1219 > Project: Aries > Issue Type: Question > Environment: Apache Karaf 3.0.1 >Reporter: Eleni Giannakopoulou >Priority: Major > Labels: Fly, JSR/RET, Karaf, SPI > > Trying to integrate jBPM6 in Apache Karaf 3.0.1, we came across with > ServiceLoader.load() issues and for that reason we have used dynamic weaving > of Aries SPI Fly. > While some classloading of jBPM classes, we get the following exception: > java.lang.ClassFormatError: Weaving hook failed. > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2074) > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1501) > at > org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75) > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_45] > ... > Caused by: java.lang.RuntimeException: JSR/RET are not supported with > computeFrames option > at org.objectweb.asm.Frame.a(Unknown Source) > at org.objectweb.asm.MethodWriter.visitJumpInsn(Unknown Source) > at org.objectweb.asm.MethodVisitor.visitJumpInsn(Unknown Source) > at org.objectweb.asm.ClassReader.a(Unknown Source) > at org.objectweb.asm.ClassReader.b(Unknown Source) > at org.objectweb.asm.ClassReader.accept(Unknown Source) > at org.objectweb.asm.ClassReader.accept(Unknown Source) > at > org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:61) > at > org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1127) > at > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2057) > It seems that there is a problem with StackMap tables used in jBPM6. jBPM6 > has been built using JDK 1.6.0_45 and the JVM runs 1.7.0_45. > Any suggestions would be appreciated as this is a blocking issue for us. > Thank you in advance, > Eleni. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2090) Verify and improve Aries JAXRS Whiteboard Karaf features repository
[ https://issues.apache.org/jira/browse/ARIES-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653037#comment-17653037 ] ASF subversion and git services commented on ARIES-2090: Commit 005719c6aa17054ab71251d97532374064dcc0e8 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=005719c ] Merge pull request #199 from jbonofre/ARIES-2090 [ARIES-2090] Refactore and fix Karaf features > Verify and improve Aries JAXRS Whiteboard Karaf features repository > --- > > Key: ARIES-2090 > URL: https://issues.apache.org/jira/browse/ARIES-2090 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2090) Verify and improve Aries JAXRS Whiteboard Karaf features repository
[ https://issues.apache.org/jira/browse/ARIES-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653036#comment-17653036 ] ASF subversion and git services commented on ARIES-2090: Commit db4317c28614b7b0de9c6f4039dd0884061a4513 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=db4317c ] [ARIES-2090] Refactore and fix Karaf features > Verify and improve Aries JAXRS Whiteboard Karaf features repository > --- > > Key: ARIES-2090 > URL: https://issues.apache.org/jira/browse/ARIES-2090 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2104) Upgrade to flatten-maven-plugin 1.3.0
[ https://issues.apache.org/jira/browse/ARIES-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653032#comment-17653032 ] ASF subversion and git services commented on ARIES-2104: Commit 16253469dbddab2ce5dd659b91e998e65ce8d963 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=1625346 ] [ARIES-2104] Upgrade to flatten-maven-plugin 1.3.0 > Upgrade to flatten-maven-plugin 1.3.0 > - > > Key: ARIES-2104 > URL: https://issues.apache.org/jira/browse/ARIES-2104 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2104) Upgrade to flatten-maven-plugin 1.3.0
[ https://issues.apache.org/jira/browse/ARIES-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653033#comment-17653033 ] ASF subversion and git services commented on ARIES-2104: Commit 207e6a402226af3be604d0e487f4acb0f06dc7f0 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=207e6a4 ] Merge pull request #223 from jbonofre/ARIES-2104 [ARIES-2104] Upgrade to flatten-maven-plugin 1.3.0 > Upgrade to flatten-maven-plugin 1.3.0 > - > > Key: ARIES-2104 > URL: https://issues.apache.org/jira/browse/ARIES-2104 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2091) Upgrade to CXF 3.5.5
[ https://issues.apache.org/jira/browse/ARIES-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652493#comment-17652493 ] ASF subversion and git services commented on ARIES-2091: Commit 250cd3d4e3e6eef6a5e24399dcf0a2b5ae13cc5e in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=250cd3d ] [ARIES-2091] Upgrade to CXF 3.5.5 > Upgrade to CXF 3.5.5 > > > Key: ARIES-2091 > URL: https://issues.apache.org/jira/browse/ARIES-2091 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2091) Upgrade to CXF 3.5.5
[ https://issues.apache.org/jira/browse/ARIES-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652494#comment-17652494 ] ASF subversion and git services commented on ARIES-2091: Commit 841c96a52802f7a9736924e7046bd12a1b7ef9fe in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=841c96a ] Merge pull request #215 from jbonofre/ARIES-2091 [ARIES-2091] Upgrade to CXF 3.5.5 > Upgrade to CXF 3.5.5 > > > Key: ARIES-2091 > URL: https://issues.apache.org/jira/browse/ARIES-2091 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2094) Upgrade to Jettison 1.5.3
[ https://issues.apache.org/jira/browse/ARIES-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652400#comment-17652400 ] ASF subversion and git services commented on ARIES-2094: Commit 21fcaa277fc0997e37bdc16689d270d3d5ed9156 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=21fcaa2 ] Merge pull request #212 from jbonofre/ARIES-2094 [ARIES-2094] Upgrade to jettison 1.5.3 > Upgrade to Jettison 1.5.3 > - > > Key: ARIES-2094 > URL: https://issues.apache.org/jira/browse/ARIES-2094 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2094) Upgrade to Jettison 1.5.3
[ https://issues.apache.org/jira/browse/ARIES-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652399#comment-17652399 ] ASF subversion and git services commented on ARIES-2094: Commit d6b56bcdbdacec29bfd92252373bf3ac698396d9 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=d6b56bc ] [ARIES-2094] Upgrade to jettison 1.5.3 > Upgrade to Jettison 1.5.3 > - > > Key: ARIES-2094 > URL: https://issues.apache.org/jira/browse/ARIES-2094 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2092) Upgrade to jackson 2.14.1
[ https://issues.apache.org/jira/browse/ARIES-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652394#comment-17652394 ] ASF subversion and git services commented on ARIES-2092: Commit b5655f1a58318f67650637763a7887357a922903 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=b5655f1 ] [ARIES-2092] Upgrade to Jackson 2.14.1 > Upgrade to jackson 2.14.1 > - > > Key: ARIES-2092 > URL: https://issues.apache.org/jira/browse/ARIES-2092 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2092) Upgrade to jackson 2.14.1
[ https://issues.apache.org/jira/browse/ARIES-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652395#comment-17652395 ] ASF subversion and git services commented on ARIES-2092: Commit bf4b90eda4d9825b8b4001e6dfaed60d5e48 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=bf4b90e ] Merge pull request #214 from jbonofre/ARIES-2092 [ARIES-2092] Upgrade to Jackson 2.14.1 > Upgrade to jackson 2.14.1 > - > > Key: ARIES-2092 > URL: https://issues.apache.org/jira/browse/ARIES-2092 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2103) Upgrade to shiro 1.10.1
[ https://issues.apache.org/jira/browse/ARIES-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652391#comment-17652391 ] ASF subversion and git services commented on ARIES-2103: Commit a950281b0a52038cec4c8577062437628d02720c in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=a950281 ] [ARIES-2103] Upgrade to shiro 1.10.1 > Upgrade to shiro 1.10.1 > --- > > Key: ARIES-2103 > URL: https://issues.apache.org/jira/browse/ARIES-2103 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2103) Upgrade to shiro 1.10.1
[ https://issues.apache.org/jira/browse/ARIES-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652392#comment-17652392 ] ASF subversion and git services commented on ARIES-2103: Commit 674c134e2340854ae6db8e2d0f561768b042c970 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=674c134 ] Merge pull request #213 from jbonofre/ARIES-2103 [ARIES-2103] Upgrade to shiro 1.10.1 > Upgrade to shiro 1.10.1 > --- > > Key: ARIES-2103 > URL: https://issues.apache.org/jira/browse/ARIES-2103 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2096) Upgrade to json-unit-assertj 2.36.0
[ https://issues.apache.org/jira/browse/ARIES-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652382#comment-17652382 ] ASF subversion and git services commented on ARIES-2096: Commit 400e6dfd52f51f453f528185cd1ab814395e035c in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=400e6df ] Merge pull request #211 from jbonofre/ARIES-2096 [ARIES-2096] Upgrade to json-unit-assertj 2.36.0 > Upgrade to json-unit-assertj 2.36.0 > --- > > Key: ARIES-2096 > URL: https://issues.apache.org/jira/browse/ARIES-2096 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2098) Upgrade to Felix ConfigAdmin 1.9.26
[ https://issues.apache.org/jira/browse/ARIES-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652377#comment-17652377 ] ASF subversion and git services commented on ARIES-2098: Commit b9825694fb4e27e8f6408f853900773168fe028a in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=b982569 ] [ARIES-2098] Upgrade to Felix ConfigAdmin 1.9.26 > Upgrade to Felix ConfigAdmin 1.9.26 > --- > > Key: ARIES-2098 > URL: https://issues.apache.org/jira/browse/ARIES-2098 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2096) Upgrade to json-unit-assertj 2.36.0
[ https://issues.apache.org/jira/browse/ARIES-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652381#comment-17652381 ] ASF subversion and git services commented on ARIES-2096: Commit 8f0b254af5272052e93338a3fb3bcf9c9a8a5e68 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=8f0b254 ] [ARIES-2096] Upgrade to json-unit-assertj 2.36.0 > Upgrade to json-unit-assertj 2.36.0 > --- > > Key: ARIES-2096 > URL: https://issues.apache.org/jira/browse/ARIES-2096 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2098) Upgrade to Felix ConfigAdmin 1.9.26
[ https://issues.apache.org/jira/browse/ARIES-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652378#comment-17652378 ] ASF subversion and git services commented on ARIES-2098: Commit 6acea878841a6b44185428a076cdb71f71a6c771 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=6acea87 ] Merge pull request #204 from jbonofre/ARIES-2098 [ARIES-2098] Upgrade to Felix ConfigAdmin 1.9.26 > Upgrade to Felix ConfigAdmin 1.9.26 > --- > > Key: ARIES-2098 > URL: https://issues.apache.org/jira/browse/ARIES-2098 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2097) Upgrade to spifly 1.3.6
[ https://issues.apache.org/jira/browse/ARIES-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652380#comment-17652380 ] ASF subversion and git services commented on ARIES-2097: Commit 53b08d0f157ea3c8b7ef3382ed4db7a3a9224dca in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=53b08d0 ] Merge pull request #205 from jbonofre/ARIES-2097 [ARIES-2097] Upgrade to spifly 1.3.6 > Upgrade to spifly 1.3.6 > --- > > Key: ARIES-2097 > URL: https://issues.apache.org/jira/browse/ARIES-2097 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2097) Upgrade to spifly 1.3.6
[ https://issues.apache.org/jira/browse/ARIES-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652379#comment-17652379 ] ASF subversion and git services commented on ARIES-2097: Commit be0e4091b47d44636d5eaec5ef1b854c0e1d6b01 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=be0e409 ] [ARIES-2097] Upgrade to spifly 1.3.6 > Upgrade to spifly 1.3.6 > --- > > Key: ARIES-2097 > URL: https://issues.apache.org/jira/browse/ARIES-2097 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2100) Upgrade to johnzon 1.2.19
[ https://issues.apache.org/jira/browse/ARIES-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651941#comment-17651941 ] ASF subversion and git services commented on ARIES-2100: Commit eca6e0ec61a98e93177836def67257d61e908b9a in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=eca6e0e ] Merge pull request #203 from jbonofre/ARIES-2100 [ARIES)-2100] Upgrade to johnzon 1.2.19 > Upgrade to johnzon 1.2.19 > - > > Key: ARIES-2100 > URL: https://issues.apache.org/jira/browse/ARIES-2100 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2101) Upgrade to assertj 3.23.1
[ https://issues.apache.org/jira/browse/ARIES-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651936#comment-17651936 ] ASF subversion and git services commented on ARIES-2101: Commit cf66c1cc879f29e36fc862bc670817eb7344f8ed in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=cf66c1c ] Merge pull request #202 from jbonofre/ARIES-2101 [ARIES-2101] Upgrade to assertj 3.23.1 > Upgrade to assertj 3.23.1 > - > > Key: ARIES-2101 > URL: https://issues.apache.org/jira/browse/ARIES-2101 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2101) Upgrade to assertj 3.23.1
[ https://issues.apache.org/jira/browse/ARIES-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651935#comment-17651935 ] ASF subversion and git services commented on ARIES-2101: Commit c07aaa6e38bb13849111de51b67034b34f904511 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=c07aaa6 ] [ARIES-2101] Upgrade to assertj 3.23.1 > Upgrade to assertj 3.23.1 > - > > Key: ARIES-2101 > URL: https://issues.apache.org/jira/browse/ARIES-2101 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2093) Upgrade to bnd 6.4.0
[ https://issues.apache.org/jira/browse/ARIES-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651859#comment-17651859 ] ASF subversion and git services commented on ARIES-2093: Commit 9ab269fb8616abc5405e168c391b84d698e37535 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=9ab269f ] Merge pull request #200 from jbonofre/ARIES-2093 [ARIES-2093] Upgrade to bnd 6.4.0 > Upgrade to bnd 6.4.0 > > > Key: ARIES-2093 > URL: https://issues.apache.org/jira/browse/ARIES-2093 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2093) Upgrade to bnd 6.4.0
[ https://issues.apache.org/jira/browse/ARIES-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651858#comment-17651858 ] ASF subversion and git services commented on ARIES-2093: Commit d10d7400067046c2a8a7c8b1f27b447659bf1056 in aries-jax-rs-whiteboard's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=d10d740 ] [ARIES-2093] Upgrade to bnd 6.4.0 > Upgrade to bnd 6.4.0 > > > Key: ARIES-2093 > URL: https://issues.apache.org/jira/browse/ARIES-2093 > Project: Aries > Issue Type: Dependency upgrade > Components: jax-rs-whiteboard >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2095) Fix HttpWhiteboardCoexistenceTest tests
[
https://issues.apache.org/jira/browse/ARIES-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651857#comment-17651857
]
ASF subversion and git services commented on ARIES-2095:
Commit d8a2287e695fd4a33cad2a8e6e098b9ae21853ce in aries-jax-rs-whiteboard's
branch refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=d8a2287 ]
Merge pull request #201 from jbonofre/ARIES-2095
[ARIES-2095] Simple fix related to bnd 6.2.0 update
> Fix HttpWhiteboardCoexistenceTest tests
> ---
>
> Key: ARIES-2095
> URL: https://issues.apache.org/jira/browse/ARIES-2095
> Project: Aries
> Issue Type: Bug
> Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-2.0.2
>
>
> Since this commit (upgrade to bnd 6.2.0):
> {code:java}
> commit 54ffc31723e26e947a3ce3671d260753ad0a9a93
> Author: Raymond Augé
> Date: Sun Apr 10 22:47:32 2022 -0400
> update bnd to 6.2.0
>
> Signed-off-by: Raymond Auge {code}
> The itest fails. I'm fixing that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2095) Fix HttpWhiteboardCoexistenceTest tests
[
https://issues.apache.org/jira/browse/ARIES-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651856#comment-17651856
]
ASF subversion and git services commented on ARIES-2095:
Commit 4d1bb95d4702290c0112735506a60376a894643d in aries-jax-rs-whiteboard's
branch refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=4d1bb95 ]
[ARIES-2095] Simple fix related to bnd 6.2.0 update
> Fix HttpWhiteboardCoexistenceTest tests
> ---
>
> Key: ARIES-2095
> URL: https://issues.apache.org/jira/browse/ARIES-2095
> Project: Aries
> Issue Type: Bug
> Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-2.0.2
>
>
> Since this commit (upgrade to bnd 6.2.0):
> {code:java}
> commit 54ffc31723e26e947a3ce3671d260753ad0a9a93
> Author: Raymond Augé
> Date: Sun Apr 10 22:47:32 2022 -0400
> update bnd to 6.2.0
>
> Signed-off-by: Raymond Auge {code}
> The itest fails. I'm fixing that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARIES-2086) Add JDK 19 support
[ https://issues.apache.org/jira/browse/ARIES-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644398#comment-17644398 ] ASF subversion and git services commented on ARIES-2086: Commit 12d322043e5c3c2bc7e907662ad37ff06c1a711e in aries's branch refs/heads/dependabot/maven/samples/org.apache.derby-derby-10.14.2.0 from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=12d322043 ] [ARIES-2086] Add JDK19 support > Add JDK 19 support > -- > > Key: ARIES-2086 > URL: https://issues.apache.org/jira/browse/ARIES-2086 > Project: Aries > Issue Type: New Feature > Components: Proxy >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2084) Upgrade to ASM 9.4
[ https://issues.apache.org/jira/browse/ARIES-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644397#comment-17644397 ] ASF subversion and git services commented on ARIES-2084: Commit 396d72f223462f06f5ddd80db90a7c6e5ea06b43 in aries's branch refs/heads/dependabot/maven/samples/org.apache.derby-derby-10.14.2.0 from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=396d72f22 ] [ARIES-2084] Upgrade to ASM 9.4 > Upgrade to ASM 9.4 > -- > > Key: ARIES-2084 > URL: https://issues.apache.org/jira/browse/ARIES-2084 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2070) aries-proxy incompatible with asm 5
[
https://issues.apache.org/jira/browse/ARIES-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644396#comment-17644396
]
ASF subversion and git services commented on ARIES-2070:
Commit 46e8662265b332157357b06360833bf4bc6ce547 in aries's branch
refs/heads/dependabot/maven/samples/org.apache.derby-derby-10.14.2.0 from
Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=46e866226 ]
Merge pull request #144 from holger-at-work/trunk
ARIES-2070 changed asm minimum version to 9
> aries-proxy incompatible with asm 5
> ---
>
> Key: ARIES-2070
> URL: https://issues.apache.org/jira/browse/ARIES-2070
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.11
>Reporter: Holger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: proxy-impl-1.1.13
>
>
> Scenario:
> Our Apache Karaf 4.3.3 based application provides two versions of asm: 5.2
> and 9.2.0
> When starting karaf, the following exception occurs:
> {code:java}
> 2022-03-24 15:38:28,216 | ERROR | tures-3-thread-1 |
> o.a.a.b.c.BlueprintContainerImpl | 192 - org.apache.aries.blueprint |
> 1.10.3 | Unable to start container for blueprint bundle
> org.apache.karaf.shell.core/4.3.3
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> java.lang.NoClassDefFoundError: org/objectweb/asm/commons/AdviceAdapter
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:190)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:737)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:433)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180)
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2336)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
>
[jira] [Commented] (ARIES-2070) aries-proxy incompatible with asm 5
[
https://issues.apache.org/jira/browse/ARIES-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644395#comment-17644395
]
ASF subversion and git services commented on ARIES-2070:
Commit dbf5c9821a61f496a20963ddd31daa80cbae0b27 in aries's branch
refs/heads/dependabot/maven/samples/org.apache.derby-derby-10.14.2.0 from hs79aa
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=dbf5c9821 ]
ARIES-2070 changed asm minimum version to 9
> aries-proxy incompatible with asm 5
> ---
>
> Key: ARIES-2070
> URL: https://issues.apache.org/jira/browse/ARIES-2070
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.11
>Reporter: Holger
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: proxy-impl-1.1.13
>
>
> Scenario:
> Our Apache Karaf 4.3.3 based application provides two versions of asm: 5.2
> and 9.2.0
> When starting karaf, the following exception occurs:
> {code:java}
> 2022-03-24 15:38:28,216 | ERROR | tures-3-thread-1 |
> o.a.a.b.c.BlueprintContainerImpl | 192 - org.apache.aries.blueprint |
> 1.10.3 | Unable to start container for blueprint bundle
> org.apache.karaf.shell.core/4.3.3
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> java.lang.NoClassDefFoundError: org/objectweb/asm/commons/AdviceAdapter
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:190)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:737)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:433)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180)
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2336)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
>
[jira] [Commented] (ARIES-2086) Add JDK 19 support
[ https://issues.apache.org/jira/browse/ARIES-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614359#comment-17614359 ] ASF subversion and git services commented on ARIES-2086: Commit 12d322043e5c3c2bc7e907662ad37ff06c1a711e in aries's branch refs/heads/trunk from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=12d322043 ] [ARIES-2086] Add JDK19 support > Add JDK 19 support > -- > > Key: ARIES-2086 > URL: https://issues.apache.org/jira/browse/ARIES-2086 > Project: Aries > Issue Type: New Feature > Components: Proxy >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2084) Upgrade to ASM 9.4
[ https://issues.apache.org/jira/browse/ARIES-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614357#comment-17614357 ] ASF subversion and git services commented on ARIES-2084: Commit 396d72f223462f06f5ddd80db90a7c6e5ea06b43 in aries's branch refs/heads/trunk from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=396d72f22 ] [ARIES-2084] Upgrade to ASM 9.4 > Upgrade to ASM 9.4 > -- > > Key: ARIES-2084 > URL: https://issues.apache.org/jira/browse/ARIES-2084 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.13 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARIES-2070) aries-proxy incompatible with asm 5
[
https://issues.apache.org/jira/browse/ARIES-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614354#comment-17614354
]
ASF subversion and git services commented on ARIES-2070:
Commit dbf5c9821a61f496a20963ddd31daa80cbae0b27 in aries's branch
refs/heads/trunk from hs79aa
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=dbf5c9821 ]
ARIES-2070 changed asm minimum version to 9
> aries-proxy incompatible with asm 5
> ---
>
> Key: ARIES-2070
> URL: https://issues.apache.org/jira/browse/ARIES-2070
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.11
>Reporter: Holger
>Priority: Major
>
> Scenario:
> Our Apache Karaf 4.3.3 based application provides two versions of asm: 5.2
> and 9.2.0
> When starting karaf, the following exception occurs:
> {code:java}
> 2022-03-24 15:38:28,216 | ERROR | tures-3-thread-1 |
> o.a.a.b.c.BlueprintContainerImpl | 192 - org.apache.aries.blueprint |
> 1.10.3 | Unable to start container for blueprint bundle
> org.apache.karaf.shell.core/4.3.3
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> java.lang.NoClassDefFoundError: org/objectweb/asm/commons/AdviceAdapter
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:190)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:737)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:433)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180)
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2336)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160)
> at
[jira] [Commented] (ARIES-2070) aries-proxy incompatible with asm 5
[
https://issues.apache.org/jira/browse/ARIES-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614355#comment-17614355
]
ASF subversion and git services commented on ARIES-2070:
Commit 46e8662265b332157357b06360833bf4bc6ce547 in aries's branch
refs/heads/trunk from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=46e866226 ]
Merge pull request #144 from holger-at-work/trunk
ARIES-2070 changed asm minimum version to 9
> aries-proxy incompatible with asm 5
> ---
>
> Key: ARIES-2070
> URL: https://issues.apache.org/jira/browse/ARIES-2070
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.11
>Reporter: Holger
>Priority: Major
>
> Scenario:
> Our Apache Karaf 4.3.3 based application provides two versions of asm: 5.2
> and 9.2.0
> When starting karaf, the following exception occurs:
> {code:java}
> 2022-03-24 15:38:28,216 | ERROR | tures-3-thread-1 |
> o.a.a.b.c.BlueprintContainerImpl | 192 - org.apache.aries.blueprint |
> 1.10.3 | Unable to start container for blueprint bundle
> org.apache.karaf.shell.core/4.3.3
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> java.lang.NoClassDefFoundError: org/objectweb/asm/commons/AdviceAdapter
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:141)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:810)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:784)
> at
> org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:765)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:699)
> at
> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:666)
> at
> org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:81)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:90)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:360)
> at
> org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:190)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:737)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:433)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180)
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2336)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165)
> at
>
[jira] [Commented] (ARIES-2072) Aries CDI doesn't support Java 17
[
https://issues.apache.org/jira/browse/ARIES-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531998#comment-17531998
]
ASF subversion and git services commented on ARIES-2072:
Commit ea3e639b781ab3e111661c92afdb61f5d574bd61 in aries-cdi's branch
refs/heads/master from Jakub Herkel
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=ea3e639 ]
ARIES-2072 update karaf feature.xml & create a karaf feature for weld CDI
provider
> Aries CDI doesn't support Java 17
> -
>
> Key: ARIES-2072
> URL: https://issues.apache.org/jira/browse/ARIES-2072
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Affects Versions: cdi-1.1.5
> Environment: Apache Karaf 4.3.6
> Openjdk 17
> Fedora 36
>Reporter: Jakub Herkel
>Priority: Major
>
> I tried the latest unreleased version 1.1.5 with a Apache Karaf running under
> Java17 (with classes compiled with Java17) and I can see this exception:
> {code:java}
> The activate method has thrown an exception
> java.lang.IllegalArgumentException: Unsupported class file major version 61
> at org.apache.xbean.asm8.ClassReader.(ClassReader.java:196) ~[?:?]
> at org.apache.xbean.asm8.ClassReader.(ClassReader.java:177) ~[?:?]
> at org.apache.xbean.asm8.ClassReader.(ClassReader.java:163) ~[?:?]
> at org.apache.xbean.asm8.ClassReader.(ClassReader.java:284) ~[?:?]
> at
> org.apache.xbean.finder.BundleAssignableClassFinder.isSuperClassAssignable(BundleAssignableClassFinder.java:222)
> ~[?:?]
> at
> org.apache.xbean.finder.BundleAssignableClassFinder.isClassAcceptable(BundleAssignableClassFinder.java:114)
> ~[?:?]
> at
> org.apache.xbean.finder.BundleAssignableClassFinder.isClassAcceptable(BundleAssignableClassFinder.java:125)
> ~[?:?]
> at
> org.apache.xbean.osgi.bundle.util.BundleClassFinder.scanDirectory(BundleClassFinder.java:257)
> ~[?:?] {code}
> Probably aries cdi should be updated from org.apache.xbean/xbean-asm8-shaded
> to xbean-asm9-shaded.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARIES-2073) Aries JPA 2.7 wrong behavior with SUPPORTS transaction methods
[ https://issues.apache.org/jira/browse/ARIES-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17524878#comment-17524878 ] ASF subversion and git services commented on ARIES-2073: Commit 9579cf3e4ee5bccf06191c750184f02785fd20a0 in aries's branch refs/heads/trunk from Grzegorz Grzybek [ https://gitbox.apache.org/repos/asf?p=aries.git;h=9579cf3e4 ] Merge pull request #151 from grgrzybek/ARIES-2073 [ARIES-2073] SUPPORTS TX attribute should not create additional coord… > Aries JPA 2.7 wrong behavior with SUPPORTS transaction methods > --- > > Key: ARIES-2073 > URL: https://issues.apache.org/jira/browse/ARIES-2073 > Project: Aries > Issue Type: Bug > Components: JPA >Affects Versions: jpa-2.7.3 >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > > When calling two methods, one with REQUIRES and one with SUPPORTS behaviour, > JPA access in the 2nd method should look up the existing EM associated with > previous coordination. No new coordination should be created. > SUPPORTS case is one (of six) missing behavior after some work was done in > ARIES-2050. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ARIES-2073) Aries JPA 2.7 wrong behavior with SUPPORTS transaction methods
[ https://issues.apache.org/jira/browse/ARIES-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17524876#comment-17524876 ] ASF subversion and git services commented on ARIES-2073: Commit f5d057e558ea9121ed44c0c15f6d26274a460e69 in aries's branch refs/heads/trunk from Grzegorz Grzybek [ https://gitbox.apache.org/repos/asf?p=aries.git;h=f5d057e55 ] [ARIES-2073] SUPPORTS TX attribute should not create additional coordination if one is present > Aries JPA 2.7 wrong behavior with SUPPORTS transaction methods > --- > > Key: ARIES-2073 > URL: https://issues.apache.org/jira/browse/ARIES-2073 > Project: Aries > Issue Type: Bug > Components: JPA >Affects Versions: jpa-2.7.3 >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > > When calling two methods, one with REQUIRES and one with SUPPORTS behaviour, > JPA access in the 2nd method should look up the existing EM associated with > previous coordination. No new coordination should be created. > SUPPORTS case is one (of six) missing behavior after some work was done in > ARIES-2050. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ARIES-2075) transaction-blueprint Coordinations should check existing TX
[
https://issues.apache.org/jira/browse/ARIES-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17524877#comment-17524877
]
ASF subversion and git services commented on ARIES-2075:
Commit b9a69d798d5c21636c8392b9c97fa481b3a46e5c in aries's branch
refs/heads/trunk from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=b9a69d798 ]
[ARIES-2075] Create a coordination for existing transaction when needed
> transaction-blueprint Coordinations should check existing TX
>
>
> Key: ARIES-2075
> URL: https://issues.apache.org/jira/browse/ARIES-2075
> Project: Aries
> Issue Type: Bug
>Affects Versions: transaction-blueprint-2.3.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have this unannotated method:
> {code:java}
> transactionManager.begin();
> try {
> nestedTestService.testExternalTransaction();
> } finally {
> transactionManager.rollback();
> }
> {code}
> And this annotated {{nestedTestService.testExternalTransaction()}}:
> {code:java}
> @Transactional(TxType.REQUIRED)
> public void testExternalTransaction() {
> TestEntity testEntity = testDao.createNew();
> ...
> {code}
> While the dao uses this EntityManager with the support from {{ />}}:
> {code:java}
> @PersistenceContext(unitName = "unit.1")
> private EntityManager entityManager;
> {code}
> The problem is that after ARIES-2050 fixes,
> {{org.apache.aries.transaction.TxInterceptorImpl#preCall()}} is not blindly
> creating new coordination if there's existing transaction.
> ARIES-2050 fix was not complete (see also ARIES-2073) but also I've
> mishandled the scenario where transaction is created not by another
> {{TxInterceptorImpl.preCall()}}, but by manual
> {{javax.transaction.TransactionManager#begin()}} invocation.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARIES-2067) Avoid NPE during startup
[
https://issues.apache.org/jira/browse/ARIES-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485006#comment-17485006
]
ASF subversion and git services commented on ARIES-2067:
Commit 55446d6d899c34ebf82afce24e012495a532956e in aries-cdi's branch
refs/heads/master from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=55446d6 ]
ARIES-2067 Avoid NPE during startup
Signed-off-by: Raymond Augé
> Avoid NPE during startup
>
>
> Key: ARIES-2067
> URL: https://issues.apache.org/jira/browse/ARIES-2067
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
> Fix For: cdi-1.1.5
>
>
> When starting a minimal use case there may be NPE during init.
> {code}
> java.lang.NullPointerException: A prototype scope
> org.apache.aries.cdi.spi.CDIContainerInitializer service must be available.
> at java.util.Objects.requireNonNull(Objects.java:228)
> at
> org.apache.aries.cdi.container.internal.container.ContainerBootstrap.(ContainerBootstrap.java:78)
> at
> org.apache.aries.cdi.container.internal.Activator.doCreateExtension(Activator.java:212)
> at
> org.apache.felix.utils.extender.AbstractExtender.createExtension(AbstractExtender.java:242)
> at
> org.apache.felix.utils.extender.AbstractExtender.modifiedBundle(AbstractExtender.java:227)
> at
> org.apache.felix.utils.extender.AbstractExtender.addingBundle(AbstractExtender.java:187)
> at
> org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:475)
> at
> org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:1)
> at
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at
> org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)
> at org.osgi.util.tracker.BundleTracker.open(BundleTracker.java:159)
> at
> org.apache.felix.utils.extender.AbstractExtender.startTracking(AbstractExtender.java:150)
> at
> org.apache.felix.utils.extender.AbstractExtender.doStart(AbstractExtender.java:142)
> at
> org.apache.felix.utils.extender.AbstractExtender.start(AbstractExtender.java:114)
> at
> org.apache.aries.cdi.container.internal.Activator.start(Activator.java:140)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl$2.run(BundleContextImpl.java:814)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl$2.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:806)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:763)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1028)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:371)
> at org.eclipse.osgi.container.Module.doStart(Module.java:605)
> at org.eclipse.osgi.container.Module.start(Module.java:468)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445)
> at aQute.launcher.Launcher.start(Launcher.java:686)
> at aQute.launcher.Launcher.startBundles(Launcher.java:666)
> at aQute.launcher.Launcher.activate(Launcher.java:572)
> at aQute.launcher.Launcher.launch(Launcher.java:402)
> at aQute.launcher.Launcher.run(Launcher.java:184)
> at aQute.launcher.Launcher.main(Launcher.java:160)
> at
> aQute.launcher.pre.EmbeddedLauncher.executeWithRunPath(EmbeddedLauncher.java:170)
> at
> aQute.launcher.pre.EmbeddedLauncher.findAndExecute(EmbeddedLauncher.java:135)
> at aQute.launcher.pre.EmbeddedLauncher.main(EmbeddedLauncher.java:52)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARIES-2068) Don't log an error just if the config admin isn't available yet
[ https://issues.apache.org/jira/browse/ARIES-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485007#comment-17485007 ] ASF subversion and git services commented on ARIES-2068: Commit 372d23d75d81540db2a295bfbc1c7a2579d7c4d8 in aries-cdi's branch refs/heads/master from Raymond Augé [ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=372d23d ] ARIES-2068 Don't log an error just if the config admin isn't available yet Signed-off-by: Raymond Augé > Don't log an error just if the config admin isn't available yet > --- > > Key: ARIES-2068 > URL: https://issues.apache.org/jira/browse/ARIES-2068 > Project: Aries > Issue Type: Improvement > Components: CDI >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > Fix For: cdi-1.1.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARIES-2068) Don't log an error just if the config admin isn't available yet
[ https://issues.apache.org/jira/browse/ARIES-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485008#comment-17485008 ] ASF subversion and git services commented on ARIES-2068: Commit cbe42d747917bca6a8e56db2e1da3f5b03d2bf76 in aries-cdi's branch refs/heads/master from Raymond Augé [ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=cbe42d7 ] ARIES-2068 Don't log an error just if the config admin isn't available yet Signed-off-by: Raymond Augé > Don't log an error just if the config admin isn't available yet > --- > > Key: ARIES-2068 > URL: https://issues.apache.org/jira/browse/ARIES-2068 > Project: Aries > Issue Type: Improvement > Components: CDI >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > Fix For: cdi-1.1.5 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARIES-2065) ConcurrentModificationException at java.util.HashMap.computeIfAbsent
[
https://issues.apache.org/jira/browse/ARIES-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478922#comment-17478922
]
ASF subversion and git services commented on ARIES-2065:
Commit 6e95dc4435c746d8b7d8977227a705e3d045eb1f in aries-component-dsl's branch
refs/heads/dependabot/maven/org.eclipse.platform-org.eclipse.osgi-3.17.100 from
Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;h=6e95dc4 ]
ARIES-2065 ConcurrentModificationException at java.util.HashMap.computeIfAbsent
Signed-off-by: Raymond Augé
> ConcurrentModificationException at java.util.HashMap.computeIfAbsent
>
>
> Key: ARIES-2065
> URL: https://issues.apache.org/jira/browse/ARIES-2065
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Reporter: Arthur Naseef
>Assignee: Raymond Augé
>Priority: Major
>
> Using aries-jax-rs-whiteboard with resources from 2 different bundles, I hit
> the following.
> {code:java}
> java.util.ConcurrentModificationException
> at java.base/java.util.HashMap.computeIfAbsent(Unknown Source)
> at org.apache.aries.component.dsl.OSGi.lambda$null$79(OSGi.java:734)
> at
> org.apache.aries.component.dsl.internal.JustOSGiImpl.lambda$new$2(JustOSGiImpl.java:47)
> at
> org.apache.aries.component.dsl.internal.OSGiImpl.run(OSGiImpl.java:50){code}
> Debugging, this was tracked back to {{OSGi.splitBy()}} and it's use of
> {color:#172b4d}HashMap{color}.
> When this happens, the services fail to start up. Since this is a race
> condition, it does not happen every time.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARIES-2065) ConcurrentModificationException at java.util.HashMap.computeIfAbsent
[
https://issues.apache.org/jira/browse/ARIES-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478921#comment-17478921
]
ASF subversion and git services commented on ARIES-2065:
Commit 6e95dc4435c746d8b7d8977227a705e3d045eb1f in aries-component-dsl's branch
refs/heads/dependabot/maven/org.apache-apache-24 from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;h=6e95dc4 ]
ARIES-2065 ConcurrentModificationException at java.util.HashMap.computeIfAbsent
Signed-off-by: Raymond Augé
> ConcurrentModificationException at java.util.HashMap.computeIfAbsent
>
>
> Key: ARIES-2065
> URL: https://issues.apache.org/jira/browse/ARIES-2065
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Reporter: Arthur Naseef
>Assignee: Raymond Augé
>Priority: Major
>
> Using aries-jax-rs-whiteboard with resources from 2 different bundles, I hit
> the following.
> {code:java}
> java.util.ConcurrentModificationException
> at java.base/java.util.HashMap.computeIfAbsent(Unknown Source)
> at org.apache.aries.component.dsl.OSGi.lambda$null$79(OSGi.java:734)
> at
> org.apache.aries.component.dsl.internal.JustOSGiImpl.lambda$new$2(JustOSGiImpl.java:47)
> at
> org.apache.aries.component.dsl.internal.OSGiImpl.run(OSGiImpl.java:50){code}
> Debugging, this was tracked back to {{OSGi.splitBy()}} and it's use of
> {color:#172b4d}HashMap{color}.
> When this happens, the services fail to start up. Since this is a race
> condition, it does not happen every time.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARIES-2065) ConcurrentModificationException at java.util.HashMap.computeIfAbsent
[
https://issues.apache.org/jira/browse/ARIES-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478886#comment-17478886
]
ASF subversion and git services commented on ARIES-2065:
Commit 6e95dc4435c746d8b7d8977227a705e3d045eb1f in aries-component-dsl's branch
refs/heads/master from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;h=6e95dc4 ]
ARIES-2065 ConcurrentModificationException at java.util.HashMap.computeIfAbsent
Signed-off-by: Raymond Augé
> ConcurrentModificationException at java.util.HashMap.computeIfAbsent
>
>
> Key: ARIES-2065
> URL: https://issues.apache.org/jira/browse/ARIES-2065
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Reporter: Arthur Naseef
>Priority: Major
>
> Using aries-jax-rs-whiteboard with resources from 2 different bundles, I hit
> the following.
> {code:java}
> java.util.ConcurrentModificationException
> at java.base/java.util.HashMap.computeIfAbsent(Unknown Source)
> at org.apache.aries.component.dsl.OSGi.lambda$null$79(OSGi.java:734)
> at
> org.apache.aries.component.dsl.internal.JustOSGiImpl.lambda$new$2(JustOSGiImpl.java:47)
> at
> org.apache.aries.component.dsl.internal.OSGiImpl.run(OSGiImpl.java:50){code}
> Debugging, this was tracked back to {{OSGi.splitBy()}} and it's use of
> {color:#172b4d}HashMap{color}.
> When this happens, the services fail to start up. Since this is a race
> condition, it does not happen every time.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARIES-2062) aries.proxy:ensure to support JDK18
[ https://issues.apache.org/jira/browse/ARIES-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467553#comment-17467553 ] ASF subversion and git services commented on ARIES-2062: Commit f8493eb436c47089f438c5ed1ffca5c3d1bbcbee in aries's branch refs/heads/trunk from Freeman Fang [ https://gitbox.apache.org/repos/asf?p=aries.git;h=f8493eb ] [ARIES-2062]aries.proxy:ensure to support JDK18 > aries.proxy:ensure to support JDK18 > --- > > Key: ARIES-2062 > URL: https://issues.apache.org/jira/browse/ARIES-2062 > Project: Aries > Issue Type: Task > Components: Proxy >Reporter: Freeman Yue Fang >Assignee: Jean-Baptiste Onofré >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARIES-2062) aries.proxy:ensure to support JDK18
[ https://issues.apache.org/jira/browse/ARIES-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467554#comment-17467554 ] ASF subversion and git services commented on ARIES-2062: Commit 6dc0e2c783f1642d18d1d637d222af68249afa12 in aries's branch refs/heads/trunk from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=6dc0e2c ] Merge pull request #137 from ffang/ARIES-2062 [ARIES-2062]aries.proxy:ensure to support JDK18 > aries.proxy:ensure to support JDK18 > --- > > Key: ARIES-2062 > URL: https://issues.apache.org/jira/browse/ARIES-2062 > Project: Aries > Issue Type: Task > Components: Proxy >Reporter: Freeman Yue Fang >Assignee: Jean-Baptiste Onofré >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARIES-2059) Component properties are sometimes merged in the incorrect order
[
https://issues.apache.org/jira/browse/ARIES-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416202#comment-17416202
]
ASF subversion and git services commented on ARIES-2059:
Commit 31b7e3e2a82785c491c7559ee1aeec9c48a17f6e in aries-cdi's branch
refs/heads/dependabot/maven/org.apache.felix-org.apache.felix.converter-1.0.18
from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=31b7e3e ]
ARIES-2059 Component properties are sometimes merged in the incorrect order
Signed-off-by: Raymond Augé
> Component properties are sometimes merged in the incorrect order
>
>
> Key: ARIES-2059
> URL: https://issues.apache.org/jira/browse/ARIES-2059
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
> Fix For: cdi-1.1.4
>
>
> Component properties are sometimes merged in the incorrect order.
> This was caused by the following misuse of the CDI annotated APIs as follows:
> When a repeatable annotation is defined on a class, the API
> {{javax.enterprise.inject.spi.Annotated}} can be misleading because {{ extends Annotation> Set getAnnotations(Class annotationType);}} returns
> a Set.
> This means that implementations are free to return annotations not in
> definition order.
> Aries CDI mistakenly used this API to retrieve {{@PID}} annotations (which
> are repeatable.)
> The work around is pretty simple, when needing to retrieve repeatable
> annotations in definition order pass the container annotationType (all
> repeatable annotations have a container annotation type) to the method
> instead, in this case {{getAnnotations(PIDs.class)}} and then get the
> {{@PIDs.value()}} array which contains the {{@PID}} annotations in definition
> order.
> Note that when there is only a single instance of a repeatable annotation,
> only an instance of the repeatable annotation is used in the class and NOT an
> instance of the container with an array of length 1. This means that you need
> to check first for the container, and then for single instances in order to
> catch all usage scenarios.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2059) Component properties are sometimes merged in the incorrect order
[
https://issues.apache.org/jira/browse/ARIES-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17415743#comment-17415743
]
ASF subversion and git services commented on ARIES-2059:
Commit 31b7e3e2a82785c491c7559ee1aeec9c48a17f6e in aries-cdi's branch
refs/heads/master from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=31b7e3e ]
ARIES-2059 Component properties are sometimes merged in the incorrect order
Signed-off-by: Raymond Augé
> Component properties are sometimes merged in the incorrect order
>
>
> Key: ARIES-2059
> URL: https://issues.apache.org/jira/browse/ARIES-2059
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Raymond Augé
>Assignee: Raymond Augé
>Priority: Major
> Fix For: cdi-1.1.4
>
>
> Component properties are sometimes merged in the incorrect order.
> This was caused by the following misuse of the CDI annotated APIs as follows:
> When a repeatable annotation is defined on a class, the API
> {{javax.enterprise.inject.spi.Annotated}} can be misleading because {{ extends Annotation> Set getAnnotations(Class annotationType);}} returns
> a Set.
> This means that implementations are free to return annotations not in
> definition order.
> Aries CDI mistakenly used this API to retrieve {{@PID}} annotations (which
> are repeatable.)
> The work around is pretty simple, when needing to retrieve repeatable
> annotations in definition order pass the container annotationType (all
> repeatable annotations have a container annotation type) to the method
> instead, in this case {{getAnnotations(PIDs.class)}} and then get the
> {{@PIDs.value()}} array which contains the {{@PID}} annotations in definition
> order.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2047) Remove Karaf standard repository from feature.xml
[ https://issues.apache.org/jira/browse/ARIES-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395878#comment-17395878 ] ASF subversion and git services commented on ARIES-2047: Commit 2c28b15f6db83c2a63ae8c633ab85ef9263bba85 in aries-jax-rs-whiteboard's branch refs/heads/maint-1.x from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=2c28b15 ] [ARIES-2047] Remove Karaf standard repository from feature.xml > Remove Karaf standard repository from feature.xml > - > > Key: ARIES-2047 > URL: https://issues.apache.org/jira/browse/ARIES-2047 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: jax-rs-whiteboard-2.0.1 > > > The Karaf standard repository should not be use in the feature.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395786#comment-17395786
]
ASF subversion and git services commented on ARIES-2050:
Commit 125a4aef647d7356768854883f7b3d8e040ce2bb in aries-jpa's branch
refs/heads/master from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=125a4ae ]
[ARIES-2050] Use org.apache.aries.transaction.blueprint-2.3.0
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
> Components: JPA
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: jpa-2.7.3
>
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395785#comment-17395785
]
ASF subversion and git services commented on ARIES-2050:
Commit 6fdb8e7e28255b877b1062b391c98df43a8160c6 in aries-jpa's branch
refs/heads/master from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=6fdb8e7 ]
[ARIES-2050] EMSupplier selectes better TX-related coordination to store EM
instance
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
> Components: JPA
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: jpa-2.7.3
>
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395788#comment-17395788
]
ASF subversion and git services commented on ARIES-2050:
Commit d017bd7bb735626840a63d6b79db25e28ef82a46 in aries-jpa's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=d017bd7 ]
Merge pull request #10 from apache/ARIES-2050
[ARIES-2050] EMSupplier selectes better TX-related coordination to st…
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
> Components: JPA
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: jpa-2.7.3
>
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395789#comment-17395789
]
ASF subversion and git services commented on ARIES-2050:
Commit d017bd7bb735626840a63d6b79db25e28ef82a46 in aries-jpa's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=d017bd7 ]
Merge pull request #10 from apache/ARIES-2050
[ARIES-2050] EMSupplier selectes better TX-related coordination to st…
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
> Components: JPA
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: jpa-2.7.3
>
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389254#comment-17389254
]
ASF subversion and git services commented on ARIES-2050:
Commit 125a4aef647d7356768854883f7b3d8e040ce2bb in aries-jpa's branch
refs/heads/ARIES-2050 from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=125a4ae ]
[ARIES-2050] Use org.apache.aries.transaction.blueprint-2.3.0
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: jpa-2.7.3
>
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2056) AbstractWovenProxyAdapter still uses OpCodes.ASM5
[ https://issues.apache.org/jira/browse/ARIES-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387333#comment-17387333 ] ASF subversion and git services commented on ARIES-2056: Commit cc71c3a47d7bd03fe25aa3ef11f63225531caecb in aries's branch refs/heads/trunk from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=aries.git;h=cc71c3a ] [ARIES-2056] Use OpCodes.ASM9 in AbstractWovenProxyAdapter > AbstractWovenProxyAdapter still uses OpCodes.ASM5 > - > > Key: ARIES-2056 > URL: https://issues.apache.org/jira/browse/ARIES-2056 > Project: Aries > Issue Type: Bug > Components: Proxy >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.11 > > > AbstractWovenProxyAdapter should update OpCodes to at least ASM7 (and > probably ASM9). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374592#comment-17374592
]
ASF subversion and git services commented on ARIES-2050:
Commit acd1f169032337dcae8215063d08393ea2dabc24 in aries's branch
refs/heads/trunk from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=acd1f16 ]
Merge pull request #129 from apache/ARIES-2050
[ARIES-2050] Different coordination management across TX behavior bou…
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374591#comment-17374591
]
ASF subversion and git services commented on ARIES-2050:
Commit acd1f169032337dcae8215063d08393ea2dabc24 in aries's branch
refs/heads/trunk from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=acd1f16 ]
Merge pull request #129 from apache/ARIES-2050
[ARIES-2050] Different coordination management across TX behavior bou…
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374590#comment-17374590
]
ASF subversion and git services commented on ARIES-2050:
Commit 6a2cf9c155c3d7bb838a2517aa8687c89012a0bf in aries's branch
refs/heads/trunk from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=6a2cf9c ]
[ARIES-2050] Different coordination management across TX behavior boundaries
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2052) ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
[
https://issues.apache.org/jira/browse/ARIES-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370240#comment-17370240
]
ASF subversion and git services commented on ARIES-2052:
Commit 9a1f520ac218ed2a843270caa4c8974175d7c387 in aries-cdi's branch
refs/heads/dependabot/maven/org.jboss.weld-weld-osgi-bundle-4.0.1.Final from
Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=9a1f520 ]
ARIES-2052 ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
Signed-off-by: Raymond Augé
> ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
>
>
> Key: ARIES-2052
> URL: https://issues.apache.org/jira/browse/ARIES-2052
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Grzegorz Grzybek
>Priority: Major
>
> https://issues.redhat.com/browse/WELD-2581 (fixed in weld 3.1.7+) changed
> WeldStartup behavior from:
> {code:java}
> if (!registry.get(ProxyServices.class).supportsClassDefining()) {
> // we will need to invoke CL.defineClass() ourselves, crack open those
> methods eagerly
> ClassFileUtils.makeClassLoaderMethodsAccessible();
> }
> {code}
> to:
> {code:java}
> ProxyServices proxyServices = registry.get(ProxyServices.class);
> if (!proxyServices.supportsClassDefining()) {
> throw
> BootstrapLogger.LOG.proxyServicesWithoutClassDefining(proxyServices.getClass().getName());
> }
> {code}
> However {{org.apache.aries.cdi.weld.BundleResourcesLoader()}} doesn't
> override default method from the ProxyServices interface:
> {code:java}
> default boolean supportsClassDefining() {
> return false;
> }
> {code}
> And throws an exception at runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2052) ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
[
https://issues.apache.org/jira/browse/ARIES-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370242#comment-17370242
]
ASF subversion and git services commented on ARIES-2052:
Commit 9a1f520ac218ed2a843270caa4c8974175d7c387 in aries-cdi's branch
refs/heads/dependabot/maven/org.apache.aries.jax.rs-org.apache.aries.jax.rs.whiteboard-2.0.0
from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=9a1f520 ]
ARIES-2052 ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
Signed-off-by: Raymond Augé
> ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
>
>
> Key: ARIES-2052
> URL: https://issues.apache.org/jira/browse/ARIES-2052
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Grzegorz Grzybek
>Priority: Major
>
> https://issues.redhat.com/browse/WELD-2581 (fixed in weld 3.1.7+) changed
> WeldStartup behavior from:
> {code:java}
> if (!registry.get(ProxyServices.class).supportsClassDefining()) {
> // we will need to invoke CL.defineClass() ourselves, crack open those
> methods eagerly
> ClassFileUtils.makeClassLoaderMethodsAccessible();
> }
> {code}
> to:
> {code:java}
> ProxyServices proxyServices = registry.get(ProxyServices.class);
> if (!proxyServices.supportsClassDefining()) {
> throw
> BootstrapLogger.LOG.proxyServicesWithoutClassDefining(proxyServices.getClass().getName());
> }
> {code}
> However {{org.apache.aries.cdi.weld.BundleResourcesLoader()}} doesn't
> override default method from the ProxyServices interface:
> {code:java}
> default boolean supportsClassDefining() {
> return false;
> }
> {code}
> And throws an exception at runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2053) aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
[
https://issues.apache.org/jira/browse/ARIES-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370241#comment-17370241
]
ASF subversion and git services commented on ARIES-2053:
Commit fb09f3ff11f28a011d8cb610476a03d5fb2efdab in aries-cdi's branch
refs/heads/dependabot/maven/org.apache.aries.jax.rs-org.apache.aries.jax.rs.whiteboard-2.0.0
from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=fb09f3f ]
ARIES-2053 aries-cdi-extension-el-jsp has unresolved property in JavaJSP
contract
Signed-off-by: Raymond Augé
> aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
> --
>
> Key: ARIES-2053
> URL: https://issues.apache.org/jira/browse/ARIES-2053
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Affects Versions: cdi-1.1.3
>Reporter: Grzegorz Grzybek
>Assignee: Raymond Augé
>Priority: Major
>
> If you check
> https://github.com/apache/aries-cdi/blob/org.apache.aries.cdi-1.1.3/cdi-extension-el-jsp/src/main/java/org/apache/aries/cdi/extension/el/jsp/package-info.java#L40
> there's {{jsp.version}} property, but it's unresolved during build time and
> the resulting META-INF/MANIFEST.MF requirement is:
> {noformat}
> Require-Capability: osgi.contract;filter:="(&(osgi.contract=JavaJSP)(v
> ersion=${jsp.version}))";osgi.contract=JavaJSP,...
> {noformat}
> at runtime, I'm getting:
> {noformat}
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.aries.cdi.extension.el.jsp [61](R 61.0): \
> missing requirement [org.apache.aries.cdi.extension.el.jsp [61](R 61.0)] \
> osgi.contract; (&(osgi.contract=JavaJSP)(version=${jsp.version}))
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2053) aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
[
https://issues.apache.org/jira/browse/ARIES-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370239#comment-17370239
]
ASF subversion and git services commented on ARIES-2053:
Commit fb09f3ff11f28a011d8cb610476a03d5fb2efdab in aries-cdi's branch
refs/heads/dependabot/maven/org.jboss.weld-weld-osgi-bundle-4.0.1.Final from
Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=fb09f3f ]
ARIES-2053 aries-cdi-extension-el-jsp has unresolved property in JavaJSP
contract
Signed-off-by: Raymond Augé
> aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
> --
>
> Key: ARIES-2053
> URL: https://issues.apache.org/jira/browse/ARIES-2053
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Affects Versions: cdi-1.1.3
>Reporter: Grzegorz Grzybek
>Assignee: Raymond Augé
>Priority: Major
>
> If you check
> https://github.com/apache/aries-cdi/blob/org.apache.aries.cdi-1.1.3/cdi-extension-el-jsp/src/main/java/org/apache/aries/cdi/extension/el/jsp/package-info.java#L40
> there's {{jsp.version}} property, but it's unresolved during build time and
> the resulting META-INF/MANIFEST.MF requirement is:
> {noformat}
> Require-Capability: osgi.contract;filter:="(&(osgi.contract=JavaJSP)(v
> ersion=${jsp.version}))";osgi.contract=JavaJSP,...
> {noformat}
> at runtime, I'm getting:
> {noformat}
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.aries.cdi.extension.el.jsp [61](R 61.0): \
> missing requirement [org.apache.aries.cdi.extension.el.jsp [61](R 61.0)] \
> osgi.contract; (&(osgi.contract=JavaJSP)(version=${jsp.version}))
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2052) ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
[
https://issues.apache.org/jira/browse/ARIES-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370238#comment-17370238
]
ASF subversion and git services commented on ARIES-2052:
Commit 9a1f520ac218ed2a843270caa4c8974175d7c387 in aries-cdi's branch
refs/heads/master from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=9a1f520 ]
ARIES-2052 ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
Signed-off-by: Raymond Augé
> ProxyServices#supportsClassDefining() in weld 3.1.7 breaks aries-cdi
>
>
> Key: ARIES-2052
> URL: https://issues.apache.org/jira/browse/ARIES-2052
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Reporter: Grzegorz Grzybek
>Priority: Major
>
> https://issues.redhat.com/browse/WELD-2581 (fixed in weld 3.1.7+) changed
> WeldStartup behavior from:
> {code:java}
> if (!registry.get(ProxyServices.class).supportsClassDefining()) {
> // we will need to invoke CL.defineClass() ourselves, crack open those
> methods eagerly
> ClassFileUtils.makeClassLoaderMethodsAccessible();
> }
> {code}
> to:
> {code:java}
> ProxyServices proxyServices = registry.get(ProxyServices.class);
> if (!proxyServices.supportsClassDefining()) {
> throw
> BootstrapLogger.LOG.proxyServicesWithoutClassDefining(proxyServices.getClass().getName());
> }
> {code}
> However {{org.apache.aries.cdi.weld.BundleResourcesLoader()}} doesn't
> override default method from the ProxyServices interface:
> {code:java}
> default boolean supportsClassDefining() {
> return false;
> }
> {code}
> And throws an exception at runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2053) aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
[
https://issues.apache.org/jira/browse/ARIES-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370237#comment-17370237
]
ASF subversion and git services commented on ARIES-2053:
Commit fb09f3ff11f28a011d8cb610476a03d5fb2efdab in aries-cdi's branch
refs/heads/master from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries-cdi.git;h=fb09f3f ]
ARIES-2053 aries-cdi-extension-el-jsp has unresolved property in JavaJSP
contract
Signed-off-by: Raymond Augé
> aries-cdi-extension-el-jsp has unresolved property in JavaJSP contract
> --
>
> Key: ARIES-2053
> URL: https://issues.apache.org/jira/browse/ARIES-2053
> Project: Aries
> Issue Type: Bug
> Components: CDI
>Affects Versions: cdi-1.1.3
>Reporter: Grzegorz Grzybek
>Assignee: Raymond Augé
>Priority: Major
>
> If you check
> https://github.com/apache/aries-cdi/blob/org.apache.aries.cdi-1.1.3/cdi-extension-el-jsp/src/main/java/org/apache/aries/cdi/extension/el/jsp/package-info.java#L40
> there's {{jsp.version}} property, but it's unresolved during build time and
> the resulting META-INF/MANIFEST.MF requirement is:
> {noformat}
> Require-Capability: osgi.contract;filter:="(&(osgi.contract=JavaJSP)(v
> ersion=${jsp.version}))";osgi.contract=JavaJSP,...
> {noformat}
> at runtime, I'm getting:
> {noformat}
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.aries.cdi.extension.el.jsp [61](R 61.0): \
> missing requirement [org.apache.aries.cdi.extension.el.jsp [61](R 61.0)] \
> osgi.contract; (&(osgi.contract=JavaJSP)(version=${jsp.version}))
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2055) Support Swagger annotations on JAX-RS applications
[
https://issues.apache.org/jira/browse/ARIES-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366206#comment-17366206
]
ASF subversion and git services commented on ARIES-2055:
Commit 3851504540db372ef4bdc3fd6884397c887a5b82 in aries-jax-rs-whiteboard's
branch refs/heads/master from Jozsef Borcsok
[ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=3851504 ]
ARIES-2055: support Swagger annotations on JAX-RS application
> Support Swagger annotations on JAX-RS applications
> --
>
> Key: ARIES-2055
> URL: https://issues.apache.org/jira/browse/ARIES-2055
> Project: Aries
> Issue Type: Improvement
> Components: jax-rs-whiteboard
>Affects Versions: jax-rs-whiteboard-1.1.0, jax-rs-whiteboard-2.0.0
>Reporter: Börcsök József
>Priority: Major
>
> JAX-RS annotations (i.e. OpenAPIDefinition) on JAX-RS application should be
> supported (similar to JaxrsApplicationAndResourcePackagesAnnotationScanner in
> swagger-core integration).
> Sample:
> {code:java}
> @OpenAPIDefinition(
> info = @Info(
> title = "My Service",
> description = "Service REST API",
> contact = @Contact(
> email = "oschweit...@me.com"
> )
> )
> )
> public class TestApplicationWithClasses extends Application {
> // ...
> }{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362772#comment-17362772
]
ASF subversion and git services commented on ARIES-2050:
Commit 6fdb8e7e28255b877b1062b391c98df43a8160c6 in aries-jpa's branch
refs/heads/ARIES-2050 from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=6fdb8e7 ]
[ARIES-2050] EMSupplier selectes better TX-related coordination to store EM
instance
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362769#comment-17362769
]
ASF subversion and git services commented on ARIES-2050:
Commit cc6409ffefa8e7e0f270c483a4cc1b4d5a518f03 in aries-jpa's branch
refs/heads/ARIES-2050 from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries-jpa.git;h=cc6409f ]
[ARIES-2050] EMSupplier selectes better TX-related coordination to store EM
instance
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2050) Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
[
https://issues.apache.org/jira/browse/ARIES-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362764#comment-17362764
]
ASF subversion and git services commented on ARIES-2050:
Commit 6a2cf9c155c3d7bb838a2517aa8687c89012a0bf in aries's branch
refs/heads/ARIES-2050 from Grzegorz Grzybek
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=6a2cf9c ]
[ARIES-2050] Different coordination management across TX behavior boundaries
> Aries JPA 2.7 shouldn't always reuse EM instance from previous coordinations
>
>
> Key: ARIES-2050
> URL: https://issues.apache.org/jira/browse/ARIES-2050
> Project: Aries
> Issue Type: Bug
>Affects Versions: jpa-2.7.2
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a scenario consisting of the following call graph:
> {noformat}
> testService.performTest() [ @Transactional(TxType.REQUIRED) ]
> +-- List cars = carDao.getAllCars()
> | +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> | (em is injected using @PersistenceContext(unitName = "xa-test-unit"))
> |
> +-- carDao.createNew(car);
> | +-- em.persist(car);
> |
> +-- newTxTestService.testNewTransaction(transactionManager.getTransaction())
> [ @Transactional(TxType.REQUIRES_NEW) ]
> +-- List cars = carDao.getAllCars();
> +-- return em.createQuery("select c from Car c",
> Car.class).getResultList()
> {noformat}
> The problem is that inside the method marked with
> {{@Transactional(TxType.REQUIRES_NEW)}} the {{em}} proxy uses the same
> underlying {{em}} instance because of:
> {code:java}
> Coordination getTopCoordination() {
> Coordination coordination = coordinator.peek();
> while (coordination != null && coordination.getEnclosingCoordination() !=
> null) {
> coordination = coordination.getEnclosingCoordination();
> }
> return coordination;
> }
> {code}
> And even if the suspended transaction is not yet committed, the em returns
> the persisted (but not yet committed) cars.
> The coordination stack consists of (names of coordination objects):
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.TestServiceImpl.performTest
> *
> txInterceptor.org.apache.aries.jpa.container.itest.bundle.blueprint.impl.NewTxTestServiceImpl.testNewTransaction
> * jpa
> the top coordination contains {{em}} variable associated with suspended
> transaction.
> I'm working on a solution that properly assigns _current_ em respecting
> tx-demarcated coordinations.
> [~cschneider], [~gnodet], [~jbonofre] if you have an idea about the best
> solution, please share.
> For now I think both aries-jpa and aries-blueprint-transaction have to be
> fixed (the latter one should put some magical variable to the coordination
> objects pushed inside {{org.apache.aries.transaction.TxInterceptorImpl}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2047) Remove Karaf standard repository from feature.xml
[ https://issues.apache.org/jira/browse/ARIES-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17348801#comment-17348801 ] ASF subversion and git services commented on ARIES-2047: Commit 6a1b4fb835082ac26ddf3c39717016ad8d68d067 in aries-jax-rs-whiteboard's branch refs/heads/dependabot/maven/junit.jupiter.version-5.7.2 from francois papon [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=6a1b4fb ] [ARIES-2047] Remove Karaf standard repository from feature.xml > Remove Karaf standard repository from feature.xml > - > > Key: ARIES-2047 > URL: https://issues.apache.org/jira/browse/ARIES-2047 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Reporter: Francois Papon >Priority: Major > Fix For: jax-rs-whiteboard-2.0.1 > > > The Karaf standard repository should not be use in the feature.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2047) Remove Karaf standard repository from feature.xml
[ https://issues.apache.org/jira/browse/ARIES-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17348794#comment-17348794 ] ASF subversion and git services commented on ARIES-2047: Commit 6a1b4fb835082ac26ddf3c39717016ad8d68d067 in aries-jax-rs-whiteboard's branch refs/heads/master from francois papon [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=6a1b4fb ] [ARIES-2047] Remove Karaf standard repository from feature.xml > Remove Karaf standard repository from feature.xml > - > > Key: ARIES-2047 > URL: https://issues.apache.org/jira/browse/ARIES-2047 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Reporter: Francois Papon >Priority: Major > Fix For: jax-rs-whiteboard-2.0.1 > > > The Karaf standard repository should not be use in the feature.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2044) aries-proxy does not work with JDK16
[
https://issues.apache.org/jira/browse/ARIES-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314408#comment-17314408
]
ASF subversion and git services commented on ARIES-2044:
Commit 186c327ab73b2eb17f0d791e61c3f0f91add6195 in aries's branch
refs/heads/trunk from Robert Varga
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=186c327 ]
[ARIES-2044] Add support for JRE16/17
> aries-proxy does not work with JDK16
>
>
> Key: ARIES-2044
> URL: https://issues.apache.org/jira/browse/ARIES-2044
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.9
>Reporter: Robert Varga
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> Attempting to run Karaf-4.3.1 with JDK16 results in:
> {noformat}
> 2021-04-03T21:20:24,053 | INFO | features-2-thread-1 | ServiceRecipe
> | 28 - org.apache.aries.blueprint.core - 1.10.3 | Unable to create
> a proxy object for the service .component-1 defined in bundle
> org.apache.aries.blueprint.core/1.10.3 with id. Returning the original object
> instead.
> java.lang.IllegalArgumentException: Invalid Java version 60
> at
> org.apache.aries.proxy.impl.ProxyUtils.getWeavingJavaVersion(ProxyUtils.java:88)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceCombiningClassAdapter.(InterfaceCombiningClassAdapter.java:79)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.createProxyClass(ProxyClassLoader.java:155)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator.getProxyInstance(InterfaceProxyGenerator.java:97)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AsmProxyManager.createNewProxy(AsmProxyManager.java:80)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:77)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createInterceptingProxy(AbstractProxyManager.java:55)
> ~[?:?]
> at
> org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:568)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:216)
> ~[?:?]
> at
> java.security.AccessController.doPrivileged(AccessController.java:312) ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:213)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:114)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:547)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:533)
> ~[?:?]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:656)
> ~[?:?]
> at
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:115)
> ~[?:?]
> [...]
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2044) aries-proxy does not work with JDK16
[
https://issues.apache.org/jira/browse/ARIES-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314409#comment-17314409
]
ASF subversion and git services commented on ARIES-2044:
Commit a2be80e7b344647a5f0ace5bc741e015a383f13f in aries's branch
refs/heads/trunk from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=a2be80e ]
Merge pull request #115 from rovarga/aries2044
[ARIES-2044] Add support for JRE16/17
> aries-proxy does not work with JDK16
>
>
> Key: ARIES-2044
> URL: https://issues.apache.org/jira/browse/ARIES-2044
> Project: Aries
> Issue Type: Bug
> Components: Proxy
>Affects Versions: proxy-impl-1.1.9
>Reporter: Robert Varga
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> Attempting to run Karaf-4.3.1 with JDK16 results in:
> {noformat}
> 2021-04-03T21:20:24,053 | INFO | features-2-thread-1 | ServiceRecipe
> | 28 - org.apache.aries.blueprint.core - 1.10.3 | Unable to create
> a proxy object for the service .component-1 defined in bundle
> org.apache.aries.blueprint.core/1.10.3 with id. Returning the original object
> instead.
> java.lang.IllegalArgumentException: Invalid Java version 60
> at
> org.apache.aries.proxy.impl.ProxyUtils.getWeavingJavaVersion(ProxyUtils.java:88)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceCombiningClassAdapter.(InterfaceCombiningClassAdapter.java:79)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.createProxyClass(ProxyClassLoader.java:155)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator.getProxyInstance(InterfaceProxyGenerator.java:97)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AsmProxyManager.createNewProxy(AsmProxyManager.java:80)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createDelegatingInterceptingProxy(AbstractProxyManager.java:77)
> ~[?:?]
> at
> org.apache.aries.proxy.impl.AbstractProxyManager.createInterceptingProxy(AbstractProxyManager.java:55)
> ~[?:?]
> at
> org.apache.aries.blueprint.container.ServiceRecipe$TriggerServiceFactory.getService(ServiceRecipe.java:568)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:216)
> ~[?:?]
> at
> java.security.AccessController.doPrivileged(AccessController.java:312) ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:213)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:114)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:547)
> ~[?:?]
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:533)
> ~[?:?]
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:656)
> ~[?:?]
> at
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:115)
> ~[?:?]
> [...]
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARIES-2043) LocalDiscovery not updated when listener scope changes
[ https://issues.apache.org/jira/browse/ARIES-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298728#comment-17298728 ] ASF subversion and git services commented on ARIES-2043: Commit f2d25032e8c6039dbbc51131904c78d1e6933024 in aries-rsa's branch refs/heads/master from Amichai Rothman [ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=f2d2503 ] ARIES-2043 - Fix LocalDiscovery not updated when listener scope changes > LocalDiscovery not updated when listener scope changes > -- > > Key: ARIES-2043 > URL: https://issues.apache.org/jira/browse/ARIES-2043 > Project: Aries > Issue Type: Bug > Components: Remote Service Admin >Affects Versions: rsa-1.16.0 >Reporter: Amichai Rothman >Assignee: Amichai Rothman >Priority: Major > > EnpointListenerManager updates the scope via the service properties when > there is a new interest in a service, but LocalDelivery does not get updated > accordingly, so it does not match any service listeners added after a bundle > is initially started. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2042) Local discovery missing from repository
[ https://issues.apache.org/jira/browse/ARIES-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298727#comment-17298727 ] ASF subversion and git services commented on ARIES-2042: Commit 9ea56cbf008b5d6f9dc0f8a37782abdd2421d9a5 in aries-rsa's branch refs/heads/master from Amichai Rothman [ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=9ea56cb ] ARIES-2042 - Add missing local discovery dependency to repository > Local discovery missing from repository > --- > > Key: ARIES-2042 > URL: https://issues.apache.org/jira/browse/ARIES-2042 > Project: Aries > Issue Type: Bug > Components: Remote Service Admin >Affects Versions: rsa-1.16.0 >Reporter: Amichai Rothman >Assignee: Amichai Rothman >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2030) Create an integration that implements OSGi Rest Management Specification
[ https://issues.apache.org/jira/browse/ARIES-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292286#comment-17292286 ] ASF subversion and git services commented on ARIES-2030: Commit a250d573ba8f0ffb407dca80401208e952257159 in aries-jax-rs-whiteboard's branch refs/heads/master from Raymond Auge [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=a250d57 ] ARIES-2030 implement extensions Signed-off-by: Raymond Auge > Create an integration that implements OSGi Rest Management Specification > > > Key: ARIES-2030 > URL: https://issues.apache.org/jira/browse/ARIES-2030 > Project: Aries > Issue Type: New Feature > Components: jax-rs-whiteboard >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > Fix For: jax-rs-whiteboard-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2030) Create an integration that implements OSGi Rest Management Specification
[ https://issues.apache.org/jira/browse/ARIES-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288861#comment-17288861 ] ASF subversion and git services commented on ARIES-2030: Commit b0943eba7942e4505ef41c9be99230499cf71696 in aries-jax-rs-whiteboard's branch refs/heads/master from Raymond Auge [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=b0943eb ] ARIES-2030 major improvements and refactoring Signed-off-by: Raymond Auge > Create an integration that implements OSGi Rest Management Specification > > > Key: ARIES-2030 > URL: https://issues.apache.org/jira/browse/ARIES-2030 > Project: Aries > Issue Type: New Feature > Components: jax-rs-whiteboard >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2030) Create an integration that implements OSGi Rest Management Specification
[ https://issues.apache.org/jira/browse/ARIES-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288860#comment-17288860 ] ASF subversion and git services commented on ARIES-2030: Commit c3fdcccd6a96a5dce9e76ad832ada6ed8f1a3764 in aries-jax-rs-whiteboard's branch refs/heads/master from Raymond Auge [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=c3fdccc ] ARIES-2030 wip Signed-off-by: Raymond Auge > Create an integration that implements OSGi Rest Management Specification > > > Key: ARIES-2030 > URL: https://issues.apache.org/jira/browse/ARIES-2030 > Project: Aries > Issue Type: New Feature > Components: jax-rs-whiteboard >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2030) Create an integration that implements OSGi Rest Management Specification
[ https://issues.apache.org/jira/browse/ARIES-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17288848#comment-17288848 ] ASF subversion and git services commented on ARIES-2030: Commit 546bbdf4c12fcc2c8bb0e2dbe274b8a8f936b626 in aries-jax-rs-whiteboard's branch refs/heads/ARIES-2030 from Raymond Auge [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=546bbdf ] ARIES-2030 major improvements and refactoring Signed-off-by: Raymond Auge > Create an integration that implements OSGi Rest Management Specification > > > Key: ARIES-2030 > URL: https://issues.apache.org/jira/browse/ARIES-2030 > Project: Aries > Issue Type: New Feature > Components: jax-rs-whiteboard >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2036) Upgrade to Aries Proxy API 1.1.1 & Aries Proxy Impl 1.1.9
[ https://issues.apache.org/jira/browse/ARIES-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284692#comment-17284692 ] ASF subversion and git services commented on ARIES-2036: Commit 8626009b86c863c93cb4a7c75d91fe1bb8b149e8 in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=8626009 ] [ARIES-2036] Upgrade to Aries Proxy Impl 1.1.9 > Upgrade to Aries Proxy API 1.1.1 & Aries Proxy Impl 1.1.9 > - > > Key: ARIES-2036 > URL: https://issues.apache.org/jira/browse/ARIES-2036 > Project: Aries > Issue Type: Dependency upgrade > Components: Blueprint >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: blueprint-core-1.10.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-1990) Hardcoded starting bundle timeout to 60 second
[
https://issues.apache.org/jira/browse/ARIES-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284567#comment-17284567
]
ASF subversion and git services commented on ARIES-1990:
Commit 6487e1ec1a45ebbea663505cd5aa26af606bfb65 in aries's branch
refs/heads/trunk from jbonofre
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=6487e1e ]
[ARIES-1990] Introduce BLUEPRINT_EXECUTOR_TIMEOUT env variable and
blueprint.executor.timeout system property allowing user to define the
blueprint executor timeout
> Hardcoded starting bundle timeout to 60 second
> --
>
> Key: ARIES-1990
> URL: https://issues.apache.org/jira/browse/ARIES-1990
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
>Affects Versions: blueprint-core-1.10.2
>Reporter: nizar.ben.mansour
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: blueprint-core-1.10.3
>
>
> Hello,
> in BlueprintEventDispatcher ,we have 60 second as timeout .This will apply
> when starting a bundle.
>
> {code:java}
> private void callListener(final BlueprintListener listener, final
> BlueprintEvent event) throws RejectedExecutionException {
> try {
> executor.invokeAny(Collections.>singleton(new
> Callable() {
> public Void call() throws Exception {
> listener.blueprintEvent(event);
> return null;
> }
> }), 60L, TimeUnit.SECONDS);
> } catch (InterruptedException ie) {
> LOGGER.warn("Thread interrupted", ie);
> Thread.currentThread().interrupt();
> } catch (TimeoutException te) {
> LOGGER.warn("Listener timed out, will be ignored", te);
> listeners.remove(listener);
> } catch (ExecutionException ee) {
> LOGGER.warn("Listener caused an exception, will be ignored", ee);
> listeners.remove(listener);
> }
> }{code}
>
>
> We are having an issue that results in a warning for a
> java.util.concurrent.TimeoutException.
>
> {code:java}
> 2020-07-21T11:58:00,852 | DEBUG | ActiveMQ InactivityMonitor Worker |
> AbstractInactivityMonitor | 97 - org.apache.activemq.activemq-osgi -
> 5.15.9 | Running WriteCheck[tcp://10.68.248.156:61616]2020-07-21T11:58:00,852
> | DEBUG | ActiveMQ InactivityMonitor Worker | AbstractInactivityMonitor
> | 97 - org.apache.activemq.activemq-osgi - 5.15.9 | Running
> WriteCheck[tcp://10.68.248.156:61616]2020-07-21T11:58:00,853 | DEBUG |
> HikariPool-2 housekeeper | HikariPool | 63 -
> com.zaxxer.HikariCP - 2.4.11 | HikariPool-2 - Pool stats (total=10, active=0,
> idle=10, waiting=0)2020-07-21T11:58:01,878 | WARN | FelixStartLevel |
> BlueprintEventDispatcher | 100 - org.apache.aries.blueprint.core -
> 1.10.2 | Listener timed out, will be
> ignoredjava.util.concurrent.TimeoutException: null at
> java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:184)
> ~[?:?] at
> java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:225)
> ~[?:?] at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185)
> ~[100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446)
> ~[100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33)
> ~[100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443)
> ~[100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180)
> ~[100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:188)
> [100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178)
> [100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133)
> [100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447)
> [100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> [100:org.apache.aries.blueprint.core:1.10.2] at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:311)
> [100:org.apache.aries.blueprint.core:1.10.2] at
>
[jira] [Commented] (ARIES-2036) Upgrade to Aries Proxy API 1.1.1 & Aries Proxy Impl 1.1.9
[ https://issues.apache.org/jira/browse/ARIES-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284340#comment-17284340 ] ASF subversion and git services commented on ARIES-2036: Commit 4495e4b36eb0bcfdfbfb231903fb374d2822d07b in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=4495e4b ] [ARIES-2036] Upgrade to Aries Proxy API 1.1.1 & Impl 1.1.9-SNAPSHOT > Upgrade to Aries Proxy API 1.1.1 & Aries Proxy Impl 1.1.9 > - > > Key: ARIES-2036 > URL: https://issues.apache.org/jira/browse/ARIES-2036 > Project: Aries > Issue Type: Dependency upgrade > Components: Blueprint >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: blueprint-core-1.10.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2035) Upgrade to Aries Blueprint annotation & api 1.0.1
[ https://issues.apache.org/jira/browse/ARIES-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284338#comment-17284338 ] ASF subversion and git services commented on ARIES-2035: Commit fcec37917eba07aa2e5641f4c9671cbf4c287669 in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=fcec379 ] [ARIES-2035] Upgrade to Aries Blueprint API & annotation 1.0.1 > Upgrade to Aries Blueprint annotation & api 1.0.1 > - > > Key: ARIES-2035 > URL: https://issues.apache.org/jira/browse/ARIES-2035 > Project: Aries > Issue Type: Dependency upgrade > Components: Blueprint >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: blueprint-core-1.10.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2037) Upgrade to Felix Utils 1.11.6
[ https://issues.apache.org/jira/browse/ARIES-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284335#comment-17284335 ] ASF subversion and git services commented on ARIES-2037: Commit 7bd2aaa2b750a48f326eb4e03efb34fb0c367fe8 in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=7bd2aaa ] [ARIES-2037] Upgrade to Felix Utils 1.11.6 > Upgrade to Felix Utils 1.11.6 > - > > Key: ARIES-2037 > URL: https://issues.apache.org/jira/browse/ARIES-2037 > Project: Aries > Issue Type: Dependency upgrade > Components: Blueprint >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: blueprint-core-1.10.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2038) Upgrade to easymock 4.2
[ https://issues.apache.org/jira/browse/ARIES-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284332#comment-17284332 ] ASF subversion and git services commented on ARIES-2038: Commit 91f9dc6b30f8b9f61c72e43047e977977354ddfd in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=91f9dc6 ] [ARIES-2038] Upgrade to easymock 4.2 > Upgrade to easymock 4.2 > --- > > Key: ARIES-2038 > URL: https://issues.apache.org/jira/browse/ARIES-2038 > Project: Aries > Issue Type: Dependency upgrade > Components: Blueprint >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: blueprint-core-1.10.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-2022) Upgrade to ASM 9.1
[ https://issues.apache.org/jira/browse/ARIES-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284211#comment-17284211 ] ASF subversion and git services commented on ARIES-2022: Commit 9908258ebe335eb117fdf2a192a061b7c8c7168c in aries's branch refs/heads/trunk from jbonofre [ https://gitbox.apache.org/repos/asf?p=aries.git;h=9908258 ] [ARIES-2022] Upgrade to ASM 9.1 > Upgrade to ASM 9.1 > -- > > Key: ARIES-2022 > URL: https://issues.apache.org/jira/browse/ARIES-2022 > Project: Aries > Issue Type: Dependency upgrade > Components: Proxy >Reporter: Benjamin Graf >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: proxy-impl-1.1.9 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARIES-1995) [blueprint core] importing spring context with custom namespace does not wait for NamespaceHandler to be registered
[
https://issues.apache.org/jira/browse/ARIES-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284096#comment-17284096
]
ASF subversion and git services commented on ARIES-1995:
Commit b79c449bce2ed372ebdaa4124ba9bde057983be1 in aries's branch
refs/heads/trunk from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=b79c449 ]
Merge pull request #111 from amergey/trunk-with-additional-namespace
ARIES-1995 ability to force waiting for custom namespace handlers
> [blueprint core] importing spring context with custom namespace does not wait
> for NamespaceHandler to be registered
> ---
>
> Key: ARIES-1995
> URL: https://issues.apache.org/jira/browse/ARIES-1995
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
>Affects Versions: blueprint-core-1.10.2
>Reporter: Arnaud MERGEY
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: blueprint-core-1.10.3
>
>
> In a blueprint application importing spring context with custom namespace
> using aries blueprint-spring integration does not wait for custom namespace.
> For example
> with this blueprint context
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:spring="http://www.springframework.org/schema/beans;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:security="http://www.springframework.org/schema/security;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;
> default-activation="eager" default-availability="mandatory">
> {code}
> importing this spring context
> {code:java}
> http://www.springframework.org/schema/security; xmlns="http://www.springframework.org/schema/security;
> xmlns:b="http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> https://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/security
> https://www.springframework.org/schema/security/spring-security.xsd;>
> class="org.springframework.security.crypto.password.NoOpPasswordEncoder"/>
>/>
> {code}
> fails with this stacktrace:
> {code:java}
> java.lang.RuntimeException:
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Failed to import bean definitions from URL location
> [classpath:spring/security.xml] Offending resource: URL
> [bundleentry://103.fwk1077514876/OSGI-INF/blueprint/config.xml]; nested
> exception is
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Unable to locate Spring NamespaceHandler for XML
> schema namespace [http://www.springframework.org/schema/security] Offending
> resource: class path resource [spring/security.xml] at
> org.apache.aries.blueprint.spring.BlueprintNamespaceHandler.parse(BlueprintNamespaceHandler.java:132)
> at
> org.apache.aries.blueprint.parser.Parser.parseCustomElement(Parser.java:1369)
> at org.apache.aries.blueprint.parser.Parser.loadComponents(Parser.java:427)
> at org.apache.aries.blueprint.parser.Parser.populate(Parser.java:331) at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:371)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106)
> at
> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
[jira] [Commented] (ARIES-1995) [blueprint core] importing spring context with custom namespace does not wait for NamespaceHandler to be registered
[
https://issues.apache.org/jira/browse/ARIES-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284095#comment-17284095
]
ASF subversion and git services commented on ARIES-1995:
Commit cc82cfbf40937054275a82b64561ed3bf6aa2843 in aries's branch
refs/heads/trunk from arnaud-mergey
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=cc82cfb ]
ARIES-1995 ability to force waiting for custom namespace handlers
> [blueprint core] importing spring context with custom namespace does not wait
> for NamespaceHandler to be registered
> ---
>
> Key: ARIES-1995
> URL: https://issues.apache.org/jira/browse/ARIES-1995
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
>Affects Versions: blueprint-core-1.10.2
>Reporter: Arnaud MERGEY
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: blueprint-core-1.10.3
>
>
> In a blueprint application importing spring context with custom namespace
> using aries blueprint-spring integration does not wait for custom namespace.
> For example
> with this blueprint context
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:spring="http://www.springframework.org/schema/beans;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:security="http://www.springframework.org/schema/security;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;
> default-activation="eager" default-availability="mandatory">
> {code}
> importing this spring context
> {code:java}
> http://www.springframework.org/schema/security; xmlns="http://www.springframework.org/schema/security;
> xmlns:b="http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> https://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/security
> https://www.springframework.org/schema/security/spring-security.xsd;>
> class="org.springframework.security.crypto.password.NoOpPasswordEncoder"/>
>/>
> {code}
> fails with this stacktrace:
> {code:java}
> java.lang.RuntimeException:
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Failed to import bean definitions from URL location
> [classpath:spring/security.xml] Offending resource: URL
> [bundleentry://103.fwk1077514876/OSGI-INF/blueprint/config.xml]; nested
> exception is
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Unable to locate Spring NamespaceHandler for XML
> schema namespace [http://www.springframework.org/schema/security] Offending
> resource: class path resource [spring/security.xml] at
> org.apache.aries.blueprint.spring.BlueprintNamespaceHandler.parse(BlueprintNamespaceHandler.java:132)
> at
> org.apache.aries.blueprint.parser.Parser.parseCustomElement(Parser.java:1369)
> at org.apache.aries.blueprint.parser.Parser.loadComponents(Parser.java:427)
> at org.apache.aries.blueprint.parser.Parser.populate(Parser.java:331) at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:371)
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106)
> at
> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:45)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
>
[jira] [Commented] (ARIES-2030) Create an integration that implements OSGi Rest Management Specification
[ https://issues.apache.org/jira/browse/ARIES-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276677#comment-17276677 ] ASF subversion and git services commented on ARIES-2030: Commit d298485617b290a524ecb076ac0e8b24902dd51f in aries-jax-rs-whiteboard's branch refs/heads/ARIES-2030 from Raymond Auge [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=d298485 ] ARIES-2030 wip Signed-off-by: Raymond Auge > Create an integration that implements OSGi Rest Management Specification > > > Key: ARIES-2030 > URL: https://issues.apache.org/jira/browse/ARIES-2030 > Project: Aries > Issue Type: New Feature > Components: jax-rs-whiteboard >Reporter: Raymond Augé >Assignee: Raymond Augé >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
