Hey Thomas,
thanks for your reply and support.
Using the static injection works fine and now the Provicer
gets injected.
I will change this to service as soon as I got time for that.
So, thanks again for your help and patience :)
Regards,
Manuel
--
You received this message because you are s
On Tuesday, February 5, 2013 8:48:35 AM UTC+1, Manuel wrote:
>
> Hey,
>
> I had a look and used this to implement a servlet-module:
> http://code.google.com/p/google-guice/wiki/ServletModule
> My Module looks like the example from your session per request link:
> http://code.google.com/p/google
Hey,
I had a look and used this to implement a servlet-module:
http://code.google.com/p/google-guice/wiki/ServletModule
My Module looks like the example from your session per request link:
http://code.google.com/p/google-guice/wiki/JPA#Web_Environments_%28session-per-http-request%29
In the web.
On Monday, February 4, 2013 3:39:14 PM UTC+1, Manuel wrote:
>
> Oh, ok :)
> But actually I dont got a ServletModule... Or do I got one?
> Or how to implement one?
>
> So if i get this implemented, I got to use @Transactional and @Inject
> annotations on my employee class, right?
>
If you don't
Oh, ok :)
But actually I dont got a ServletModule... Or do I got one?
Or how to implement one?
So if i get this implemented, I got to use @Transactional and @Inject
annotations on my employee class, right?
--
You received this message because you are subscribed to the Google Groups
"Google Web
On Monday, February 4, 2013 1:27:36 PM UTC+1, Manuel wrote:
>
> Hey,
>
> thanks for your replies. I just had a look at Spring and OpenSessionInView.
> I never used Spring so far and it will take some time to get it working I
> guess.
>
You don't have to use Spring. OpenSessionInView is a *patte
Hey,
thanks for your replies. I just had a look at Spring and OpenSessionInView.
I never used Spring so far and it will take some time to get it working I
guess.
Will I need to implement the whole spring stuff or is there just a .jar and
some code for my web.xml and it will work ?
Goes this wi
> both, findEmployee() and persist() created a new EntityManager() and
> closed it after the work is done.
> So each request creates a new EntityManager instance and close it.
*Request updateReq = request.persist().using(editableEmployee**);*
This request once fired to the server will first
On Monday, February 4, 2013 11:16:50 AM UTC+1, Manuel wrote:
>
> Hi Jens,
>
> both, findEmployee() and persist() created a new EntityManager() and
> closed it after the work is done.
> So each request creates a new EntityManager instance and close it.
>
You SHOULD (as in “must unless you really
Hi Jens,
both, findEmployee() and persist() created a new EntityManager() and closed
it after the work is done.
So each request creates a new EntityManager instance and close it.
But when i want to persist() my Entity (that i received from server, and is
already stored in the db), it says its
findEmployee() will be called before calling the instance method persist()
so persist operates on a closed EntityManager I guess?
In general you should use a single EntityManager instance for a single
server request. Typically you could create a single EntityManager instance
in a servlet filter
Hi everyone,
I just started with GWT and Im using RequestFactory and JPA (Hibernate).
I got a View that provides a List of records and the possibility to update
these records (create, update).
When I implemented the update - Method, I recognized that I got to get the
entity that I want to edit,
12 matches
Mail list logo
