You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt Stam (JIRA)" <ju...@ws.apache.org> on 2008/12/13 17:05:44 UTC
[jira] Updated: (JUDDI-145) Adjust model to meet UDD v3
requirements
[ https://issues.apache.org/jira/browse/JUDDI-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam updated JUDDI-145:
----------------------------
Assignee: Tom Cunningham (was: Kurt Stam)
> Adjust model to meet UDD v3 requirements
> ----------------------------------------
>
> Key: JUDDI-145
> URL: https://issues.apache.org/jira/browse/JUDDI-145
> Project: jUDDI
> Issue Type: Task
> Reporter: Jeff Faath
> Assignee: Tom Cunningham
> Priority: Blocker
> Fix For: 3.0alpha
>
>
> The model is missing some key requirements to be compatible with UDDI v3. Here is the list so far:
> 1) The "operator" and "authorizedName" properties on BusinessEntity and TModel no longer exist in v3 but are in the persistence layer objects.
> 2) CategoryBags now allow one to group KeyedReference groups in a KeyedReferenceGroup structure which refers to a TModel. There is no way to persist this structure in the model.
> 3) The Tmodel entity in the persistence layer seems incorrect. There's no reference to an OverviewDoc and in fact in v3, there should be a collection of OverviewDocs. There's a TmodelOverview class, but I don't see it referenced anywhere. I also see a collection of TmodelDocDescr, which is presumably the OverviewDoc descriptions? Anyway, I think some work needs to be done here.
> 4) Contacts allow a collection of personNames in v3 as opposed to just the one provided by the model.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.