[jira] Closed: (JUDDI-149) BusinessEntities require serviceProjections collection

["Kurt T Stam (JIRA)" <ju...@ws.apache.org>]

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

Kurt T Stam closed JUDDI-149.
-----------------------------

    Resolution: Fixed

Added the mapping to the JPA layer. 

> BusinessEntities require serviceProjections collection
> ------------------------------------------------------
>
>                 Key: JUDDI-149
>                 URL: https://issues.apache.org/jira/browse/JUDDI-149
>             Project: jUDDI
>          Issue Type: Task
>    Affects Versions: 3.0
>            Reporter: Jeff Faath
>            Assignee: Kurt T Stam
>             Fix For: 3.0beta
>
>
> According to v3 spec, a businessEntity can be saved containing businessServices that belong to another businessEntity.  In this case, the saved businessEntity considers this service a "service projection".  This must be saved in a different collection then the businessServices collections - the serviceProjections collection.
> Behind the scenes, the serviceProjection table will simply be a "join table" with a many-to-many relationship between business and services.  Thus it will contain two columns: business_key and service_key.  However from the persistence point of view, only the business needs to refer to this table with a one-to-many link using the serviceProjections collection.  Services don't need to know what businesses are projecting them (ie. a businessService doesn't have a projectedForBusiness collection).

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