I have a page that acts as an editor for multiple distinct entity classes- Person and Skills. So when I save my changes, I end up having two separate calls:
personRequest.persist().using(person) skillRequest.persist().using(skill) Is there a way to create an aggregate parent entity for these two classes, so that fetch/persist can be done in a single call on the aggregate object? The advantage would be (presumably) a common transaction on the server end, and also simplification of editor bindings on the GWT side. I'm aware that I can already do this (via CASCADE) if the two entities already have a relationship, but sometimes the relationship exists only as an abstraction on the GWT page. It strikes me that this is sort of like a ValueProxy in reverse, where the real entities would be embedded into the aggregator class instead of the other way around. -- 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.
