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.

Bug 83654

Summary: Add capability to filter Assign mappings via the Navigator
Product: soa Reporter: Joshua Sandusky <jsandusky>
Component: BPEL MapperAssignee: Joshua Sandusky <jsandusky>
Status: RESOLVED FIXED    
Severity: blocker    
Priority: P2    
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:
Bug Depends on:    
Bug Blocks: 89926    

Description Joshua Sandusky 2006-08-29 03:02:11 UTC 
It would be nice to be able to filter out mappings involving the Assign activity
by opening the Navigator and clicking on individual Copy children that may exist
inside the Assign activity. When the user clicks on the Copy children in the
Navigator, only that particular Copy assignment would show inside the Assign
mapper... this effectively filters out all mappings except our Copy of interest.
Comment 1 Joshua Sandusky 2006-08-29 23:19:57 UTC 
*** Issue 81873 has been marked as a duplicate of this issue. ***
Comment 2 Vitaly Bychkov 2006-11-02 08:17:49 UTC 
*** Issue 87385 has been marked as a duplicate of this issue. ***
Comment 3 Michael Frisino 2006-11-02 15:06:46 UTC 
Actually, there was a subtle difference in the RFE 87385. It was not an exact
dupliacate. Yes, it should remain a duplicate issue, but we should consider the
subtle difference in design that was suggested in that issue.

The difference was that that issue suggested that when user selected a
particular Copy in the Navigator, then the Mapper would auto expand and
HIGHLIGHT the connections that define that particular copy rule. However, as
originally written, that would suggest that ALL of the copy rules for the
Assignment are still visible and active, the only difference is that the
selected node's connections are highlighted. 

This is slightly different from Josh description in this issue, which suggests
that ONLY the current copy rule is visible at all.

Both approaches have merit. How do we decide between them?  

One possible tie breaker is that if ALL rules are still visible it would imply
that user could start messing around with the other copy rules, not just the
ones that was originally selected (i.e. the current navigator node's rule). What
should happen then? Should the navigator and copy rule selection be synchronized
so that as user selects a rule in the mapper, the same node is selected in
Navigtor? Any problem with that?  Is that better than showing only the current
rule? 

Perhaps a filter option on Mapper would give user choice : "Show only selected
Rule" or something to that effect for users that want to reduce the noise?
Comment 4 Sergey Lunegov 2007-12-13 11:53:41 UTC 
fixed