6/29/2012 7:37:26 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:29:38 PM
commit 7634ba410e437337d00e38d2e622b4057fdca364.
We actually already store the subscription_id in the prev/next objects.
Although it makes sense in the Java code to have subscription_id in the
BusinessSubscription object, it feels weird to have it duplicated in the
table (prev/next). But let's keep it for now.
Conflicts:
analytics/src/main/java/com/ning/billing/analytics/BusinessSubscriptionTransitionRecorder.java
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 7:06:50 PM
issues, we may now need to update transitions in bst.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 6:24:41 PM
to handle future events.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/29/2012 4:27:09 PM
when future changes are requested.
Hook into the AuditedEntitlementDao and send an event on the bus right
after adding the future change on the notification queue.
Although it seems to work, there are two problems with this patch.
First, it adds some more logic in the (already complicated) dao.
Second, I am jumping through hoops to generate the actual event: since I
am in the middle of the transaction, I need to add some logic to find
the previous state for a given event the subscription is in (some of
that state might be on disk, some might still be in memory, in the transaction).
I am open to suggestions to refactor this.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/28/2012 9:13:59 PM
functional change.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
6/28/2012 8:19:57 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
|
|
|
|
|
|
