Customize Default ACL in Create Object Wizards

Question

In preparation to add some highly sensitive content to a Plumtree 4.5WS Portal, I need to implement a two-tier admin. security model. In short, I want only one or two members in the "Administrators Group" (Tier One) who can access everything without exception and a second admin. group (Tier Two) including the entire admin team who can access most of the portal. This way, the whole team can perform admin/maintenance tasks on "normal" content while access to the most sensitive content can be restricted to authorized users and the one or two people in the "Administrators Group" only. I prepared a script to add the "Tier Two" admin group to all existing object security and now I want to add the same group to the default ACL for new objects/cards/folder. Has anyone had any experience doing this? Is there a single file where I can add the customization or will I have to modify each CreateObject Wizard individually? Any experience/advice would be greatly appreciated.

Answer 1

Note that the usual and recommended way of implementing clone() also does not invoke any constructor.
public class C implements Cloneable {
  public static void main(String... args) throws Exception {
    C c1 = new C();
    C c2 = C.class.newInstance();
    C c3 = c1.clone();
  public C() {
    System.out.println("C'tor!");
  public C clone() throws CloneNotSupportedException {
    return (C)super.clone();
}All this is generally fine, because a c'tor is not supposed to perform any business logic. It's only supposed to get a newly created object into a valid state. Cloning and serialization are not about creating new objects. They're about preserving and restoring or duplicating the state of an object that's already fully functional.
Note also, that if you do end up needing to perform some other logic as part of deserialization or cloning, you can do so. These cases should be the exception, not the rule.