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] Created: (JUDDI-149) BusinessEntities require serviceProjections collection
Date Thu, 30 Oct 2008 16:38:44 GMT
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 Stam
             Fix For: 3.0

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

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