| CDO resources layout best practices [message #890872] |
Sat, 23 June 2012 09:32  |
 Mariano Navas
Messages: 3
Registered: June 2012 |
Junior Member |
|
|
Hi there,
We are dealing with a project that uses CDO repositories as the backend storage for our business model objects. We have many entities to persist, and we want to distribute them among resources in a logical manner. We think that for first level entities (the parents of the rest of the model) a unique resource is a good approach, using a naming convention. We have chosen to name our resource like this: /[nameOfEntity]/[versionOfModelEntity]/library.
This approach seems to work fine for us for those top level entities, but we have some that are referenced from several and different top level ones (to put it simple, they are shared horizontally among the model), and we need to maintain them individually, so we need a resource path for them.
Let's talk about pears and apples: two of our entities are (say) cars and walls. We store each in their corresponding resource according to the naming convention described above. Both have as an attribute a Color object, and our application allows the user to maintain (perform CRUD operations) on the colors library. Taking into account that colors are part of both cars and walls, and both cars and walls are stored in different CDO resources, ¿what resource should we use for the color entity? Is there any best practice to apply in this case? What about independent entities that are shared among even more (than two) top level entities? What CDO resource layout strategy could we use?
Thank you in advance!!
Regards,
|
|
|
| Re: CDO resources layout best practices [message #890901 is a reply to message #890872] |
Sat, 23 June 2012 11:22  |
|
Hi Mariano,
You lost me somewhere in the middle :P
Maybe it would help me to see some concrete resource paths and objects according to your cars/walls/colors example.
Please also tell how you modeled Color (EDataType?).
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 23.06.2012 11:32, schrieb Mariano Navas:
> Hi there,
>
> We are dealing with a project that uses CDO repositories as the backend storage for our business model objects. We
> have many entities to persist, and we want to distribute them among resources in a logical manner. We think that for
> first level entities (the parents of the rest of the model) a unique resource is a good approach, using a naming
> convention. We have chosen to name our resource like this: /[nameOfEntity]/[versionOfModelEntity]/library.
>
> This approach seems to work fine for us for those top level entities, but we have some that are referenced from
> several and different top level ones (to put it simple, they are shared horizontally among the model), and we need to
> maintain them individually, so we need a resource path for them.
>
> Let's talk about pears and apples: two of our entities are (say) cars and walls. We store each in their corresponding
> resource according to the naming convention described above. Both have as an attribute a Color object, and our
> application allows the user to maintain (perform CRUD operations) on the colors library. Taking into account that
> colors are part of both cars and walls, and both cars and walls are stored in different CDO resources, ¿what resource
> should we use for the color entity? Is there any best practice to apply in this case? What about independent entities
> that are shared among even more (than two) top level entities? What CDO resource layout strategy could we use?
>
> Thank you in advance!!
>
> Regards,
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03682 seconds
] 
Search
Help
Register
Login
Home
.