Ok, we are back on your initial metadata talk, exactly *what* metadata do
you need in a distributed fashion.
Please make it explicit and on jboss-dev ;-)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Holger Baxmann
|Sent: Thursday, November 02, 2000 10:38 AM
|To: jBoss
|Subject: AW: AW: [jBoss-User] J2eeDeployer broken
|
|
|> Hi!
|>
|> Holger Baxmann wrote:
|> > > > But this is not good. Part of the point is to
|> allow you to run
|> > > > jBoss more than once out of the same distribution, and in
|> order to do
|> > > > this, you need a custom standardjboss.xml and
|> jndi.properties for each
|> > > > configuration (since there are port settings in there). We
|> > > need all to go
|> > > > in conf/<config> not in conf.
|> > >
|> > > Don't worry, this will be fixed. If all else fails, we can
|> always get it
|> > > from the context classloader.
|> > >
|> > or out of a JNDI based metadata storage?
|>
|> No, from the context classloader :-) No need to do it more difficult
|> than it has to be.
|
|but i as a machine independend cluster would be happy to have this
|properties.* in a reachable point handy, don't i?
|
|bax
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
