I got a java application creates the following Collection structure:

/opt/tests/test5

by calling the following code

Collection col = org.xmldb.api.DatabaseManager.getCollection(m_dbURL + path);
if(col.getChildCollection(name) != null) return;
CollectionManagementService service = (CollectionManagementService 
col.getService("CollectionManagementService", "1.0");
service.createCollection(name);

three times such that on the first run '/opt', then '/opt/tests' and 
finally '/opt/tests/test5' is being created.
The problem that occurs since 1.1b4 is that though all corresponding directories
in the file system are being created, only the 'opt' Collection is added to 
the 'database.xml' file under '/system/SysConfig'.
If I then run my application a second time the 'tests' Collection is added and 
on a third run 'test5' is created.

I have also looked for a possible reason for this bug and I found out that 
within the 'flushConfig' method in 'org.apache.xindice.core.Database' the call 
for 'getConfig().isDirty()' only returns true one time, after that it is false 
and so the changes of the configuration are not written down.

I marked this as a major bug as this misbehaviour first of all results 
sometimes in a loss of data and secondary 'xmldbgui' does not display these 
collections (which are created in the filesystem, but not added 
to 'database.xml') any more.

My current workaround is to set the if-statement within 'flushConfig' to always 
true, but as this is obviously not the best way, it would be nice if someone 
could look for the real cause.

Greetings

Björn Eickvonder