ok i finally got this sorted.
it seems that i was making life too difficult by making tests
transactional.
by removing the @transactional on unit tests everything works nice and
simple.
thanks for your help
-lp
On Nov 15, 4:51 pm, lp lucio.picc...@gmail.com wrote:
hi vikas
thanks for the
hi vikas
nice blog u have there. However i cant reproduce your results the unit
test with spring.
can u post your spring config to see what i have done wrong.
thanks
-lp
On Nov 13, 3:58 pm, Vikas Hazrati vhazr...@gmail.com wrote:
You could get more information on the way we set up our testing
hi lucio,
I have added the requested information as an answer to your comment on
the blog post.
http://thoughts.inphina.com/2010/06/28/unit-testing-maven-based-jpa-application-on-gae/#comment-347
regards | Vikas
www.inphina.com
On Nov 15, 4:23 am, lp lucio.picc...@gmail.com wrote:
hi vikas
hi vikas
thanks for the spring config.
i got the same config but still cant get a unit test to persist data,
and then execute a query on it.
i noticed that your config does not use
bean
class=org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor
/
how does the
You could get more information on the way we set up our testing infra
here
http://thoughts.inphina.com/2010/06/28/unit-testing-maven-based-jpa-application-on-gae/
Regards | Vikas
www.inphina.com
On Nov 10, 2:37 pm, lp lucio.picc...@gmail.com wrote:
hi all,
i have been attempting to convert
Hi,
Entities that you persist in the datastore are grouped in so called
entity groups for reason of scalability and transactionality
That means that the ds groups your entities on various data servers
according to their keys: this mechanism is not transparent - it
generates the exception that
thanks for the detailed response didier.
the layout of the entities is fine, as transactions are not used in
the application itself, but as a artefact for unit testing.
i only placed the unit tests into a transaction for the purposes of
flushing the to entityManager.
since txn dont work for
Hi,
Instead of flushing, did you try a PersistenceManager.close() that
should lead to the same effect ? After the close, you get a new pm via
the PMF and that should do it.
regards
didier
On Nov 10, 10:57 pm, lp lucio.picc...@gmail.com wrote:
thanks for the detailed response didier.
the
Instead of flushing, did you try a PersistenceManager.close() that
should lead to the same effect ? After the close, you get a new pm via
the PMF and that should do it.
i dunno if i can do that so easily as the entityManager is injected by
spring.
i have a very very very simple example that
