> Relative to HttpSessions, SFSBs provide a better separation
> of presentation
> logic from application logic. If the application state is in
I agree, but
> SFSBs rather
> than HttpSessions, it is easier to use multiple presentation
> layers with a
> given application or parts of an application (e.g, a web
> interface, a Swing
> interface).
>
I think that's a myth. SFSB methods are tightly coupled to the presentation
layer. You typically have one-method-per-page, or, if using frames,
one-method-per-page-per-frame. While it would be possible to reuse the SFSBs
in the application I'm working on for a Swing UI, it would be severely
constrained.
Has anyone written a dual Swing/HTML interface? And was it designed as a
dual interface from scratch, or was the later interface retrofitted on an
existing application?
- Avi
--
This signature intentionally left blank.
===========================================================================
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".
