You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/01/30 23:05:01 UTC
[jira] [Resolved] (ARIES-1436) cm:managed-component destroy-method
will only be called when it has a single integer argument
[ https://issues.apache.org/jira/browse/ARIES-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved ARIES-1436.
------------------------------------
Resolution: Fixed
Assignee: Guillaume Nodet
Fix Version/s: blueprint-cm-1.2.0
Committing to https://svn.apache.org/repos/asf/aries/trunk ...
M blueprint/blueprint-cm/src/main/java/org/apache/aries/blueprint/compendium/cm/CmManagedServiceFactory.java
Committed r1822715
> cm:managed-component destroy-method will only be called when it has a single integer argument
> ---------------------------------------------------------------------------------------------
>
> Key: ARIES-1436
> URL: https://issues.apache.org/jira/browse/ARIES-1436
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: blueprint-cm-1.0.7
> Reporter: Benjamin Deininger
> Assignee: Guillaume Nodet
> Priority: Minor
> Fix For: blueprint-cm-1.2.0
>
>
> The destroy-method for cm:managed-components is only considered a compatible method if it contains a single integer argument. This requires the use of a placeholder integer when no argument is required, and can lead to confusion during use of blueprint-cm.
> {code:title=CmManagedServiceFactory.java|borderStyle=solid}
> private Method findDestroyMethod(Class clazz) {
> Method method = null;
> if (componentDestroyMethod != null && componentDestroyMethod.length() > 0) {
> List<Method> methods = ReflectionUtils.findCompatibleMethods(clazz, componentDestroyMethod, ----> new Class [] { int.class } <----);
> if (methods != null && !methods.isEmpty()) {
> method = methods.get(0);
> }
> }
> return method;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)