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.
Use case: BPEL activities contain references to other BPEL objects. For example BPEL Invoke source looks like this <invoke name="ReserveAirline" partnerLink="Airline" portType="ares:AirlineReservationPortType" operation="reserveAirline" inputVariable="ReserveAirlineIn"> User wants to be able to quickly navigate in the Diagram from the Invoke to the PartnerLink. Scenario: User is looking at Invoke User want to navigate to ParnterLink that is connect to this Invoke by a message flow. User selects context menu on the Invoke activity. Go To Definitions > Partner Link Diagram re-orients to show and select the Partner Link. Recommendation: Add context menu to all BPEL activities for such reference navigation. In the BPEL object model, the references are formalized. So it should be fairly easy to build list of menus dynamically from the avialable references. Issues: What should the name of this action be - Go to Definition / Go to Reference . Cant the menus be built dynamically from established refrence relationships e.g. Go To Definition : Airline [Parnter Link] or should such menus be hard coded for structural relationship e.g. Go To Definiton > Parnter Link The other big issue is that many cases of reference usage is not really visualized in the diagram. Most reference usage is of Variables and Correlation Sets. You cannot "go to" a variable definition in the diagram. One option here is that we go to the Variable declaration in the Navigator tree. However, this creates a possible confusiion for user, in some cases the Go To would change diagram selection and position, and in other cases it would only change selelection in Navigator and give navigator focus. This may be a big problem. We need to identify the full list of reference usages in order to determine if there is really a common use case with a common solution or wethher there are completely different use cases. If in fact there are only a few cases where diagram repositioning is involved, maybe we should consider them as distinct and provide a different action. Need to open a wiki issue on this.
Future release
Fixed please verify.