Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24841075.post@talk.nabble.com>
Date: Thu, 6 Aug 2009 02:41:15 -0700 (PDT)
From: expectnothing <dan.robilliard@gmail.com>
To: user@geronimo.apache.org
Subject: Client Application Container
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi,

I am currently trying to port a number of Java SE applications to a Geronimo
app server.  We are still looking to keep the fat client gui's as our ui for
the applications, with a web app for the read only aspects. 

As I'm new to Geronimo I have a few questions:

If a swing ui is deployed as an app client, what benefits are there over a
standalone client accessing the ejb jars (aside from using the server side
VM)?

Is there any need to deploy standalone clients to the server?

If the swing ui is deployed as an app client, is the user required to have
access to the geronimo bin/client.jar?

If I separate business logic (deplyed as ejb jars) from the swing ui how can
I access these from the deployed ui application.  I am already aware of how
to do this with a standalone client?

Sorry for all the questions, but I am finding some rather large holes in the
geronimo documentation for use with fat clients.

Thanks in advance.
-- 
View this message in context: http://www.nabble.com/Client-Application-Container-tp24841075s134p24841075.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.