Doesn't look that wrong. You need to add validation annotations to the
proxy class if you want to do client side proxy validation.
As you want to reuse the validation annotations on the server I would think
about defining an additional interface IEmployee so that your server
Employee class do not have to implement the EmployeeProxy. Your server
Employee is not an EmployeeProxy so it should not implement that interface.
I guess its better to do:
interface IEmployee {
//methods with validation annotations, probably with client and server
validation groups.
}
interface EmployeeProxy extends EntityProxy, IEmployee {
EntityProxyId<EmployeeProxy> stableId();
}
class Employee implements IEmployee {
//implement methods.
}
Downside is that your EmployeeProxy now always has the same methods as your
server Employee and sometimes that is not desired as a proxy could only
represent be a subset of the server class. But in that case you could
create an additional lite interface:
interface IEmployeeLite {
//subset of methods with validation annotations
}
interface IEmployee extends IEmployeeLite {
//rest of the methods with validation annotations
}
interface EmployeeProxy extends EntityProxy, IEmployeeLite {
//now only contains subset of employee methods.
}
class Employee implements IEmployee {
//implementation
}
Thats not tested by myself, but I think RequestFactory and the Validation
framework should be able to handle this.
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/gYCWAm137uIJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
