[
https://issues.apache.org/jira/browse/FELIX-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778873#action_12778873
]
Guillaume Sauthier commented on FELIX-1722:
-------------------------------------------
I've just seen the Gogo 0.2.2 release vote on the list, without that
(inoffensive) patch :)
Maybe my description was not very clear.
I'll try to do better :)
I'm trying to exposes iPOJO components as Gogo commands.
Something probably similar to what as been done for blueprint.
iPOJO components instances can be created at will, but they also needs to be
removed when they're no more in use.
In the case of a stateless command (command instance is not reused), I need to
tell iPOJO that the command was executed and that the instance can be put back
in "pool".
This is why I need a releaseAction() method (symetric to the createAction()
method) in the AbstractCommand class: a method that could be overriden by an
AbstractIPOJOCommand to realease the created Action.
Does it make sense to have that behavior (default do nothing, so no behavior
change for existing commands, no new methods to implement) or not ?
> gogo AbstractCommand should let the possibility to release the used Action
> --------------------------------------------------------------------------
>
> Key: FELIX-1722
> URL: https://issues.apache.org/jira/browse/FELIX-1722
> Project: Felix
> Issue Type: Improvement
> Components: Gogo
> Reporter: Guillaume Sauthier
> Attachments: FELIX-1722.patch
>
>
> I'm playing with gogo and I need to release the used Action because I'm using
> some kind of pool providing instances of Action.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
