Attributes represent the state of an object. By
definition and interface has no state. This differentiates an interface
from a class. An interface has behavior only. The classes that
realize the behavior manage their state invisibly to the interface. If
your interface is used to get and set values then it is done through
methods. The underlying classes define how the values are
represented internally.
Be
careful not to confuse an "Interface" with a class that happens to be used to
interface with some other component. The interface is used to implement
polymorphic behavior which is not dependent on any particular
class.
-----Original Message-----
From: Rich Denis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 29, 2001 2:58 PM
To: '[EMAIL PROTECTED]'
Subject: (ROSE) Attribues as Members of an InterfaceWhy is it not reccomended to add attributes as part of an interface? If I createan interface in Rose and "realize" that interface in another class then only the Operations show up. When I read the Online Docs under interface it says that Attributes as part of the interface is not recomended? Why is that?? And is there any way to force the attributes to be inherited within the Rose IDEThanks
Rich
