Customizing EO validation messages

Question

Example use case (JDeveloper 11.1.1.6):
- I have one EO that maps to one VO that is displayed in two different jsff tabs (tab1, tab2).
- The EO has an attribute (say Myint of type oracle.jbo.domain.Number that corresponds to a NUMBER(10,0) db type).
- Myint appears in both tabs, however in tab1 it is referred as"int1" and in tab2 as "int2".
- The attribute has a validation rule (at EO level) based on the corresponding db type (basically requesting that it is an integer).
I read/believe that validation, if possible should be done at EO level (and it makes sense as you define once and reuse in all screens).
Here are my questions:
1) In the 'Edit Validation rule ' pop-up (EO) I can define an error message based on an key from a rb.
In my case, I have a generic message like 'An integer value is required for the 'Myint' field.'
How can I customize the messages for the specific jsff tabs, e.g., get messages like:
An integer value is required for the 'int1' field.'
An integer value is required for the 'int2' field.'
I want to avoid client validation; however I would like to be able also customize my error message. Is there a way to do this?
I know I can pass a expression to the message text, but still this does not really help me.
Now if I cannot do this, does not this limits the usability of EO validation?
2) Is there a way to have ADF create the red box around the erroneous field. In my view this is nice to have as it directly identifies the issue.
Thanks

Answer 1

Hi,
I am using JDev 11g R2 and it has a red box highlighted for any validation failure of attribute (your point#2) but not sure if it's there in your jdev version :)
Coming to your issue,
For EO, it is always the same field irrespective of it coming from vo1 or vo2 and you don't have control of validation messages of vow/vo2 directly on EO however you can achieve your requirement in couple of ways
Option#1. You can have a custom entity level validation (invoke your custom method with what ever message you want to throw)
Option#2: You can create a transient attribute in your EO of String type and update your VO1 and VO2 to add the new transient attribute and always keep that transient attribute with int1 or int2 (based on your VO usage)
and now in your validation error message of attribute you can use place holder to read the value from transient attribute
for e.g. you error message looks like "Please fill the value for field {field}"
and it will populate field in token list in the same editor window, there in field value give it as Attribute name of transient attribute.
Regards,
Ravi Nuka.