[jira] [Commented] (ARIES-1887) org.apache.aries.transaction.blueprint is not thread safe

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762860#comment-16762860
 ] 

ASF GitHub Bot commented on ARIES-1887:
---

GitHub user nicolas-dutertry opened a pull request:

https://github.com/apache/aries/pull/95

[ARIES-1887] ComponentTxData in transaction-blueprint was not thread safe

I have replaced HashMap with ConcurrentHashMap.
Because ConcurrentHashMap does not support null values, I have used 
Optional as value type.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nicolas-dutertry/aries ARIES-1887

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #95


commit 49968551d414fb8a31da5c230b8a3bd4d9788a36
Author: Nicolas Dutertry 
Date:   2019-02-07T16:53:49Z

[ARIES-1887] ComponentTxData in transaction-blueprint was not thread safe




> org.apache.aries.transaction.blueprint is not thread safe
> -
>
> Key: ARIES-1887
> URL: https://issues.apache.org/jira/browse/ARIES-1887
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Affects Versions: transaction-blueprint-2.2.0
>Reporter: Nicolas Dutertry
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: transaction-blueprint-2.3.0
>
>
> The class ComponentTxData in org.apache.aries.transaction.blueprint uses a 
> HashMap
> {code:java}
> private Map txMap = new 
> HashMap();{code}
> This is very dangerous because txMap can be modified and accessed after 
> initialization.
> It should be replaced with a ConcurrentHashMap.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1849) Aries proxy does not work with interface default methods

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741777#comment-16741777
 ] 

ASF GitHub Bot commented on ARIES-1849:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/94


> Aries proxy does not work with interface default methods
> 
>
> Key: ARIES-1849
> URL: https://issues.apache.org/jira/browse/ARIES-1849
> Project: Aries
>  Issue Type: Bug
>  Components: Proxy
>Affects Versions: proxy-impl-1.1.2
>Reporter: Nicolas Dutertry
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: proxy-impl-1.1.4
>
>
> Since Java 8 it is possible to define default implementations inside 
> interface definition.
> It seems that Aries proxy is not compatible with interface default methods. 
> As a result it is not possible to use a blueprint reference to a service 
> implementing an interface with default method.
> The following unit test demonstrates the issue :
> {code:java}
> import java.util.Collections;
> import org.apache.aries.proxy.UnableToProxyException;
> import org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator;
> import org.junit.Assert;
> import org.junit.Test;
> public class InterfaceProxyGeneratorTest {
>     public static interface Service {
>     String getName();
>     
>     default String getValue() {
>     return "default";
>     }
>     }
>     
>     public static class ServiceImpl implements Service {
>     @Override
>     public String getName() {
>     return "serviceimpl";
>     }
>     
>     @Override
>     public String getValue() {
>     return "value";
>     }
>     }
>     
>     @Test
>     public void testProxy() throws UnableToProxyException {
>     ServiceImpl serviceImpl = new ServiceImpl();
>     Assert.assertEquals("serviceimpl", serviceImpl.getName());
>     Assert.assertEquals("value", serviceImpl.getValue());
>     
>     Service proxy = (Service)InterfaceProxyGenerator.getProxyInstance(
>     null, null, Collections.singleton(Service.class),
>     () -> {
>     return serviceImpl;
>     },
>     null);
>     
>     Assert.assertNotNull(proxy);    
>     Assert.assertEquals("serviceimpl", proxy.getName());
>     Assert.assertEquals("value", proxy.getValue());
>     }
> }{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1849) Aries proxy does not work with interface default methods

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739484#comment-16739484
 ] 

ASF GitHub Bot commented on ARIES-1849:
---

GitHub user rovarga opened a pull request:

https://github.com/apache/aries/pull/94

[ARIES-1849] do not use invokevirtual for interface default methods

A default method is still an interface method, hence we should use 
invokeinterface, not invokevirtual, otherwise we will get an 
IncompatibleClassChangeError from hotspot.

Signed-off-by: Robert Varga 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rovarga/aries aries1849

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/94.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #94


commit 00ea87b194df241765df0c4af324735a16f70345
Author: Robert Varga 
Date:   2019-01-10T14:51:48Z

[ARIES-1849] do not use invokevirtual for interface default methods

Signed-off-by: Robert Varga 




> Aries proxy does not work with interface default methods
> 
>
> Key: ARIES-1849
> URL: https://issues.apache.org/jira/browse/ARIES-1849
> Project: Aries
>  Issue Type: Bug
>  Components: Proxy
>Affects Versions: proxy-impl-1.1.2
>Reporter: Nicolas Dutertry
>Priority: Major
>
> Since Java 8 it is possible to define default implementations inside 
> interface definition.
> It seems that Aries proxy is not compatible with interface default methods. 
> As a result it is not possible to use a blueprint reference to a service 
> implementing an interface with default method.
> The following unit test demonstrates the issue :
> {code:java}
> import java.util.Collections;
> import org.apache.aries.proxy.UnableToProxyException;
> import org.apache.aries.proxy.impl.interfaces.InterfaceProxyGenerator;
> import org.junit.Assert;
> import org.junit.Test;
> public class InterfaceProxyGeneratorTest {
>     public static interface Service {
>     String getName();
>     
>     default String getValue() {
>     return "default";
>     }
>     }
>     
>     public static class ServiceImpl implements Service {
>     @Override
>     public String getName() {
>     return "serviceimpl";
>     }
>     
>     @Override
>     public String getValue() {
>     return "value";
>     }
>     }
>     
>     @Test
>     public void testProxy() throws UnableToProxyException {
>     ServiceImpl serviceImpl = new ServiceImpl();
>     Assert.assertEquals("serviceimpl", serviceImpl.getName());
>     Assert.assertEquals("value", serviceImpl.getValue());
>     
>     Service proxy = (Service)InterfaceProxyGenerator.getProxyInstance(
>     null, null, Collections.singleton(Service.class),
>     () -> {
>     return serviceImpl;
>     },
>     null);
>     
>     Assert.assertNotNull(proxy);    
>     Assert.assertEquals("serviceimpl", proxy.getName());
>     Assert.assertEquals("value", proxy.getValue());
>     }
> }{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1872) Provide karaf features repository

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711355#comment-16711355
 ] 

ASF GitHub Bot commented on ARIES-1872:
---

cschneider commented on issue #11: WIP: [ARIES-1872] Add Aries JAX-RS 
Whiteboard Karaf features repository
URL: 
https://github.com/apache/aries-jax-rs-whiteboard/pull/11#issuecomment-444848303
 
 
   We could simply add the capability in the feature in worst case :-)


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Provide karaf features repository
> -
>
> Key: ARIES-1872
> URL: https://issues.apache.org/jira/browse/ARIES-1872
> Project: Aries
>  Issue Type: New Feature
>  Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1872) Provide karaf features repository

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711329#comment-16711329
 ] 

ASF GitHub Bot commented on ARIES-1872:
---

jbonofre commented on issue #11: WIP: [ARIES-1872] Add Aries JAX-RS Whiteboard 
Karaf features repository
URL: 
https://github.com/apache/aries-jax-rs-whiteboard/pull/11#issuecomment-444842139
 
 
   @cschneider yes it makes sense. I'm evaluating different solutions on Karaf 
(checking the capability provided by Pax Web, using Felix servlet-api instead 
of javax one, ...).


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Provide karaf features repository
> -
>
> Key: ARIES-1872
> URL: https://issues.apache.org/jira/browse/ARIES-1872
> Project: Aries
>  Issue Type: New Feature
>  Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1872) Provide karaf features repository

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711310#comment-16711310
 ] 

ASF GitHub Bot commented on ARIES-1872:
---

cschneider closed pull request #11: WIP: [ARIES-1872] Add Aries JAX-RS 
Whiteboard Karaf features repository
URL: https://github.com/apache/aries-jax-rs-whiteboard/pull/11
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/jax-rs.features/pom.xml b/jax-rs.features/pom.xml
new file mode 100644
index 000..0520ae2
--- /dev/null
+++ b/jax-rs.features/pom.xml
@@ -0,0 +1,80 @@
+
+
+http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
+
+4.0.0
+
+
+org.apache.aries.jax.rs
+org.apache.aries.jax.rs
+1.0.2-SNAPSHOT
+
+
+org.apache.aries.jax.rs.features
+Apache Aries JAX-RS Karaf features repository
+Apache Aries JAX-RS Karaf Features
+pom
+
+
+
+
+${project.basedir}/src/main/feature
+true
+${project.build.directory}/feature
+
+
+
+
+org.apache.maven.plugins
+maven-resources-plugin
+
+
+
+resources
+
+
+
+
+
+org.codehaus.mojo
+build-helper-maven-plugin
+3.0.0
+
+
+attach-artifact
+package
+
+attach-artifact
+
+
+
+
+target/feature/feature.xml
+xml
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/jax-rs.features/src/main/feature/feature.xml 
b/jax-rs.features/src/main/feature/feature.xml
new file mode 100644
index 000..8822162
--- /dev/null
+++ b/jax-rs.features/src/main/feature/feature.xml
@@ -0,0 +1,35 @@
+
+
+http://karaf.apache.org/xmlns/features/v1.3.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 
http://karaf.apache.org/xmlns/features/v1.3.0;>
+
+
mvn:org.apache.karaf.features/standard/[4,5)/xml/features
+
+
+http
+pax-jetty
+mvn:org.apache.aries.spec/org.apache.aries.javax.jax.rs-api/1.0.1
+mvn:org.osgi/org.osgi.util.function/1.1.0
+mvn:org.osgi/org.osgi.util.promise/1.1.0
+mvn:org.osgi/org.osgi.service.jaxrs/1.0.0
+mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.annotation-api-1.3/1.3_1
+
mvn:org.apache.aries.jax.rs/org.apache.aries.jax.rs.whiteboard/${project.version}
+
+
+
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index f6c1477..7c1d117 100644
--- a/pom.xml
+++ b/pom.xml
@@ -52,6 +52,7 @@
 jax-rs.whiteboard
 jax-rs.itests
 jax-rs.itests-fragment
+jax-rs.features
 
 
 


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Provide karaf features repository
> -
>
> Key: ARIES-1872
> URL: https://issues.apache.org/jira/browse/ARIES-1872
> Project: Aries
>  Issue Type: New Feature
>  Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1872) Provide karaf features repository

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16711318#comment-16711318
 ] 

ASF GitHub Bot commented on ARIES-1872:
---

cschneider commented on issue #11: WIP: [ARIES-1872] Add Aries JAX-RS 
Whiteboard Karaf features repository
URL: 
https://github.com/apache/aries-jax-rs-whiteboard/pull/11#issuecomment-444839071
 
 
   I think we can already release it. We can figure out the missing requirement 
on the karaf side. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Provide karaf features repository
> -
>
> Key: ARIES-1872
> URL: https://issues.apache.org/jira/browse/ARIES-1872
> Project: Aries
>  Issue Type: New Feature
>  Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1872) Provide karaf features repository

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710592#comment-16710592
 ] 

ASF GitHub Bot commented on ARIES-1872:
---

jbonofre opened a new pull request #11: WIP: [ARIES-1872] Add Aries JAX-RS 
Whiteboard Karaf features repository
URL: https://github.com/apache/aries-jax-rs-whiteboard/pull/11
 
 
   I have an issue at installation:
   
   ```
   Unable to resolve org.apache.aries.jax.rs.whiteboard [48](R 48.0): missing 
requirement [org.apache.aries.jax.rs.whiteboard [48](R 48.0)] osgi.contract; 
(&(osgi.contract=JavaServlet)(version=3.1.0)) Unresolved requirements: 
[[org.apache.aries.jax.rs.whiteboard [48](R 48.0)] osgi.contract; 
(&(osgi.contract=JavaServlet)(version=3.1.0))]
   ```
   
   `JavaServlet` contract is provided by Pax Web features (in the right 
version). I'm checking.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Provide karaf features repository
> -
>
> Key: ARIES-1872
> URL: https://issues.apache.org/jira/browse/ARIES-1872
> Project: Aries
>  Issue Type: New Feature
>  Components: jax-rs-whiteboard
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: jax-rs-whiteboard-1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1793) Blueprint interceptors do not work anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707279#comment-16707279
 ] 

ASF GitHub Bot commented on ARIES-1793:
---

cschneider opened a new pull request #671: Revert "[ARIES-1793] Upgrade to 
blueprint-core 1.10.0"
URL: https://github.com/apache/karaf/pull/671
 
 
   Reverts apache/karaf#670 . Because the update to 1.10.0 breaks camel 
blueprint. We will try to create blueprint core 1.9.1 that works with camel and 
jpa.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Blueprint interceptors do not work anymore
> --
>
> Key: ARIES-1793
> URL: https://issues.apache.org/jira/browse/ARIES-1793
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.9.0
> Environment: Karaf 4.2.0
>Reporter: Nicolas Dutertry
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: blueprint-core-1.10.0
>
> Attachments: aries-interceptor.patch
>
>
> I have committed a project on Github to illustrate the issue : 
> [https://github.com/nicolas-dutertry/test-jpa]
> This project contains a blueprint bundle with a bean TestRepository annotated 
> with @PersistenceContext. This bean is then injected into another bean 
> TestServiceImpl which is then published as an osgi service :
> {code:xml}
> 
>     
> 
>      class="com.dutertry.test.karaf.jpa.service.impl.TestRepository"/>
>  class="com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl">
>     
>     
>  ref="testService"/>
> {code}
> With Karaf 4.1.5 the instance of TestRepository injected in testService is an 
> aries proxy managing JPA stuff, but with Karaf 4.2.0 the injected instance is 
> not a proxy. Thus when using testService, the following error occurs:
> {code:java}
> java.lang.IllegalStateException: Need active coordination
>     at 
> org.apache.aries.jpa.support.impl.EMSupplierImpl.get(EMSupplierImpl.java:81) 
> ~[?:?]
>     at org.apache.aries.jpa.support.osgi.impl.EmProxy.invoke(EmProxy.java:38) 
> ~[?:?]
>     at com.sun.proxy.$Proxy77.createQuery(Unknown Source) ~[?:?]
>     at Proxy4c2993b8_dc6f_46b4_8e62_524dc0ad05f5.createQuery(Unknown Source) 
> ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestRepository.list(TestRepository.java:26)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl.list(TestServiceImpl.java:25)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.cmd.ListPersonCommand.execute(ListPersonCommand.java:24)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> ~[?:?]
>     at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
>     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) [?:?]{code}
>  
> After some investigation, I have found that this bug is due to the resolution 
> of issue ARIES-1544. I have done a patch (see attached file) which solve the 
> issue I think.
> [^aries-interceptor.patch]
> Can you please integrate my patch or correct the issue another way ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1793) Blueprint interceptors do not work anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707281#comment-16707281
 ] 

ASF GitHub Bot commented on ARIES-1793:
---

cschneider closed pull request #671: Revert "[ARIES-1793] Upgrade to 
blueprint-core 1.10.0"
URL: https://github.com/apache/karaf/pull/671
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Blueprint interceptors do not work anymore
> --
>
> Key: ARIES-1793
> URL: https://issues.apache.org/jira/browse/ARIES-1793
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.9.0
> Environment: Karaf 4.2.0
>Reporter: Nicolas Dutertry
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: blueprint-core-1.10.0
>
> Attachments: aries-interceptor.patch
>
>
> I have committed a project on Github to illustrate the issue : 
> [https://github.com/nicolas-dutertry/test-jpa]
> This project contains a blueprint bundle with a bean TestRepository annotated 
> with @PersistenceContext. This bean is then injected into another bean 
> TestServiceImpl which is then published as an osgi service :
> {code:xml}
> 
>     
> 
>      class="com.dutertry.test.karaf.jpa.service.impl.TestRepository"/>
>  class="com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl">
>     
>     
>  ref="testService"/>
> {code}
> With Karaf 4.1.5 the instance of TestRepository injected in testService is an 
> aries proxy managing JPA stuff, but with Karaf 4.2.0 the injected instance is 
> not a proxy. Thus when using testService, the following error occurs:
> {code:java}
> java.lang.IllegalStateException: Need active coordination
>     at 
> org.apache.aries.jpa.support.impl.EMSupplierImpl.get(EMSupplierImpl.java:81) 
> ~[?:?]
>     at org.apache.aries.jpa.support.osgi.impl.EmProxy.invoke(EmProxy.java:38) 
> ~[?:?]
>     at com.sun.proxy.$Proxy77.createQuery(Unknown Source) ~[?:?]
>     at Proxy4c2993b8_dc6f_46b4_8e62_524dc0ad05f5.createQuery(Unknown Source) 
> ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestRepository.list(TestRepository.java:26)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl.list(TestServiceImpl.java:25)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.cmd.ListPersonCommand.execute(ListPersonCommand.java:24)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> ~[?:?]
>     at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
>     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) [?:?]{code}
>  
> After some investigation, I have found that this bug is due to the resolution 
> of issue ARIES-1544. I have done a patch (see attached file) which solve the 
> issue I think.
> [^aries-interceptor.patch]
> Can you please integrate my patch or correct the issue another way ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1793) Blueprint interceptors do not work anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707255#comment-16707255
 ] 

