Greetings, we're developing a large JEE6 application that relies on
JPA/TopLink2 to serialize its entities.
A subset of such entities is required in the GWT front-end.
e.g., let's name:
entities.A -> one of the entities:
@Entity
public class A implements Serializable{
[...]
int num;
}
entities.B -> another one, containing an object A:
@Entity
public class B implements Serializable{
[...]
int age;
A a;
}
entities.A is strictly internal to the JEE6 application, while
entities.B is used in the GWT front-end; i.e., the GWT front-end NEVER
uses B.a, but it's a field required inside the JEE6 application.
If we add to the GWT modules just B, A is included as well. Is there a
way to prevent such behavior? Is there some sort of "transient"
annotation we can use?
Obviously the issue arises in several classes, and creating duplicates
or interfaces would not be feasible.
Any help will be appreciated...
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
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.
