[
https://issues.apache.org/jira/browse/ARIES-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366705#comment-16366705
]
ASF subversion and git services commented on ARIES-1009:
--------------------------------------------------------
Commit 1824428 from [~gnt] in branch 'aries/trunk'
[ https://svn.apache.org/r1824428 ]
[ARIES-1009] BlueprintContainerImpl - Add INFO logging when the blueprint
container has been created
> BlueprintContainerImpl - Add INFO logging when the blueprint container has
> been created
> ---------------------------------------------------------------------------------------
>
> Key: ARIES-1009
> URL: https://issues.apache.org/jira/browse/ARIES-1009
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: 1.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: blueprint-core-1.10.0
>
>
> I am looking into an issue with reload() on aries blueprint, and needed to
> turn on DEBUG logging on various packages to see what goes on.
> What I am missing is also at normal usage an INFO logging that logs when the
> blueprint container has been created.
> eg in BlueprintContainerImpl, you have this code
> {code}
> eventDispatcher.blueprintEvent(new
> BlueprintEvent(BlueprintEvent.CREATED, getBundleContext().getBundle(),
> getExtenderBundle()));
> state = State.Created;
> {code}
> I suggest to add a INFO logging with details about the blueprint container
> has been created.
> Then people can easier spot that the container has been created in their
> logs. Now you need to enable DEBUG log and look for BlueprintEventDispatcher
> when it sends the even for CREATED.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
