I'm assuming that in a JBoss cluster Enterprise
Applications are distributed from one node (possibly a
Master) to all other nodes (possibly Slaves).
I was considering this with respect to the Jetty
integration.
I'm assuming that a JBoss/Jetty cluster user may wish
to deploy some legacy content, seeing as they have a
shining new cluster available to them, and some
cobwebby old files that they need to make available.
By legacy I mean, content such as html, cgi etc.
I can either ignore the problem, or as I have chosen
to do - consider it (I do so since Jetty is also a
decent WebServer and from a Jetty point of view it
would be good to continue to support this
functionality within a cluster).
I assume that distributable unit of choice here for
web-content is still a WAR (probably within an EAR -
if you wish more control over your context).
Thus if I wish to distribute some static HTML files -
no problem. I can bundle them up into a WAR and hot
deploy them onto one node - and they will be copied
everywhere ?
With CGI things get a little more difficult. Ideally I
would like to bundle up the directory structure into a
WAR and deploy it in the same way as the static
content. However there are two problems with this.
Firstly I would need to specify some mappings for the
CGI Servlet - so it knew which files were scripts and
what was static and secondly JAR seems to throw away
executable bits on files - so unless I build a list of
all of these (we're talking Unix now...) before
archiving, then have the CGI Servlet reset these in
it's init() method, WARs are not going to work for me
here.
Alternatively we could consider another type of
deployable - perhaps a TAR file. So I would drop my
legacy.tar into the deploy directory, whence it would
be distributed to all nodes' TARDeployers for
unpacking....
A nicer idea might be a WEB-INF/cgi-web.xml which just
remembers which files need their executable bit
setting at init() time. This could also store other
information that might be needed such as external
requirements on script interpreters, paths,
environments etc..
A little off topic I know...
In summary,
Is this how RH will distribute Applications ?
Can I deploy into any node directly - or only a Master
node ?
Is there a way to preserve executable bits within JARs
- or do I need to workaround ?
Thanks for your time folks,
Jules
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
