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 139658

Summary:	mapper - very hard to work with repeating nodes
Product:	soa	Reporter:	Murali Pottlapelli <mpottlapelli>
Component:	BPEL Mapper	Assignee:	Sergey Lunegov <slunegov>
Status:	NEW ---
Severity:	blocker
Priority:	P1
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Murali Pottlapelli 2008-07-11 00:39:26 UTC

To map from one repeating node to another node, define an index (predicate) to select a node and use the predicated node
for the mapping. 

To do this user needs to open a predicate window (tool opens mapper window) where user defines a literal number or
variable with index value and close the window. Opening predicate window and closing is too tedious for defining simple
index and user easily gets lost on the node if they are working node that is deeper in the tree.

We should add a context menu to define index with literal value/variable.

Comment 1 kiran_bhumana 2008-07-11 01:58:10 UTC

I guess what Murali suggested could be something like, "createSimpleExpressionPredicateNode" or "createIndexNode". We
need to word this correctly.

Also, once the user creates the node, whether it is using the current mechanism or the simplified mechanism being talked
here, we need to make sure the selection on the mapper will be the node that the user created.

Comment 2 Nikita Krjukov 2008-07-16 19:39:34 UTC

Now a new predicate is added with "Add Predicate" pop-up menu action in the BPEL mapper. 
I see 2 solutions: 
-- Add second action like "Add Simple Predicate" to the pop-up menu. It will show simple text dialog where the user can
input any text. Other functionality remains untouched.
-- Add a text field inside of existing Predicate dialog to which the user can input any text. The text will be
synchronized with mapper view in the dialog. Loading of the mapper usually doesn't take much time because the mapper
inside is much simple then main mapper. 

Also there is another use-case - a predicate can be modified with pop-up menu action "Modify Predicate". 
Again I see 3 solutions:
-- Add second action like "Edit Simple Predicate" and show simple text dialog. 
-- Use existing predicate editor with additional text field.
-- Automatically detect if the predicate is simple or not and show one of the dialogs. The menu item remains single. 

As for me, for both use-cases I prefer the variant with "existing predicate editor with additional text field"