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 2011/02/17 18:45:24 UTC
[jira] Updated: (ARIES-481) BlueprintEvent may mutate after
creation
[ https://issues.apache.org/jira/browse/ARIES-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated ARIES-481:
----------------------------------
Fix Version/s: blueprint-0.2.1
> BlueprintEvent may mutate after creation
> ----------------------------------------
>
> Key: ARIES-481
> URL: https://issues.apache.org/jira/browse/ARIES-481
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: 0.2
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
> Priority: Minor
> Fix For: 0.3, blueprint-0.2.1
>
>
> Running findbugs on the org.osgi.service.blueprint package results in the
> following error:
> org.osgi.service.blueprint.container.BlueprintEvent(int, Bundle, Bundle,
> String[], Throwable) may expose internal representation by storing an
> externally mutable object into BlueprintEvent.dependencies MALICIOUS_CODE
> EI_EXPOSE_REP2 229 Medium
> I think the worst that can happen is that if the BlueprintContainer
> implementation changed the dependencies array it passes to the extender two
> different event handlers could see different dependencies.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira