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.
This is when trying to fetch an external wsdl document using: new file -->xml--> external wsdl document or external xml schema document to fetch existing wsdl/schema from URL or some local directory. The way it creates the directory structure for fetched wsdl/xsd is not user friendly. (See attached screen shot when trying to fetch http://ws.xwebservices.com/XWebEmailValidation/V2/XWebEmailValidation.wsdl ) When this wizard comes up it should create the wsdl/xsd with a suitable name in the folder which is chosen by user in the wizard. Instead currently it created a bunch of folders automatically and there it puts principal wsdl/xsd etc there. In this case it should have created XWebEmailValidation.wsdl in the folder as selected in the wizard and any imported wsdl/xsd relative to this. Instead it creates a folder ws.xwebservices.com then a sub folder V2 then there it created wsdl/xsd.
Created attachment 32848 [details] screen shot of the problem
There are some subtle ramifications to this request, consider the following retrieved URL http://www.acme.com/soa/schemas/order/xyz.xsd with a schema file containing the include <xsd:include schemaLocation="../../common/types.xsd"> If we didn't create the strangely named directory and lets say the project has a structure like: myProject build.xml ... src If the user selected src when retrieving http://www.acme.com/soa/schemas/order/xyz.xsd then if we wanted to keep the relative links from the import we would be creating types.xsd in ../../common which would be outside the project. If we also have only a single catalog per project, then adding relative entries in here will not be fool proof, as there could be files which need to be resolved differently based on the same URI. This could be argued to be a corner case, but having relative URI's in the catalog must be done with care. Plus the structure we would need to create would not necessarily make locating files easier.
I think we should think about a way to solve this. This is a low priority bug and you can downgrade it but from a user point of view if I launch the retriever on a directory then I would like to see this top level wsdl/xsd at that directory. If we do not do it then when I want import this top level wsdl, I need to go find these nested directories and then select my top level wsdl.
Should this issue be addressed by providing a more direct way through the import wizard to select the top level imported artifacts. Perhaps, we could add a Retrieved catagory which would show the retrieved files so that the user would not have to navigate through these folders.
Adding retriever in import dialog make sense. Currenly user comes to import dialog and realize that he needs to fetch something from the URL so he cancels import dialog then go to new-file- >file/folder\xml\external wsdl. So if we provide this in import dialog then that would be positive to the user. Also people were confused with new wsdl wizard and new external wsdl. They want one new wsdl\new schema wizard and have the functionality of retriever available there.