This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The new "Composite Application Service Assembly" (CASA) editor is way cool and everything, but usage of the term CASA is very confusing. I see two problems: 1. It is redundant. The terms "Composite Application" and "Service Assembly" mean the exact same thing. So instead of CASA we could just as well have called it CACA (for Composite Application Composite Application) editor. Or SASA. 2. The term "Service Assembly" should probably not be used anywhere in the user interface. See related IZ: http://www.netbeans.org/issues/show_bug.cgi?id=95635 So when I open up the CASA editor in a recent daily build of 5.5.1 and I see over in my Navigator window things like: "CASA Logical View" and a top-level node called "CASA" it sort of makes my head spin. As someone who is new to this technology, I immediately wonder: What is a CASA? Please replace it with the words "Composite Application" in the user interface. Using a <casa> element in the XML is fine by me as is the usage of .casa as a filename extension. But please, let's not confuse the users any more than we have to. :-)
Tien assigning to you as this involves product/marketing issues.
All suggestions made in this request have been implemented in NB6.0
You don't want to know what CACA means in French...
>All suggestions made in this request have been implemented in NB6.0 Great! Does that by chance also mean that we can close http://www.netbeans.org/issues/show_bug.cgi?id=95635 ? Thanks, Gregg
Reopening this issue. In NetBeans IDE 6 Beta 2 I see "CASA" all over the help file contents. Please fix before FCS - this is *way* confusing.
We beleive it is very fitting to name the editor as the "Composite Application Service Assembly" (CASA) editor. The term "Composite Application" in this context referring to the composite application project of NetBeans. The term "Service Assembly" means a JBI specific deployment packaging format. The "Composite Application Service Assembly" editor was designed as a tool that takes a composite application project and generates a JBI service assebmly according to user specified compositions, i.e., ports and connections. The full name Composite Application Service Assembly is too long to be used directly in UI. Since using CASA on the UI may be confusing to beginner users, we agreed to remove all direct usages of the term "CASA" in UI. However, we don't seen any problem using the terms "Composite Application Service Assembly editor" or "CSAS editor" in documentations such as on-line help.
Since we have now added the Service Assembly to the Composite Application, and not changed the CASA term, and Tientien doesn't intend to, I will verify that this hasn't been fixed.