"In UML these are the "Visibility" definitions... (+) public - usabile by others (#) protected - usable only by objects that inherit (-) private - usable only by this object (the symbol on the left is the standard UML notation for the uml visibility)"
There is also: (~) package - usable by objects within the same package "In CFC's all base attributes are (+)... if you have access to the CFC. The methods (<cffunction>s) are one of a number of settings... (private, package, public, remote). While the reason for the differences makes sense... it means the standard UML tools are not appropriate for modeling at this point." I don't see where the problem is. I use UML all the time for modeling CFCs, using these standard visibility options. "Remote" to me is as Sean said - "very public". Package is package, public is public, and I use the private symbol for CF's rendition of "private". If you want to be a stickler, maybe you would use the protected symbol instead of private. I fail to see where the conflict occurs! ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
