[JUDDI-149] BusinessEntities require serviceProjections collection

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0beta
• Assignee: Kurt T Stam
• Reporter: Jeff Faath
• Created: 30/Oct/08 16:38
• Updated: 19/Feb/09 15:18
• Resolved: 19/Feb/09 15:18

Description

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).

Issue Links

• blocks: JUDDI-150 Implement service projections in the publish API