these files should NOT be there... we use the server ones by default
in fact i DONT know why they are there (EJX????)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
|Sent: Tuesday, October 24, 2000 10:15 AM
|To: jBoss
|Subject: Re: [jBoss-User] jBoss, firewalls & SSL/TLS
|
|
|On Tue, 24 Oct 2000, Aaron Mulder wrote:
|> Okay, no problem. It looks like JRMPContainerInvoker loads its
|> content directly from the XML Element in the new MetaData scheme, so that
|> should be a trivial fix. I'll go ahead. I'll make it default to
|> anonymous ports if the tag is not present, so you only specify it if you
|> have something to specify.
|
| I remember why this is a bad idea. standardjboss.xml is still in
|a JAR, which means that we can't expect users to change it. So if you
|want to run 2 servers on the same machine, you have to create a jboss.xml
|for every EJB JAR, and then make 2 copies with different settings for this
|different server. This is really ugly too.
| I guess the solution is to move standardjboss.xml and
|standardjaws.xml out of the JARs, which is one of the things on my task
|list anyway. I'll play around with that a little. I'd really like them
|to go in jboss/conf, and since that should already be on the classpath,
|this shouldn't be a problem. Any thoughts?
|
|Aaron
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
