[ https://forge.continuent.org/jira/browse/CAROB-96?page=all ]
Gilles Rayrat resolved CAROB-96:
--------------------------------
Resolution: Fixed
Was due to buggy comparison in a comparator. Fixed in CVS
> Connection Policy does not iterate through the controller list at each new
> connection
> -------------------------------------------------------------------------------------
>
> Key: CAROB-96
> URL: https://forge.continuent.org/jira/browse/CAROB-96
> Project: Carob
> Type: Bug
> Components: C++ API
> Versions: Carob 0.5, Carob 0.1
> Reporter: Gilles Rayrat
> Assignee: Gilles Rayrat
> Fix For: Carob 1.0beta
>
> Original Estimate: 2 days
> Remaining: 2 days
>
> When creating two connections with the same parameters, the connection policy
> should affect different controllers to the two connections
> It is not the case because the connection policy is created by the connection.
> Solution: connection policy should be created by the connection parameters.
> Thus, two successive connections with the same parameters will use two
> different controllers.
> issue: the addController() method in connection parameters should be
> forbidden once a connection has been created with these parameters. A simple
> way to do that is to forbid addController() call once getController() method
> has been called. This way, we don't change the API and ensure integrity
> For convenience, a second constructor should be added taking a controller
> list as parameter (instead of 1 controller + addController calls)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
