What we are doing is using JavaBeans to collect data from Entity or Session
beans. This seems to work nice in that the java beans are then invoked by
the presentation layer and scoped appropriately. This approach has not
introduced any performance issues.
Just a thought.
-Danno
----- Original Message -----
From: "Rafael Alvarez" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Tuesday, October 10, 2000 2:07 PM
Subject: Re: Performance
> Hi,
>
> This mail is useful only if you're using entity EJBs.
> Because EJB is RMI on steroids (is more than that, but let's keep it
> simple), if you need more that one entity to get the data you need for
> the presentation layer you end up opening a lot of rmi connections,
> with the overhead it implies.
> The solution is simple, yet elegant: Create a Session Bean, collect
> all the data (raw data, not the remotes) from the Entity Beans and use
> that for the presentation. That way you use only one rmi connection.
>
>
> Hope this help.
>
>
> --
> Best regards,
> Rafael mailto:[EMAIL PROTECTED]
>
>
>
>
