java.util.Currency field generated with --notNull constraint breaks generated tests

[Andreas Klöber]

If an entity field with type java.util.Currency is created like this:

project --topLevelPackage com.example --projectName example --java 6
jpa setup --provider HIBERNATE --database HYPERSONIC_IN_MEMORY 
entity jpa --class com.example.AccountingTransaction --testAutomatically 
field other --fieldName currency --type java.util.Currency --notNull

the automated tests fail because of the @NotNull constraint on this field:

 
testCountAccountingTransactions(com.example.AccountingTransactionIntegrationTest): [ConstraintDescriptorImpl{annotation=javax.validation.constraints.NotNull, payloads=[], hasComposingConstraints=true, isReportAsSingleInvalidConstraint=false, elementType=FIELD, definedOn=DEFINED_LOCALLY, groups=[interface javax.validation.groups.Default], attributes={message={javax.validation.constraints.NotNull.message}, payload=[Ljava.lang.Class;@3cd713fe, groups=[Ljava.lang.Class;@4c61a7e6}}:kann nicht null sein=null]

This is because of the following generated implementation in aspect AccountingTransactionDataOnDemand_Roo_DataOnDemand :

    public void AccountingTransactionDataOnDemand.setCurrency(AccountingTransaction obj, int index) {
        Currency currency = null;
        obj.setCurrency(currency);
    }

How can this be fixed properly without modifying the generated aspect myself?

[mmartinez]

How can this be fixed properly without modifying the generated aspect myself?

Make a push-in of setCurrency method and modify it.

Regards !

[Andreas Klöber]

Make a push-in of setCurrency method and modify it.

Thanks, that worked!