10/21/2013 11:21:53 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
|
|
|
|
10/18/2013 3:59:07 PM
differently when CTD exists but is in the past
(This solves an issue where effectiveDate for cancellation events for instnace would end up in the past and priod other events, whcih create an invalid state)
|
10/18/2013 10:48:21 AM
weren't respecting the default billing policy when specifying
only an entitlement policy in the cancellation call.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
10/18/2013 10:47:34 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
10/18/2013 10:34:02 AM
sure that, when transforming a LocalDate to a DateTime,
we don't end up in the past if the day is today.
This was causing a bug when cancelling an entitlement end-of-term
during trial.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
10/17/2013 4:04:25 PM
sure the default billing policy is respected by the
cancelEntitlementWithPolicy call.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
10/17/2013 4:02:00 PM
extra catch blocks - tests will fail if the exception is thrown.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
10/16/2013 5:25:33 PM
proper retrieval of audit logs.
First of all, when creating audit logs, the BindBeanFactory will see the TableName
attribute of the EntityAudit object as an enum, and thus it will bind
its name via EnumArgumentFactory (the enum name is written to the database).
When reading audit logs, we were directly binding TableName. The
BindBeanFactory in this case was binding the tableName argument of the enum,
which is the table name string (lower cased): we were comparing
table_name to TABLE_NAME in the queries. This has been fixed: we now
use the enum name for the retrieval queries.
Second, depending on the collation, the queries would return an empty set.
Tests never caught it because the collation wasn't set in our ddl (we
were performing case insensitive comparisons). This has been fixed and closes #101.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
