hi, for every persistent entity, there is a class automatically generated (its name starts with underscore "_"), in those classes, we define property names as static final strings but they are never used by the methods : readProperty and writeProperty.. why ?
Primarily because the static final strings are assigned to a $propertyName variable value in the template... and so are the strings in readProperty and writeProperty. Since it's an auto-generated class, there isn't much point to using the static string declarations in the read/write properties. The static variables are there as a convenience to user-code, so you don't have to hard-code the property names (and you get to utilize code completion in your IDE), a convenience that I greatly miss when using hibernate. :) Robert On Nov 2, 2011, at 11/23:58 PM , stéphane Lestoclet wrote: > hi, > > for every persistent entity, there is a class automatically generated (its name starts with underscore "_"), > in those classes, we define property names as static final strings but they are never used by the methods : > readProperty and writeProperty.. > why ?
I've been meaning to fix that in the template for ages now, but keep forgetting. There isn't any hidden reason for not using the constants, I just haven't updated the template to use them. mrg On Wed, Nov 2, 2011 at 4:58 PM, stéphane Lestoclet <stephane.lestoclet <at> yahoo.fr> wrote: > hi, > > for every persistent entity, there is a class automatically generated (its name starts with underscore "_"), > in those classes, we define property names as static final strings but they are never used by the methods : > readProperty and writeProperty.. > why ? >
Hi all! Most of our projects share a set of common DB tables (users, permissions etc). The code and cayenne.xml for these entities resides in a standalone project, works great. However, I'm wondering if I can create relationships from entities in our client projects to entities in the common project? And if so, do I have to do it in code, or is there any way for CayenneModeler to pick up the entities in the common project, so I can model the relationships in the GUI? Cheers, - hugi PS: I started a huge thread regarding outer joins, and I haven't had the time to respond yet. Preparing a massive thesis on that one
This is one of the unsolved things. The relationships between DataMaps are supported in runtime (all DataMaps are loaded in a single namespace, so entities can reference each other freely). During modeling I am not sure how we can do that. We just had this discussion in my company recently, but no solution yet. If there are ideas how that can be implemented, let's discuss. Andrus On Nov 3, 2011, at 1:45 PM, Hugi Thordarson wrote: > Hi all! > > Most of our projects share a set of common DB tables (users, permissions etc). The code and cayenne.xml for these entities resides in a standalone project, works great. > However, I'm wondering if I can create relationships from entities in our client projects to entities in the common project? And if so, do I have to do it in code, or is there any way for CayenneModeler to pick up the entities in the common project, so I can model the relationships in the GUI? > > Cheers, > - hugi > > > PS: I started a huge thread regarding outer joins, and I haven't had the time to respond yet. Preparing a massive thesis on that one
EOModeler had model groups where you could reference external models. That's probably the approach Cayenne Modeler would need to take. On Thu, Nov 3, 2011 at 9:12 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: > This is one of the unsolved things. The relationships between DataMaps are supported in runtime (all DataMaps are loaded in a single namespace, so entities can reference each other freely). > > During modeling I am not sure how we can do that. We just had this discussion in my company recently, but no solution yet. If there are ideas how that can be implemented, let's discuss. > > Andrus > > > On Nov 3, 2011, at 1:45 PM, Hugi Thordarson wrote: > >> Hi all! >> >> Most of our projects share a set of common DB tables (users, permissions etc). The code and cayenne.xml for these entities resides in a standalone project, works great. >> However, I'm wondering if I can create relationships from entities in our client projects to entities in the common project? And if so, do I have to do it in code, or is there any way for CayenneModeler to pick up the entities in the common project, so I can model the relationships in the GUI? >> >> Cheers, >> - hugi >> >> >> PS: I started a huge thread regarding outer joins, and I haven't had the time to respond yet. Preparing a massive thesis on that one(Continue reading)
What does that mean in practical terms? How do we define that "group" in the Modeler? On Nov 3, 2011, at 4:25 PM, Michael Gentry wrote: > EOModeler had model groups where you could reference external models. > That's probably the approach Cayenne Modeler would need to take. > > On Thu, Nov 3, 2011 at 9:12 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: >> This is one of the unsolved things. The relationships between DataMaps are supported in runtime (all DataMaps are loaded in a single namespace, so entities can reference each other freely). >> >> During modeling I am not sure how we can do that. We just had this discussion in my company recently, but no solution yet. If there are ideas how that can be implemented, let's discuss. >> >> Andrus >> >> >> On Nov 3, 2011, at 1:45 PM, Hugi Thordarson wrote: >> >>> Hi all! >>> >>> Most of our projects share a set of common DB tables (users, permissions etc). The code and cayenne.xml for these entities resides in a standalone project, works great. >>> However, I'm wondering if I can create relationships from entities in our client projects to entities in the common project? And if so, do I have to do it in code, or is there any way for CayenneModeler to pick up the entities in the common project, so I can model the relationships in the GUI? >>> >>> Cheers, >>> - hugi >>>(Continue reading)
You'd add to CM a place to look for other other models (either a classpath approach or explicitly identify the other models). CM wouldn't need to edit the other models, but in the relationship inspector allow referencing the other entities in the model group. At least that's a first approach. I didn't use model groups extensively and my memory is a bit rusty. I can try to find more info on them later if that helps. Thanks, mrg On Thu, Nov 3, 2011 at 9:33 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: > What does that mean in practical terms? How do we define that "group" in the Modeler? > > On Nov 3, 2011, at 4:25 PM, Michael Gentry wrote: > >> EOModeler had model groups where you could reference external models. >> That's probably the approach Cayenne Modeler would need to take. >> >> On Thu, Nov 3, 2011 at 9:12 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: >>> This is one of the unsolved things. The relationships between DataMaps are supported in runtime (all DataMaps are loaded in a single namespace, so entities can reference each other freely). >>> >>> During modeling I am not sure how we can do that. We just had this discussion in my company recently, but no solution yet. If there are ideas how that can be implemented, let's discuss. >>> >>> Andrus >>> >>>(Continue reading)
A quick Google gives this API-wise: http://www.spice-of-life.net/wodock/api/com/webobjects/eoaccess/EOModelGroup.html and this UI-wise: http://www.rdbprime.com/Documentation/WebObjects/UsingEOModeler/5WorkingWithRelationships/index.html?http://www.rdbprime.com/Documentation/WebObjects/UsingEOModeler/5WorkingWithRelationships/Forming_Rel_ata_Sources.html mrg On Thu, Nov 3, 2011 at 9:46 AM, Michael Gentry <mgentry <at> masslight.net> wrote: > You'd add to CM a place to look for other other models (either a > classpath approach or explicitly identify the other models). CM > wouldn't need to edit the other models, but in the relationship > inspector allow referencing the other entities in the model group. At > least that's a first approach. I didn't use model groups extensively > and my memory is a bit rusty. I can try to find more info on them > later if that helps. > > Thanks, > > mrg > > On Thu, Nov 3, 2011 at 9:33 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: >> What does that mean in practical terms? How do we define that "group" in the Modeler? >> >> On Nov 3, 2011, at 4:25 PM, Michael Gentry wrote: >> >>> EOModeler had model groups where you could reference external models. >>> That's probably the approach Cayenne Modeler would need to take.(Continue reading)
In the Apple world everything you have is installed in /Library/Frameworks, so it is always easy to find(Continue reading)On Nov 3, 2011, at 5:28 PM, Michael Gentry wrote: > A quick Google gives this API-wise: > > http://www.spice-of-life.net/wodock/api/com/webobjects/eoaccess/EOModelGroup.html > > and this UI-wise: > > http://www.rdbprime.com/Documentation/WebObjects/UsingEOModeler/5WorkingWithRelationships/index.html?http://www.rdbprime.com/Documentation/WebObjects/UsingEOModeler/5WorkingWithRelationships/Forming_Rel_ata_Sources.html > > mrg > > > On Thu, Nov 3, 2011 at 9:46 AM, Michael Gentry <mgentry <at> masslight.net> wrote: >> You'd add to CM a place to look for other other models (either a >> classpath approach or explicitly identify the other models). CM >> wouldn't need to edit the other models, but in the relationship >> inspector allow referencing the other entities in the model group. At >> least that's a first approach. I didn't use model groups extensively >> and my memory is a bit rusty. I can try to find more info on them >> later if that helps. >> >> Thanks, >> >> mrg >> >> On Thu, Nov 3, 2011 at 9:33 AM, Andrus Adamchik <andrus <at> objectstyle.org> wrote: >>> What does that mean in practical terms? How do we define that "group" in the Modeler?
RSS Feed30 | |
|---|---|
72 | |
24 | |
43 | |
17 | |
73 | |
103 | |
82 | |
50 | |
76 | |
62 | |
87 | |
74 | |
105 | |
186 | |
152 | |
84 | |
100 | |
72 | |
77 | |
162 | |
163 | |
65 | |
46 | |
98 | |
32 | |
43 | |
68 | |
80 | |
44 | |
103 | |
122 | |
114 | |
65 | |
76 | |
87 | |
206 | |
180 | |
86 | |
99 | |
86 | |
74 | |
90 | |
78 | |
167 | |
77 | |
120 | |
102 | |
93 | |
164 | |
161 | |
106 | |
79 | |
72 | |
90 | |
64 | |
122 | |
184 | |
97 | |
153 | |
197 | |
120 | |
191 | |
152 | |
127 | |
93 | |
126 | |
131 | |
112 | |
114 | |
127 | |
220 | |
93 | |
186 | |
197 | |
213 | |
68 | |
169 | |
92 | |
174 | |
185 | |
160 | |
166 | |
198 | |
173 | |
283 | |
87 | |
27 | |
5 | |
313 | |
189 | |
169 | |
244 | |
149 | |
174 | |
55 | |
2 | |
1 | |
1 | |
1 |
