On Thu, Sep 16, 2010 at 3:54 AM, <[email protected]> wrote: > Hmm that's very strange. Our environments appear to be identical. Is there > anything else I would have to do in server.xml or anywhere else that is > non-default, in order to be able to use these additional schemas? Even > despite setting m-disabled to FALSE, they just refuse to appear in any of > the class lists. This seems to be true of any schema that is similar that is > already preloaded, for example the corba one. I am going to try creating a > new one myself to see what difference that might make can you create a new connection to the server in studio and check > > > On 16/09/10 12:19 AM, Kiran Ayyagari wrote: >> >> On Wed, Sep 15, 2010 at 7:42 PM,<[email protected]> wrote: >>> >>> Do you think this might be a bug that's crept into recent version? Can >>> you >>> try it yourself and see what happens? (Very simple to reproduce in >>> Studio). >> >> yeap, I did with server version 1.5.7 and studio version >> 1.5.3.v20100330. I was able to see >> the 'mozillaAbPersonObsolete' after enabling the mozilla schema and >> reloading schema in studio. >> i >
-- Kiran Ayyagari
