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.
When adding a fault handler, and a reply within the catch scope, one can not select the catch-variable to use in the reply if we wanted to. This is similar to 83845 where the catch-variable doesn't show up in the mapper, but this is for the use in Reply as suggested by Kiran Bhumana http://www.netbeans.org/issues/show_bug.cgi?id=83845
You want special catch-variable to be visible in the general Variable chooser. Yes? I know Nikita is aware of this issue, so this may be a duplicate bug.
According to specification: Note that the <reply> activity corresponding to a given request has two potential forms. If the response to the request is normal, the faultName attribute is not used and the variable attribute, when present, will indicate a variable of the normal response message type. If, on the other hand, the response indicates a fault, the faultName attribute is used and the variable attribute, when present, will indicate a variable of the message type for the corresponding fault. I'm going to do the following: - extend the Reply property dialog to allow specifying in what mode does it have to work: normal responce or fault responce. - add separate field for specifying the fault variable. The normal responce variable and fault variable have to be alternative. - Remove possibility to edit the fault name from the property sheet. - Show the fault variable in property sheet as an additional variable.
Fixing the issue comes to the following chages in UI - The appearance of the Reply property dialog significantly changed - The tree structure of the Variable chooser is changed. Now not only the Variable containers are shown but also all other elements which can contain declarations of variables: ForEach, Catch, OnEvent. - Added the Fault variable property for the Reply element.
verified in build 061003