[switchyard-issues] [JBoss JIRA] (SWITCHYARD-804) Validate diagram (and avoid creating unusable configs)

Brian Fitzpatrick created SWITCHYARD-804: -------------------------------------------- Summary: Validate diagram (and avoid creating unusable configs) Key: SWITCHYARD-804 URL: https://issues.jboss.org/browse/SWITCHYARD-804 Project: SwitchYard Issue Type: Enhancement Components: tooling Affects Versions: 0.5 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 0.5 These qualities come from https://community.jboss.org/thread/199987 * All component and service references require a single interface. * A component must have an implementation, but it's not required to be present when first created (abstract design use case). * Composite services and references may have a single interface. If they do not have one, then they inherit the promoted component interface. * Components can have zero or one service. Zero is a kind of edge case, but possible (e.g. CDI bean with @Reference invoked from a webapp). More than one service is technically valid, but we don't fully support it now, so treat it as invalid until we do. * Components can have zero to many references. * A component service can be promoted multiple times (each composite service name would have to be unique). * A component reference can be promoted once. Stritcly speaking, this should be multiple, but it's not super important so we don't support it at the moment. * A composite service can have zero to many bindings. * A composite reference can have zero or one binding. Strictly speaking, this should be multiple, but it's not super important so we don't support it at the moment. Each of these will need to be handled in the UI. Validation markers can be added to the diagram showing that things need to be completed or are out of whack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira