Issue 14088: Add startLaunch also to DomainApplication/NodeApplication (deployment-rtf) Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen(at)remedy.nl) Nature: Clarification Severity: Minor Summary: Only the DomainApplicationManager and NodeApplicationManager have a startLaunch, on both classes this leads to a call to a DomainApplication/NodeApplication but this has no name in figure 9.1. We propose to seperate construction with the real functionality. Add startLaunch also to DomainApplication/NodeApplication which means adding it also to the application interface Resolution: Revised Text: Actions taken: July 21, 2009: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 21 Jul 2009 14:19:47 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Johnny Willemsen Company: Remedy IT mailFrom: jwillemsen@remedy.nl Notification: Yes Specification: Deployment Section: 9.10 FormalNumber: 06-04-02 Version: 4 RevisionDate: April 2006 Page: 121 (135 pdf) Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Description Only the DomainApplicationManager and NodeApplicationManager have a startLaunch, on both classes this leads to a call to a DomainApplication/NodeApplication but this has no name in figure 9.1. We propose to seperate construction with the real functionality. Add startLaunch also to DomainApplication/NodeApplication which means adding it also to the application interface