Hello. I'm trying to create a service method that encapsulates a particular business logic. I want to make this feature transactional such that its job is accomplished atomically(?). The problem is the service logic involves accessing different entities that do not belong to the same entity group which is not allowed in GAE.
At the moment, I've temporarily disabled transaction management to the service method. However, I feel I'd need to manage transactions eventually. I'm thinking of revising the model design but from how I see it, the model classes are good as they are--unrelated by ownership. Btw, within the service logic is some methods that are transactional. I'm using Spring framework to annotate transaction management. Can anyone help me on how I can go about this? Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
