Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of jaydmchugh@gmail.com designates
 209.85.221.201 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=pIoLMbpKEaQRNFDMvRMDHBuhMIIHMl8rRA5atoAGV6PY158loexWatebJCjbDqd+vq
         e3yKa17IuGYDZ4ZELicN7MmnBwoiUWG0vY0aLnZep/Jf/GxyMUUhYcn3p3OzsJlKEH93
         yEQSFfRtcimC/F/RRlvyd/8TMZ7ZE8NGRltyE=
Message-ID: <4AAFE0AF.601@gmail.com>
Date: Tue, 15 Sep 2009 13:45:03 -0500
From: "Jay D. McHugh" <jaydmchugh@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: user@geronimo.apache.org
Subject: Re: EntityManager & Servlets
References: <25221488.post@talk.nabble.com>
 <slrnh9nbv3.g9b.fredrik@scout.jonson.org> <25226546.post@talk.nabble.com>
In-Reply-To: <25226546.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Sorry for the late reply to this.

Geronimo should not allow you to add container managed entity managers
to servlets.  They would not be thread safe.

I haven't looked at the example in a while - but I believe it is using a
stateless session bean to access the entity manager.  That is perfectly
acceptable (and correct)...

I just took a look at the example and it does in fact use a stateless
bean (AccountBean).  So, that is why it is able to use container managed
persistence.

I don't think that it would actually make projects simpler to move the
data access logic into each of the servlets that need it.  For me at
least, centralizing the logic into session beans means that I am forced
to consider exactly what I will be doing with the data and only write
the code once to do it.

Hope that helps,

Jay

tornike wrote:
> Yes, but if it's in their example maybe it's OK for Geronimo to use container
> managed EntityManager with the servlet and there won't be any threading
> issues. If it's true then we wouldn't need any EJB's in the project and
> simply communicate to JPA entities even when using container managed
> EntityManager. As far as I know this method is discouraged but if it's ok to
> do in Geronimo it would greatly simplify many projects. 
> 
> 
> 
> Fredrik Jonson-3 wrote:
>> In <25221488.post@talk.nabble.com> tornike wrote:
>>
>>>  EntityManager is not thread safe and it should not be injected into the
>>>  servlet. (container managed one) However in the example of ejb-JPA 
>>>
>>> http://cwiki.apache.org/GMOxDOC21/container-managed-persistence-with-jpa.html
>>>
>>>  I have tested the example works without problems so are there conditions
>>>  when it can be done or am I understanding it the wrong way?
>> I'd say the example is wrong or at least careless. So I'm also interested
>> if someone thinks otherwise.
>>
>> If I would have done it I'd inject a EntityManagerFactory in the servlet
>> and
>> acquired a new EntityManager from the pool for each request to doGet
>> method:
>>
>> public class Example extends HttpServlet {
>>   @PersistenceUnit
>>   private EntityManagerFactory emf;
>>
>>   @Override
>>   protected void doGet(HttpServletRequest request, HttpServletResponse
>> response)
>>     throws ServletException, IOException {
>>       EntityManager em = emf.createEntityManager();
>>       // do stuff
>>
>> -- 
>> Fredrik Jonson
>>
>>
>>
>