[jira] [Updated] (ARIES-1456) Spring support

2015-12-14 Thread Christian Schneider (JIRA) 

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

Christian Schneider updated ARIES-1456:
---
Fix Version/s: blueprint-parser-1.4.0

> Spring support
> --
>
> Key: ARIES-1456
> URL: https://issues.apache.org/jira/browse/ARIES-1456
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-parser-1.4.0
>
>
> Support for spring namespaces would be a great feature and would allow users 
> to completely get rid of spring-dm easily.



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

[jira] [Updated] (ARIES-1456) Spring support

2015-12-14 Thread Christian Schneider (JIRA) 

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

Christian Schneider updated ARIES-1456:
---
Fix Version/s: blueprint-spring-0.1.0

> Spring support
> --
>
> Key: ARIES-1456
> URL: https://issues.apache.org/jira/browse/ARIES-1456
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Affects Versions: blueprint-parser-1.3.2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-parser-1.4.0, blueprint-spring-0.1.0
>
>
> Support for spring namespaces would be a great feature and would allow users 
> to completely get rid of spring-dm easily.



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

[jira] [Updated] (ARIES-1456) Spring support

2015-12-14 Thread Christian Schneider (JIRA) 

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

Christian Schneider updated ARIES-1456:
---
Affects Version/s: blueprint-parser-1.3.2

> Spring support
> --
>
> Key: ARIES-1456
> URL: https://issues.apache.org/jira/browse/ARIES-1456
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Affects Versions: blueprint-parser-1.3.2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-parser-1.4.0, blueprint-spring-0.1.0
>
>
> Support for spring namespaces would be a great feature and would allow users 
> to completely get rid of spring-dm easily.



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

[jira] [Created] (ARIES-1479) Add service requirements and capabilities

2015-12-14 Thread Christian Schneider (JIRA) 
Christian Schneider created ARIES-1479:
--

 Summary: Add service requirements and capabilities
 Key: ARIES-1479
 URL: https://issues.apache.org/jira/browse/ARIES-1479
 Project: Aries
  Issue Type: Improvement
  Components: JPA
Affects Versions: jpa-2.3.0
Reporter: Christian Schneider
Assignee: Christian Schneider






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

[jira] [Closed] (ARIES-1468) Aries Transaction Blueprint bundle fails to start sometimes

2015-12-14 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov closed ARIES-1468.


> Aries Transaction Blueprint bundle fails to start sometimes
> ---
>
> Key: ARIES-1468
> URL: https://issues.apache.org/jira/browse/ARIES-1468
> Project: Aries
>  Issue Type: Bug
>  Components: JMX, Transaction
>Affects Versions: transaction-manager-1.3.0, jmx-1.1.5, 
> transaction-blueprint-2.0.0
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Christian Schneider
>Priority: Blocker
> Fix For: jmx-1.1.6
>
>
> I have found some unstable behavior when starting Karaf 4.0.3.
> Apache Aries Transaction Blueprint 2.0.0 bundle start success is random.
> I have to restart Karaf several (about 3 to 10) times to get the error.
> It looks like it is some sort of a bundle race or something.
> The list of features to be installed:
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> Exception during Karaf start:
> karaf@root()> ERROR: Bundle org.apache.aries.blueprint.core [13] 
> EventDispatcher: Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:126)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:991)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:839)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:546)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:459)
> at 
> org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:193)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:710)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:385)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:270)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Cut from bundle:list command result:
> 108 | Active   |  80 | 1.2 | javax.interceptor API
> 109 | Active   |  80 | 1.2 | javax.transaction API
> 110 | Active   |  80 | 1.1.1   | Apache Aries Transaction 
> Blueprint
> 111 | Failure  |  80 | 2.0.0   | Apache Aries Transaction 
> Blueprint
> 112 | Active   |  80 | 1.3.0   | Apache Aries Transaction 
> Manager
> Diag command result for problem bundle:
> Apache Aries Transaction Blueprint (111)
>

[jira] [Created] (ARIES-1478) Avoid possible IllegalStateException when registering a service

2015-12-14 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created ARIES-1478:
--

 Summary: Avoid possible IllegalStateException when registering a 
