Is there a reason why an expression can not be used for 'invalidValueMessage' on the @PossibleValues annotation. The @Validation.message() resolves any expression used in the text.
Currently the text is passed directly to the MessageFormat object:
Caused by: java.lang.IllegalArgumentException: can't parse argument number Parent.Id == null ? "" : concat("' for", Parent.Id, "'")
at java.text.MessageFormat.makeFormat(MessageFormat.java:1339)
at java.text.MessageFormat.applyPattern(MessageFormat.java:458)
at java.text.MessageFormat.<init>(MessageFormat.java:350)
at java.text.MessageFormat.format(MessageFormat.java:811)
at org.eclipse.sapphire.services.internal.ModelBasedPossibleValuesService.getInvalidValueMessage(ModelBasedPossibleValuesService.java:125)
at org.eclipse.sapphire.services.internal.PossibleValuesValidationService.compute(PossibleValuesValidationService.java:72)
at org.eclipse.sapphire.services.internal.PossibleValuesValidationService.compute(PossibleValuesValidationService.java:1)
at org.eclipse.sapphire.services.DataService.refresh(DataService.java:103)
... 153 more
When using Possible Values within tables, it is essential to supply an identifier where the error occurs.
] 
Search
Help
Register
Login
Home