ASF GitHub Bot commented on ARIES-1793:
---

cschneider closed pull request #670: [ARIES-1793] Upgrade to blueprint-core 
1.10.0
URL: https://github.com/apache/karaf/pull/670
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/pom.xml b/pom.xml
index 81f8d40447..36fcad37c6 100644
--- a/pom.xml
+++ b/pom.xml
@@ -218,7 +218,7 @@
 1.0.0
 
1.0.0
 1.0.1
-1.9.0
+1.10.0
 
1.0.0
 1.2.0
 1.0.1


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Blueprint interceptors do not work anymore
> --
>
> Key: ARIES-1793
> URL: https://issues.apache.org/jira/browse/ARIES-1793
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.9.0
> Environment: Karaf 4.2.0
>Reporter: Nicolas Dutertry
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: blueprint-core-1.10.0
>
> Attachments: aries-interceptor.patch
>
>
> I have committed a project on Github to illustrate the issue : 
> [https://github.com/nicolas-dutertry/test-jpa]
> This project contains a blueprint bundle with a bean TestRepository annotated 
> with @PersistenceContext. This bean is then injected into another bean 
> TestServiceImpl which is then published as an osgi service :
> {code:xml}
> 
>     
> 
>      class="com.dutertry.test.karaf.jpa.service.impl.TestRepository"/>
>  class="com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl">
>     
>     
>  ref="testService"/>
> {code}
> With Karaf 4.1.5 the instance of TestRepository injected in testService is an 
> aries proxy managing JPA stuff, but with Karaf 4.2.0 the injected instance is 
> not a proxy. Thus when using testService, the following error occurs:
> {code:java}
> java.lang.IllegalStateException: Need active coordination
>     at 
> org.apache.aries.jpa.support.impl.EMSupplierImpl.get(EMSupplierImpl.java:81) 
> ~[?:?]
>     at org.apache.aries.jpa.support.osgi.impl.EmProxy.invoke(EmProxy.java:38) 
> ~[?:?]
>     at com.sun.proxy.$Proxy77.createQuery(Unknown Source) ~[?:?]
>     at Proxy4c2993b8_dc6f_46b4_8e62_524dc0ad05f5.createQuery(Unknown Source) 
> ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestRepository.list(TestRepository.java:26)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl.list(TestServiceImpl.java:25)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.cmd.ListPersonCommand.execute(ListPersonCommand.java:24)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> ~[?:?]
>     at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
>     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) [?:?]{code}
>  
> After some investigation, I have found that this bug is due to the resolution 
> of issue ARIES-1544. I have done a patch (see attached file) which solve the 
> issue I think.
> [^aries-interceptor.patch]
> Can you please integrate my patch or correct the issue another way ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1793) Blueprint interceptors do not work anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707244#comment-16707244
 ] 

ASF GitHub Bot commented on ARIES-1793:
---

Smasherr opened a new pull request #670: [ARIES-1793] Upgrade to blueprint-core 
1.10.0
URL: https://github.com/apache/karaf/pull/670
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Blueprint interceptors do not work anymore
> --
>
> Key: ARIES-1793
> URL: https://issues.apache.org/jira/browse/ARIES-1793
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.9.0
> Environment: Karaf 4.2.0
>Reporter: Nicolas Dutertry
>Assignee: Guillaume Nodet
>Priority: Blocker
> Fix For: blueprint-core-1.10.0
>
> Attachments: aries-interceptor.patch
>
>
> I have committed a project on Github to illustrate the issue : 
> [https://github.com/nicolas-dutertry/test-jpa]
> This project contains a blueprint bundle with a bean TestRepository annotated 
> with @PersistenceContext. This bean is then injected into another bean 
> TestServiceImpl which is then published as an osgi service :
> {code:xml}
> 
>     
> 
>      class="com.dutertry.test.karaf.jpa.service.impl.TestRepository"/>
>  class="com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl">
>     
>     
>  ref="testService"/>
> {code}
> With Karaf 4.1.5 the instance of TestRepository injected in testService is an 
> aries proxy managing JPA stuff, but with Karaf 4.2.0 the injected instance is 
> not a proxy. Thus when using testService, the following error occurs:
> {code:java}
> java.lang.IllegalStateException: Need active coordination
>     at 
> org.apache.aries.jpa.support.impl.EMSupplierImpl.get(EMSupplierImpl.java:81) 
> ~[?:?]
>     at org.apache.aries.jpa.support.osgi.impl.EmProxy.invoke(EmProxy.java:38) 
> ~[?:?]
>     at com.sun.proxy.$Proxy77.createQuery(Unknown Source) ~[?:?]
>     at Proxy4c2993b8_dc6f_46b4_8e62_524dc0ad05f5.createQuery(Unknown Source) 
> ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestRepository.list(TestRepository.java:26)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.service.impl.TestServiceImpl.list(TestServiceImpl.java:25)
>  ~[?:?]
>     at 
> com.dutertry.test.karaf.jpa.cmd.ListPersonCommand.execute(ListPersonCommand.java:24)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  ~[?:?]
>     at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
> ~[?:?]
>     at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
> ~[?:?]
>     at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
>     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
>     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) [?:?]{code}
>  
> After some investigation, I have found that this bug is due to the resolution 
> of issue ARIES-1544. I have done a patch (see attached file) which solve the 
> issue I think.
> [^aries-interceptor.patch]
> Can you please integrate my patch or correct the issue another way ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699161#comment-16699161
 ] 

ASF GitHub Bot commented on ARIES-1783:
---

cschneider closed pull request #3: ARIES-1783 EM joins transaction when needed
URL: https://github.com/apache/aries-jpa/pull/3
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/itests/jpa-container-blueprint-testbundle/src/main/java/org/apache/aries/jpa/container/itest/bundle/blueprint/impl/CarServiceWithRequiresNew.java
 
b/itests/jpa-container-blueprint-testbundle/src/main/java/org/apache/aries/jpa/container/itest/bundle/blueprint/impl/CarServiceWithRequiresNew.java
index d1b041c..754bdd8 100644
--- 
a/itests/jpa-container-blueprint-testbundle/src/main/java/org/apache/aries/jpa/container/itest/bundle/blueprint/impl/CarServiceWithRequiresNew.java
+++ 
b/itests/jpa-container-blueprint-testbundle/src/main/java/org/apache/aries/jpa/container/itest/bundle/blueprint/impl/CarServiceWithRequiresNew.java
@@ -17,6 +17,7 @@
 
 import java.util.Arrays;
 import java.util.Collection;
+import java.util.List;
 
 import javax.transaction.Transactional;
 import javax.transaction.Transactional.TxType;
@@ -53,7 +54,9 @@ public void addCar(Car car) {
 ref = getService();
 CarService carService = bundleContext.getService(ref);
 carService.addCar(c);
-return Arrays.asList(this.getCar("TR123"));
+final List returnVal = Arrays.asList(this.getCar("TR123"));
+carService.deleteCar("TR123");
+return returnVal;
 } finally {
 if (ref != null) {
 bundleContext.ungetService(ref);
@@ -75,7 +78,9 @@ public void updateCar(Car car) {
 }
 
 @Override
+@Transactional
 public void deleteCar(String id) {
+em.remove(this.getCar(id));
 }
 
 public void setBundleContext(BundleContext bundleContext) {
diff --git 
a/itests/jpa-container-itest/src/test/java/org/apache/aries/jpa/blueprint/aries/itest/BlueprintTest.java
 
b/itests/jpa-container-itest/src/test/java/org/apache/aries/jpa/blueprint/aries/itest/BlueprintTest.java
index 507ff3e..ab516c4 100644
--- 
a/itests/jpa-container-itest/src/test/java/org/apache/aries/jpa/blueprint/aries/itest/BlueprintTest.java
+++ 
b/itests/jpa-container-itest/src/test/java/org/apache/aries/jpa/blueprint/aries/itest/BlueprintTest.java
@@ -43,10 +43,10 @@
 public class BlueprintTest extends AbstractCarJPAITest {
 @Inject
 Coordinator coordinator;
-
+
 @Inject
 UserTransaction ut;
-
+
 @Test
 public void testCoordination() {
 assertNoCoordination();
@@ -66,7 +66,7 @@ public void testCoordination() {
 Assert.assertEquals(0, carService.getCars().size());
 }
 }
-
+
 @Test
 public void testInjectToMethod() throws Exception {
 carLifecycle(getCarService("method"));
@@ -86,7 +86,7 @@ public void testEmf() throws Exception {
 public void testEm() throws Exception {
 carLifecycle(getCarService("em"));
 }
-
+
 @Test
 public void testEmJtaAnn() throws Exception {
 carLifecycle(getCarService("emJtaAnn"));
@@ -96,17 +96,17 @@ public void testEmJtaAnn() throws Exception {
 public void testSupplier() throws Exception {
 carLifecycle(getCarService("supplier"));
 }
-
+
 @Test
 public void testRealTransactional() throws Exception {
 carRealTransactionalLifecycle(getCarService("emJtaAnn"));
 }
-
+
 @Test
 public void testInlined() throws Exception {
 carRealTransactionalLifecycle(getCarService("emJtaAnnInlined"));
 }
-
+
 @Test
 public void testCoordinationLifecycle() throws InterruptedException, 
ExecutionException {
 CarService carService = getCarService("em");
@@ -127,7 +127,6 @@ public void testCoordinationLifecycle() throws 
InterruptedException, ExecutionEx
 }
 
 @Test
-@Ignore
 public void testCarWithRequiresNewAnnotation() throws Exception {
 CarService cs = getCarService("rn");
 cs.getCars();
@@ -146,7 +145,7 @@ private void carLifecycle(CarService carService) {
 assertBlueCar(carService.getCar(BLUE_PLATE));
 carService.deleteCar(BLUE_PLATE);
 }
-
+
 private void carRealTransactionalLifecycle(CarService carService) throws 
IllegalStateException, SystemException, NotSupportedException {
 assertNoCoordination();
 if (carService.getCar(BLACK_CAR_PLATE) != null) {
@@ -162,7 +161,7 @@ private void assertNoCoordination() {
 Coordination coord = coordinator.peek();
 Assert.assertNull("There should not be a coordination on 

[jira] [Commented] (ARIES-1783) TransactionRequiredException when non-transactional method precedes a transactional one in the same service.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699134#comment-16699134
 ] 

ASF GitHub Bot commented on ARIES-1783:
---

Smasherr opened a new pull request #3: ARIES-1783 EM joins transaction when 
needed
URL: https://github.com/apache/aries-jpa/pull/3
 
 
   EMSupplier makes a cached EM join a transaction if there is currently
   an active one.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> TransactionRequiredException when non-transactional method precedes a 
> transactional one in the same service.
> 
>
> Key: ARIES-1783
> URL: https://issues.apache.org/jira/browse/ARIES-1783
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-2.5.0
>Reporter: Daniel Estermann
>Priority: Major
>
> Assume I have a service implementation with a method annotated with 
> @Transactional and one of TxTypes not starting a transaction:
>  * NEVER
>  * NOT_SUPPORTED
>  * SUPPORTS
> From that non-transactional method I want to use a self-reference resolved 
> via BundleContext to call a transactional method in the same service, 
> annotated with one of those TxTypes:
>  * REQUIRED
>  * REQURES_NEW
> Since the resolved self-reference is a proxied object I expect it to be able 
> to start a new transaction. This is not the case however and the subject 
> exception occurs.
>  
> I created a test case revealing the issue in the following pull request: 
> https://github.com/apache/aries-jpa/pull/2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1826) blueprint-maven-plugin IllegalArgumentException from ASM, possibly Java 9 related

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619119#comment-16619119
 ] 

ASF GitHub Bot commented on ARIES-1826:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/87


> blueprint-maven-plugin IllegalArgumentException from ASM, possibly Java 9 
> related
> -
>
> Key: ARIES-1826
> URL: https://issues.apache.org/jira/browse/ARIES-1826
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.10.0
>Reporter: Michael Vorburger
>Priority: Major
>
> From [https://jira.opendaylight.org/browse/ODLPARENT-167] :
> {code:java}
> [INFO] --- blueprint-maven-plugin:1.10.0:blueprint-generate (default) @ 
> northbound-api ---
> [INFO] Package org.opendaylight will be scanned
> (...)
> [ERROR] Failed to execute goal 
> org.apache.aries.blueprint:blueprint-maven-plugin:1.10.0:blueprint-generate 
> (default) on project northbound-api: Error during blueprint generation: 
> IllegalArgumentException -> [Help 1]{code}
> With {{mvn-X}} (details in 
> [ODLPARENT-167|https://jira.opendaylight.org/browse/ODLPARENT-167]) we find 
> it's {{Caused by: java.lang.IllegalArgumentException at 
> org.apache.xbean.asm5.ClassReader.}}, which could be related to it 
> scanning some Java > 8 (9/10/11) class in some JAR?
> [~gnt] or [~ch...@die-schneider.net], I don't suppose this is a known issue 
> for which you already have a fix, or an thoughts? [~skitt] FYI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1826) blueprint-maven-plugin IllegalArgumentException from ASM, possibly Java 9 related

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618148#comment-16618148
 ] 

ASF GitHub Bot commented on ARIES-1826:
---

GitHub user vorburger opened a pull request:

https://github.com/apache/aries/pull/87

ARIES-1826 Bump xbean-finder from 4.5 to 4.9



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vorburger/aries 
ARIES-1826_blueprint-maven-plugin

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/87.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #87


commit 4b31632dbb52249ff799f3b98e7c49c2f2f1d83b
Author: Michael Vorburger 
Date:   2018-09-17T21:00:24Z

ARIES-1826 Bump xbean-finder from 4.5 to 4.9

Signed-off-by: Michael Vorburger 




> blueprint-maven-plugin IllegalArgumentException from ASM, possibly Java 9 
> related
> -
>
> Key: ARIES-1826
> URL: https://issues.apache.org/jira/browse/ARIES-1826
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.10.0
>Reporter: Michael Vorburger
>Priority: Major
>
> From [https://jira.opendaylight.org/browse/ODLPARENT-167] :
> {code:java}
> [INFO] --- blueprint-maven-plugin:1.10.0:blueprint-generate (default) @ 
> northbound-api ---
> [INFO] Package org.opendaylight will be scanned
> (...)
> [ERROR] Failed to execute goal 
> org.apache.aries.blueprint:blueprint-maven-plugin:1.10.0:blueprint-generate 
> (default) on project northbound-api: Error during blueprint generation: 
> IllegalArgumentException -> [Help 1]{code}
> With {{mvn-X}} (details in 
> [ODLPARENT-167|https://jira.opendaylight.org/browse/ODLPARENT-167]) we find 
> it's {{Caused by: java.lang.IllegalArgumentException at 
> org.apache.xbean.asm5.ClassReader.}}, which could be related to it 
> scanning some Java > 8 (9/10/11) class in some JAR?
> [~gnt] or [~ch...@die-schneider.net], I don't suppose this is a known issue 
> for which you already have a fix, or an thoughts? [~skitt] FYI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1809) Run rat plugin by default

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540451#comment-16540451
 ] 

ASF GitHub Bot commented on ARIES-1809:
---

Github user alien11689 closed the pull request at:

https://github.com/apache/aries/pull/86


> Run rat plugin by default
> -
>
> Key: ARIES-1809
> URL: https://issues.apache.org/jira/browse/ARIES-1809
> Project: Aries
>  Issue Type: Improvement
>  Components: Parent
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
>Priority: Major
>
> The easiest way is to activate rat profile by default in aries parent pom and 
> bump parent pom in depending modules one by one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1809) Run rat plugin by default

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507331#comment-16507331
 ] 

ASF GitHub Bot commented on ARIES-1809:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/86

[ARIES-1809] Run rat plugin by default



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-1809-rat-by-default

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/86.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #86


commit ce4c0158aacc778cbf548cf3ea923ebf828d901c
Author: Dominik Adam Przybysz 
Date:   2018-06-10T10:12:31Z

[ARIES-1809] Run rat plugin by default




> Run rat plugin by default
> -
>
> Key: ARIES-1809
> URL: https://issues.apache.org/jira/browse/ARIES-1809
> Project: Aries
>  Issue Type: Improvement
>  Components: Parent
>Reporter: Dominik Przybysz
>Priority: Major
>
> The easiest way is to activate rat profile by default in aries parent pom and 
> bump parent pom in depending modules one by one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1805) Blueprint core dose not honor Java beans specification

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496703#comment-16496703
 ] 

ASF GitHub Bot commented on ARIES-1805:
---

GitHub user valdar opened a pull request:

https://github.com/apache/aries/pull/85

Modified ReflectionUtilsTest#testDuplicateGetter to reflect ARIES-1805

The test is not passing, is just as a reference for implementation.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/valdar/aries ARIES-1805

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/85.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #85


commit e2d31d45331c47b42c86668d732b0e3ed48a1394
Author: Andrea Tarocchi 
Date:   2018-05-31T15:19:42Z

Modified ReflectionUtilsTest#testDuplicateGetter to reflect ARIES-1805




> Blueprint core dose not honor Java beans specification
> --
>
> Key: ARIES-1805
> URL: https://issues.apache.org/jira/browse/ARIES-1805
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.8.0
>Reporter: Andrea Tarocchi
>Priority: Major
>
> Aries blueprint core, to consider a property legit, checks that is and get 
> access methods are not present at the same time: 
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/ReflectionUtils.java#L222-L255
>  specifically: 
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/ReflectionUtils.java#L249
> looking at java bean specification: 
> http://download.oracle.com/otn-pub/jcp/7224-javabeans-1.01-fr-spec-oth-JSpec/beans.101.pdf?AuthParam=1527758194_593d6e2c9336cf75e216a390c7b9
> it seems that both access methods ({{is}} and {{get}}) are allowed to be 
> present at the same time, in that case, the {{is}} has to be used:
> bq. *8.3.2* Boolean properties In addition, for boolean properties, we allow 
> a getter method to match the pattern: public boolean is(); This 
> “is” method may be provided instead of a “get” 
> method, or it may be provided in addition to a “get” method. In 
> either case, if the “is” method is present for a boolean 
> property then we will use the “is” method to read the property 
> value.
> Should the Aries implementation b modified accordingly?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1803) Upgrade proxy to ASM 6.1.1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488896#comment-16488896
 ] 

ASF GitHub Bot commented on ARIES-1803:
---

GitHub user jbonofre opened a pull request:

https://github.com/apache/aries/pull/84

[ARIES-1803] Upgrade proxy to ASM 6.1.1



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/aries ARIES-1803

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/84.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #84


commit c3e65403390c8217dd5da40235ae0bd2cc28fdc3
Author: Jean-Baptiste Onofré 
Date:   2018-05-24T12:28:43Z

[ARIES-1803] Upgrade proxy to ASM 6.1.1




> Upgrade proxy to ASM 6.1.1
> --
>
> Key: ARIES-1803
> URL: https://issues.apache.org/jira/browse/ARIES-1803
> Project: Aries
>  Issue Type: Dependency upgrade
>  Components: Proxy
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1800) rollbackOn element of Transactional annotation ignored when set on class level

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475547#comment-16475547
 ] 

ASF GitHub Bot commented on ARIES-1800:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/83


> rollbackOn element of Transactional annotation ignored when set on class level
> --
>
> Key: ARIES-1800
> URL: https://issues.apache.org/jira/browse/ARIES-1800
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Affects Versions: transaction-blueprint-2.2.0
>Reporter: Daniel Estermann
>Priority: Major
>
> Since ARIES-1690 the methods throwing a checked exception cause a rollback if 
> the related exception is marked for a rollback using rollbackOn element of 
> Transactional annotation set on a method. However this doesn't work for 
> Transactional annotations on the class level.
> We also need to clarify how we should handle a exceptions set on both levels 
> class and method. There are at least two options:
> * The resulting set of exceptions marked for rollback is an aggregation from 
> both class level and method level annotation.
> * Exception set defined on the method level overrides exceptions of the class 
> leve.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1800) rollbackOn element of Transactional annotation ignored when set on class level

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467238#comment-16467238
 ] 

