Sorry for the long delay. I haven't been monitoring this list for a while. Hope this is still relevant.
It looks like the Domain is bootstrapped during initialization of the JAAS LoginModule instead of by the SlideServlet which is the way it should be. In this case the Domain is not given a specific location to load the domain configuration from so it attempts to locate it by itself.
Now I haven't run into this problem. It is probably something specific to the way the application server you are using is starting its services or it may be a classloader issue. The former used to be the case with the Tomcat SlideRealm and I remember working around this by initializing the realm lazily to give the servlet time to bootstrap the Domain first.
Hope this gives you some pointers as to where to start debugging this thing.
Cheers, Unico --
I have had some issues with jar conflicts and sealed packages etc.. Because I am devoping an application server the libraries can be loaded by the web application of the application server which loads jetty. I still have quite a bit to go through in order to eliminate some of these issues first. But I am using slide at the web application level (as the servlet) and also above jetty at the application level for administrating slide webdav users/groups, it may well be I am loading it twice and hence this could be the cause, I will be doing more with it to check out some of these possible issues. I assume i am doing the right thing by using the static :
Domain.getDefaultNamespace();
I could access the slide servlets NamespaceAccessToken from jetty's context, but i figured this may cause issues on transactions etc.. I assumed that using the Domain static method was the way one should get the NamespaceAccessToken . Is this a correct assumption?
Correct, yes. This is what the LoginModule does also. But keep in mind that when calling this method the servlet should have had the chance to initialize the Domain else the Domain will try to initialize using a configuration from a standard location.
Btw. how do you figure using the NamespaceAccessToken from the servlet context would cause issues with transactions?
-- Unico
-- Unico
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
