Marcus Ahnve wrote:
> The point, at least mine, is to have an independent interface, and then
> use EJB to implement that interface. No one has mentioned not using
> session beans, they are far too useful preventing what you are
> mentioning. But instead of having your session bean client - applet,
> jsp, servlet, application - make a direct call with all the
> InitialContext.lookup etc you wrap that code with an object that has an
> EJB independent interface. That way you are EJB independent from a
> client point of view. And since the session bean is a client to the
> entity bean, let it call a wrapping object too. In the end you will have
> all layers isolated and EJB independent.
>
> Laird, are these your thoughts too, or am I way off?

Nope, you're right on.

Cheers,
Laird

===========================================================================
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".

Reply via email to