On Fri, 6 Jun 2003 00:01, [EMAIL PROTECTED] wrote:
> Brian,
>
> The XDoclet utilobject pattern caches Remote and (Local Homes the latter
> is of course only valid w/in one JVM), I've seen this mentioned on
> theserverside.com and elsewhere as a best practice, and after digging
> through the spec to
e for JBoss is available, so if one has doubts, one can always "go
to the source."
Dave
Brian Wallis <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/05/2003 08:43 PM
Please respond to jboss-user
To:
[EMAIL PROTECTED], [EMAIL PROTECTED]
cc:
That is exactly what I was looking for Dave.
Thanks very much,
Brian
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 3:01
PM
Subject: Re: [JBoss-user] Should I cache
ejbRefs?
Brian, The XDoclet utilobject
I think they are talking about the EJBHomeFactory pattern as shown at http://java.sun.com/blueprints/patterns/ServiceLocator.html
Brian McSweeney wrote:
Hi
all, my app is fronended
with struts, using local beans.The
local beans use stateless session facades asa
frontend. In a book
discussing st
(not Homes).
Hope that helps.
Dave
"Brian McSweeney" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/05/2003 08:47 AM
Please respond to jboss-user
To:
<[EMAIL PROTECTED]>
cc:
Subject:
[JBoss-user] Should I cach
Hi all,
my app is fronended with struts, using local
beans.
The local beans use stateless session facades
as
a frontend.
In a book discussing struts there is a chapter on
using entity beans which describes how it is a good
idea to cache the ejb refs in application
scope.
The idea is,
