Information about Port Delegations Lost In Planning
Legacy Issue Number: 8984
Source: Zuehlke Engineering ( Frank Pilhofer)
The resolution for issue 6392 introduced the ability
for a monolithic implementation to delegate some of its
ports to a resource.
To this effect, the ImplementationRequirement element
has three attributes, "resourceUsage", "resourcePort"
and "componentPort" to identify how the component
instance uses the resource.
In the deployment plan, the InstanceResourceDeployment-
Description element captures which resource was chosen
to satisfy the requirement. It has a "resorceUsage",
but neither "resourcePort" and "componentPort"
This information is necessary in the deployment plan.
Add "resourcePort" and "componentPort" attributes to
the InstanceResourceDeploymentDescription element, to
carry the information from the original implementation
In section 126.96.36.199, add two attributes:
resourcePort [0..1]: The resource port used by the
component instance. Copied from the original
componentPort [0..1]: The component port delegated
to or used by the resource. Copied from the
Reported: DEPL 1.0 — Wed, 31 Aug 2005 04:00 GMT
Disposition: Resolved — DEPL 4.0
No Data Available
Updated: Wed, 11 Mar 2015 01:53 GMT