service
 Key: ARIES-1478
 URL: https://issues.apache.org/jira/browse/ARIES-1478
 Project: Aries
  Issue Type: Bug
  Components: Blueprint
Affects Versions: blueprint-core-1.4.5
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: blueprint-core-1.5.0






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

[jira] [Resolved] (ARIES-1468) Aries Transaction Blueprint bundle fails to start sometimes

2015-12-14 Thread Christian Schneider (JIRA) 

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

Christian Schneider resolved ARIES-1468.

Resolution: Fixed

> Aries Transaction Blueprint bundle fails to start sometimes
> ---
>
> Key: ARIES-1468
> URL: https://issues.apache.org/jira/browse/ARIES-1468
> Project: Aries
>  Issue Type: Bug
>  Components: JMX, Transaction
>Affects Versions: transaction-manager-1.3.0, jmx-1.1.5, 
> transaction-blueprint-2.0.0
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Christian Schneider
>Priority: Blocker
> Fix For: jmx-1.1.6
>
>
> I have found some unstable behavior when starting Karaf 4.0.3.
> Apache Aries Transaction Blueprint 2.0.0 bundle start success is random.
> I have to restart Karaf several (about 3 to 10) times to get the error.
> It looks like it is some sort of a bundle race or something.
> The list of features to be installed:
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> Exception during Karaf start:
> karaf@root()> ERROR: Bundle org.apache.aries.blueprint.core [13] 
> EventDispatcher: Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:126)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:991)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:839)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:546)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:459)
> at 
> org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:193)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:710)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:385)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:270)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Cut from bundle:list command result:
> 108 | Active   |  80 | 1.2 | javax.interceptor API
> 109 | Active   |  80 | 1.2 | javax.transaction API
> 110 | Active   |  80 | 1.1.1   | Apache Aries Transaction 
> Blueprint
> 111 | Failure  |  80 | 2.0.0   | Apache Aries Transaction 
> Blueprint
> 112 | Active   |  80 | 1.3.0   | Apache Aries Transaction 
> Manager
> Diag command result for problem bundle:
> Apache Aries Transaction Blueprint (111)
>

[jira] [Created] (ARIES-1480) Spring extender support

2015-12-14 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created ARIES-1480:
--

 Summary: Spring extender support
 Key: ARIES-1480
 URL: https://issues.apache.org/jira/browse/ARIES-1480
 Project: Aries
  Issue Type: New Feature
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: blueprint-spring-extender-0.1.0


