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: | "Add WSDL Import" and "Add Schema Import" should use the same Import dialog as those used by WSDL Editor and Schema Editor | ||
---|---|---|---|
Product: | soa | Reporter: | _ hong_lin <hong_lin> |
Component: | BPEL Project | Assignee: | Nikita Krjukov <supernikita> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
BPEL WSDL Import dialog
BPEL Schema Import dialog Import dialog from WSDL Editor Import dialog from Schema Editor Screen shot of the new "Add WSDL Import" dialog Screen shot of the new "Add Schema Import" dialog |
Description
_ hong_lin
2007-01-17 23:58:28 UTC
Created attachment 37466 [details]
BPEL WSDL Import dialog
Created attachment 37467 [details]
BPEL Schema Import dialog
Created attachment 37468 [details]
Import dialog from WSDL Editor
Created attachment 37469 [details]
Import dialog from Schema Editor
Fixed by supernikita as part of fix for 80243. Vwrified the fix is in Gavotte daily build 070214_2. But the fix is not 100% correct. I will file a separate bug. For example, I created a SynchronousSample project. Here is my observation: After clicking "Add WSDL Import" item, the import dialog pops up (See attached BPELWsdlImport.png file): 1) the title of the dialog should be "Add Import", or "Add WSDL Import". Right now, it is "Create New Import". 2) Under "By Namespace", there are two "SynchronousSample.wsdl" items listed. One of them is even selectable. This is not right. 3) The default prefixes are all set to "ns1", each of them should be a unique value, something like ns0, ns1, ns2, ... After clicking "Add Schema Import" item, the import dialog pops up (See attached BPELSchemaImport.png file): 1) the title of the dialog should be "Add Import", or "Add Schema Import". Right now, it is "Create New Import". 2) Under "By Namespace", there are two "SynchronousSample.wsdl" items listed. One of them is even selectable. This is not right. 3) Missing the prefixes default setting. I am re-opening this issue. Please let me know if you prefer to log a new bug about these issues and close this one. Created attachment 38513 [details]
Screen shot of the new "Add WSDL Import" dialog
Created attachment 38514 [details]
Screen shot of the new "Add Schema Import" dialog
Nikita, please take a look. Here is the response to the observations of hong_li:
1) I changed the title of dialogs to "Add WSDL Import" and "Add Schema Import"
correspondingly.
2) I can't reproduce the mentioned wrong behaviour with a new SynchronousSample:
>> Under "By Namespace", there are two "SynchronousSample.wsdl" items listed.
>> One of them is even selectable. This is not right.
I suppose the WSDL file should appear at the tree only once. If it appears
twice then it's obviously a defect. Maybe it worth to log a new issue for it.
But a detailed description is required to be able to reproduce it. I think it
should be able to reproduced this problem not only in dialogs in BPEL but also
in WSDL and other places where the ExternalReferenceCreator class is used.
3) Current implementation behaves the following way:
-- If the resource file is already imported, then its prefix is displayed.
User doesn't allowed to modify the prefix.
-- If the resource file isn't imported yet, then prefix isn't provided
automatically. But user able to specify whatever prefix he want. If user
doesn't specify prefix explicitly, then an automatically generated prefix will
be assigned.
I don't think it reasonable to generate automatic prefixes preliminarily.
If user doesn't want to assign a specific value for prefix, then it doesn't
matter to he what prefix will be generated. The only important thing for user
in this case is to be sure that prefixes will be unique.
If you insist that all prefixes should be shown, I suggest to create a new
issue and assign to it the FEATURE or ENHANCEMENT type.
Please change the status to "RESOLVED" instead of "INVALID". The original issue was a valid one. I will log an ENHANCEMENT later. Thanks. Should reopen to resolve it as fixed. fixed indeed Verified |