Changes between Version 42 and Version 43 of PRO_LIB_CORE_TUTORIAL

Timestamp:

07/14/09 14:51:53 (16 years ago)

Author:

peko

Comment:

--

PRO_LIB_CORE_TUTORIAL

@@ -717 +717 @@
 }}}
    * '''This should never happen.''' Every object that is a value of a property or is a value in a list property should either be a ProObject or an Immutable. Having objects like this one will never force an AutoProperty update if this AutoProperty depends on the "badObject()'s" property. Same applied to other properties depending on "badObject()'s" property. If a non-ProObject or non-@Immutable is really needed, use the resource property, where it is created and different things are set to it.
+ 
+ ==== One "child" owned by two separate parents ====
+ 
+  * Suppose we have:
+{{{
+        class Child extends BaseProObject {
+                //empty.
+        }
+        
+        class Parent extends BaseProObject {
+                
+                @Own
+                public RwProp<Child> child() {
+                        return getBean().makeValueProp("child", Child.class);
+                }       
+                
+        }
+}}}
+ 
+  * The following should will not work and will throw an AlreadyOwnedException. Despite not working, it worth mentioning. Same applied to have any kind of value or list property that has the @Own annotation.
+{{{
+    Child child = new Child();
+    Parent parent1 = new Parent();
+    Parent parent2 = new Parent();
+    parent1.child().set(child);
+    parent2.child().set(child); //throws an exception!!!
+}}}
+
+
 
 == Debugging ProLib ==