Not opposite, just orthogonal. One is deployment, one is jmx
management. Either way, JBoss has a lot to offer. In Advanced
Training, I seem to remember Marc saying there was someone already working on
making JBoss the basis for gui development. Hope they can weigh in.
Absolutely! In fact, here is an snippet from an
email I sent directly to
Dimitri the other day as a followup to my
question about any java client
application frameworks having been built
on Jboss already:
<quote>
Dimitri,
Well, I'm specifically talking about constructing a Swing-based (read:
Java rich client) platform that offers functionality needed by a desktop
application just as certain features are needed by a j2ee platform. For
a rich client, you need things like:
1. plugins that can be inserted and removed at a minimum at startup,
maybe even hotdeployed. Plugins could be components that produce visual
functionality, or not -- think of pluggable Javabeans, but with a
context of the application they are in and the other services around
them (more like EJBs I guess).
2. timers like the scheduler in Jboss
3. management using JMX, which you get for free in Jboss, since its
built on JMX 4. a unified method of component communication that offers
a better loose coupling mechanism than just the observer/observable
pattern 5. A graphical framework from which this platform could offer a
starting point for the ui, with pluggable menu services, etc.
...And so on...
I guess its little like Lisp is the building blocks to Emacs, and with a
new library installed in emacs you often get new menus and
options/services that extend your application.
My idea is that the Jboss kernel, with JMX and some of their core
services, could be used as a starting platform for the development of a
rich client platform. Just as we now develop EJBs for our business tier
and servlets for the bridge between the web tier and business tier, and
JSP for our view (or a similar solution), so could you begin to identify
and unify simliar needs for a swing application. Using the Jboss kernel
would be, it seems to me, a great starting point to begin building this
platform and in essence craft a true J2SE that is more akin to J2EE than
a mismatch of java libraries put together under a single umbrella (real
component development beyond javabeans, etc.).
So, based on your email from earlier today, I'm talking about the
opposite I think - not launching swing from a Jboss server, but rather
constructing a swing-based platform on top of the jboss kernel, with
some contextual information provided the application about its
environment and the services available.
Thanks for your interest. Does this make more sense? Anything I could
better clarify? James
</quote>
> -----Original Message-----
> From: Greg Turner [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 16, 2002 3:48 PM
> To:
[EMAIL PROTECTED]
> Subject: Re: [JBoss-user]
Launching Swing Applications from
> JBoss 3.0.0
>
>
> > The potential of JBoss is not limited to EJBs.
>
> Once this is understood, then the true power of JBoss starts
showing.
>
> Greg Turner, JBoss Authorized Consultant
>
> Tiburon Enterprise Systems
> http://www.tiburon-e-systems.com
> Box 1171
> Tiburon, CA 94920
> 415-332-3363
>
>
>
>
>
-------------------------------------------------------
> This sf.net
email is sponsored by: OSDN - Tired of that same
> old cell
phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1>
&refcode1=vs3390
>
>
>
_______________________________________________
> JBoss-user mailing
list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/j>
boss-user
>
-------------------------------------------------------
This sf.net
email is sponsored by: OSDN - Tired of that same old
cell phone?
Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing
list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
