[Exist-development] Problem with new permissions stuff...

[Andrzej J. T. <an...@ch...>]

Adam:

Why did I know this was going to break things for us? ;-)

If you try to use your newest permissions code base to access a remote db (which is still running an
older version of eXist without the new permissions stuff) then you get the following NPE:

/home/andrzej/coalese/dev/raven/build.xml:656: java.lang.NullPointerException
	at java.util.Arrays$ArrayList.<init>(Arrays.java:3357)
	at java.util.Arrays.asList(Arrays.java:3343)
	at org.exist.xmldb.RemoteCollection.readCollection(RemoteCollection.java:432)
	at org.exist.xmldb.RemoteCollection.getChildCollection(RemoteCollection.java:159)
	at org.exist.xmldb.RemoteCollection.getChildCollection(RemoteCollection.java:153)
	at org.exist.xmldb.DatabaseImpl.readCollection(DatabaseImpl.java:248)
	at org.exist.xmldb.DatabaseImpl.getRemoteCollection(DatabaseImpl.java:225)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:158)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:151)
	at org.xmldb.api.DatabaseManager.getCollection(Unknown Source)
	at org.exist.ant.AbstractXMLDBTask.mkcol(AbstractXMLDBTask.java:141)
	at org.exist.ant.XMLDBStoreTask.execute(XMLDBStoreTask.java:105)

This is something we do all the time....we use ant tasks that point to a more or less current SVN
copy of eXist to access remote databases to deploy various items (xqueries, create collections,
etc.) in the remote DB.

Sure would be nice if this was backward compatible in this particular scenario, since this has
worked for about 4 years now....but the latest permissions code has broken compatibility.

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com