> In some cases, we could have the necessity to only get read-only data
> (perform a sort of lookup) to display them to the end-user so that he
> will be able to select the right objects he want to work with.
> ...
> I know that with the current version of the EJB specs (1.0) entity beans
> are optional but I would like to know:
> - Are they any EJB server/container vendors that provide added features
> to allow developers to perform a search without instantiating the Entity
> Beans for lookup reasons?
My company's product, Novera jBusiness, is an application server that
offers this capability. jBusiness supports session and entity beans,
but also offers a number of facilities designed for higher
performance. The basic idea is to avoid the overhead of creating an
entity bean for each business object, and the overhead of a remote
call for every method invocation on a business object.
The application server manages a cache of business objects which
represent information retrieved from the database. These can be
accessed by a client in the usual EJB style, as remote objects with
the overhead that has already been described.
Alternatively, lightweight objects representing the state of a
business object can be passed by value. For example, suppose you have
a AccountEntity bean. You can obtain the state of this object as an
AccountValues object, and pass it by value to the client. The client
can use AccountValues for display purposes. The client can also update
these Values objects, and send them back to the server so that the
database can be updated.
Many of our customers write applications in this style and the
resulting applications have excellent performance.
John Piekos
Novera Software
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
