Hi Florin, It's just not done yet. One issue is that setting the port for JBoss is done in one of the config file I think. So we'll need to include this file in the default Cactus config for JBoss. But then, if you provide your own jboss config, how can the Cactus port setting have any effect on it?
There may be some Jboss system property that I'm not aware of. Thanks -Vincent > -----Original Message----- > From: Florin Vancea [mailto:[EMAIL PROTECTED] > Sent: 06 August 2003 17:30 > To: 'Cactus Developers List' > Subject: setPort is missing on JBoss3xContainer > > Hi all. > > Why there's no > > public final void setPort(int thePort) > > in org.apache.cactus.integration.ant.container.jboss.JBoss3xContainer? > > About all other sibling Containers have it. > > OK, I understand that currently there's no (simple) way to "move around" > programatically an existing JBoss installation, but one should be able to > move the JBoss installation manually, then specify cactus.port=xxxx . > > I have to run a Cactus setup on a server where 8080 is already taken by > another server and I cannot afford to move it. > > If setPort would be available in JBoss3xContainer, then I could setup my > JBoss on e.g. 9080 (which I actually did) and just tell Cactus to look for > it there. > > If it's acceptable, can some of you kind souls make the addition to > JBoss3xContainer, so it can get into the next nightly jar or such? > > Many thanks, > Florin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
