> Ok, we are back on your initial metadata talk, exactly *what* metadata do
> you need in a distributed fashion.
yeap, you get it.

>
> Please make it explicit and on jboss-dev ;-)
>
i try to become a _user_ of jBoss, so i am right here. what i want to know:
if there is anybody out there who is thinking about driving many, and i mean
many, instances of jboss on some machines, how could one think of administer
and maintain these instances.
the metaphor for this is quiete simple: "what i can't measure (because i
dont have a JNDI context for), doesn't exist."
so we need to have a bootstrap point.
is it possible to make a interceptor for the whole /conf stuff, that at
first look in a LDAP for the config objects and if they not exist, take
these out of the filesystem and put them into these LDAP?

unfortunately one needs a baseDN, for looking up, as a commandline
parameter.

bax
> 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]
>



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to