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.
Currently, user need to pick up the jbi module project from the native filesystem to add the jbi module to the compapp project even when the jbi module project ( bpel, xslt, etc) is in the projects tab. It would be more user friendly if user is able to select the existing jbi module in the project tab to include it in the compapp project directly. This can be achieved in several ways like 1. drag and drop jbi module project to the compapp project node to add the jbi module project to the compapp. 2. drag and drop jbi module project to the casa editor to add jbi module project to composite app which is currently supported, but this requires casa view of the compapp to be present on the editor pane by default. 3. add jbi module action that brings project browser should be enhanced to include the currently available jbi module projects in the project tab in addition to browsing the native filesytem for the jbi module project. 4. user can select (optional) to which compapp the jbi module should be added during the jbi module creation time which requires a standard wizard ui in all jbi module project templates to pickup the available compapps present in the project tab ( a simple combobox to list the compapps) I would like the DnD of created jbi module in the project tab to compapp project node or casa editor to add the jbi module to the compapp project.
Srinivasan Chikkala wrote: > Hi Jun, > > See my comments below > > thanks, > > Srinivasan Chikkala > Open ESB Community (http://open-esb.org) > > > > Jun Qian wrote: >> Comments in-line... >> >> Srinivasan Chikkala wrote: >>> Hi Tien, >>> >>> This is to continue the discussion on DnD facility to add jbi module projects to compapp project. Currently, user need to pick up the jbi module project from the native filesystem to add the jbi module to the compapp project even when the jbi module project ( bpel, xslt, etc) is in the projects tab. >>> >>> It would be more user friendly if user is able to select the existing jbi module in the project tab to include it in the compapp project directly. This can be achieved in several ways like >>> 1. drag and drop jbi module project to the compapp project node to add the jbi module project to the compapp. >> -1 // This is not standard NB behavior and it could be confusing. > Well, I think, nobody so far implemented this behavior as appose to NB UI guidelines prohibiting, IMO. When I look at the DnD between JavaSE projects ( I looked at DnD classes between JavaSE projects ), they apply control keys ( DnD -> for move, DnD+Ctrl -> for copy, DnD+Ctrl+Shit for linking) to define the DnD behaviour. I guess that linking behaviour is what we should use if that is the standard in NB. IMO, we can just use DnD without the control keys as it is the main behaviour for our project type which is what we have implemented in CASA editor also. >>> 2. drag and drop jbi module project to the casa editor to add jbi module project to composite app which is currently supported, but this requires casa view of the compapp to be present on the editor pane by default. >> +1 >>> 3. add jbi module action that brings project browser should be enhanced to include the currently available jbi module projects in the project tab in addition to browsing the native filesytem for the jbi module project. >> A filesystem project chooser and an open-project project chooser at the same time? Visually, it might be too busy. > Agreed. If it is too clutered to show both in the same dialog, we should add two actions, add module from project tab, add module from filesystem that bring up these two different project browsers. >>> 4. user can select (optional) to which compapp the jbi module should be added during the jbi module creation time which requires a standard wizard ui in all jbi module project templates to pickup the available compapps present in the project tab ( a simple combobox to list the compapps) >> If we do this, the we should also consider the opposite, that is, to present a list of available jbi module projects in the compapp creation wizard. For bottom-up development, this seems be to more useful. > Agreed. >> >>> >>> I would like the DnD of created jbi module in the project tab to compapp project node or casa editor to add the jbi module to the compapp project. >>> >>> Any comments? Do you think we should support this facility in compapp tools? >>> >>> regards, >>>