ASF GitHub Bot commented on ARIES-1800:
---

GitHub user Smasherr opened a pull request:

https://github.com/apache/aries/pull/83

ARIES-1800: Collect exceptions from class level annotations

The commit fixes the bug and adds a test

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Smasherr/aries ARIES-1800

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #83


commit 54e025bc0b92ff2695f503b0ddd49d539b1f0de5
Author: Daniel Estermann 
Date:   2018-05-08T09:28:06Z

ARIES-1800: Collect exceptions from class level annotations




> rollbackOn element of Transactional annotation ignored when set on class level
> --
>
> Key: ARIES-1800
> URL: https://issues.apache.org/jira/browse/ARIES-1800
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Affects Versions: transaction-blueprint-2.2.0
>Reporter: Daniel Estermann
>Priority: Major
>
> Since ARIES-1690 the methods throwing a checked exception cause a rollback if 
> the related exception is marked for a rollback using rollbackOn element of 
> Transactional annotation set on a method. However this doesn't work for 
> Transactional annotations on the class level.
> We also need to clarify how we should handle a exceptions set on both levels 
> class and method. There are at least two options:
> * The resulting set of exceptions marked for rollback is an aggregation from 
> both class level and method level annotation.
> * Exception set defined on the method level overrides exceptions of the class 
> leve.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARIES-1321) NPE when calling ServiceLoader.load with a variable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322230#comment-16322230
 ] 

ASF GitHub Bot commented on ARIES-1321:
---

GitHub user mnlipp opened a pull request:

https://github.com/apache/aries/pull/82

Support variable as argument for ServiceLoader.load.

Fixes [#1321](https://issues.apache.org/jira/browse/ARIES-1321). (Took me 
*hours* to find out that the problem wasn't my configuration of 
osgi.serviceloader but a critical(!) bug in the implementation opened 2.5 years 
ago.) The fix is based on [Olivier 
Nouguier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cheleb)'s 
patch. I improved it a bit to handle an additional possible problem and added 
test cases.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mnlipp/aries 1321-fix-NPE

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/82.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #82


commit 47cf4fed2809a9ffa3c842edd2f04712dea10d94
Author: Michael N. Lipp 
Date:   2018-01-11T13:39:25Z

Support variable as argument for ServiceLoader.load.

Fixes #1321.




> NPE when calling ServiceLoader.load with a variable
> ---
>
> Key: ARIES-1321
> URL: https://issues.apache.org/jira/browse/ARIES-1321
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Affects Versions: spifly-1.0.2
>Reporter: Olivier NOUGUIER
>Priority: Critical
> Attachments: ARIES-1321.diff
>
>
> When ServiceLoader is called with a variable (aka not a constant):
> aMethod(Class type ){
>   ServiceLoader.load(type).
> }
> Then the weaver result in a NPE in TCCLMethodVisitor because lastLDCType is 
> null.
> Patch provided.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1752) Upgrade to ASM 6.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16218194#comment-16218194
 ] 

ASF GitHub Bot commented on ARIES-1752:
---

GitHub user jbonofre opened a pull request:

https://github.com/apache/aries/pull/81

[ARIES-1752] Upgrade Aries SPI Fly to ASM 6.0



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/aries SPI-FLY_ASM6

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #81


commit 3877a6a2ccaf2317c6816768e42741b557704f5b
Author: Jean-Baptiste Onofré 
Date:   2017-10-25T07:02:39Z

[ARIES-1752] Upgrade Aries SPI Fly to ASM 6.0




> Upgrade to ASM 6.0
> --
>
> Key: ARIES-1752
> URL: https://issues.apache.org/jira/browse/ARIES-1752
> Project: Aries
>  Issue Type: Dependency upgrade
>  Components: SPI Fly
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: spifly-1.0.10
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191149#comment-16191149
 ] 

ASF GitHub Bot commented on ARIES-1746:
---

GitHub user thusithathilina reopened a pull request:

https://github.com/apache/aries/pull/75

ARIES-1746: Add SPIFly support for InitialContextFactory

According to the OSGi spec when we register an InitialContextFactory, we 
need to register that for both implementation and InitialContextFactory 
classes. This PR will provide that support.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/thusithathilina/aries trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #75


commit 0921c41d7a50ad00bf69f70c9841a0d4e057aff4
Author: Thusitha Dayaratne 
Date:   2017-10-04T05:23:53Z

ARIES-1746: Add SPIFly support for InitialContextFactory

commit 138c7ce3513b5e2f6423fcc7ec67e87c06c1eb75
Author: Thusitha Dayaratne 
Date:   2017-10-04T11:31:24Z

ARIES-1746: Fix test cases




> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190839#comment-16190839
 ] 

ASF GitHub Bot commented on ARIES-1746:
---

Github user thusithathilina closed the pull request at:

https://github.com/apache/aries/pull/75


> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1746) SPIFly support for InitialContextFactory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190828#comment-16190828
 ] 

ASF GitHub Bot commented on ARIES-1746:
---

GitHub user thusithathilina opened a pull request:

https://github.com/apache/aries/pull/75

ARIES-1746: Add SPIFly support for InitialContextFactory

According to the OSGi spec when we register an InitialContextFactory, we 
need to register that for both implementation and InitialContextFactory 
classes. This PR will provide that support.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/thusithathilina/aries trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #75


commit 0921c41d7a50ad00bf69f70c9841a0d4e057aff4
Author: Thusitha Dayaratne 
Date:   2017-10-04T05:23:53Z

ARIES-1746: Add SPIFly support for InitialContextFactory




> SPIFly support for InitialContextFactory
> 
>
> Key: ARIES-1746
> URL: https://issues.apache.org/jira/browse/ARIES-1746
> Project: Aries
>  Issue Type: Improvement
>  Components: SPI Fly
>Reporter: Thusitha Thilina Dayaratne
>
> I'm trying to use Aries SPYFly with one of our projects. According to the 
> OSGi spec when we register an InitialContextFactory, we need to register that 
> for both implementation and InitialContextFactory classes.
> IMHO it would be great if we can support that with SPY-Fly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARIES-1636) mvn install fails due to old dependency versions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030440#comment-16030440
 ] 

ASF GitHub Bot commented on ARIES-1636:
---

Github user tadayosi closed the pull request at:

https://github.com/apache/aries/pull/59


> mvn install fails due to old dependency versions
> 
>
> Key: ARIES-1636
> URL: https://issues.apache.org/jira/browse/ARIES-1636
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint, Samples, Transaction
>Reporter: Tadayoshi Sato
>Assignee: Christian Schneider
>
> Currently {{mvn clean install -DskipTests}} fails because some subprojects 
> have dependencies to old Aries snapshot versions or 3rd party libraries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1276) Add monitoring capability via MBean to Aries Transaction JDBC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029867#comment-16029867
 ] 

ASF GitHub Bot commented on ARIES-1276:
---

Github user graben closed the pull request at:

https://github.com/apache/aries/pull/57


> Add monitoring capability via MBean to Aries Transaction JDBC
> -
>
> Key: ARIES-1276
> URL: https://issues.apache.org/jira/browse/ARIES-1276
> Project: Aries
>  Issue Type: Improvement
>  Components: Transaction
>Affects Versions: transaction-jdbc-2.1.1
>Reporter: Benjamin Graf
>Assignee: Christian Schneider
>
> It would be good to have monitoring capability via JMX to get static and 
> runtime information.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1578) blueprint-cm doesn't support org.osgi.service.cm.ConfigurationPlugin

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029422#comment-16029422
 ] 

ASF GitHub Bot commented on ARIES-1578:
---

Github user paoloantinori closed the pull request at:

https://github.com/apache/aries/pull/49


> blueprint-cm doesn't support org.osgi.service.cm.ConfigurationPlugin
> 
>
> Key: ARIES-1578
> URL: https://issues.apache.org/jira/browse/ARIES-1578
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Paolo Antinori
>Assignee: Guillaume Nodet
> Fix For: blueprint-cm-1.0.9
>
>
> I have found an issue with the {{blueprint-cm}} module:
> it doesn't integrate with possible implementation of 
> {{org.osgi.service.cm.ConfigurationPlugin}} registered in the OSGi framework.
> That interface allows to intercept {{ConfigAdmin}} properties updates, 
> allowing to manipulate their content without persisting them anywhere.
> A sample usacase can be a decrypt component that decrypts values on the fly.
> The issue on {{blueprint-cm}} is with the current implementation of 
> {{CmPropertyPlaceholder}}:
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-cm/src/main/java/org/apache/aries/blueprint/compendium/cm/CmPropertyPlaceholder.java#L130-L140
> {code:java}
> public void updated(Dictionary props) {
> if ("reload".equalsIgnoreCase(updateStrategy) && !equals(properties, 
> props)) {
> LOGGER.debug("Configuration updated for pid={}", persistentId);
> // Run in a separate thread to avoid re-entrance
> new Thread() {
> public void run() {
> blueprintContainer.reload();
> }
> }.start();
> }
> {code}
>  {{updated()}} is correctly forwarded the {{props}} param, containing 
> eventual manipulation of registered {{ConfigurationPlugin}} instances, but 
> that content is discarded. The event will trigger a reload of the whole 
> blueprint context, that will fetch the configuration from {{ConfigAdmin}} 
> directly, thus bypassing the plugin behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1550) aries-transaction-jdbc: Calls to getConnection() with null user and password

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16029413#comment-16029413
 ] 

ASF GitHub Bot commented on ARIES-1550:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/47


> aries-transaction-jdbc: Calls to getConnection() with null user and password
> 
>
> Key: ARIES-1550
> URL: https://issues.apache.org/jira/browse/ARIES-1550
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Affects Versions: transaction-jdbc-2.1.1
>Reporter: Jörn Gersdorf
>
> This is a follow-up to ARIES-1171.
> aries-transaction-jdbc can wrap a "normal" DataSource with pooling 
> functionality. If that happens, it calls DataSource.getConnection(String, 
> String) with null user/password (in case {{aries.xa.username}} and/or 
> {{aries.xa.password}} are not set.
> In some {{DataSource}}-implementations this causes a NPE, e. g. DB2. Derby 
> and H2 for example also work with null parameters.
> A fix similar to ARIES-1171 is proposed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1690) Ignored rollbackOn element of Transactional annotation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021114#comment-16021114
 ] 

ASF GitHub Bot commented on ARIES-1690:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/72


> Ignored rollbackOn element of Transactional annotation
> --
>
> Key: ARIES-1690
> URL: https://issues.apache.org/jira/browse/ARIES-1690
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Reporter: Kevin Vanbockryck
>
> Here is a simple example-method, when I use this the document ends up in the 
> database.
>   @Transactional(value = Transactional.TxType.REQUIRED
> ,rollbackOn = {Exception.class}
> )
> public void store(Document document) throws Exception {
> entityManager.persist(document);
> throw new Exception();
> }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1720) java.lang.NullPointerException while processing OSGI-INF as a directory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020246#comment-16020246
 ] 

