|> 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. | |JMX. yes and no, need distribution of JMX instances and access to the global naming structure. JMX could be it, if we distribute it and sync on several nodes. | |> 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? | |No, we do not want to tie ourselves to LDAP. hmmmm the storing mechanism is orthogonal to the jndi namespace. We work on the visibility, we don't really say anything about the persistence. In fact we would want to replicate the namespace ala weblogic, and whether we move from memory to disk is open at this point. |> unfortunately one needs a baseDN, for looking up, as a commandline |> parameter. | |We could change the bootstrap so that if a URL is given as configuration |name, then that is used. E.g. "default" -> "../conf/default/" is used, |but "http://somehost/jbossconf/" -> load configuration files from that |URL. The problem with that comes with saving new configurations (i.e. |the .jcml files). May not be a big problem though. | |For more discussions on this, please use jboss-dev or put a RFE in |BugZilla. yes on both accounts, we really need to streamline ideas here... bax, please follow it marc | |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] | |
