Very interesting, Jake, thank you, i'll look into it.
I think i'm solving my problem just trying to modify the status of object
inside a transaction - at the end it is throwing an exception that it can't
commit. I'm testing if it really doing what i need.

-- Tony

On Wed, Apr 7, 2010 at 8:59 PM, jbrookover <[email protected]> wrote:

>
> Finally!  I've found others who are looking into Wicket on GAE.  :)
>
> Something else to look into, that is frequently mentioned on the GAE/J
> lists
> but not here, is Objectify - a very thin layer over the GAE datastore.  I
> was using JDO, PMF, etc and found Objectify to be a pretty easy switch.
> Also, in the process, I discovered several cases where JDO "features" were
> not implemented as I thought.  For example, I thought I could use JDO
> transactions to prevent race conditions in a case where two users were
> trying to create identical objects (when I only wanted one).  It turns out
> that may not be the case and I would need to manage the lock/permissions
> myself.
>
> See:
>
> http://groups.google.com/group/objectify-appengine/browse_thread/thread/d71889d94ebf8302
>
> Glad to find other GAE/Wicket users!
>
> Jake
>
>
> intmanch wrote:
> >
> > Hi all,
> >
> >       I've been actively using wicket on GAE for quite a lot of months
> and
> > I
> > love it, but I've quite serious performance problems. I already checked
> > all
> > the advices to speed up the performance but still is quite slow specially
> > for some requests or opening a bookmarkable page. I don't know what to
> do,
> > I
> > use DataView, that it's quite performant, LoadableDetachableModels
> > everywhere, session is ok in size, so I don't know if there is something
> I
> > can tune on the RequestCycle servlet?
> >
> >       Thanks!
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Wicket-GAE-performance-tp28118591p28164599.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to