FWD » Bugs

When double clicking the instance column in ACL view of the admin applet the "Move ACL to another instance" dialog appears. Unchecking the "Shared Instance" checkbox, entering the name of an existing one in the appropriate text-box and clicking "Save" did not move the ACL item to the private instance.

After a short chat with Costantin, he reproduced this behavior and assumed that it's a faulty use of the communication API.

In server code, the com.goldencode.p2j.admin.AdminServerImpl.moveAcl(String resourceType, String instanceName, int oid, String newInstanceName) got called with instanceName null instead of "" (empty string), thus, the method was issuing an "instance names can't be omitted" message and returning.
On the client side, the corresponding parameter (in com.goldencode.p2j.admin.client.AdminACL.handleChangeInstance()) is row.acl.origin which seems to be null when the table model is populated in com.goldencode.p2j.admin.client.AdminACL.populateACLList() (list[i].aclDef.server null).

However, this was happening a couple days ago. At this moment I am unable to reproduce it. The directory.xml has changed a bit meanwhile, I wonder if this could be the cause for the self-fixing ?