Gabby,
I don't think that EJB standard provide a way to keep client
applications synchronized, but you'd take a look at Marimba Castanet wich is
supposed to provide a way to push automatically updated applications
to your clients.
http://www.marimba.com
Regards,
Mauro Bertapelle
[EMAIL PROTECTED]
--
Gabby Tal wrote:
>
> Hi all,
>
> We are designing a distributed application based on EJB and the N-tier
> architecture.
> We're using a standalone Java application for the presentation tier (our
> target is Intranet environment)
> There are two issues we're trying to resolve:
> 1. How to minimize the effort of installing (and upgrading) the desktop
> client application considering
> the following facts:
> * The JavaPC or SUN's JavaStation is not applicable in our case.
> * We do consider using InstallShields Java addition.
>
> 2. How to verify the client's version once the user logs in?
> As far as i understand, one way to do so may be to send the clien's version
> to its associated sessionBean following the authentication verification, and
> in case of out-of-date version notifying the user about the version
> incompatability (and optionaly trigger a download process of the latest
> client from a server located in the intranet).
> The question is whether there is a built in mechanism or a standard way to
> do so.
>
> Thanks in advance,
>
> Gabby
>
> ===========================================================================
> 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".
