Juddi accept model keys that don't exist in binding template 
TModelInstanceInfos.
---------------------------------------------------------------------------------

         Key: JUDDI-85
         URL: http://issues.apache.org/jira/browse/JUDDI-85
     Project: jUDDI
        Type: Bug

    Versions: 0.9    
 Environment: Oracle
    Reporter: Rémi Flament
 Assigned to: 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 :

"ALTER TABLE TMODEL_INSTANCE_INFO add CONSTRAINT fk_tmodel FOREIGN KEY 
(TMODEL_KEY) REFERENCES TMODEL(TMODEL_KEY);"

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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to