Problem with custom validated data types using domain on 11g

Question

Hi,
I ' m on a migration process from 10 to 11 and I notice that a custom domain didn't work correctly anymore
to be more specific every time that I was submiting a page a was getting an error cannot convert from myclass to oracle.jbo.domain.String
I search the forum and I saw a similar problem
Cannot convert type class java.lang.String to class oracle.jbo.domain.Clob
at which Frank says that it is a known bug and suggests a work around.
I use the workaround and it worked but some more issues came up:
1. If the validation fails I get the error that I throw at the validate method not in a popup with just my message
but in the whole window with the whole error stack, meaning that my custom validation is not handled like native ADF validation errors by
the framework (at 10.1.3.4 worked OK)
2 If i dont give a value at the attribute in the validation phase mdata variable is not null but is length is zero (at 10.1.3.4 its value was null)
public class AFM implements DomainInterface, Serializable {
public AFM(String val) {
mData = new String(val);
validate();
private String mData;
protected void validate() {
// ### Implement custom domain validation logic here. ###
mData==null // returns false
mData.length()==0 // returns true
3. Can i force validation only for new or updated values? I saw that the validation process is taking place every time a row is fetched.
This is not only a performance issue, the bigger problem is that if a fetched from the DB value fails the validation an error is return but the
user cannot change the value to correct it.
TIA
Tilemahos

Answer 1

since i don't get any answer I wonder if i should have use a more provocative title like
"custom domains in 11g don't work"
is it true?
Tilemahos