Hi!
Sacha Labourey wrote:
> I have several general questions regarding JBoss. If you are not hungry
> enough to
> answer them all, do not hesitate to just answer some!
>
> - Does JBoss support some sort of (automatic) load-balancing or fail-over?
Net yet, will be soon.
> - (depending on previous answer) Is is possible to deploy an EJB
> application
> on several servers at the same time (for load balancing or
>fail-over)?
Not yet, will be soon.
> - As I tried JBoss, I have maybe not seen every tool available.
> Consequently:
> - Is there any GUI tool for "physical" deployement?
You can edit deployment files (jboss.xml and ejb-jar.xml) through the
EJX (/bin/ejx.jar) tool. You can deploy EJB's remotely by using the
/client/deploy.jar tool. You can deploy through webinterface by surfing
to localhost:8082 and invoke "deploy" in ContainerFactory with the URL
to the file you want to deploy.
> - Is there any GUI tool for EJB management (who's alive, on which
>server,
> which load, stats, ...)?
No, no yet.
> - Is there any GUI tool (linked to the EJB management tool for
>example)
> for manually changing the location of an EJB (to force an
>EJB to
> work on a particular system for example)
No, since there is no clustering.
> - Is it possible to automatically upgrade an EJB while it may be used
> (compatible with the old one)? (maybe it is more an EJB question)
Yes, we support hot deployment. If you deploy by putting your JAR file
in /deploy, simply put the new version there and it will be upgraded
into the server.
> And for the end, a more EJB question:
>
> Imagine a situation where each workstation should run JBoss and some EJB.
> These EJB should be able to access some shared ressources (EJB, MOM, ...) on
> central servers (all running JBoss) but may also be deconnected from the
> network (for any reason) and should be able to continue working (and
> postpone their communication with central sites). How this may work?
Should be no problem.
> Is
> there in EJB the idea of "domain" which may help? When accessing the JNDI
> context to resolve some names, some should be local (i.e. available even
> when the station is disconnected from the network) and some should be global
> (i.e. centrally managed by the servers for example and made availble only
> when stations are connected or, even better, replicated/synchronized on each
> station). I hope you have understood the general idea of my problem. Any
> idea/hint/... for this kind of environment would be greattttly appreciated.
> It is always possible to develop this again and again but I secretly hope
> the EJB/JNDI/... environement will be of some help for this ;)
Yes, the bean bindings you do in java:comp/env can either be to local
beans in your local server, or to beans running on some other (central)
server.
There is no notion of synchronization, but this is an application notion
that you could accomplish anyway. For example, let's say you have an
EntityBean both "locally" and in your central server. First you do local
changes. Then you want to synch that with the server. You should then
have some session bean in your local server which you can tell "I am now
connected. Synch this local EntityBean with the central server's
EntityBean". The session then extracts state from the local EntityBean
and applies it on the server, either by modifying existing bean
identities, or by creating/removing on the server. You will need some
kind of log locally to keep track of what changes to propagate.
So, in short, yes that kind of application is possible (and I would be
*very* interested in hearing about the results!), but most of the stuff
is application specific so you would have to do it by yourself.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
