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.
| Summary: | Mapper is not opened automatically when selecting assignments | ||
|---|---|---|---|
| Product: | soa | Reporter: | Mikhail Kondratyev <mikk> |
| Component: | BPEL Mapper | Assignee: | Joshua Sandusky <jsandusky> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | jkopsa |
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Mikhail Kondratyev
2006-06-27 09:52:33 UTC
Ultimately the BPEL Mapper window should appear automatically when BPEL editor is opened or gets focused, unless it was closed explicitly by the user before. This issue is related to the issue #78066 (same UI pattern): http://www.netbeans.org/issues/show_bug.cgi?id=78066 *** Issue 80216 has been marked as a duplicate of this issue. *** fixed, the bpel mapper is now part of the bpel editor window group, and will open/close accordingly. This looks great! When you first open BPEL Editor, you just have the Orchestrator. 1. If you create an Assign, While, ForEach, RepeatUntil or any other activity that requires a mapping, the mapper will open. 2. If you click on an activity that doesn't require mapping, the mapper will close. 3. If you explicitly close the BPEL Mapper, the mapper will remain closed. 4. If you explicitly open the BPEL Mapper, the mapper will follow the rules of #1 and #2. I actually found a bug where the mapper does not initially open if the mapper module was not initialized. This was probably caused by my removal of the ModuleInstall, which pre-loads the mapper module before the bpel editor ever opens. Instead of pre-loading the mapper upon module install, I need to create a service provider interface in the bpel editor, and then implement that interface in the mapper. Thus, the bpel editor can load the mapper when it needs to. Currently, the mapper does not get loaded by the bpel editor, and instead must be explicitly opened from the menu before its window grouping auto-open/close capabilities become operable. the mapper window group now automatically opens, without the need for the ModuleInstall mechanism. The mapper implements a service provider interface in the bpel editor to accomplish the same, yet in a smarter way Verified in build from 06.08.25 |