:
EntityManager has a getTransaction method that you can use along with the
constructor I mentioned previously to explicitly begin and end transactions
in your code.
derek
On Fri, May 15, 2009 at 11:45 AM, ngug naftoli...@gmail.com wrote:
One entity group per transaction is a GAE requirement
think that the current form processing code has any facility for a per-form
exception handler, although that might be a useful feature.
Derek
On Tue, May 19, 2009 at 1:09 PM, ngug naftoli...@gmail.com wrote:
Sorry for the delay in responding. My question was not about
transaction API, my
בה using the FormProcessor, all my exceptions seem to have
disappeared. Now I have a problem, that although seems to be a
separate problem is very much intertwined with everything else and I
think it's really one issue.
The page basically looks like this:
Nature Name: [text field]
Locations:
P.S. I wrote a method to handle the boilerplate of opening/closing/
checking whether to rollback transactions. Shouldn't ScalaJPA have
such a method? Or does it?
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
, May 19, 2009 at 2:07 PM, ngug naftoli...@gmail.com wrote:
P.S. I wrote a method to handle the boilerplate of opening/closing/
checking whether to rollback transactions. Shouldn't ScalaJPA have
such a method? Or does it?
Thanks.
--~--~-~--~~~---~--~~
You
and books.
Derek
On Tue, May 19, 2009 at 2:42 PM, ngug naftoli...@gmail.com wrote:
On May 19, 4:31 pm, Derek Chen-Becker dchenbec...@gmail.com wrote:
It should already. The closeEM method on both LocalEM and JndiEM checks
to
see if the transaction has been marked rollback only and should
One entity group per transaction is a GAE requirement. But my question
about handling transactions was more specific - because form
processing is specified piecemeal in separate closures, you can't
use the normal try/finally. It seems a little too much effort to
create a hidden field before and
In any case, how would I handle transactions manually? An SHtml.hidden
before and after every form? It's confusing because SHtml lumps the
get and set side by side when they happen in two different requests
and the entity needs to be reloaded in between. In any case, GAE seems
to require tighter
In any case, how would I handle transactions manually? An SHtml.hidden
before and after every form? It's confusing because SHtml lumps the
get and set side by side when they happen in two different requests
and the entity needs to be reloaded in between. In any case, GAE seems
to require tighter
In any case, how would I handle transactions manually? An SHtml.hidden
before and after every form? It's confusing because SHtml lumps the
get and set side by side when they happen in two different requests
and the entity needs to be reloaded in between. In any case, GAE seems
to require tighter
Well since he may have meant that, to disable it you put in Boot:
LiftRules.enableLiftGC = false
On May 12, 8:01 pm, Timothy Perrett timo...@getintheloop.eu wrote:
This im aware of - however it just seems more likely that if he
asked for comet behavior by inserting the comet tag he would
I guess I should include the views too to make it easier to reproduce
the problem. Here is edit.html:
lift:surround with=default at=content
head
titlelift:loc
lift:Natures.newOrEdit
if:editEdit/if:edit
Thanks for looking. The stack traces aren't very helpful because they
concern the state which is caused by the previous sequence of events.
Anyway, why is there a transaction taking place in the first place?
--~--~-~--~~~---~--~~
You received this message because
Personally I couldn't find anything free, except for EatJ, which has a
free trial. Apparently you have to restart the server every 6? hours
in trial mode. Anyway, soon after I registered it didn't let me log in
anymore, not sure why.
On Apr 20, 8:56 am, Jeremy Mawson jeremy.mawson.w...@gmail.com
I made the beginnings of a lift app for GAE. It's for a volunteer
medical assistance organization, to manage requests that they get.
Every request has a nature, e.g., transportation, hospital visitation,
etc. Each nature has a OneToMany association with a
NatureLocationType, which means that when
15 matches
Mail list logo
