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 92661 - FAST: ALASKA: CANNOT SELECT INPUT / OUTPUT VARIABLES WITHIN VARIABLE CHOOSER POPUP
Summary: FAST: ALASKA: CANNOT SELECT INPUT / OUTPUT VARIABLES WITHIN VARIABLE CHOOSER ...
Status: CLOSED DUPLICATE of bug 86958
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-17 01:12 UTC by lpolycarpou
Modified: 2008-01-20 02:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Alaska screenshot with annotations (213.79 KB, application/octet-stream)
2007-01-17 01:14 UTC, lpolycarpou 		Details
Alaska / NetBeans project test case (13.62 KB, application/octet-stream)
2007-01-17 01:19 UTC, lpolycarpou 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2007-01-17 01:12:10 UTC 
In the Invoke activity property dialogue, you have two options to Browse for
possible Input and Output variables (respectively) for the selected Operation. 
Selecting a VALID input variable, for example, in the Input Variable Chooser,
enables the OK button.  However, hitting OK does not populate the Input Variable
on the Invoke Property Editor.  See attached screenshot and sample project.
Comment 1 lpolycarpou 2007-01-17 01:14:58 UTC 
Created attachment 37427 [details]
Alaska screenshot with annotations
Comment 2 lpolycarpou 2007-01-17 01:19:31 UTC 
Created attachment 37428 [details]
Alaska / NetBeans project test case
Comment 3 Nikita Krjukov 2007-03-09 14:09:10 UTC 
The BPEL file in the referenced project contains an ns3 prefix for the 
namespace, which is shared by 3 WSDL files. There is ambiguities of various 
definitions there. 

It's quite difficult to provide correct work of the dialog with an invalid 
source data. So I suggest to treat this defect as a duplicate of the Issue 
#86958. 
See also the issue #92660. 

I can provide more detailed result of analysis by request.


*** This issue has been marked as a duplicate of 86958 ***