You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Amita Vadhavkar <am...@gmail.com> on 2007/10/16 10:12:49 UTC
[DAS] external static model based Types - gaps
When DAS uses the external model.xsd to get Types from SDO, if there are
containment properties, DAS can
use the information to 1) form Relationships in DAS Config with name same as
containment property name
2) Also similar to Dynamic Types behavior of DAS, it can modify child Type
to have a property with
"relationship_opposite" of parent Type.
DAS is missing this processing for static model based Types at present and
so when used in static way, needs
to be supplied relationship information through external DAS Config (or
implied relationships if Convention over config
is followed).
If 1) and 2) is provided, and if the Type names match the DB entity names,
user can use model.xsds and dynamic queries
to get results and will not need external config. Thus DAS Config will be
better aligned with static model.
If external config is also available in the above case, it can take
precedence in forming relationships,
TableName<->TypeName mapping etc.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Also, in ConfigHelper.addRelationship() API, can give parameter to pass in
relationship name (optional), so it
does not always need to default to the implicit name formation rule of DAS
Regards,
Amita
Re: [DAS] external static model based Types - gaps
Posted by Amita Vadhavkar <am...@gmail.com>.
For this , support for keyref is required from SDO , which will be there in
SDO 3 (as per some old mails). With keyref, FK
relationships in DB can be mapped in model XSDs and there will be no need of
DAS config/COC to provide relationshp info.
Regards,
Amita
On Oct 16, 2007 1:42 PM, Amita Vadhavkar <am...@gmail.com> wrote:
> When DAS uses the external model.xsd to get Types from SDO, if there are
> containment properties, DAS can
> use the information to 1) form Relationships in DAS Config with name same
> as containment property name
> 2) Also similar to Dynamic Types behavior of DAS, it can modify child Type
> to have a property with
> "relationship_opposite" of parent Type.
>
> DAS is missing this processing for static model based Types at present and
> so when used in static way, needs
> to be supplied relationship information through external DAS Config (or
> implied relationships if Convention over config
> is followed).
>
> If 1) and 2) is provided, and if the Type names match the DB entity names,
> user can use model.xsds and dynamic queries
> to get results and will not need external config. Thus DAS Config will be
> better aligned with static model.
>
> If external config is also available in the above case, it can take
> precedence in forming relationships,
> TableName<->TypeName mapping etc.
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Also, in ConfigHelper.addRelationship() API, can give parameter to pass in
> relationship name (optional), so it
> does not always need to default to the implicit name formation rule of DAS
>
> Regards,
> Amita
>