juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Faath (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Closed: (JUDDI-85) Juddi accept model keys that don't exist in binding template TModelInstanceInfos.
Date Wed, 19 Sep 2007 22:34:13 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jeff Faath closed JUDDI-85.

    Resolution: Incomplete

Did some investigation...there definitely isn't a check to see if the tModelKey provided in
the TmodelInstanceInfo is in the registry.  However, this happens all over.  For example,
anytime you save an entity with a categoryBag or IdentifierBag using a keyedReference with
a tModelKey specified, no check is perfomed to verify the tModel is in the registry.  I've
looked over the specs and can find nothing that explicitly states the tModel Key in these
examples must reside in the registry.  Logically, it makes sense though.

In any case, this doesn't seem to effect anything in juddi.  You can still search for the
binding (even using the non-existent tModel key provided when saving it), you can still retrieve
the binding template detail, etc.

I am going to close for now and mark as incomplete since we need more information.  Please
re-open if more information becomes available.

> Juddi accept model keys that don't exist in binding template TModelInstanceInfos.
> ---------------------------------------------------------------------------------
>                 Key: JUDDI-85
>                 URL: https://issues.apache.org/jira/browse/JUDDI-85
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: Oracle
>            Reporter: Rémi Flament
>            Assignee: Steve Viens
> I tried to add the HTTP model key "UUID:68DE9E80-AD09-469D-8A37-088422BFBC36" to a TModelInstanceInfo
in a TModelInstanceDetails of a binding template.
> This key doesn't exist in Juddi, but it accepted it anyway.
> After doing this, access to juddi is completely broken (impossible to do anything except
remove from db) because juddi assumes a TModel whose key is "UUID:68DE9E80-AD09-469D-8A37-088422BFBC36"
exist in db...
> I corrected this by adding a foreign key in oracle script :
> But maybe it would be better to do checks in a store independant way.
> Regards,
> Rémi Flament.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org

View raw message