Issue 3929: ExecutablePlacement definition (components-ftf) Source: Open Networks Engineering (Mr. Jean-Christophe Dubois, jcd(at)one.com) Nature: Uncategorized Issue Severity: Summary: In the componentAssembly DTD the executablePlacement is defined as follow: <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref , invocation? , destination? , extension* )> <!ATTLIST executableplacement id ID #REQUIRED cardinality CDATA "1" > It seems to me that the DTD should not enforce the componentimplref as this might depend on the deployment And there is no reason the assembler should know where the executable is going to be deployed. For example the componentimplref should be different between a Solaris, a Linux or an NT placement. Therefore I would propose to make componentimplref optional (as it is in homePlacement) and change the executablePlacement definition to: <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref? , invocation? , destination? , extension* )> <!ATTLIST executableplacement id ID #REQUIRED cardinality CDATA "1" > Resolution: see below Revised Text: In ptc/99-10-04 section 69.7.2.22 page 69-311, replace <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref , invocation? , destination? , extension* )> by <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref? , invocation? , destination? , extension* )> In ptc/99-10-04 section 695.4 page 695-349, replace <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref , invocation? , destination? , extension* , invocation? , destination? , extension* )> )> by <!ELEMENT executableplacement ( usagename? , componentfileref , componentimplref? Actions taken: October 3, 2000: received issue May 13, 2002: closed issue Discussion: When the assembler describes an executable placement, he/she could not always know what the executable implementation is because this implementation could be dependent of the physical placement selected at deployment time. Require to change the mandatory "componentimplref" child element to an optional child element of the "executableplacement" element in the component assembly XML DTD in order to apply the same rule defined in the "homeplacement" element. End of Annotations:===== From: "Jean-Christophe Dubois" To: Cc: Subject: ExecutablePlacement definition Date: Tue, 3 Oct 2000 13:06:51 -0400 Organization: Open Network Engineering MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: <4Rld9 In the componentAssembly DTD the executablePlacement is defined as follow: It seems to me that the DTD should not enforce the componentimplref as this might depend on the deployment And there is no reason the assembler should know where the executable is going to be deployed. For example the componentimplref should be different between a Solaris, a Linux or an NT placement. Therefore I would propose to make componentimplref optional (as it is in homePlacement) and change the executablePlacement definition to: Regards JC ----------------------------------------------------------------------- Jean-Christophe DUBOIS Open Networks Engineering, Inc. (ONE) Fax: (734) 975-6940 2725 South Industrial Hwy, Suite 100 Voice: (734) 975-7326 Ann Arbor, MI 48104 -----------------------------------------------------------------------