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 terms used to define how a Partner Link is to be implement are inconsistent and confusing within the product. Within the BPEL editor they are referred to as 'My Role' and 'Partner Role' where as in the CASA editor they are provider and consumer. The improve the usability of the product they should be consistent and I would suggest that the CASA "Provide" be used in preference to 'My Role' and and 'Consume' be used in preference 'Partner Role' --------------------------------- KEYWORDS VERSION: ALASKA 200702090600 (KENAI) TEAM: FAST
There is apparently a conflict in terminology between BPEL (roles) and JBI (providers/consumers). Someone must decide whichever should take preference. Andi, what's your opinion on this?
Comments from Andi: There is dilemma here; people really into BPEL will understand partnerlink, everyone else will not. Also the reason the terminology used is different is because what you see in CASA is actually and "internal endpoint name", which just happens to be made up (in part) of the partner link details. Not trying to defend, just give some background. I do believe we need to make the naming in our product more approachable; less centric on technologies such as WSDL and even BPEL to some degree; however, I would also say there should be "side notes", some way for folks that know the technologies to understand what it maps to. Now in principle I would agree, if we can find a better generically understood term (that still matches the concept) rather than partner link, we should use it. Obviously we would have to run it by the BPEL team to makes sure there is no hole in describing it a provides/consumes.