Hi JD, We released the api for this feature ahead of the backend support so you'll need to wait for the next release (currently making its way through QA) to be able to take advantage of transactional tasks. Once the feature is enabled, tasks that are added to queues when there is an active datastore transaction will be automatically enlisted in the datastore transaction so most of the time you won't actually need to get ahold of the active com.google.appengine.api.datastore.Transaction. That said, you can always get ahold of the active datastore transaction via DatastoreService.getCurrentTransaction().
Hope this helps, Max On Mon, Jan 25, 2010 at 5:11 PM, JD <liva...@gmail.com> wrote: > The Queue interface has a method: > TaskHandle add(Transaction txn, > TaskOptions taskOptions) > > > How does one get a handle on > com.google.appengine.api.datastore.Transaction in the first place ? > The persistent manager only returns a transaction of type > javax.jdo.Transaction which is not compatible with > com.google.appengine.api.datastore.Transaction expected by the task > queue API. > > > Is this a bug ? > > JD > > -- > 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<google-appengine-java%2bunsubscr...@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.