ASF GitHub Bot commented on ARIES-1720:
---

GitHub user cvgaviao opened a pull request:

https://github.com/apache/aries/pull/73

ARIES-1720 - fixed NullPointerException



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cvgaviao/aries ARIES-1720

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/73.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #73


commit 57498972ab7cb935203a18e717a435ff0a5a2fab
Author: Cristiano Gavião 
Date:   2017-05-22T21:36:31Z

ARIES-1720 - fixed NullPointerException




> java.lang.NullPointerException while processing OSGI-INF as a directory
> ---
>
> Key: ARIES-1720
> URL: https://issues.apache.org/jira/browse/ARIES-1720
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-1.0.1
>Reporter: Cristiano Gavião
>
> Depends on which tool and the way was used to created a .esa file, the 
> OSGI-INF can be seen by RawSubsystemResource as a normal directory entry and 
> then be processed by its computeResources() method.
> This method will throw an java.lang.NullPointerException:
> {quote}
> 08:38:33.903||DEBUG|File "OSGI-INF" in subsystem with location 
> "org.c8tech.runtime.esa.kernel-1493206713882" will be ignored because it is 
> not recognized as a supported 
> resource|o.a.a.s.c.i.RawSubsystemResource||o.a.a.s.c.i.RawSubsystemResource@496[Start
>  Level: Equinox Container: b3c76716-7e67-4fbd-aadb-6d5936b057d9]
> java.lang.NullPointerException: null
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeManifest(BundleResource.java:62)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.(BundleResource.java:73)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.addResource(RawSubsystemResource.java:492)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.computeResources(RawSubsystemResource.java:459)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:134)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:1)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:677)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:730)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:304)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:1)
> {quote}
> {code}
> for (IFile file : directory.listFiles()) {
> if (file.isFile()) {
> addResource(file, file.convertNested(), manifest, result);
> } else {
> -->addResource(file, file.convert(), manifest, result);
> }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1690) Ignored rollbackOn element of Transactional annotation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958634#comment-15958634
 ] 

ASF GitHub Bot commented on ARIES-1690:
---

GitHub user fwassmer opened a pull request:

https://github.com/apache/aries/pull/72

ARIES-1690: Add Transactional dontRollbackOn/rollbackOn evaluation

Implemented dontRollbackOn/rollbackOn element evaluation for Transactional 
annotation.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fwassmer/aries trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/72.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #72


commit 8298d1b493c932705fe0b0d9f61f5887f576f511
Author: Felix Wassmer 
Date:   2017-04-05T16:39:18Z

ARIES-1690: Add Transactional dontRollbackOn/rollbackOn evaluation




> Ignored rollbackOn element of Transactional annotation
> --
>
> Key: ARIES-1690
> URL: https://issues.apache.org/jira/browse/ARIES-1690
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Reporter: Kevin Vanbockryck
>
> Here is a simple example-method, when I use this the document ends up in the 
> database.
>   @Transactional(value = Transactional.TxType.REQUIRED
> ,rollbackOn = {Exception.class}
> )
> public void store(Document document) throws Exception {
> entityManager.persist(document);
> throw new Exception();
> }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1634) BlueprintContainer are leaked when destroyed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938243#comment-15938243
 ] 

ASF GitHub Bot commented on ARIES-1634:
---

Github user adetalhouet closed the pull request at:

https://github.com/apache/aries/pull/58


> BlueprintContainer are leaked when destroyed
> 
>
> Key: ARIES-1634
> URL: https://issues.apache.org/jira/browse/ARIES-1634
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.4.2
> Environment: OSx
>Reporter: Alexis de Talhouët
>Assignee: Guillaume Nodet
>  Labels: easyfix
> Fix For: blueprint-core-1.8.1
>
>
> When the BlueprintContainer is #destroy(), it is not unregistered from the 
> OSGi registry hence is retained in the memory.
> But when the BlueprintContainer is #quiesce() it is correctly unregistered 
> from the OSGi registry.
> The workaround it to first #quiesce() the container, then #destroy() it, so 
> no service is retaining it, and it can be GC.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903371#comment-15903371
 ] 

ASF GitHub Bot commented on ARIES-1590:
---

GitHub user tomdw opened a pull request:

https://github.com/apache/aries/pull/70

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems

Fixes ARIES-1590, ARIES-1591, ARIES-1588

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tomdw/aries ARIES-1590-fix-resolve-errors

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit eb3a6245511fe74edee2854b5cbeb3d12ccea14f
Author: Tom De Wolf 
Date:   2017-03-09T16:08:24Z

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems




> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will 
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to 
> package 'org.aspectj.bridge' from resources 
> com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and 
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.aspectj.bridge
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package=org.aspectj.weaver; 
> uses:=org.aspectj.weaver.patterns
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
>  |
> export: osgi.wiring.package: org.aspectj.weaver.patterns; 
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
>   org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that 
> exports the package and the other of the 2 chains points to the base 
> subsystem already installed in the runtime. In fact the bundle is part of 
> that subsystem so it should consider both as exactly the same and not 
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but 
> that commit does affect how already installed subsystems are taken into 
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0, verified it has the same problem 
> with 1.8.0
> Steps to reproduce:
> 1. 

[jira] [Commented] (ARIES-1650) Maven plugin no longer includes non-bundle artifacts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897193#comment-15897193
 ] 

ASF GitHub Bot commented on ARIES-1650:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/63


> Maven plugin no longer includes non-bundle artifacts
> 
>
> Key: ARIES-1650
> URL: https://issues.apache.org/jira/browse/ARIES-1650
> Project: Aries
>  Issue Type: Improvement
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>Assignee: David Bosschaert
> Fix For: esa-maven-plugin-1.0.0
>
>
> The ESA Maven plugin currently includes artifacts in the ESA Archive 
> regardless of whether these artifacts are OSGi bundles. Non-bundle artifacts 
> included in the ESA Archive cause issues while installing the subsystem. 
> The ESA Maven Plugin should be adapted to either log warnings or fail when 
> trying to include a non-bundle artifact in the archive. Detecting whether an 
> artifact is a bundle can be done by checking if the Bundle-SymbolicName 
> header is present in the manifest.
> Example error when trying to install an archive containing a non-bundle 
> artifact:
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.aries.subsystem.core.archive.FragmentHostCapability.initializeAttributes(FragmentHostCapability.java:38)
>   at 
> org.apache.aries.subsystem.core.archive.FragmentHostCapability.(FragmentHostCapability.java:67)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeOsgiWiringHostCapability(BundleResource.java:191)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeRequirementsOtherThanService(BundleResource.java:245)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeRequirementsAndCapabilities(BundleResource.java:216)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.(BundleResource.java:74)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.addResource(RawSubsystemResource.java:444)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.computeResources(RawSubsystemResource.java:429)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:131)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:54)
>   ... 37 more



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1490) The esa maven plugin provides more flexibility when creating the subsystem manifest

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892544#comment-15892544
 ] 

ASF GitHub Bot commented on ARIES-1490:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/69


> The esa maven plugin provides more flexibility when creating the subsystem 
> manifest
> ---
>
> Key: ARIES-1490
> URL: https://issues.apache.org/jira/browse/ARIES-1490
> Project: Aries
>  Issue Type: New Feature
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>Assignee: David Bosschaert
>
> When determining which dependencies are included in the archive, the ESA 
> maven plugin provides different possibilities as to which dependencies are 
> included (transitive dependencies vs only direct dependencies). 
> When generating the subsystem manifest, the plugin always decides to only 
> list the direct dependencies and therefore it does not include the transitive 
> dependencies as part of the subsystem content even though they are present in 
> the archive.
> Additionally, the type of the dependencies (e.g. 'pom') is not taken into 
> account. This makes it impossible to extract a sequence of related 
> dependencies into a separate pom file to improve the overall readability. The 
> readability would improve greatly if a related set of dependencies could be 
> imported from another pom.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887593#comment-15887593
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

Github user grgrzybek closed the pull request at:

https://github.com/apache/aries/pull/42


> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Jean-Baptiste Onofré
> Fix For: blueprint-core-1.6.1, blueprint-core-1.7.1
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:242)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1429)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:626)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
>   at 
> 

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887591#comment-15887591
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

Github user grgrzybek closed the pull request at:

https://github.com/apache/aries/pull/56


> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Jean-Baptiste Onofré
> Fix For: blueprint-core-1.6.1, blueprint-core-1.7.1
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:242)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1429)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:626)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
>   at 
> 

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887590#comment-15887590
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

Github user grgrzybek closed the pull request at:

https://github.com/apache/aries/pull/43


> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Jean-Baptiste Onofré
> Fix For: blueprint-core-1.6.1, blueprint-core-1.7.1
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseGlobal(XSDElementTraverser.java:242)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1429)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:626)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
>   at 
> 

[jira] [Commented] (ARIES-1682) Aries Blueprint Core 1.7.1 breaks relative JAR URI handling

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882401#comment-15882401
 ] 

ASF GitHub Bot commented on ARIES-1682:
---

Github user johnpoth closed the pull request at:

https://github.com/apache/aries/pull/65


> Aries Blueprint Core 1.7.1 breaks relative JAR URI handling
> ---
>
> Key: ARIES-1682
> URL: https://issues.apache.org/jira/browse/ARIES-1682
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.7.1
>Reporter: John Poth
>Assignee: Grzegorz Grzybek
>
> When 
> [resolving|(https://github.com/apache/aries/blob/fbc9ce10264b5c87e2a466b163824045c1817dcb/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java#L577]
>  relative xsd paths, blueprint will throw the error:
> {code}
> java.lang.RuntimeException: java.net.MalformedURLException: no protocol: 
> ../wsdl/http-conf.xsd
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl$Loader.resolveResource(NamespaceHandlerRegistryImpl.java:514)
>   at 
> com.sun.org.apache.xerces.internal.util.DOMEntityResolverWrapper.resolveEntity(DOMEntityResolverWrapper.java:117)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:1081)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.resolveDocument(XMLSchemaLoader.java:657)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.resolveSchemaSource(XSDHandler.java:2109)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1092)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:623)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
>   at 
> com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:255)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.createSchema(NamespaceHandlerRegistryImpl.java:628)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.doGetSchema(NamespaceHandlerRegistryImpl.java:458)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:443)
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:343)
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:276)
>   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:48)
>   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:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.MalformedURLException: no protocol: ../wsdl/http-conf.xsd
>   at java.net.URL.(URL.java:593)
>   at java.net.URL.(URL.java:490)
>   at java.net.URL.(URL.java:439)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl$Loader.resolveResource(NamespaceHandlerRegistryImpl.java:512)
>   ... 26 more
> {code}
> This was caused by the relative path in 
> [CXF|https://github.com/apache/cxf/blob/a8bf13d406548837a307842aca3e8cbcc267135c/rt/transports/http/src/main/resources/schemas/configuration/http-conf.xsd#L34]
>  in the xsd. 
> To reproduce simply deploy any bundle using the  
> http://cxf.apache.org/transports/http/configuration namespace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1682) Aries Blueprint Core 1.7.1 breaks relative JAR URI handling

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857736#comment-15857736
 ] 

ASF GitHub Bot commented on ARIES-1682:
---

GitHub user johnpoth opened a pull request:

https://github.com/apache/aries/pull/65

[ARIES-1682] Use the URL Api when resolving relative URIs

https://issues.apache.org/jira/browse/ARIES-1682

Checkout 
http://stackoverflow.com/questions/13046150/java-net-uri-relativize-doesnt-work-with-jar-uris
 for more information on why the URI api doesn't work on JAR URIs but URL does. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/aries ARIES-1682

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/65.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #65


commit a7e8ad0d876e1f85b67ee2fac8524744c92436df
Author: jpoth 
Date:   2017-02-08T09:42:39Z

[ARIES-1682] Use the URL Api when resolving relative URIs




> Aries Blueprint Core 1.7.1 breaks relative JAR URI handling
> ---
>
> Key: ARIES-1682
> URL: https://issues.apache.org/jira/browse/ARIES-1682
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.7.1
>Reporter: John Poth
>
> When 
> [resolving|(https://github.com/apache/aries/blob/fbc9ce10264b5c87e2a466b163824045c1817dcb/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java#L577]
>  relative xsd paths, blueprint will throw the error:
> {code}
> java.lang.RuntimeException: java.net.MalformedURLException: no protocol: 
> ../wsdl/http-conf.xsd
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl$Loader.resolveResource(NamespaceHandlerRegistryImpl.java:514)
>   at 
> com.sun.org.apache.xerces.internal.util.DOMEntityResolverWrapper.resolveEntity(DOMEntityResolverWrapper.java:117)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:1081)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.resolveDocument(XMLSchemaLoader.java:657)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.resolveSchemaSource(XSDHandler.java:2109)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.constructTrees(XSDHandler.java:1092)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:623)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:613)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:572)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:538)
>   at 
> com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:255)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.createSchema(NamespaceHandlerRegistryImpl.java:628)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.doGetSchema(NamespaceHandlerRegistryImpl.java:458)
>   at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:443)
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:343)
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:276)
>   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:48)
>   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:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 

[jira] [Commented] (ARIES-1646) Improve upward compatibility of SPI Fly to ASM Version 6.x

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839560#comment-15839560
 ] 

ASF GitHub Bot commented on ARIES-1646:
---

Github user cfiehe closed the pull request at:

https://github.com/apache/aries/pull/62


> Improve upward compatibility of SPI Fly to ASM Version 6.x
> --
>
> Key: ARIES-1646
> URL: https://issues.apache.org/jira/browse/ARIES-1646
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Reporter: Jens Offenbach
>Assignee: Guillaume Nodet
> Fix For: spifly-1.0.10
>
>
> In order to get Pax Web 6.0.1-SNAPSHOT (with Jetty) running in Apache Karaf 
> 4.1-SNAPSHOT using the provided feature, an update of the ASM package is 
> required. SPI Fly is required, because the Jetty packages rely on Java's 
> service provider mechanism by placing configuration files in 
> {{META-INF/services}}.
> Is it possible to get a new snapshot release?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836898#comment-15836898
 ] 

ASF GitHub Bot commented on ARIES-1665:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/64


> Initial contribution of implementation of OSGi RFC-193
> --
>
> Key: ARIES-1665
> URL: https://issues.apache.org/jira/browse/ARIES-1665
> Project: Aries
>  Issue Type: New Feature
>Reporter: Raymond Augé
>Assignee: David Bosschaert
>
> This contribution will begin to implement *RFC-193 CDI Integration*
> https://github.com/osgi/design/blob/master/rfcs/rfc0193/rfc-0193-CDI-Integration.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830092#comment-15830092
 ] 

ASF GitHub Bot commented on ARIES-1665:
---

GitHub user rotty3000 opened a pull request:

https://github.com/apache/aries/pull/64

ARIES-1665 Initial contribution of implementation of OSGi RFC-193

Signed-off-by: Raymond Augé 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rotty3000/aries ARIES-1665

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/64.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #64


commit 2903cd1d1af1845cefba8c7062038c3958fd7dbe
Author: Raymond Augé 
Date:   2017-01-19T15:06:59Z

ARIES-1665 Initial contribution of implementation of OSGi RFC-193

Signed-off-by: Raymond Augé 




> Initial contribution of implementation of OSGi RFC-193
> --
>
> Key: ARIES-1665
> URL: https://issues.apache.org/jira/browse/ARIES-1665
> Project: Aries
>  Issue Type: New Feature
>Reporter: Raymond Augé
>
> This contribution will begin to implement *RFC-193 CDI Integration*
> https://github.com/osgi/design/blob/master/rfcs/rfc0193/rfc-0193-CDI-Integration.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1650) Maven plugin no longer includes non-bundle artifacts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798369#comment-15798369
 ] 

ASF GitHub Bot commented on ARIES-1650:
---

GitHub user WouterBanckenACA opened a pull request:

https://github.com/apache/aries/pull/63

ARIES-1650 Optionally exclude non bundle artifacts in ESA maven plugin

