|
Generated by JDiff |
||||||||
| PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES | |||||||||
This file contains all the changes in documentation in the packageorg.cyclos.impl.bankingas colored differences. Deletions are shownlike this, and additions are shown like this.
If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.
Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.
Checks that the given account is active, throwing an IllegalActionException in case it is an inactive user account, or the owner is inactive @see #checkActive(Class AccountServiceLocal, void createMissingOrActivateAccount(UserAccountType, ProductOwner)AccountOwnerInternalAccountOwner)
Creates the account for the given account type if it still doesn't exists for the given ProductOwner, or activates it. If the account alreadyClass AccountServiceLocal, void disposeAccounts(User, Collection<UserAccount>)existsexists and is active, doesnothing @param upperCreditLimit @param creditLimitnothing
Class AccountServiceLocal, List<AccountWithStatusVO> getAccountsWithStatus(InternalAccountOwner, Date, Date, boolean)DisposesDisables theaccounts for the user. Thegiven accountsare either removed (if there is no account history) or disabled (if there isofan accountthe givenhistory)user.
Note that the calling method is responsible for checking if this account really needs to be disposed (for example because it is associated via another product).
The method does the following:@param user @param lostAccounts the accounts to be disposed of @throws IllegalActionException if any of the accounts cannot be disposed of because of existing dependencies (scheduled payments, amount reservations, balances).
- cancel all user's webshop orders with any pending status.
- delete all user's webshop orders which are still in a shopping cart
- cancel all scheduled payments to the account being lost, plus notification to users involved.
- remove or disable the account
- Check if the currency of the account is also lost, that is: not associated via another account of the same user. If the currency is also lost:
- set all ads which refer via their price to this currency to status DISABLED
- disable all user's delivery methods referring to the currency
Similar to .list(AccountOwnerInternalAccountOwner), but returns each account with the account status, at the given time point.
Cancels all payment requests from or to the givenuseraccount
Applies a transfer, that is:Class RateHandler, FromRatesData getFromRates(Account, TransferType, BigDecimal, Date, RateVisibility)@param transfer the transfer to be applied.
- gets the rate from the fromAccount
- sets those to the transfer
- gets
There is nothing saved tothe rate of the toAccountany- merges
accounts,transfer and toAccountasRatesthis- persists from rates if changed due
happensto creationonly- persists
atto accountclosingrates.
gets the future rates of a from accountforthatawill be after the transaction has been applied. It takes into account:
* null rates are replaced by init values
* if the balance isn't sufficient creation values are applied for the unsufficient part, and the rateBalanceCorrection and virtualRatedBalance are updated. In this case,FromRatesData.changedDueToCreationis set to true. This does NOT happen in case of an unlimited account.
* transfer type defaults are applied if needed.
* maturity policy other than always may result in transfer rates and from account rates that differ from each other. Under normal circumstances from account rates and transfer rates are always equal, but maturity policy other than aALWAYS may enforce a zero D-rate on the transfer, thus leaving the from account with a higher D. This is reflected in the special fields of the FromRatesData.
@param fromAccount the account which is the from account of the transfer @param transferType the transfertype of the transfer @param amount the transfer amount @param date the processing date of the transfer; if null, now is used. @param visibility the visibility to be applied. This is usually RateVisibility.PARAMS in case the result is to be shown directly to users, or RateVisibility.ALL in case it is further processed in a transfer.
Adapts the from account rates after it has been retrieved from the account, and adapts the fields to specific additional rate rules. The rate balance correction and virtual rated balance are NOT adapted. The following rules are applied:*Note that there is no check whatsoever if the transferType is accessible for the fromAccount. This is considered the responsibility of the calling method. @param rates - the rates as retrieved by requesting the rates from the from account, without considering the balance or the transfer type. @param fromAccount @param transferType @param amount
- in case of D-rate: if the from account is unlimited and there is a creation value D-rate set on the transferType,
this is used asthethe D-rate.*- in case of insufficient balance: the total amount is considered to consist of two sets: one set coming from
thethe from account, beingthethe complete balance and having the rates of the from accounts, and another set whichisis newly created against the rate creation values, andbeingbeing the transaction amount minus the balance.These sets are merged in order to get the rates to be used for the transfer.
If there was insufficient balance, the FromRatesData.changedDueToCreation field is set to true.
Cancels all scheduled payments to or from the givenuseraccount
getsGets the authorizable accountTypes which can be viewed by the accountOwner
Returns a validator filled with all common validations, plus some other data which was already loaded.Class TransactionServiceLocal, T receive(InternalAccountOwner, Callable<T>)@param validateNFCChallenge only taken into account if the payer was located by a NFC token.
Sets up the session data for receiving a transaction from the given user, invoking the given callable in it.Class TransactionServiceLocal, String ATTR_FROM_OWNERPrincipalType may be null
Script bind variable: theAccountOwnerInternalAccountOwner from