New extender supporting META-INF/spring/*.xml 



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

[jira] [Updated] (ARIES-1456) Spring support

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated ARIES-1456:
---
Fix Version/s: blueprint-spring-extender-0.1.0

> Spring support
> --
>
> Key: ARIES-1456
> URL: https://issues.apache.org/jira/browse/ARIES-1456
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Affects Versions: blueprint-parser-1.3.2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-parser-1.4.0, blueprint-spring-0.1.0, 
> blueprint-spring-extender-0.1.0
>
>
> Support for spring namespaces would be a great feature and would allow users 
> to completely get rid of spring-dm easily.



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

[jira] [Updated] (ARIES-1480) Complete spring extender support

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated ARIES-1480:
---
Summary: Complete spring extender support  (was: Spring extender support)

> Complete spring extender support
> 
>
> Key: ARIES-1480
> URL: https://issues.apache.org/jira/browse/ARIES-1480
> Project: Aries
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-spring-extender-0.1.0
>
>
> New extender supporting META-INF/spring/*.xml 



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

[jira] [Commented] (ARIES-1480) Complete spring extender support

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on ARIES-1480:


ARIES-1456 provides initial support for spring namespaces and spring bundles.
But there are elements not supported, particularly in the osgi (only  
and  elements are supported) and compendium namespaces (none is 
supported, though the whole code could easily leverage the existing cm 
namespace, as it has been built to support the same elements).

> Complete spring extender support
> 
>
> Key: ARIES-1480
> URL: https://issues.apache.org/jira/browse/ARIES-1480
> Project: Aries
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-spring-extender-0.1.0
>
>
> New extender supporting META-INF/spring/*.xml 



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

[jira] [Resolved] (ARIES-1456) Spring support

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet resolved ARIES-1456.

Resolution: Fixed

> Spring support
> --
>
> Key: ARIES-1456
> URL: https://issues.apache.org/jira/browse/ARIES-1456
> Project: Aries
>  Issue Type: New Feature
>  Components: Blueprint
>Affects Versions: blueprint-parser-1.3.2
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-parser-1.4.0, blueprint-spring-0.1.0
>
>
> Support for spring namespaces would be a great feature and would allow users 
> to completely get rid of spring-dm easily.



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

[jira] [Commented] (ARIES-1468) Aries Transaction Blueprint bundle fails to start sometimes

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet commented on ARIES-1468:


I've fixed the 2 exceptions in ARIES-1477 and ARIES-1478.
Let me know if this fixes this issue.

> Aries Transaction Blueprint bundle fails to start sometimes
> ---
>
> Key: ARIES-1468
> URL: https://issues.apache.org/jira/browse/ARIES-1468
> Project: Aries
>  Issue Type: Bug
>  Components: JMX, Transaction
>Affects Versions: transaction-manager-1.3.0, jmx-1.1.5, 
> transaction-blueprint-2.0.0
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Christian Schneider
>Priority: Blocker
> Fix For: jmx-1.1.6
>
>
> I have found some unstable behavior when starting Karaf 4.0.3.
> Apache Aries Transaction Blueprint 2.0.0 bundle start success is random.
> I have to restart Karaf several (about 3 to 10) times to get the error.
> It looks like it is some sort of a bundle race or something.
> The list of features to be installed:
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> Exception during Karaf start:
> karaf@root()> ERROR: Bundle org.apache.aries.blueprint.core [13] 
> EventDispatcher: Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:126)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:991)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:839)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:546)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:459)
> at 
> org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:193)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:710)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:385)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:270)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Cut from bundle:list command result:
> 108 | Active   |  80 | 1.2 | javax.interceptor API
> 109 | Active   |  80 | 1.2 | javax.transaction API
> 110 | Active   |  80 | 1.1.1   | Apache Aries Transaction 
> Blueprint
> 111 | Failure  |  80 | 2.0.0   | Apache Aries Transaction 
> Blueprint
> 112 | Active   |  80 | 1.3.0   | Apache Aries

[jira] [Updated] (ARIES-1479) Add service requirements and capabilities

2015-12-14 Thread Christian Schneider (JIRA) 

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

Christian Schneider updated ARIES-1479:
---
Fix Version/s: jpa-2.4.0

> Add service requirements and capabilities
> -
>
> Key: ARIES-1479
> URL: https://issues.apache.org/jira/browse/ARIES-1479
> Project: Aries
>  Issue Type: Improvement
>  Components: JPA
>Affects Versions: jpa-2.3.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: jpa-2.4.0
>
>




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

[VOTE] blueprint-parser-1.4.0, org.apache.aries.blueprint.core-1.5.0,

2015-12-14 Thread Christian Schneider 

I've staged some releases for vote.


 blueprint-parser-1.4.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1054

Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334350

** New Feature
* [ARIES-1456] - Spring support


 blueprint-core-1.5.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1055


Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334309

** Bug
* [ARIES-1467] - Blueprint creates unnecessary prototype bean instances
* [ARIES-1477] - NPE in NamespaceHandlerRegistryImpl
* [ARIES-1478] - Avoid possible IllegalStateException when 
registering a service



 org.apache.aries.blueprint.spring-0.1.0
 org.apache.aries.blueprint.spring.extender-0.1.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1056

Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334353
** New Feature
* [ARIES-1456] - Spring support
* [ARIES-1480] - Complete spring extender support

https://issues.apache.org/jira/browse/ARIES/fixforversion/12334351
** New Feature
* [ARIES-1456] - Spring support

Please review and vote:
  [ ] +1 Release the above artifacts
  [ ] -1 Do not

Here is my +1

Cheers,
Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [VOTE] Aries jpa-2.3.0, transaction.blueprint-2.1.0 and blueprint-maven-plugin-1.3.0

2015-12-14 Thread David Bosschaert 
Hi Christian,

I guess I find it a bit odd that we're voting on two seemingly
unrelated components: JPA and blueprint - would it not make sense to
split these into two separate votes?

+1 from me in any case

Cheers,

David

On 13 December 2015 at 12:34, Jean-Baptiste Onofré  wrote:
>
>
> +1
> RegardsJB
>
>
> Sent from my Samsung device
>
>  Original message 
> From: Christian Schneider 
> Date: 13/12/2015  12:17  (GMT+01:00)
> To: dev@aries.apache.org
> Subject: [VOTE] Aries jpa-2.3.0, transaction.blueprint-2.1.0 and 
> blueprint-maven-plugin-1.3.0
>
> I've staged some releases for vote.
>
>
>   JPA-2.3.0
>
> Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1052
>
> Release Notes
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12333867
>
> ** Bug
>  * [ARIES-1433] - Persistence units are not picked up while bundle
> is in status resolved
>  * [ARIES-1438] - NPE in XAJpaTemplate#txExpr if Coordinator is null
>  * [ARIES-1455] - JpaComponentProcessor is not scanning the nested
> beans inside service definition
>  * [ARIES-1469] - JPA container should not embed spec packages
>  * [ARIES-1473] - Aries JPA creates derby.log outside target
>
> ** Improvement
>  * [ARIES-1448] - Fix Issues reported by Sonar
>
>
>   transaction.blueprint-2.1.0
>
> Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1051
>
>
> Release Notes
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12334327
>
> ** Bug
>  * [ARIES-1454] - NPE in TxInterceptor
>
> ** Improvement
>  * [ARIES-1380] - Remove remaining NLS usage
>  * [ARIES-1450] - Cache computation of effective txType
>
>
>   blueprint-maven-plugin-1.3.0
>
> Repository:
> https://repository.apache.org/content/repositories/orgapachearies-1053
>
> Release Notes - Aries - Version blueprint-maven-plugin-1.3.0
> https://issues.apache.org/jira/browse/ARIES/fixforversion/12333650
>
> ** Improvement
>  * [ARIES-1422] - Support m2e incremental build in
> blueprint-maven-plugin
>  * [ARIES-1464] - Improve blueprint-maven-plugin: add
> prototype-scope support
>
>
> Please review and vote:
>[ ] +1 Release the above artifacts
>[ ] -1 Do not
>
> Here is my +1
>
> Cheers,
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>

[jira] [Created] (ARIES-1481) blueprint-maven-plugin: fix detection of inherited @OsgiService/@PersistenceContext/Unit-annotated fields

2015-12-14 Thread Sam Wright (JIRA) 
Sam Wright created ARIES-1481:
-

 Summary: 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)

[GitHub] aries pull request: [Aries-1481] Fix inheritance of @OsgiService a...

2015-12-14 Thread samwright 
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.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ARIES-1481) blueprint-maven-plugin: fix detection of inherited @OsgiService/@PersistenceContext/Unit-annotated fields

2015-12-14 Thread 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)

Re: [VOTE] blueprint-parser-1.4.0, org.apache.aries.blueprint.core-1.5.0,

2015-12-14 Thread Sergey Beryozkin 

+1

Sergey
On 14/12/15 15:47, Christian Schneider wrote:

I've staged some releases for vote.


  blueprint-parser-1.4.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1054

Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334350

** New Feature
 * [ARIES-1456] - Spring support


  blueprint-core-1.5.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1055


Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334309

** Bug
 * [ARIES-1467] - Blueprint creates unnecessary prototype bean
instances
 * [ARIES-1477] - NPE in NamespaceHandlerRegistryImpl
 * [ARIES-1478] - Avoid possible IllegalStateException when
registering a service


  org.apache.aries.blueprint.spring-0.1.0
  org.apache.aries.blueprint.spring.extender-0.1.0

Repository:
https://repository.apache.org/content/repositories/orgapachearies-1056

Release Notes
https://issues.apache.org/jira/browse/ARIES/fixforversion/12334353
** New Feature
 * [ARIES-1456] - Spring support
 * [ARIES-1480] - Complete spring extender support

https://issues.apache.org/jira/browse/ARIES/fixforversion/12334351
** New Feature
 * [ARIES-1456] - Spring support

Please review and vote:
   [ ] +1 Release the above artifacts
   [ ] -1 Do not

Here is my +1

Cheers,
Christian




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

[jira] [Commented] (ARIES-1478) Avoid possible IllegalStateException when registering a service

2015-12-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on ARIES-1478:


Commit 1719867 from [~gnt] in branch 'aries/trunk'
[ https://svn.apache.org/r1719867 ]

[ARIES-1478] Avoid possible IllegalStateException when registering a service

> Avoid possible IllegalStateException when registering a service
> ---
>
> Key: ARIES-1478
> URL: https://issues.apache.org/jira/browse/ARIES-1478
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.4.5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.5.0
>
>




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

[jira] [Commented] (ARIES-1468) Aries Transaction Blueprint bundle fails to start sometimes

2015-12-14 Thread Viktor Kozlov (JIRA) 

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

Viktor Kozlov commented on ARIES-1468:
--

I've done some test runs with new snapshot. It looks like fixed for my 
environment.

> Aries Transaction Blueprint bundle fails to start sometimes
> ---
>
> Key: ARIES-1468
> URL: https://issues.apache.org/jira/browse/ARIES-1468
> Project: Aries
>  Issue Type: Bug
>  Components: JMX, Transaction
>Affects Versions: transaction-manager-1.3.0, jmx-1.1.5, 
> transaction-blueprint-2.0.0
> Environment: Windows 7 version 6.1 x64
> Java 1.7.0_80 x64
>Reporter: Viktor Kozlov
>Assignee: Christian Schneider
>Priority: Blocker
> Fix For: jmx-1.1.6
>
>
> I have found some unstable behavior when starting Karaf 4.0.3.
> Apache Aries Transaction Blueprint 2.0.0 bundle start success is random.
> I have to restart Karaf several (about 3 to 10) times to get the error.
> It looks like it is some sort of a bundle race or something.
> The list of features to be installed:
> feature:install -v eventadmin;
> feature:install -v http-whiteboard;
> feature:install -v jdbc;
> feature:install -v pax-jdbc-pool-dbcp2;
> feature:install -v eclipselink/2.6.0;
> feature:install -v jpa/2.2.0;
> Exception during Karaf start:
> karaf@root()> ERROR: Bundle org.apache.aries.blueprint.core [13] 
> EventDispatcher: Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.addingService(NamespaceHandlerRegistryImpl.java:126)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:991)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:839)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:546)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:459)
> at 
> org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:193)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:710)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:385)
> at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:270)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Cut from bundle:list command result:
> 108 | Active   |  80 | 1.2 | javax.interceptor API
> 109 | Active   |  80 | 1.2 | javax.transaction API
> 110 | Active   |  80 | 1.1.1   | Apache Aries Transaction 
> Blueprint
> 111 | Failure  |  80 | 2.0.0   | Apache Aries Transaction 
> Blueprint
> 112 | Active   |  80 | 1.3.0   | Apache Aries Transaction 
> Manager

Re: [VOTE] Aries jpa-2.3.0, transaction.blueprint-2.1.0 and blueprint-maven-plugin-1.3.0

2015-12-14 Thread Christian Schneider 
I just put together the releases I needed to do at that point. So it was
mainly for convenience of people voting. If you prefer separate votes I can
do that for new votes.

Btw. I would rather consider the blueprint-maven-plugin unrelated :-)
transaction.blueprint and jpa are quite closely related even if the have no
dependency on each other.

Christian

2015-12-14 17:04 GMT+01:00 David Bosschaert :

> Hi Christian,
>
> I guess I find it a bit odd that we're voting on two seemingly
> unrelated components: JPA and blueprint - would it not make sense to
> split these into two separate votes?
>
> +1 from me in any case
>
> Cheers,
>
> David
>
> On 13 December 2015 at 12:34, Jean-Baptiste Onofré 
> wrote:
> >
> >
> > +1
> > RegardsJB
> >
> >
> > Sent from my Samsung device
> >
> >  Original message 
> > From: Christian Schneider 
> > Date: 13/12/2015  12:17  (GMT+01:00)
> > To: dev@aries.apache.org
> > Subject: [VOTE] Aries jpa-2.3.0, transaction.blueprint-2.1.0 and
> blueprint-maven-plugin-1.3.0
> >
> > I've staged some releases for vote.
> >
> >
> >   JPA-2.3.0
> >
> > Repository:
> > https://repository.apache.org/content/repositories/orgapachearies-1052
> >
> > Release Notes
> > https://issues.apache.org/jira/browse/ARIES/fixforversion/12333867
> >
> > ** Bug
> >  * [ARIES-1433] - Persistence units are not picked up while bundle
> > is in status resolved
> >  * [ARIES-1438] - NPE in XAJpaTemplate#txExpr if Coordinator is null
> >  * [ARIES-1455] - JpaComponentProcessor is not scanning the nested
> > beans inside service definition
> >  * [ARIES-1469] - JPA container should not embed spec packages
> >  * [ARIES-1473] - Aries JPA creates derby.log outside target
> >
> > ** Improvement
> >  * [ARIES-1448] - Fix Issues reported by Sonar
> >
> >
> >   transaction.blueprint-2.1.0
> >
> > Repository:
> > https://repository.apache.org/content/repositories/orgapachearies-1051
> >
> >
> > Release Notes
> > https://issues.apache.org/jira/browse/ARIES/fixforversion/12334327
> >
> > ** Bug
> >  * [ARIES-1454] - NPE in TxInterceptor
> >
> > ** Improvement
> >  * [ARIES-1380] - Remove remaining NLS usage
> >  * [ARIES-1450] - Cache computation of effective txType
> >
> >
> >   blueprint-maven-plugin-1.3.0
> >
> > Repository:
> > https://repository.apache.org/content/repositories/orgapachearies-1053
> >
> > Release Notes - Aries - Version blueprint-maven-plugin-1.3.0
> > https://issues.apache.org/jira/browse/ARIES/fixforversion/12333650
> >
> > ** Improvement
> >  * [ARIES-1422] - Support m2e incremental build in
> > blueprint-maven-plugin
> >  * [ARIES-1464] - Improve blueprint-maven-plugin: add
> > prototype-scope support
> >
> >
> > Please review and vote:
> >[ ] +1 Release the above artifacts
> >[ ] -1 Do not
> >
> > Here is my +1
> >
> > Cheers,
> > Christian
> >
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Open Source Architect
> > http://www.talend.com
> >
>



-- 
-- 
Christian Schneider
http://www.liquid-reality.de


Open Source Architect
http://www.talend.com

[jira] [Created] (ARIES-1477) NPE in NamespaceHandlerRegistryImpl

2015-12-14 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created ARIES-1477:
--

 Summary: NPE in NamespaceHandlerRegistryImpl
 Key: ARIES-1477
 URL: https://issues.apache.org/jira/browse/ARIES-1477
 Project: Aries
  Issue Type: Bug
  Components: Blueprint
Affects Versions: blueprint-core-1.4.5
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: blueprint-core-1.5.0






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

[jira] [Commented] (ARIES-1477) NPE in NamespaceHandlerRegistryImpl

2015-12-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on ARIES-1477:


Commit 1719864 from [~gnt] in branch 'aries/trunk'
[ https://svn.apache.org/r1719864 ]

[ARIES-1477] NPE in NamespaceHandlerRegistryImpl

> NPE in NamespaceHandlerRegistryImpl
> ---
>
> Key: ARIES-1477
> URL: https://issues.apache.org/jira/browse/ARIES-1477
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.4.5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.5.0
>
>




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

[jira] [Resolved] (ARIES-1477) NPE in NamespaceHandlerRegistryImpl

2015-12-14 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet resolved ARIES-1477.

Resolution: Fixed

Committing to https://svn.apache.org/repos/asf/aries/trunk ...
M   
blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java
Committed r1719864


> NPE in NamespaceHandlerRegistryImpl
> ---
>
> Key: ARIES-1477
> URL: https://issues.apache.org/jira/browse/ARIES-1477
> Project: Aries
>  Issue Type: Bug
>  Components: Blueprint
>Affects Versions: blueprint-core-1.4.5
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: blueprint-core-1.5.0
>
>




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