Em Qui, 2004-03-18 às 15:58, Philipp Hug escreveu: > sounds good. one thing to think about is support for multiple configuration:
very important... > 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 well, this actually doesn't solve the problem, just bypass it... > 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) Something like the init levels? and the update-j2ee-appserver-rc.d selecting in which configuration to create the links to the deploy dir... it would be nice... > 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 Same as 1... doesn't solve the problem, just bypass (I know bypassing is the easiest way of dealing with a problem:) > 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) I don't know if this is necessary, and I don't have a clue of how to do it... :) > 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. exactly... > 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) how to deal with tomcat is a good question, I use tomcat embedded in jboss, which simpliflies a lot... do we need to ask to split tomcat into tomcat-standalone and tomcat-embedded? > 2. debconf to change the jboss.xml file (enable/disable features,...) very important, since it's a pain to edit that file... daniel