Implementation for ARIES-1650
Made the new feature optional (by default disabled)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/WouterBanckenACA/aries 
ARIES-1650_ESA_plugin_no_longer_includes_non-bundle_artifacts

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/63.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #63


commit 73410a244dd371018ba120af62382af21c38997c
Author: Wouter Bancken 
Date:   2017-01-04T14:16:17Z

ARIES-1650 Optionally exclude non bundle artifacts in ESA maven plugin




> Maven plugin no longer includes non-bundle artifacts
> 
>
> Key: ARIES-1650
> URL: https://issues.apache.org/jira/browse/ARIES-1650
> Project: Aries
>  Issue Type: Improvement
>  Components: ESA Maven Plugin
>Affects Versions: esa-maven-plugin-1.0.0
>Reporter: Wouter Bancken
>
> The ESA Maven plugin currently includes artifacts in the ESA Archive 
> regardless of whether these artifacts are OSGi bundles. Non-bundle artifacts 
> included in the ESA Archive cause issues while installing the subsystem. 
> The ESA Maven Plugin should be adapted to either log warnings or fail when 
> trying to include a non-bundle artifact in the archive. Detecting whether an 
> artifact is a bundle can be done by checking if the Bundle-SymbolicName 
> header is present in the manifest.
> Example error when trying to install an archive containing a non-bundle 
> artifact:
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.aries.subsystem.core.archive.FragmentHostCapability.initializeAttributes(FragmentHostCapability.java:38)
>   at 
> org.apache.aries.subsystem.core.archive.FragmentHostCapability.(FragmentHostCapability.java:67)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeOsgiWiringHostCapability(BundleResource.java:191)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeRequirementsOtherThanService(BundleResource.java:245)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.computeRequirementsAndCapabilities(BundleResource.java:216)
>   at 
> org.apache.aries.subsystem.core.internal.BundleResource.(BundleResource.java:74)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.addResource(RawSubsystemResource.java:444)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.computeResources(RawSubsystemResource.java:429)
>   at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:131)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:54)
>   ... 37 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1646) Upgrade to ASM Version 6.0_ALPHA

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15794854#comment-15794854
 ] 

ASF GitHub Bot commented on ARIES-1646:
---

GitHub user cfiehe opened a pull request:

https://github.com/apache/aries/pull/62

[ARIES-1646] Upgrade to ASM Version 6.0_ALPHA



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cfiehe/aries ARIES-1646

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #62


commit f5c9d8524d163573b24c2a5f64fb2bc0671246df
Author: Christoph Fiehe 
Date:   2017-01-03T11:37:20Z

[ARIES-1646] Upgrade to ASM Version 6.0_ALPHA




> Upgrade to ASM Version 6.0_ALPHA 
> -
>
> Key: ARIES-1646
> URL: https://issues.apache.org/jira/browse/ARIES-1646
> Project: Aries
>  Issue Type: Bug
>  Components: SPI Fly
>Reporter: Jens Offenbach
>
> In order to get Pax Web 6.0.1-SNAPSHOT (with Jetty) running in Apache Karaf 
> 4.1-SNAPSHOT using the provided feature, an update of the ASM package is 
> required. SPI Fly is required, because the Jetty packages rely on Java's 
> service provider mechanism by placing configuration files placed in 
> {{META-INF/services}}.
> Is it possible to get a new snapshot release?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1639) Convert blueprint-maven-plugin-annotation from jar to bundle

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15792954#comment-15792954
 ] 

ASF GitHub Bot commented on ARIES-1639:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/61


> Convert blueprint-maven-plugin-annotation from jar to bundle
> 
>
> Key: ARIES-1639
> URL: https://issues.apache.org/jira/browse/ARIES-1639
> Project: Aries
>  Issue Type: Improvement
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.6.0
>
>
> Now it is just jar, without OSGi entries in Manifest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1641) OsgiServiceProvider annotation does not publish service.ranking property as integer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15792955#comment-15792955
 ] 

ASF GitHub Bot commented on ARIES-1641:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/60


> OsgiServiceProvider annotation does not publish service.ranking property as 
> integer
> ---
>
> Key: ARIES-1641
> URL: https://issues.apache.org/jira/browse/ARIES-1641
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
>Priority: Critical
> Fix For: blueprint-maven-plugin-1.6.0
>
>
> There is no such option to generate service.ranking property using 
> @OsgiServiceProvider annotation. 
> {code:groovy}
> @OsgiServiceProvider(classes = [TaskRepository])
> @Properties([
> @Property(name = "type", value = "db"),
> @Property(name = "service.ranking", value = "100"),
> ])
> {code}
> generates blueprint
> {code:xml}
>  interface="org.github.alien11689.osgi.task.api.TaskRepository">
> 
> 
> 
> 
> 
> {code}
> and service properties in Apache Karaf:
> {code}
>  osgi.service.blueprint.compname = dbRepository
>  service.bundleid = 54
>  service.id = 274
>  service.scope = bundle
>  type = db
> {code}
> The best option is to convert service.ranking property from @Property 
> annotation as ranking attribute in service element.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1639) Convert blueprint-maven-plugin-annotation from jar to bundle

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766590#comment-15766590
 ] 

ASF GitHub Bot commented on ARIES-1639:
---

GitHub user michaldabrowski opened a pull request:

https://github.com/apache/aries/pull/61

[ARIES-1639] Convert blueprint-maven-plugin-annotation from jar to bundle

https://issues.apache.org/jira/browse/ARIES-1639

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/michaldabrowski/aries ARIES-1639

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #61


commit 16a6bd949ca184273a692ecd7b80e436f6dd777a
Author: Michał Dąbrowski 
Date:   2016-12-21T09:30:49Z

[ARIES-1639] Convert blueprint-maven-plugin-annotation from jar to bundle




> Convert blueprint-maven-plugin-annotation from jar to bundle
> 
>
> Key: ARIES-1639
> URL: https://issues.apache.org/jira/browse/ARIES-1639
> Project: Aries
>  Issue Type: Improvement
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.6.0
>
>
> Now it is just jar, without OSGi entries in Manifest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1641) OsgiServiceProvider annotation does not publish service.ranking property as integer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15764093#comment-15764093
 ] 

ASF GitHub Bot commented on ARIES-1641:
---

GitHub user michaldabrowski opened a pull request:

https://github.com/apache/aries/pull/60

[ARIES-1641] Read "service.ranking" property as ranking attribute in 
service element

https://issues.apache.org/jira/browse/ARIES-1641

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/michaldabrowski/aries ARIES-1641

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/60.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #60


commit ae92f181eeb66ac5eb2db4f395f5ea3ecd27331b
Author: Michał Dąbrowski 
Date:   2016-12-20T12:15:05Z

[ARIES-1641] Read "service.ranking" property as ranking attribute in 
service element




> OsgiServiceProvider annotation does not publish service.ranking property as 
> integer
> ---
>
> Key: ARIES-1641
> URL: https://issues.apache.org/jira/browse/ARIES-1641
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
>Priority: Critical
> Fix For: blueprint-maven-plugin-1.6.0
>
>
> There is no such option to generate service.ranking property using 
> @OsgiServiceProvider annotation. 
> {code:groovy}
> @OsgiServiceProvider(classes = [TaskRepository])
> @Properties([
> @Property(name = "type", value = "db"),
> @Property(name = "service.ranking", value = "100"),
> ])
> {code}
> generates blueprint
> {code:xml}
>  interface="org.github.alien11689.osgi.task.api.TaskRepository">
> 
> 
> 
> 
> 
> {code}
> and service properties in Apache Karaf:
> {code}
>  osgi.service.blueprint.compname = dbRepository
>  service.bundleid = 54
>  service.id = 274
>  service.scope = bundle
>  type = db
> {code}
> The best option is to convert service.ranking property from @Property 
> annotation as ranking attribute in service element.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1636) mvn install fails due to old dependency versions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748228#comment-15748228
 ] 

ASF GitHub Bot commented on ARIES-1636:
---

GitHub user tadayosi opened a pull request:

https://github.com/apache/aries/pull/59

[ARIES-1636] mvn install fails due to old dependency versions

https://issues.apache.org/jira/browse/ARIES-1636

Updated Aries blueprint snapshot versions and pax-swissbox-tinybundles 
version. Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tadayosi/aries ARIES-1636

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/59.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #59


commit 40842d59f1d6e1cf36736ee36cb400e59d0252bc
Author: Tadayoshi Sato 
Date:   2016-12-14T12:23:35Z

[ARIES-1636] mvn install fails due to old dependency versions




> mvn install fails due to old dependency versions
> 
>
> Key: ARIES-1636
> URL: https://issues.apache.org/jira/browse/ARIES-1636
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint, Samples, Transaction
>Reporter: Tadayoshi Sato
>
> Currently {{mvn clean install -DskipTests}} fails because some subprojects 
> have dependencies to old Aries snapshot versions or 3rd party libraries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1634) BlueprintContainer are leaked when destroyed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671254#comment-15671254
 ] 

ASF GitHub Bot commented on ARIES-1634:
---

GitHub user adetalhouet opened a pull request:

https://github.com/apache/aries/pull/58

ARIES-1634 BlueprintContainer are leaked when destroyed

While destroying the BlueprintContainer, the associated
ServiceRegistration isn't unregistered, although it should
be to completely release the BlueprintContainer.

The #quiesce() method does that correctly, so current workaround
is to first quiesce the bundle then destroy it. But it feels like
an oversight in the #destroy() method.

Signed-off-by: Alexis de Talhouët 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/adetalhouet/aries blueprint-container-leak

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #58


commit 777079e5164ca7969ab7c0006b43c6b9e2944db2
Author: Alexis de Talhouët 
Date:   2016-11-16T18:39:29Z

ARIES-1634 BlueprintContainer are leaked when destroyed

While destroying the BlueprintContainer, the associated
ServiceRegistration isn't unregistered, although it should
be to completely release the BlueprintContainer.

The #quiesce() method does that correctly, so current workaround
is to first quiesce the bundle then destroy it. But it feels like
an oversight in the #destroy() method.

Signed-off-by: Alexis de Talhouët 




> BlueprintContainer are leaked when destroyed
> 
>
> Key: ARIES-1634
> URL: https://issues.apache.org/jira/browse/ARIES-1634
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.4.2
> Environment: OSx
>Reporter: Alexis de Talhouët
>  Labels: easyfix
>
> When the BlueprintContainer is #destroy(), it is not unregistered from the 
> OSGi registry hence is retained in the memory.
> But when the BlueprintContainer is #quiesce() it is correctly unregistered 
> from the OSGi registry.
> The workaround it to first #quiesce() the container, then #destroy() it, so 
> no service is retaining it, and it can be GC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1276) Add monitoring capability via MBean to Aries Transaction JDBC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667648#comment-15667648
 ] 

ASF GitHub Bot commented on ARIES-1276:
---

GitHub user graben opened a pull request:

https://github.com/apache/aries/pull/57

ARIES-1276: Add monitoring capability via MBean to Aries Transaction …



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/graben/aries ARIES-1276

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #57


commit fbaf8988efbc6a0877160c4dd44cebe6d92d0d16
Author: Benjamin Graf 
Date:   2016-11-15T16:55:15Z

ARIES-1276: Add monitoring capability via MBean to Aries Transaction JDBC




> Add monitoring capability via MBean to Aries Transaction JDBC
> -
>
> Key: ARIES-1276
> URL: https://issues.apache.org/jira/browse/ARIES-1276
> Project: Aries
>  Issue Type: Improvement
>  Components: Transaction
>Affects Versions: transaction-jdbc-2.1.1
>Reporter: Benjamin Graf
>
> It would be good to have monitoring capability via JMX to get static and 
> runtime information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546333#comment-15546333
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

GitHub user grgrzybek opened a pull request:

https://github.com/apache/aries/pull/56

[ARIES-1503] Check global handlers when mapping URI to NamespaceHandler



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/grgrzybek/aries ARIES-1503-KARAF-4720

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/56.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #56


commit 246bea3dc3eb2725e16e4629f8bcc0b647222f16
Author: Grzegorz Grzybek 
Date:   2016-10-04T19:05:41Z

[ARIES-1503] Check global handlers when mapping URI to NamespaceHandler




> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Jean-Baptiste Onofré
> Fix For: blueprint-core-1.6.1
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> 

[jira] [Commented] (ARIES-1606) Extract SPI from blueptin maven plugin to external project

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512307#comment-15512307
 ] 

ASF GitHub Bot commented on ARIES-1606:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/54


> Extract SPI from blueptin maven plugin to external project
> --
>
> Key: ARIES-1606
> URL: https://issues.apache.org/jira/browse/ARIES-1606
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1606) Extract SPI from blueptin maven plugin to external project

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15480440#comment-15480440
 ] 

ASF GitHub Bot commented on ARIES-1606:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/54

[ARIES-1606] Extract SPI from blueptin maven plugin to external project



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-1606

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit ec64ea6f6aaea504ad088d2cd9225f64199fbe01
Author: Dominik Przybysz 
Date:   2016-09-10T20:48:45Z

[ARIES-1606] Extract SPI from blueptin maven plugin to external project




> Extract SPI from blueptin maven plugin to external project
> --
>
> Key: ARIES-1606
> URL: https://issues.apache.org/jira/browse/ARIES-1606
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1601) Support for nested property placeholders

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458016#comment-15458016
 ] 

ASF GitHub Bot commented on ARIES-1601:
---

Github user lburgazzoli closed the pull request at:

https://github.com/apache/aries/pull/53


> Support for nested property placeholders
> 
>
> Key: ARIES-1601
> URL: https://issues.apache.org/jira/browse/ARIES-1601
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Luca Burgazzoli
>Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.6.3
>
>
> As today property placeholders are resolved sequentially but it would be nice 
> to have the possibility to resolve nested placeholders like:
> {code}
> ${jre-${java.specification.version}}
> {code}
> The problem in blueprint seems to be located in 
> [AbstractPropertyPlaceholder|https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/ext/AbstractPropertyPlaceholder.java#L429-L455]
> I've been using StrSubstitutor from Commons-Lang and could be ported to 
> blueprint-ext.
> See:
> - https://issues.apache.org/jira/browse/LANG-482 
> - 
> https://commons.apache.org/proper/commons-lang/javadocs/api-3.4/org/apache/commons/lang3/text/StrSubstitutor.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1601) Support for nested property placeholders

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435239#comment-15435239
 ] 

ASF GitHub Bot commented on ARIES-1601:
---

GitHub user lburgazzoli opened a pull request:

https://github.com/apache/aries/pull/53

ARIES-1601: Support for nested property placeholders



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lburgazzoli/apache-aries ARIES-1601

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/53.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #53


commit 29da5bc0872ef6406f734f7d265d120aa3d83568
Author: lburgazzoli 
Date:   2016-08-24T16:36:45Z

ARIES-1601: Support for nested property placeholders




> Support for nested property placeholders
> 
>
> Key: ARIES-1601
> URL: https://issues.apache.org/jira/browse/ARIES-1601
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Luca Burgazzoli
>
> As today property placeholders are resolved sequentially but it would be nice 
> to have the possibility to resolve nested placeholders like:
> {code}
> ${jre-${java.specification.version}}
> {code}
> The problem in blueprint seems to be located in 
> [AbstractPropertyPlaceholder|https://github.com/apache/aries/blob/trunk/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/ext/AbstractPropertyPlaceholder.java#L429-L455]
> I've been using StrSubstitutor from Commons-Lang and could be ported to 
> blueprint-ext.
> See:
> - https://issues.apache.org/jira/browse/LANG-482 
> - 
> https://commons.apache.org/proper/commons-lang/javadocs/api-3.4/org/apache/commons/lang3/text/StrSubstitutor.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1565) Performance Improvement: unpack subsystem artifacts to tmp folder to avoid directly reading from zip archive

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393347#comment-15393347
 ] 

ASF GitHub Bot commented on ARIES-1565:
---

GitHub user WouterBanckenACA opened a pull request:

https://github.com/apache/aries/pull/50

ARIES-1565 Add unpacking filesystem with unzips artifacts for perform…

