|
|
|
|
3/6/2013 8:30:17 PM
any plugin service
|
3/4/2013 9:31:12 PM
serlvet
|
3/4/2013 5:09:31 PM
shouldn't return null.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/2/2013 11:49:43 PM
introduced a regression as
payment methods were tied to plugins, not instances.
I'm not sure though if using the OSGI service name in the long run is
the way to go. Could we instead auto-discover at runtime which plugin
is supposed to handle a given payment method?
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/2/2013 9:59:07 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 11:19:09 PM
is generic enough to have it in the PaymentPluginApi.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 9:31:59 PM
match the value passed in the
addPaymentMethod call. Tests broke after 00dc2dbadd8ec3e2cdd524b9e683f955dac67a8f.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 9:00:38 PM
may not have a default payment method yet.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|