Community
Participate
Working Groups
In the "new web service wizard" (same for the "new web service client" wizard) when building a web service from a wsdl file: If I select the option "Define custom mapping for namespace to package" it would be great if in the next step the table would be pre-filled with the values Axis uses to generate the java sources. There is some logic which takes the target namespace from the WSDL file and converts it to java packages. For example the attached WSDL file (target namespace is "http://adb.hr-online.de/WortDerWocheService/") results in a java package "de.hr_online.adb.WortDerWocheService". So this mapping should be displayed in the table. I will attach a screenshot where I entered the values (to show how I would expect it to look like). It makes sense to prefill the table because a) for beginners like me it is quite hard to understand how to use this wizard page (no doc available). b) input of the WSDL target namespace is not required, just change the java package name.
Created attachment 40128 [details] This is the WSDL file which contains the target namespace mentioned in the bug
Created attachment 40129 [details] This is how I expect the wizard to look like
I agree this would be very handy, and is something we've also wanted to do for some time. The catch is it's hard to do this without either predicting what conversion rules the Axis emitters will use or running the Axis emitters twice - once to produce the default mappings and a second time, if required, to generate code/XML using the customized mappings. The first is a maintenance nightmare, and the second has performance ramifications. We'll look into this for a future release.
Is there no public axis api availabe ? Axis needs to guess the packages either, and hopefully there might be a method "getClassesFromWSDL" or something like that ;-) ? If there is no chance: what about a button "create default" mappings in the wizard dialog which runs the axis emitter ? This way the user can run the dummy axis class creation on demand and is not always hit by the duplicate generation delay.
We would not be able to address this given the current resource on the team. We would welcome help from the community to contribute code for this if the community feels that this is important. Please note that starting with WTP 2.0, we now support creating Axis2 Web service in addition to Axis1 Web service. In the Axis2 client and skeleton page, the default namespace and package mapping is shown.
We currently don't have any plan to address this requirement.
Please verify the defect you originated with a recent WTP driver which could be found in: http://download.eclipse.org/webtools/downloads/ If defects in resolved state is not verified within a couple of weeks, the development team might verify and close the defect on the originator's behalf. Thank you for your attention!
Closing...