…ance improvements

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/WouterBanckenACA/aries ARIES-1565

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit 9bc697621f6cfd62675c51686a2ed41be9154b4a
Author: Wouter Bancken 
Date:   2016-07-25T14:36:05Z

ARIES-1565 Add unpacking filesystem with unzips artifacts for performance 
improvements




> Performance Improvement: unpack subsystem artifacts to tmp folder to avoid 
> directly reading from zip archive
> 
>
> Key: ARIES-1565
> URL: https://issues.apache.org/jira/browse/ARIES-1565
> Project: Aries
>  Issue Type: Improvement
>  Components: Subsystem, Util
>Affects Versions: subsystem-2.0.8, util-1.1.2
>Reporter: Wouter Bancken
> Attachments: 1565.patch, Call_Tree_2_0_8.html, 
> Call_Tree_John_Ross.html, Call_Tree_Wouter_Bancken.html, 
> aries1565-profile.png, test-service-subsystem-4.0.2-SNAPSHOT.esa
>
>
> h4. Description
> Aries copies ESA archives to a temporary zip file during the installation 
> phase. Afterwards, bundles are read directly from this temporary zip which 
> has a large impact on the startup performance of Aries applications. By 
> unpacking the esa artifact into the temporary folder it is unpacked only 
> once. Subsequent reads for the bundles (jars) can be read directly from the 
> folder. 
> h4. Pull request
> https://github.com/apache/aries/compare/subsystem-2.0.x...WouterBanckenACA:io_performance_optimalisation?expand=1
> h4. Mailinglist
> http://mail-archives.apache.org/mod_mbox/aries-user/201606.mbox/%3CCAL5nZgTq5FxDvURJbzcEZ9YHx6vTs3HAOuFYDYA3ec9OZbmwjA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1570) Prepare extension machanism in blueprint maven plugin

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357380#comment-15357380
 ] 

ASF GitHub Bot commented on ARIES-1570:
---

Github user alien11689 closed the pull request at:

https://github.com/apache/aries/pull/48


> Prepare extension machanism in blueprint maven plugin
> -
>
> Key: ARIES-1570
> URL: https://issues.apache.org/jira/browse/ARIES-1570
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.4.0
>Reporter: Dominik Przybysz
>Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.5.0
>
>
> Goals:
> - create SPI for processing external annotations on classes, methods, 
> constructors, fields 
> - move Spring annotation handling to separate package and let it implement SPI
> - move bleurpint plugin core (handling javax.** annotations and maven 
> specific parts) to separate package - impl
> Packages structures should look like:
> - core
> - spi
> - spring
> core package will use only spi package and will not use/know classes from 
> spring package.
> spring package will not use core clases, it will only implement interfaces 
> from spi package.
> All currently green tests should pass after these changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1578) blueprint-cm doesn't support org.osgi.service.cm.ConfigurationPlugin

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348473#comment-15348473
 ] 

ASF GitHub Bot commented on ARIES-1578:
---

GitHub user paoloantinori opened a pull request:

https://github.com/apache/aries/pull/49

ARIES-1578 - blueprint-cm added support for org.osgi.service.cm.Conf…

…igurationPlugin

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paoloantinori/aries fix_enc

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/49.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #49


commit 776ae09de8685dd2df6caa51cf74d85d40e3d44f
Author: Paolo Antinori 
Date:   2016-06-23T15:46:05Z

ENTESB-5392 - blueprint-cm added support for 
org.osgi.service.cm.ConfigurationPlugin




> blueprint-cm doesn't support org.osgi.service.cm.ConfigurationPlugin
> 
>
> Key: ARIES-1578
> URL: https://issues.apache.org/jira/browse/ARIES-1578
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Paolo Antinori
>
> I have found an issue with the {{blueprint-cm}} module:
> it doesn't integrate with possible implementation of 
> {{org.osgi.service.cm.ConfigurationPlugin}} registered in the OSGi framework.
> That interface allows to intercept {{ConfigAdmin}} properties updates, 
> allowing to manipulate their content without persisting them anywhere.
> A sample usacase can be a decrypt component that decrypts values on the fly.
> The issue on {{blueprint-cm}} is with the current implementation of 
> {{CmPropertyPlaceholder}}:
> https://github.com/apache/aries/blob/trunk/blueprint/blueprint-cm/src/main/java/org/apache/aries/blueprint/compendium/cm/CmPropertyPlaceholder.java#L130-L140
> {code:java}
> public void updated(Dictionary props) {
> if ("reload".equalsIgnoreCase(updateStrategy) && !equals(properties, 
> props)) {
> LOGGER.debug("Configuration updated for pid={}", persistentId);
> // Run in a separate thread to avoid re-entrance
> new Thread() {
> public void run() {
> blueprintContainer.reload();
> }
> }.start();
> }
> {code}
>  {{updated()}} is correctly forwarded the {{props}} param, containing 
> eventual manipulation of registered {{ConfigurationPlugin}} instances, but 
> that content is discarded. The event will trigger a reload of the whole 
> blueprint context, that will fetch the configuration from {{ConfigAdmin}} 
> directly, thus bypassing the plugin behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1560) Upgrade Aries JDBC Transaction to 2.1.2

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346159#comment-15346159
 ] 

ASF GitHub Bot commented on ARIES-1560:
---

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/193


> Upgrade Aries JDBC Transaction to 2.1.2
> ---
>
> Key: ARIES-1560
> URL: https://issues.apache.org/jira/browse/ARIES-1560
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Reporter: John Poth
>
> Fixes https://issues.apache.org/jira/browse/ARIES-1542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1560) Upgrade Aries JDBC Transaction to 2.1.2

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313893#comment-15313893
 ] 

ASF GitHub Bot commented on ARIES-1560:
---

GitHub user johnpoth opened a pull request:

https://github.com/apache/karaf/pull/193

Upgrade Aries JDBC Transaction to 2.1.2

https://issues.apache.org/jira/browse/ARIES-1560

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/karaf ARIES-1560

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/193.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #193


commit 694fc00c0b4b9f01e25241637a95b01a40643827
Author: jpoth 
Date:   2016-06-03T09:21:20Z

Upgrade Aries JDBC Transaction to 2.1.2




> Upgrade Aries JDBC Transaction to 2.1.2
> ---
>
> Key: ARIES-1560
> URL: https://issues.apache.org/jira/browse/ARIES-1560
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Reporter: John Poth
>
> Fixes https://issues.apache.org/jira/browse/ARIES-1542



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1550) aries-transaction-jdbc: Calls to getConnection() with null user and password

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289723#comment-15289723
 ] 

ASF GitHub Bot commented on ARIES-1550:
---

GitHub user j0xaf opened a pull request:

https://github.com/apache/aries/pull/47

[ARIES-1550] getConnection with null user

Call underlying datasource´s getConnection() if no
aries.xa.username is set. Relates to ARIES-1171.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/j0xaf/aries 
ARIES-1550-transaction-jdbc-getConnection-with-null-user-password

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/47.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #47


commit 89e54d6a792d31ec9d5bc0de972b458a2129b5f9
Author: Joern Gersdorf 
Date:   2016-05-11T20:45:13Z

[ARIES-1550] getConnection with null user

Call underlying datasource´s getConnection() if no
aries.xa.username is set. Relates to ARIES-1171.




> aries-transaction-jdbc: Calls to getConnection() with null user and password
> 
>
> Key: ARIES-1550
> URL: https://issues.apache.org/jira/browse/ARIES-1550
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Affects Versions: transaction-jdbc-2.1.1
>Reporter: Jörn Gersdorf
>
> This is a follow-up to ARIES-1171.
> aries-transaction-jdbc can wrap a "normal" DataSource with pooling 
> functionality. If that happens, it calls DataSource.getConnection(String, 
> String) with null user/password (in case {{aries.xa.username}} and/or 
> {{aries.xa.password}} are not set.
> In some {{DataSource}}-implementations this causes a NPE, e. g. DB2. Derby 
> and H2 for example also work with null parameters.
> A fix similar to ARIES-1171 is proposed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1542) Aries transaction manager fails with background connection validation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266573#comment-15266573
 ] 

ASF GitHub Bot commented on ARIES-1542:
---

GitHub user johnpoth opened a pull request:

https://github.com/apache/aries/pull/46

[ARIES-1542] Fix reflection problem in org.apache.aries.transaction.j…

…dbc.internal.ValidatingGenericConnectionManager

https://issues.apache.org/jira/browse/ARIES-1542 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/aries ARIES-1542

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit 50bb9829b154e4d60c21a122282379aa07c2e7f4
Author: jpoth 
Date:   2016-05-02T13:11:01Z

[ARIES-1542] Fix reflection problem in 
org.apache.aries.transaction.jdbc.internal.ValidatingGenericConnectionManager




> Aries transaction manager fails with background connection validation
> -
>
> Key: ARIES-1542
> URL: https://issues.apache.org/jira/browse/ARIES-1542
> Project: Aries
>  Issue Type: Bug
>  Components: Transaction
>Reporter: John Poth
>
> This seems to be a defect in 
> org.apache.aries.transaction.jdbc.internal.ValidatingGenericConnectionManager,
>  reflection should be called on the "current" field, not stack. This can 
> cause the following exception:
> {quote}
> Caused by: java.lang.RuntimeException: java.lang.NoSuchFieldException: pool
>   at 
> org.apache.aries.transaction.jdbc.internal.Reflections.get(Reflections.java:56)
>   at 
> org.apache.aries.transaction.jdbc.internal.ValidatingGenericConnectionManager.(ValidatingGenericConnectionManager.java:89)
>   at 
> org.apache.aries.transaction.jdbc.internal.ConnectionManagerFactory.init(ConnectionManagerFactory.java:152)
>   at 
> org.apache.aries.transaction.jdbc.RecoverableDataSource.start(RecoverableDataSource.java:235)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1531) Add arguments to produced bean based on factory method parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266243#comment-15266243
 ] 

ASF GitHub Bot commented on ARIES-1531:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/44


> Add arguments to produced bean based on factory method parameters
> -
>
> Key: ARIES-1531
> URL: https://issues.apache.org/jira/browse/ARIES-1531
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1539) Allow for setting name of generated file

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266236#comment-15266236
 ] 

ASF GitHub Bot commented on ARIES-1539:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/45


> Allow for setting name of generated file
> 
>
> Key: ARIES-1539
> URL: https://issues.apache.org/jira/browse/ARIES-1539
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Christian Schneider
>Priority: Minor
> Fix For: blueprint-maven-plugin-1.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1539) Allow for setting name of generated file

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258425#comment-15258425
 ] 

ASF GitHub Bot commented on ARIES-1539:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/45

[ARIES-1539] Allow for setting name of generated file



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-1539

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/45.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #45


commit 9f8c4529453c43ed2d63b6789cd0e30f1e7b3574
Author: Dominik Przybysz 
Date:   2016-04-26T16:40:07Z

[ARIES-1539] Allow for setting name of generated file




> Allow for setting name of generated file
> 
>
> Key: ARIES-1539
> URL: https://issues.apache.org/jira/browse/ARIES-1539
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1531) Add arguments to produced bean based on factory method parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239515#comment-15239515
 ] 

ASF GitHub Bot commented on ARIES-1531:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/44

[ARIES-1531] Add arguments to produced bean based on factory method p…

…arameters

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-1531

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/44.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #44


commit f3f581260b36a6970c8260c18b4949cf46cd0b32
Author: Dominik Przybysz 
Date:   2016-04-13T16:12:00Z

[ARIES-1531] Add arguments to produced bean based on factory method 
parameters




> Add arguments to produced bean based on factory method parameters
> -
>
> Key: ARIES-1531
> URL: https://issues.apache.org/jira/browse/ARIES-1531
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234253#comment-15234253
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

GitHub user grgrzybek opened a pull request:

https://github.com/apache/aries/pull/43

[ARIES-1503] CmNamespaceHandler instanceof NamespaceHandler2 didn't work



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/grgrzybek/aries namespace-handler-fixes-cm

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #43


commit 10d74ca0da3877fd9d1b3705d8864eadca766ab4
Author: Grzegorz Grzybek 
Date:   2016-04-10T18:48:03Z

[ARIES-1503] CmNamespaceHandler instanceof NamespaceHandler2 didn't work




> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Jean-Baptiste Onofré
> Fix For: blueprint-core-1.6.1, blueprint-cm-1.0.9
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> 

[jira] [Commented] (ARIES-1521) Inject constructor parameters without @Inject when class has only one constructor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229985#comment-15229985
 ] 

ASF GitHub Bot commented on ARIES-1521:
---

Github user alien11689 closed the pull request at:

https://github.com/apache/aries/pull/41


> Inject constructor parameters without @Inject when class has only one 
> constructor
> -
>
> Key: ARIES-1521
> URL: https://issues.apache.org/jira/browse/ARIES-1521
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1503) Timing issue when cm blueprint references ext namespaces

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229813#comment-15229813
 ] 

ASF GitHub Bot commented on ARIES-1503:
---

GitHub user grgrzybek opened a pull request:

https://github.com/apache/aries/pull/42

[ARIES-1503] Use NamespaceHandler to resolve namespace URI only when …

…it's supported

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/grgrzybek/aries namespace-handler-fixes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 69ac34a6c6c3d77d57d6c04cce024a1c7789048e
Author: Grzegorz Grzybek 
Date:   2016-04-06T13:04:52Z

[ARIES-1503] Use NamespaceHandler to resolve namespace URI only when it's 
supported




> Timing issue when cm blueprint references ext namespaces
> 
>
> Key: ARIES-1503
> URL: https://issues.apache.org/jira/browse/ARIES-1503
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.5.0, blueprint-parser-1.4.0, 
> blueprint-cm-1.0.7
>Reporter: Grzegorz Grzybek
>Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.6.0, blueprint-cm-1.0.8
>
>
> Since version 1.0.6, blueprint-cm's XSDs started to import ext namespaces, to 
> reflect Java hierarchy of 
> {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} and 
> {{org.apache.aries.blueprint.ext.PropertyPlaceholder}}, however, sometimes we 
> fail with:
> {noformat}
> org.xml.sax.SAXParseException; systemId: 
> jar:file:/home/ggrzybek/.m2/repository/org/apache/aries/blueprint/org.apache.aries.blueprint.cm/1.0.7/org.apache.aries.blueprint.cm-1.0.7.jar!/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.0.0.xsd;
>  lineNumber: 80; columnNumber: 79; src-resolve: Cannot resolve the name 
> 'ext100:ignore-missing-locations' to a(n) 'attribute declaration' component.
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>   at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4158)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4141)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1674)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:90)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:615)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseGlobal(XSDAttributeGroupTraverser.java:145)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1897)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeGroupTraverser.traverseLocal(XSDAttributeGroupTraverser.java:80)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:643)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexContent(XSDComplexTypeTraverser.java:836)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:315)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseGlobalDecl(XSDHandler.java:1884)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getGlobalDecl(XSDHandler.java:1772)
>   at 
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(XSDElementTraverser.java:405)
>   at 
> 

[jira] [Commented] (ARIES-1521) Inject constructor parameters without @Inject when class has only one constructor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228585#comment-15228585
 ] 

ASF GitHub Bot commented on ARIES-1521:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/41

[ARIES-1521] Inject constructor parameters without @Inject when class…

… has only one constructor

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-1521

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/41.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #41


commit 1116e99aaf2a97833d0d90281b8830f3eea64fa8
Author: Dominik Przybysz 
Date:   2016-04-06T16:32:30Z

[ARIES-1521] Inject constructor parameters without @Inject when class has 
only one constructor




> Inject constructor parameters without @Inject when class has only one 
> constructor
> -
>
> Key: ARIES-1521
> URL: https://issues.apache.org/jira/browse/ARIES-1521
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Dominik Przybysz
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1508) Name produced beans

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206359#comment-15206359
 ] 

ASF GitHub Bot commented on ARIES-1508:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/39


> Name produced beans
> ---
>
> Key: ARIES-1508
> URL: https://issues.apache.org/jira/browse/ARIES-1508
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.4.0
>
>
> Let beans created with annotation @Produces could be named with @Named



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1508) Name produced beans

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204035#comment-15204035
 ] 

