Hello Miguel,
I'm also working with the JNDIPrincipalStore. I think the problem is the way the file
based stores are implemented. You have set the security and lock store to be a file
based store. Earlier I've tried to separate data of an ExtendedStore by spreading it
over 6 file based stores each using different directories. It didn't work.
The error could lie in AbstractXMLResourceDescriptor.encodeObject() (if you don't use
an old version of Slide):
Element aElementObjectNode = new Element("objectnode");
if (object != null) {
aElementObjectNode.setAttribute("classname", object.getClass().getName());
aElementObjectNode.setAttribute("uri", object.getUri());
if (object instanceof LinkNode) {
aElementObjectNode.setAttribute("linkTo", ((LinkNode) object).getLinkedUri());
}
} else {
// for null locks
aElementObjectNode.setAttribute("classname", "null");
aElementObjectNode.setAttribute("uri", uri.toString());
}
aElementObjectNode.addContent(createBindings("children", "child",
object.enumerateBindings()));
aElementObjectNode.addContent(createBindings("parents", "parent",
object.enumerateParentBindings()));
aElementObjectNode.addContent(createElements("links", "link",
object.enumerateLinks()));
return aElementObjectNode;
First there is distinguished between an object being null or not. After that there is
always tried to access the child bindings of object - even if it's null.
Try replacing your security and lock store by a JDBCStore. For me it works that way.
Stefan
Am Tue, 14 Sep 2004 11:42:17 +0100 schrieb Miguel Figueiredo <[EMAIL PROTECTED]>:
Hello folks,
I've been trying to configure slide to use an ldap server for authentication
purposes.
I've been successful at that, but with a cost of an annoying null pointer
exception when tomcat is starting up:
org.apache.slide.common.ServiceAccessException: Service
TxXMLFileDescriptorsStore at users/store/metadata working on us
ers/work/metadata access error : java.lang.NullPointerException
at
org.apache.slide.store.txfile.AbstractXMLResourceDescriptor.encodeObje
ct(AbstractXMLResourceDescriptor.java:662)
My current setup is the tomcat 5.0.19 / slide 2.1b1 bundle with the attached
domain.xml file.
I suspect that it works well because JNDIPrincipalStore is read-only, so,
maybe it wouldn't need it's corresponding working directory, to witch this
exception relates to. Or perhaps I still didn't found any problem witch
shall occur more soon than later...
Does slide use the 'users working directory' in any of its use-cases? Am I
doing something wrong in the Domain.xml file?
Thanks in advance,
Miguel Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
