Hey
Aaron Mulder wrote:
> On Tue, 24 Oct 2000, Rickard Oberg wrote:
> > Nope, I think it would be better to add this to
> > org.jboss.ejb.deployment.JRMPContainerInvokerConfiguration where it belongs.
>
> Okay, the change is in CVS. This coincided with moving the
> standardXXX.xml files out of JARs and into the conf directory. In order
> to change the port that the RMI objects are registered on, edit
> conf/standardjboss.xml and change all appearances of "4444" to something
> else. Or you can remove the parameter altogether and then each object
> will pick its own port to listen on. It's in there once for each
> container configuration.
Remember that explicitly setting port to "0" will also give you a
Whatever Port(tm). It may be good to keep the setting in there, but set
to 0, so that you can easily change to something more explicit later on.
> You still can't run the server twice out of the same installation
> directory unless you remove the port setting and use anonymous ports
> (because both instances of the server read the same standardjboss.xml
> file). However, you can remove the parameter, and then set up a second
> set of configuration files as Rickard discussed in another thread, and
> that should work.
> I'll add this to the discussion in the manual on default ports and
> multiple server instances per machine.
I have thought about the configuration thingy and have an idea. The
current workings are not very good, and a simpler and better solution
would be like this:
Instead of having the startup parameter mean "look in foo.conf,
foo.jcml" etc., it should mean "look in foo/jboss.conf, foo/jboss.jcml"
etc., i.e. it should be a directory prefix. This would have the benefit
of having the same name for each conf file (which should reduce
confusion considerably, and it would also make it easier to actually
locate the files. Why? Because all we have to do is add
"../conf/<confname>/" to the app classloader and then code can access
files such as "../conf/<confname>/jboss.conf" by simply doing
getClass().getClassLoader().getResource("jboss.conf")!!! So, all we have
to do is change what directory is added to classpath and then all the
jBoss code can access those files.
Makes sense? It's a 1-minute fix too, so it's very to implement.
Let me know if there are any objections, otherwise I will go ahead with
this (i.e. move jboss.conf+jboss.jcml to
/jboss/jboss.conf+/jboss/jboss.jcml and add ../conf/<confname> to
classpath).
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]