ASF GitHub Bot commented on ARIES-1508:
---

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/39

[ARIES-1508] Let beans created with annotation @Produces could be named 
with @Named

https://issues.apache.org/jira/browse/ARIES-1508

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries nameProducedBeans

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/39.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #39


commit 95b96dc4dc5d70d9604e09d890e5d6823d5add8b
Author: Dominik Przybysz 
Date:   2016-03-21T11:02:30Z

[ARIES-1508] Let beans created with annotation @Produces could be named 
with @Named




> Name produced beans
> ---
>
> Key: ARIES-1508
> URL: https://issues.apache.org/jira/browse/ARIES-1508
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Dominik Przybysz
>
> Let beans created with annotation @Produces could be named with @Named



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-458) ${version} is deprecated in maven 3 - use ${project.version}

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15181867#comment-15181867
 ] 

ASF GitHub Bot commented on ARIES-458:
--

GitHub user alien11689 opened a pull request:

https://github.com/apache/aries/pull/38

[ARIES-458] Replace ${version} with ${project.version}



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alien11689/aries ARIES-458

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/38.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #38


commit 42cbeed1a02ac4135d9638dcd9aacd5addc5c08b
Author: Dominik Adam Przybysz 
Date:   2016-03-05T22:10:36Z

[ARIES-458] Replace ${version} with ${project.version}




> ${version} is deprecated in maven 3 - use ${project.version}
> 
>
> Key: ARIES-458
> URL: https://issues.apache.org/jira/browse/ARIES-458
> Project: Aries
>  Issue Type: Improvement
>Affects Versions: 0.3
>Reporter: Jeremy Hughes
>Priority: Trivial
>
> There are a lot of deprecation warnings when running with maven 3



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1475) blueprint-maven-plugin: support methods annotated with @Transactional

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093920#comment-15093920
 ] 

ASF GitHub Bot commented on ARIES-1475:
---

Github user samwright closed the pull request at:

https://github.com/apache/aries/pull/34


> blueprint-maven-plugin: support methods annotated with @Transactional
> -
>
> Key: ARIES-1475
> URL: https://issues.apache.org/jira/browse/ARIES-1475
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.3.0
>Reporter: Sam Wright
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.4.0
>
>
> Currently @Transactional is only supported when annotating a class. Blueprint 
> supports specifying the transactional type for all methods and/or for 
> individual methods by adding more  elements.
> Patch incoming...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1476) blueprint-maven-plugin: support 0 or multiple OsgiServiceProvider#classes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093921#comment-15093921
 ] 

ASF GitHub Bot commented on ARIES-1476:
---

Github user samwright closed the pull request at:

https://github.com/apache/aries/pull/35


> blueprint-maven-plugin: support 0 or multiple OsgiServiceProvider#classes
> -
>
> Key: ARIES-1476
> URL: https://issues.apache.org/jira/browse/ARIES-1476
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.3.0
>Reporter: Sam Wright
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.4.0
>
>
> Currently blueprint-maven-plugin supports annotating beans with 
> @OsgiServiceProvider(classes = ...) to expose the bean as an OSGi service, 
> but only when given exactly 1 interface class to expose it under.
> This improvement adds support for passing 0 classes, which creates:
> {code}
> 
> {code}
> and also adds support for passing multiple classes, which creates:
> {code}
> 
>     
>     com.example.ServiceA
>     com.example.ServiceB
>     
> 
> {code}
> Patch incoming...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1474) blueprint-maven-plugin: Inherited init/destroy methods are ignored

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093919#comment-15093919
 ] 

ASF GitHub Bot commented on ARIES-1474:
---

Github user samwright closed the pull request at:

https://github.com/apache/aries/pull/33


> blueprint-maven-plugin: Inherited init/destroy methods are ignored
> --
>
> Key: ARIES-1474
> URL: https://issues.apache.org/jira/browse/ARIES-1474
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-maven-plugin-1.3.0
>Reporter: Sam Wright
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.4.0
>
>
> Current behaviour:
> {code}
> public class A {
> @PostConstruct
> public void init() {}
> @PreDestroy
> public void destroy() {}
> }
> public class B extends A {}
> public class C extends B {
> @Override
> public void init() {}
> @PostConstruct
> public void secondInit()
> }
> {code}
> Three problems:
> * The A.destroy() method is ignored
> * The C.init() method overrides A.init() without the @PostConstruct 
> annotation, but is still taken to be the init method. This means the subclass 
> can't disable a superclass' init method.
> * The C.secondInit() method is silently ignored because another init method 
> is found first. 
> Patch incoming...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1148) Deploying a subsystem file with directory entries causes a NPE

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094217#comment-15094217
 ] 

ASF GitHub Bot commented on ARIES-1148:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/16


> Deploying a subsystem file with directory entries causes a NPE
> --
>
> Key: ARIES-1148
> URL: https://issues.apache.org/jira/browse/ARIES-1148
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-2.0.6, subsystem-2.0.8
>Reporter: David Bosschaert
> Attachments: npe.esa
>
>
> The attached npe.esa file contains the following entries:
> {code}$ jar tvf npe.esa
>  0 Wed Jan 15 15:07:04 GMT 2014 OSGI-INF/
>199 Wed Jan 15 15:07:04 GMT 2014 OSGI-INF/DEPLOYMENT.MF
>175 Wed Jan 15 15:01:30 GMT 2014 OSGI-INF/SUBSYSTEM.MF{code}
> Deploying it will cause an NPE.
> Creating the zip file without directory entries solves the problem, so that's 
> a workaround, but I think subsystems should be forgiving about this and 
> simply ignore directory entries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1047) Update Aries for JPA 2.1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061876#comment-15061876
 ] 

ASF GitHub Bot commented on ARIES-1047:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/3


> Update Aries for JPA 2.1
> 
>
> Key: ARIES-1047
> URL: https://issues.apache.org/jira/browse/ARIES-1047
> Project: Aries
>  Issue Type: New Feature
>Reporter: Brett E. Meyer
>Assignee: Jean-Baptiste Onofré
>
> While implementing OSGi support in Hibernate, I forked Aries JPA and updated 
> it for JPA 2.1 -- we needed it as a test bed.  The spec is not yet out 
> (currently in a final draft and will hopefully soon be voted on).  The fork 
> uses Hibernate's current implementation of the 2.1 API.
> I'm creating a pull request with the work, just in case you want it as a 
> starting point for whenever you begin to support 2.1.  It's pretty simplistic 
> -- updated the POMs and manifests, added un-implemented methods, etc.  There 
> are several places where features, new to 2.1, may need to be implemented, 
> however some of them may just need to throw Unsupported.
> Pull request: https://github.com/apache/aries/pull/3
> Feel free to take it or leave it!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1481) blueprint-maven-plugin: fix detection of inherited @OsgiService/@PersistenceContext/Unit-annotated fields

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056296#comment-15056296
 ] 

ASF GitHub Bot commented on ARIES-1481:
---

GitHub user samwright opened a pull request:

https://github.com/apache/aries/pull/36

[Aries-1481] Fix inheritance of @OsgiService and @PersistenceContext/Unit 
fields

https://issues.apache.org/jira/browse/ARIES-1481

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/samwright/aries ARIES-1481

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/36.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #36


commit a905bd2917d7b5272418449c53b1d86879c226cd
Author: Samuel Wright 
Date:   2015-12-12T16:38:35Z

[ARIES-1474] Fix init/destroy method inheritence.

commit 154b046302d7dcd6a64d82da41aa8f960c94da8e
Author: Sam Wright 
Date:   2015-12-12T11:44:41Z

[ARIES-1475] Implement per-method transaction support.

commit 74d0b144c742b4f9b0ee2f8227a65eb9aa4b1a73
Author: Samuel Wright 
Date:   2015-12-12T18:29:25Z

[ARIES-1476] Support 0 or multiple OsgiServiceProvider#classes.

- 0 classes adds auto-export="interfaces" to the service element
- multiple classes adds the interfaces (e.g. A and B) to the interfaces
  element:


A
B



commit 237fa704928b63d379cf4066b678ab213af37f06
Author: Sam Wright 
Date:   2015-12-14T16:48:45Z

[ARIES-1481] Fix inheritance of @OsgiService and @PersistenceContext/Unit 
fields

@Inject fields are inherited from parent classes, but @OsgiService and
@PersistenceContext/Unit annotations on fields declared in parent classes
are ignored. This commit extracts the field-getting algorithm used for 
finding
@Inject fields to a utility method which is used for finding fields for the 
other
annotations.




> blueprint-maven-plugin: fix detection of inherited 
> @OsgiService/@PersistenceContext/Unit-annotated fields
> -
>
> Key: ARIES-1481
> URL: https://issues.apache.org/jira/browse/ARIES-1481
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Sam Wright
>
> Fields inherited from parent classes annotated with @Inject are properly 
> detected by blueprint-maven-plugin, but the presence of @OsgiService,
> @PersistenceContext, and @PersistenceUnit annotations on fields declared in 
> parent classes is ignored.
> This is because @Inject-annotated fields are found in the 
> Bean.resolve(Matcher) method which recursively searches all parent classes 
> for declared fields, whereas @PersistenceContext/Unit-annotated fields are 
> discovered in Bean.getPersistenceFields() by simply using the fields declared 
> in the bean class. Similarly, @OsgiService-annotated fields are discovered in 
> Context.addServiceRefs(Class) by looking through the fields declared in the 
> bean class.
> This commit extracts the field-getting algorithm used for finding
> @Inject fields to a utility method which is used for finding fields for the 
> other
> annotations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1476) blueprint-maven-plugin: support 0 or multiple OsgiServiceProvider#classes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054552#comment-15054552
 ] 

ASF GitHub Bot commented on ARIES-1476:
---

GitHub user samwright opened a pull request:

https://github.com/apache/aries/pull/35

[Aries 1476] support 0 or multiple OsgiServiceProvider#classes

https://issues.apache.org/jira/browse/ARIES-1476

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/samwright/aries ARIES-1476

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/35.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #35


commit a905bd2917d7b5272418449c53b1d86879c226cd
Author: Samuel Wright 
Date:   2015-12-12T16:38:35Z

[ARIES-1474] Fix init/destroy method inheritence.

commit 154b046302d7dcd6a64d82da41aa8f960c94da8e
Author: Sam Wright 
Date:   2015-12-12T11:44:41Z

[ARIES-1475] Implement per-method transaction support.

commit 74d0b144c742b4f9b0ee2f8227a65eb9aa4b1a73
Author: Samuel Wright 
Date:   2015-12-12T18:29:25Z

[ARIES-1476] Support 0 or multiple OsgiServiceProvider#classes.

- 0 classes adds auto-export="interfaces" to the service element
- multiple classes adds the interfaces (e.g. A and B) to the interfaces
  element:


A
B






> blueprint-maven-plugin: support 0 or multiple OsgiServiceProvider#classes
> -
>
> Key: ARIES-1476
> URL: https://issues.apache.org/jira/browse/ARIES-1476
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Sam Wright
>
> Currently blueprint-maven-plugin supports annotating beans with 
> @OsgiServiceProvider(classes = ...) to expose the bean as an OSGi service, 
> but only when given exactly 1 interface class to expose it under.
> This improvement adds support for passing 0 classes, which creates:
> {code}
> 
> {code}
> and also adds support for passing multiple classes, which creates:
> {code}
> 
>     
>     com.example.ServiceA
>     com.example.ServiceB
>     
> 
> {code}
> Patch incoming...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1474) blueprint-maven-plugin: Inherited init/destroy methods are ignored

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054539#comment-15054539
 ] 

ASF GitHub Bot commented on ARIES-1474:
---

GitHub user samwright opened a pull request:

https://github.com/apache/aries/pull/33

[ARIES-1474] Fix init/destroy method inheritence.

https://issues.apache.org/jira/browse/ARIES-1474

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/samwright/aries ARIES-1474

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/33.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #33


commit a905bd2917d7b5272418449c53b1d86879c226cd
Author: Samuel Wright 
Date:   2015-12-12T16:38:35Z

[ARIES-1474] Fix init/destroy method inheritence.




> blueprint-maven-plugin: Inherited init/destroy methods are ignored
> --
>
> Key: ARIES-1474
> URL: https://issues.apache.org/jira/browse/ARIES-1474
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Reporter: Sam Wright
>
> Current behaviour:
> {code}
> public class A {
> @PostConstruct
> public void init() {}
> @PreDestroy
> public void destroy() {}
> }
> public class B extends A {}
> public class C extends B {
> @Override
> public void init() {}
> @PostConstruct
> public void secondInit()
> }
> {code}
> Three problems:
> * The A.destroy() method is ignored
> * The C.init() method overrides A.init() without the @PostConstruct 
> annotation, but is still taken to be the init method. This means the subclass 
> can't disable a superclass' init method.
> * The C.secondInit() method is silently ignored because another init method 
> is found first. 
> Patch incoming...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1023) Construct a persistence unit with parameters

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052768#comment-15052768
 ] 

ASF GitHub Bot commented on ARIES-1023:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/19


> Construct a persistence unit with parameters
> 
>
> Key: ARIES-1023
> URL: https://issues.apache.org/jira/browse/ARIES-1023
> Project: Aries
>  Issue Type: Bug
>  Components: JPA
>Affects Versions: jpa-blueprint-aries-1.0.4
>Reporter: Luca Burgazzoli
>Assignee: Christian Schneider
> Fix For: jpa-2.0.0
>
>
> According to http://aries.apache.org/modules/jpaproject.html it should be 
> possible to construct a persistence unit with properties supplied in the OSGi 
> blueprint.xml instead of hard-coding them in the persistence.xml but it does 
> not seem to work:
> The bean definition:
> class="lb.examples.karaf.jpa.openjpa.data.ContainerManagedDataService">
> 
> 
> 
> 
> 
> 
> 
> And the error:
> 2013-03-07 08:30:57,884 | ERROR | BlueprintContainerImpl   | 
> blueprint.container.BlueprintContainerImpl | org.apache.aries.blueprint.core 
> | Unable to start blueprint container for bundle jpa-openjpa
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
> validate xml
> at 
> org.apache.aries.blueprint.parser.Parser.validate(Parser.java:288)[7:org.apache.aries.blueprint.core:1.0.1]
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:304)[7:org.apache.aries.blueprint.core:1.0.1]
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:252)[7:org.apache.aries.blueprint.core:1.0.1]
> at 
> org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[7:org.apache.aries.blueprint.core:1.0.1]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_17]
> at 
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_17]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_17]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_17]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_17]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_17]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722)[:1.7.0_17]
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid 
> content was found starting with element 'map'. One of 
> '{"http://aries.apache.org/xmlns/jpa/v1.1.0":map}' is expected.
> at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:437)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:453)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3232)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1791)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:741)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:277)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:244)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:190)[:1.7.0_17]
> at 
> com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:109)[:1.7.0_17]
> at javax.xml.validation.Validator.validate(Unknown Source)[:2.1.0]
> at 
> 

[jira] [Commented] (ARIES-1161) ProxyGenerator uses ProxyCLassLoaded with wrong classloader

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052706#comment-15052706
 ] 

ASF GitHub Bot commented on ARIES-1161:
---

Github user grgrzybek closed the pull request at:

https://github.com/apache/aries/pull/18


> ProxyGenerator uses ProxyCLassLoaded with wrong classloader 
> 
>
> Key: ARIES-1161
> URL: https://issues.apache.org/jira/browse/ARIES-1161
> Project: Aries
>  Issue Type: Bug
>  Components: Proxy
>Affects Versions: proxy-impl-1.0.3
>Reporter: Konstantin Pelykh
>Assignee: Guillaume Nodet
> Fix For: proxy-impl-1.0.5
>
> Attachments: remove_pcl_from_cache_is_bundle_change_classloader.patch
>
>
> After bundle has been reloaded/refreshed, ProxyGenerator keeps using cached 
> version and old reference to outdated classloader. It latter results in NPE 
> when classloader tries to load class from refreshed bundle. 
> Affected version 1.0.3-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1006) Compilation error with JDK7

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052764#comment-15052764
 ] 

