I didn't follow the start of this thread, but I'd like to make a suggestin if
it's relevant. I caught the end of a very good EJB presentation at JavaOne last
June and the speaker said thatfor performance reasons, you wouldnot want an
applet to directly interact with an EJB. Using a pieceof middleware would be
much more effecient thanpassing entity bean info backa nd forth from EJB server
to client and back again. Plus, of course, the less coupled the client
(whatever it is) is to a specific middle tierimplementation, the better. That's
not because I dislike EJBs. I think they're a great idea. It's simply an issue
of code maintenance. I'd always vote for a client sending a command object to a
tier twoprogram to ask it to do work on the client's behalf. Just my $.02.
Ken
>
>Hi All,
>
> you can use Visual Cafe to create the jar packager. you add the class,
and it creates the jar with all the classes it uses. but i think you wont like
to buy it only for this... :((
>
> i'm starting to study EJB. what EJB host are you using?
>
> you says that the files needed in a applet are very large. about what
size are them?
>
> thanks,
>
> guich.
>
>
>
>---
>To unsubscribe, mail [EMAIL PROTECTED]
>To get help, mail [EMAIL PROTECTED]
===========================================================================
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".
