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.
Tien, Despite the NetBeans' xDesign team's blessing of CASA, I still have major concerns about the usability of CASA. I do think that the graphical view in CASA and the CM are comparable even if the underlying architectures are different. At the very least, customers will make this comparison. I would think that CASA does have access to WSDLs and hence can figure out what connections are in-only or in-out. If it can't, perhaps we should build something so that it can. As far of the graphical editor being free-formed: you're only allowing freedom of movement along a single axis in CASA (one dimensional). What is the reason that you cannot extend that to two dimensions? On the issue of having c and p for each port: can you give some examples where we would use both the c and the p of a single port? The only example I can come up with is JMS. If the use of ports with both c and p is indeed so limited, perhaps we can make the UI more expressive to allow for p-ports, c-ports and c/p-ports? Frank
Created attachment 54284 [details] No mechanisum to conceptualise what is shown on CASA editor
I have attached a screen shot that shows BP canvas and corresponding CASA view. It is hard to understand the relationship between endpoints shown (BPEL)SynchronousSample and business process it represents. To address this issue we should 1 - show each BP as independent unit instead of lumping all the BPs in one SU as one unit. 2 - show the partner link local name instead of role name. Retain the tool tip as it is. 3 - There is no need for _myRole or _partnerRole in the endpoint name.
These are from CompApp/CASA usability enhancement requests: 3.6 Show bpel processes instead of service units 3.7 Show the partner link local name instead of role name 3.8 Navigation to NB project artifact from CASA 3.11 Ports should not show p and c on the arrows A preliminary implemenation has been checked-in. We are still waiting for feedback from xDesign.
A clarification for myself: 3.7 means that the BPEL partnerlink element's name attribute will be displayed instead of the endpoint's name (the partnerlinktyperole name). Verified with Product Version: NetBeans IDE Dev (Build 20080313230056) Java: 1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) Userdir: /Users/lautz/sierrabuilds/JCAPS20080315/.netbeans/caps