Bug#238411: ITP: JBoss -- J2EE based application server

["Philipp Hug" <philipp@hug.cx>]

Konstantinos,

sounds good. one thing to think about is support for multiple configuration:

the standard jboss distribution looks like this:
jboss-3.2.3/bin
jboss-3.2.3/lib
jboss-3.2.3/server/all/..
jboss-3.2.3/server/default/..
jboss-3.2.3/server/minimal/..

there are many options to solve this problem:
1. Just one configuration is used e.g. jboss-3.2.3/server/debian/.. all jboss
sub-packages like database, web-console... go in here
2. Same as 1. but create a management tool to create custom configurations (with
their corresponding directories) and let the user choose what to use (--> lots
of work)
3. Same as 2, but let the user do the copying manually. just provide a debconf
interface to choose the configuration he wants to use
4. allow multiple configurations to run at the same time (--> difficult, because
jboss listens on lots of ports, and I'm not sure if we can get rid of all of
them)

J2EE-Idea
This sounds good, although there aren't many opensource j2ee app servers yet and
j2ee apps are not as comptible as they should ;-)
But with jboss it's easy to implement this: just add another deployer directory.

Some other things, that are on my wishlist:
1. apache.conf that includes something like "ProxyPass /jboss
http://localhost:8080/"; (maybe use a different port by default, because this
could cause problems with tomcat)
2. debconf to change the jboss.xml file (enable/disable features,...)
...

philipp