To me your code looks like a DAO, not a service. This pdf is my reference for
understanding the difference between the DAO and service layers:
http://apress.com/book/downloadfile/2625
Here's an example of how I'm doing it; I have transactions in the service
layer, not the dao layer:
http://code.google.com/p/waitlist/source/browse/trunk/waitlist-gae/waitlist-service/src/main/java/com/objecteffects/waitlist/service/impl/FacilityService.java
But for testing I *am* using transactions around the daos;
http://code.google.com/p/waitlist/source/browse/trunk/waitlist-gae/waitlist-db/
asianCoolz wrote:
> hi, can anyone comments whether my architecture is ok for using
> @transactional with spring on service layer?
>
> http://tinyurl.com/ybmev2b
>
> --
>
> 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 google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
