|
|
|
|
11/3/2013 4:09:55 PM
was paid using account currency or converted currency
|
11/7/2013 12:34:29 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
11/6/2013 7:24:06 PM
the same logic as in subscription base, i.e. determine if add-ons need
to be blocked in case of base plan cancellations and plan changes.
The bulk of the logic is in EntitlementUtils, called from DefaultEntitlement and
DefaultBlockingStateDao.
This is a first pass, in order to get early feedback on the implementation. We still
need to think through (and probably write tests) for uncancel and transfer scenarii (i.e.
do we do the right thing in these cases?).
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
11/2/2013 9:07:31 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
11/2/2013 8:19:27 AM
sure to get the latest state from disk before attempting
a cancellation, change plan or uncancellation.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
11/1/2013 5:03:36 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
11/1/2013 1:38:52 PM
was cancelling add-ons but entitlement is doing the same.
This was leading to duplicate CANCEL events in subscription_events for
add-ons.
This bug is actually quite old. We did fix it by
12d21a5fefb3708ba9feeadb5116e1b211f7a653 but we re-introduced it with
4bdae521d107ef04adaef9ff04162778ee91f35e.
This should hopefully fix #94.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
|
|