ASF GitHub Bot commented on ARIES-1006:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/13


> Compilation error with JDK7
> ---
>
> Key: ARIES-1006
> URL: https://issues.apache.org/jira/browse/ARIES-1006
> Project: Aries
>  Issue Type: Bug
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Attachments: ARIES-1006.patch
>
>
> When I try to compile Aries with JDK 7, I have:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 
> (default-compile) on project org.apache.aries.testsupport.unit: Compilation 
> failure: Compilation failure:
> [ERROR] could not parse error message: warning: [options] bootstrap class 
> path not set in conjunction with -source 1.5
> [ERROR] 
> /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:187:
>  warning: [deprecation] toURL() in File has been deprecated
> [ERROR] this(name,properties,location.toURL().toExternalForm());
> [ERROR] ^
> [ERROR] 
> [ERROR] 
> /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[239,17]
>  [deprecation] toURL() in File has been deprecated
> [ERROR] 
> [ERROR] 
> /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[263,60]
>  [deprecation] toURL() in File has been deprecated
> [ERROR] 
> [ERROR] 
> /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[328,65]
>  [deprecation] toURL() in File has been deprecated
> [ERROR] 
> It's due to some parent POM definition which force JDK5 support (target and 
> source).
> I don't think that the JDK5 support is still required. I gonna prepare a 
> couple of patches about that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1464) Improve blueprint-maven-plugin: add prototype-scope support

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052838#comment-15052838
 ] 

ASF GitHub Bot commented on ARIES-1464:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/32


> Improve blueprint-maven-plugin: add prototype-scope support
> ---
>
> Key: ARIES-1464
> URL: https://issues.apache.org/jira/browse/ARIES-1464
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Sam Wright
>Assignee: Christian Schneider
> Fix For: blueprint-maven-plugin-1.3.0
>
>
> -I propose adding support for configuring bean scope using 
> blueprint-maven-plugin, e.g. annotating a class with `@Scope("prototype")` 
> will add `scope = "prototype"` to the bean's xml element.-
> The JSR-330 spec says that a class can be defined as a prototype-scoped bean 
> by applying only the @Named annotation, and that to give the bean a 
> singleton-scope the @Singleton annotation should then be applied (either with 
> or replacing @Named), e.g.
> {code}
> @Singleton class AutonamedSingleton {}
> @Singleton @Named("foo") class NamedSingleton {}
> @Named AutonamedPrototype {}
> @Named("bar") NamedPrototype {}
> {code}
> The pull request implements this. NB this maintains backwards-compatibility 
> with classes annotated using @Singleton or @Component, with or without @Named.
> [~ch...@die-schneider.net] is probably the person to review this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1047) Update Aries for JPA 2.1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052766#comment-15052766
 ] 

ASF GitHub Bot commented on ARIES-1047:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/15


> Update Aries for JPA 2.1
> 
>
> Key: ARIES-1047
> URL: https://issues.apache.org/jira/browse/ARIES-1047
> Project: Aries
>  Issue Type: New Feature
>Reporter: Brett E. Meyer
>Assignee: Jean-Baptiste Onofré
>
> While implementing OSGi support in Hibernate, I forked Aries JPA and updated 
> it for JPA 2.1 -- we needed it as a test bed.  The spec is not yet out 
> (currently in a final draft and will hopefully soon be voted on).  The fork 
> uses Hibernate's current implementation of the 2.1 API.
> I'm creating a pull request with the work, just in case you want it as a 
> starting point for whenever you begin to support 2.1.  It's pretty simplistic 
> -- updated the POMs and manifests, added un-implemented methods, etc.  There 
> are several places where features, new to 2.1, may need to be implemented, 
> however some of them may just need to throw Unsupported.
> Pull request: https://github.com/apache/aries/pull/3
> Feel free to take it or leave it!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1290) Reflect cm.CmPropertyPlaceholder -> ext.PropertyPlaceholder relationship in XSD

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052767#comment-15052767
 ] 

ASF GitHub Bot commented on ARIES-1290:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/20


> Reflect cm.CmPropertyPlaceholder -> ext.PropertyPlaceholder relationship in 
> XSD
> ---
>
> Key: ARIES-1290
> URL: https://issues.apache.org/jira/browse/ARIES-1290
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-cm-1.0.4
>Reporter: Grzegorz Grzybek
>Assignee: Guillaume Nodet
> Fix For: blueprint-cm-1.0.7
>
>
> Because {{org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder}} 
> directly extends {{org.apache.aries.blueprint.ext.PropertyPlaceholder}} and 
> relevant namespace handler looks for {{ext}} namespace elements/attributes in 
> {{cm}} version of the placeholder, XSDs should reflect this fact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1177) Upgrade to Apache POM 14

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052765#comment-15052765
 ] 

ASF GitHub Bot commented on ARIES-1177:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/14


> Upgrade to Apache POM 14
> 
>
> Key: ARIES-1177
> URL: https://issues.apache.org/jira/browse/ARIES-1177
> Project: Aries
>  Issue Type: Bug
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Attachments: ARIES-1177.patch
>
>
> Some Maven plugins downloads fail as their pom refers the "old" Central repo 
> URL.
> In order to avoid this, we should upgrade to Apache POM 14.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1464) Improve blueprint-maven-plugin: add @Scope support

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037815#comment-15037815
 ] 

ASF GitHub Bot commented on ARIES-1464:
---

GitHub user samwright opened a pull request:

https://github.com/apache/aries/pull/32

[ARIES-1464] Add support for @Scope in blueprint-maven-plugin.

https://issues.apache.org/jira/browse/ARIES-1464

Add support for setting the scope of beans defined using 
blueprint-maven-plugin. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/samwright/aries scope

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/32.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #32


commit a007cbe8e112274b0a69a2b61800de0c16fa95ea
Author: Sam Wright 
Date:   2015-12-03T13:57:59Z

[ARIES-1464] Add support for @Scope in blueprint-maven-plugin.




> Improve blueprint-maven-plugin: add @Scope support
> --
>
> Key: ARIES-1464
> URL: https://issues.apache.org/jira/browse/ARIES-1464
> Project: Aries
>  Issue Type: Improvement
>  Components: Blueprint
>Reporter: Sam Wright
>
> I propose adding support for configuring bean scope using 
> blueprint-maven-plugin, e.g. annotating a class with `@Scope("prototype")` 
> will add `scope = "prototype"` to the bean's xml element.
> I'll update this with a link to the pull request in a few minutes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1453) Fragment-Host requirements with version range do not match with FragmentHostCapability

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006930#comment-15006930
 ] 

ASF GitHub Bot commented on ARIES-1453:
---

Github user asfgit closed the pull request at:

https://github.com/apache/aries/pull/30


> Fragment-Host requirements with version range do not match with 
> FragmentHostCapability
> --
>
> Key: ARIES-1453
> URL: https://issues.apache.org/jira/browse/ARIES-1453
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-2.0.6
>Reporter: Tom De Wolf
>Assignee: John Ross
>Priority: Blocker
> Fix For: subsystem-2.0.8
>
>
> According to http://wiki.osgi.org/wiki/Fragment-Host we can specify 
> Fragment-host headers using version ranges. When we do that the requirement 
> no longer matches on the capabilities in the aries subsystem implementation. 
> It results in the errors below.
> Reason for this is that the FragmentHostCapability only uses 'string' 
> attributes which results in versions "9.6.1" and "10.0.0" being compared as 
> if "10.0.0" is earlier than "9.6.1". A bundle host with version 9.6.1 
> therefore does not match the version range [9.6.0, 10.0.0). It should not do 
> string comparison but have a real 'Version' instance to compare with.
> {code}
> Error installing subsystem: org.osgi.service.subsystem.SubsystemException: 
> org.osgi.service.resolver.ResolutionException: Unable to resolve 
> /var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar:
>  missing requirement 
> org.apache.aries.subsystem.core.archive.FragmentHostRequirement: 
> namespace=osgi.wiring.host, attributes={}, 
> directives={filter=(&(osgi.wiring.host=be.aca.ui-framework)(&(bundle-version>=9.3.0)(!(bundle-version>=10.0.0},
>  
> resource=/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar
> g! at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
> at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.osgi.service.subsystem.SubsystemException: 
> org.osgi.service.resolver.ResolutionException: Unable to resolve 
> /var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar:
>  missing requirement 
> org.apache.aries.subsystem.core.archive.FragmentHostRequirement: 
> namespace=osgi.wiring.host, attributes={}, 
> directives={filter=(&(osgi.wiring.host=be.aca.ui-framework)(&(bundle-version>=9.3.0)(!(bundle-version>=10.0.0},
>  
> resource=/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:395)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:356)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:98)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:54)
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:30)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:646)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:690)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:278)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:65)
> at 
> be.aca.subsystem.internal.DefaultSubsystemService.installFromRepo(DefaultSubsystemService.java:86)
> at 
> be.aca.subsystem.internal.DefaultSubsystemService.install(DefaultSubsystemService.java:47)
> ... 30 more
> Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve 
> /var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar:
>  missing requirement 
> org.apache.aries.subsystem.core.archive.FragmentHostRequirement: 
> namespace=osgi.wiring.host, attributes={}, 
> 

[jira] [Commented] (ARIES-1453) Fragment-Host requirements with version range do not match with FragmentHostCapability

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006025#comment-15006025
 ] 

ASF GitHub Bot commented on ARIES-1453:
---

GitHub user tomdw opened a pull request:

https://github.com/apache/aries/pull/30

Aries 1453 test fragment host fix

See https://issues.apache.org/jira/browse/ARIES-1453 for a description of 
the problem.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tomdw/aries ARIES-1453-testFragmentHostFix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/30.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #30


commit 657c10e58f7e9f63fab799eb965a83510b80b97f
Author: Tom De Wolf 
Date:   2015-11-15T20:16:52Z

FragmentHostCapability should return version as real Version in order for 
correct requirement to capability matching to happen with version ranges

commit 434d0d2aa45016b8b0f3e46929ed5dfa312ab6ae
Author: Tom De Wolf 
Date:   2015-11-15T20:22:00Z

add extra test that fails when FragmentHostHeader, FragmentHostRequirement, 
and FragmentHostCapability do not match with version ranges

commit d0fca5c8d758a2eec9510e71a1ad583269382dd3
Author: Tom De Wolf 
Date:   2015-11-15T20:56:39Z

ARIES-1453 extract in separate test class




> Fragment-Host requirements with version range do not match with 
> FragmentHostCapability
> --
>
> Key: ARIES-1453
> URL: https://issues.apache.org/jira/browse/ARIES-1453
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-2.0.6
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.0.8
>
>
> According to http://wiki.osgi.org/wiki/Fragment-Host we can specify 
> Fragment-host headers using version ranges. When we do that the requirement 
> no longer matches on the capabilities in the aries subsystem implementation. 
> It results in the errors below.
> Reason for this is that the FragmentHostCapability only uses 'string' 
> attributes which results in versions "9.6.1" and "10.0.0" being compared as 
> if "10.0.0" is earlier than "9.6.1". A bundle host with version 9.6.1 
> therefore does not match the version range [9.6.0, 10.0.0). It should not do 
> string comparison but have a real 'Version' instance to compare with.
> {code}
> Error installing subsystem: org.osgi.service.subsystem.SubsystemException: 
> org.osgi.service.resolver.ResolutionException: Unable to resolve 
> /var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar:
>  missing requirement 
> org.apache.aries.subsystem.core.archive.FragmentHostRequirement: 
> namespace=osgi.wiring.host, attributes={}, 
> directives={filter=(&(osgi.wiring.host=be.aca.ui-framework)(&(bundle-version>=9.3.0)(!(bundle-version>=10.0.0},
>  
> resource=/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar
> g! at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
> at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.osgi.service.subsystem.SubsystemException: 
> org.osgi.service.resolver.ResolutionException: Unable to resolve 
> /var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar:
>  missing requirement 
> org.apache.aries.subsystem.core.archive.FragmentHostRequirement: 
> namespace=osgi.wiring.host, attributes={}, 
> directives={filter=(&(osgi.wiring.host=be.aca.ui-framework)(&(bundle-version>=9.3.0)(!(bundle-version>=10.0.0},
>  
> resource=/var/folders/9b/nqy6w5xs6gz1m1q4g6gpfr_cgn/T/inputStreamExtract8702582580344751163.zip/ui-main-13.3.1.jar
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:395)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:356)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:98)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
> 

[jira] [Commented] (ARIES-1407) Service (un)registration listener not called anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906288#comment-14906288
 ] 

ASF GitHub Bot commented on ARIES-1407:
---

Github user metatechbe closed the pull request at:

https://github.com/apache/aries/pull/28


> Service (un)registration listener not called anymore
> 
>
> Key: ARIES-1407
> URL: https://issues.apache.org/jira/browse/ARIES-1407
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
> Environment: Servicemix 5.4.1
>Reporter: metatech
> Attachments: blueprint_registration_listener_fix_v2.patch
>
>
> Service (un)registration listeners are not called anymore since Blueprint 
> 1.4.0.
> There are 2 booleans in the "ServiceRecipe" class which are tested against 
> the wrong values.
> Please find a patch which makes them work again with Blueprint 1.4.3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1407) Service (un)registration listener not called anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805185#comment-14805185
 ] 

ASF GitHub Bot commented on ARIES-1407:
---

GitHub user metatechbe opened a pull request:

https://github.com/apache/aries/pull/28

ARIES-1407 fix service registration (un)listeners



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/metatechbe/aries patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #28


commit 94ea60006cedbc6c17b1dd16d7149c46447a23c6
Author: metatechbe 
Date:   2015-09-18T08:13:11Z

ARIES-1407 fix service registration (un)listeners




> Service (un)registration listener not called anymore
> 
>
> Key: ARIES-1407
> URL: https://issues.apache.org/jira/browse/ARIES-1407
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
> Environment: Servicemix 5.4.1
>Reporter: metatech
> Attachments: blueprint_registration_listener_fix.patch
>
>
> Service (un)registration listeners are not called anymore since Blueprint 
> 1.4.0.
> There are 2 booleans in the "ServiceRecipe" class which are tested against 
> the wrong values.
> Please find a patch which makes them work again with Blueprint 1.4.3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1407) Service (un)registration listener not called anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805186#comment-14805186
 ] 

ASF GitHub Bot commented on ARIES-1407:
---

Github user metatechbe closed the pull request at:

https://github.com/apache/aries/pull/28


> Service (un)registration listener not called anymore
> 
>
> Key: ARIES-1407
> URL: https://issues.apache.org/jira/browse/ARIES-1407
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
> Environment: Servicemix 5.4.1
>Reporter: metatech
> Attachments: blueprint_registration_listener_fix.patch
>
>
> Service (un)registration listeners are not called anymore since Blueprint 
> 1.4.0.
> There are 2 booleans in the "ServiceRecipe" class which are tested against 
> the wrong values.
> Please find a patch which makes them work again with Blueprint 1.4.3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARIES-1407) Service (un)registration listener not called anymore

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARIES-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805188#comment-14805188
 ] 

ASF GitHub Bot commented on ARIES-1407:
---

GitHub user metatechbe reopened a pull request:

https://github.com/apache/aries/pull/28

ARIES-1407 fix Blueprint service registration (un)listeners



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/metatechbe/aries patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #28


commit 94ea60006cedbc6c17b1dd16d7149c46447a23c6
Author: metatechbe 
Date:   2015-09-18T08:13:11Z

ARIES-1407 fix service registration (un)listeners




> Service (un)registration listener not called anymore
> 
>
> Key: ARIES-1407
> URL: https://issues.apache.org/jira/browse/ARIES-1407
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
> Environment: Servicemix 5.4.1
>Reporter: metatech
> Attachments: blueprint_registration_listener_fix.patch
>
>
> Service (un)registration listeners are not called anymore since Blueprint 
> 1.4.0.
> There are 2 booleans in the "ServiceRecipe" class which are tested against 
> the wrong values.
> Please find a patch which makes them work again with Blueprint 1.4.3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)