| RE: [wtp-incubator-dev] Should we drop the POJO web service type in the Web Services wizard? |
|
Hi Danail, If you leave aside the support for starting with an endpoint interface we're a close match to what you described. > Also note that if the “endpointInterface” is specified, the implementation class is not required to implement the SEI via the “implements” java keyword There are a series of validation rules that check for this in the Java Editor but there was a restriction in the CXF SEI configuration page in the wizard that restricted the SEI selection to the type hierarchy. I'm fixing that as part of https://bugs.eclipse.org/bugs/show_bug.cgi?id=287352 > 1. Do not use explicit SEI (i.e. the “endpointInteface” parameter of the @WebService annotation will not be set) > 2. Use an existing SEI (the user is able to browse for existing java interface) > 3. Generate a new SEI out of the methods which the user enabled for the web service The configuration page already handled 1 and 3 and with that fix above in place it will handle the browsing aspect of item 2. >I cannot imagine that a developer would write the class, navigate to the interface, start the wizard on the interface and browse back to the implementation class… It would be simply lots of clicking J It can work out quicker actually. If you compare both starting point approaches (implementation/interface) in certain circumstances it can work out at 2 clicks less when starting from an interface to get to the end of the configuration page. Thanks, Shane See all the ways you can stay connected to friends and family |