I mean, why have inline SQL in the entity bean, or even helper classes which
manage the interaction with the RDBMS when you could have a session bean do
the same. For instance, the session bean would have insert(), delete(),
select() and update() methods. Then you have
session bean facade --> entity --> data access session.
Now you can use the same session bean to do lookups, result set listing etc
and use the same logic from your entity bean.
Dave Wolf
Internet Applications Division
Sybase
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Francis Pouatcha
> Sent: Monday, September 18, 2000 7:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Reason for using entity beans
>
>
> Hi Dave,
> can you please clarify what you mean with this:
>
> > Whats the negetive with using Stateless session beans to do the
> actual query
> > itself, and then have the EntityBeans make calls into them? In that way
> >
> > 1) All data access code is still in one place, the session beans
> > 2) The data manipulation and read is still available outside of
> the entity
> > bean for direect access if needed?
> >
> /Francis
> --
> [EMAIL PROTECTED]
>
> MATHEMA Software GmbH
> N�gelsbachstra�e 25 b
> 91052 E r l a n g e n
> D e u t s c h l a n d
> Tel +49(0)9131/8903-0
> Fax +49(0)9131/8903-55
> http://www.mathema.de
>
> ==================================================================
> =========
> 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".
>
>
===========================================================================
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".
