Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » wsgen ant task <-> preferences
wsgen ant task <-> preferences [message #224816] Mon, 08 December 2008 22:06 Go to next message
Eclipse User
Originally posted by: mail.volker-wegert.de

Hello,

I don't know whether this is a bug, so I'd like to get some opinions
before reporting it as one... When using the Ant tasks to generate web
service implementation classes, the wsgen or WSDL2Java utility uses the
flags set in the preferences (Web Services --> Axis Emitter). This can
lead to strange issues if people forget to set these preferences
correctly, especially since you can't check these settings into a SCM
repository. IMHO these options should be available from the properties
file. What do you think?

Thanks
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *
This is the Time Travelling Agency's answering machine. We're closed right now
but leave a message before the beep and we might have called you back.
Re: wsgen ant task <-> preferences [message #225246 is a reply to message #224816] Mon, 15 December 2008 16:11 Go to previous messageGo to next message
Eric Peters is currently offline Eric Peters
Messages: 27
Registered: July 2009
Junior Member
Volker Wegert wrote:

> Hello,

> I don't know whether this is a bug, so I'd like to get some opinions
> before reporting it as one... When using the Ant tasks to generate web
> service implementation classes, the wsgen or WSDL2Java utility uses the
> flags set in the preferences (Web Services --> Axis Emitter). This can
> lead to strange issues if people forget to set these preferences
> correctly, especially since you can't check these settings into a SCM
> repository. IMHO these options should be available from the properties
> file. What do you think?

> Thanks
> Volker

Hi,

Thanks for the feedback Volker. Just curious what you mean by "strange
issues"?

Regarding the lack of setting these preferences in the web service wizards
& ANT tasks property files... this is by design- we don't expect many
users would want to change these on a per-web-service or
per-web-service-client basis, but rather most commonly users would set
these preferences at the workspace level then use them for several runs of
Web Service creation (via wizards or ANT tasks). The web service wizard is
(arguably) very fat in terms of being able to (re)define a non-default web
services preferences, so we've chosen to not expose those preferences that
users would not typically change on a per-web-service or
per-web-service-client basis.
Re: wsgen ant task <-> preferences [message #227862 is a reply to message #225246] Sun, 15 February 2009 19:57 Go to previous message
Eclipse User
Originally posted by: mail.volker-wegert.de

ericdp@ca.ibm.com (Eric D. Peters) writes:
> Volker Wegert wrote:
>> I don't know whether this is a bug, so I'd like to get some opinions
>> before reporting it as one... When using the Ant tasks to generate web
>> service implementation classes, the wsgen or WSDL2Java utility uses the
>> flags set in the preferences (Web Services --> Axis Emitter). This can
>> lead to strange issues if people forget to set these preferences
>> correctly, especially since you can't check these settings into a SCM
>> repository. IMHO these options should be available from the properties
>> file. What do you think?
> Regarding the lack of setting these preferences in the web service wizards &
> ANT tasks property files... this is by design- we don't expect many users
> would want to change these on a per-web-service or per-web-service-client
> basis, but rather most commonly users would set these preferences at the
> workspace level then use them for several runs of Web Service creation (via
> wizards or ANT tasks).

Agreed. The problem is, if someone checks out a project from a
repository into a fresh workspace and then executes the ant build
without adjusting the settings, bad things will happen...

> The web service wizard is (arguably) very fat in terms
> of being able to (re)define a non-default web services preferences, so we've
> chosen to not expose those preferences that users would not typically change
> on a per-web-service or per-web-service-client basis.

Personally, I think that's a bad idea in this case because it makes an
automated task dependent on some values that are set somewhere else, far
off the mental map.

Volker
Previous Topic:Launching the WSDL Editor from PlugIn
Next Topic:[Dynamic Web Project] JSP - Servlet - web.xml
Goto Forum:
  


Current Time: Tue Sep 23 08:24:28 GMT 2014

Powered by FUDForum. Page generated in 0.16894 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software