Home » Language IDEs » ServerTools (WTP) » Flakiness of web services tools
| Flakiness of web services tools [message #143434] |
Thu, 13 October 2005 14:24  |
 Jeff Shirley
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Hi,
First let me say that I really appreciate the work all you guys
developing WTP are doing. I've been an Eclipse user for quite some time
and I really like the direction things are going. WTP seems a little bit
rough around the edges to me right now, however.
(Some/all of these things are most likely the result of my specific
circumstances. I've managed to find workarounds for most, but not all,
of them.)
1. Automatic deployment of dependency JARs. I have a web service project
which depends on several other Eclipse packages as well as an external
JAR file. Right now, it doesn't appear to be possible to satisfy the
runtime requirements on the Tomcat 5.5 server I'm using without manually
copying the JAR files over. Ideally if a web project depends on other
projects or JAR files to build and run all this should automatically
happen. At the moment, I can't seem to get it to work that way (although
a bug I commented on was recently fixed allowing a partial solution to
the problem - thanks!). This could be my fault for not configuring
something correctly in Eclipse.
2. When I generate a webservice from a Java bean with certain classes as
parameters, it spits out a WSDL namespace error in the generated WSDL
file and refuses to go on. This appears to happen with some, but not
all, classes from the standard library (specifically X509Certificate or
RSAPublicKey do create the error but String or primitive types do not).
Do I need to update a schema somewhere in WTP's configuration to get
this to work? Right now I'm working around it using
ByteArray{Input,Output}Stream and some code I have to encode byte arrays
as a hex string. I can give more detail on this error if needed.
3. What version of the JDK and Tomcat are ideally recommended for use
with WTP? I'm using JDK 1.5 and Tomcat 5.5x, FWIW (Axis 1.2.1). Is this
configuration recommended or should I drop to older versions?
4. I seem to have problems with webservices taking as parameters or
returning array types. It seems to bomb out/generate an invalid WSDL
file, although the methods do show up in the wizard. Is this an Axis
problem?
Again, thanks for your time and thanks for the hard work on WTP. Much
appreciated!
|
|
|
| Re: Flakiness of web services tools [message #143607 is a reply to message #143434] |
Fri, 14 October 2005 11:44  |
Eclipse User |
|
|
|
Originally posted by: ns_dkerber.ns_WarrenRogersAssociates.com
In article <dilqnq$594$1@news.eclipse.org>, jshirley@cs.virginia.edu
says...
> Hi,
> First let me say that I really appreciate the work all you guys
> developing WTP are doing. I've been an Eclipse user for quite some time
> and I really like the direction things are going. WTP seems a little bit
> rough around the edges to me right now, however.
>
> (Some/all of these things are most likely the result of my specific
> circumstances. I've managed to find workarounds for most, but not all,
> of them.)
>
> 1. Automatic deployment of dependency JARs. I have a web service project
> which depends on several other Eclipse packages as well as an external
> JAR file. Right now, it doesn't appear to be possible to satisfy the
> runtime requirements on the Tomcat 5.5 server I'm using without manually
> copying the JAR files over. Ideally if a web project depends on other
> projects or JAR files to build and run all this should automatically
> happen. At the moment, I can't seem to get it to work that way (although
> a bug I commented on was recently fixed allowing a partial solution to
> the problem - thanks!). This could be my fault for not configuring
> something correctly in Eclipse.
Do you mean on your production or development machine? For production,
it's a pain to keep changing settings to keep my dependency jars from
being included in the built war, because I have them deployed in the
shared/lib folder on my production Tomcat server. On my development
machine, there is an issue where I need to put them in the project's
web-inf/lib folder, even when they are added to the build path dialog.
There is certainly room for some improvement with dependency settings in
the WTP, but I've always managed to get things to work the way I need to
(though sometimes it took a while to get the right combination of
settings).
....
> 3. What version of the JDK and Tomcat are ideally recommended for use
> with WTP? I'm using JDK 1.5 and Tomcat 5.5x, FWIW (Axis 1.2.1). Is this
> configuration recommended or should I drop to older versions?
I use WTP with two different jdk/tomcat installations, one is the same
as yours: JDK 1.5 and Tomcat 5.5.9 (recently upgraded to 5.5.12), and
the other is a 1.4.2_08 with the latest Tomcat 4.x. The 1.5/5.5.12
installation is much more stable than the 1.4/4.x.
--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
|
|
|
| Re: Flakiness of web services tools [message #143885 is a reply to message #143607] |
Fri, 14 October 2005 17:22 |
Jeff Shirley
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
David Kerber wrote:
> In article <dilqnq$594$1@news.eclipse.org>, jshirley@cs.virginia.edu
> says...
>
>>Hi,
>>First let me say that I really appreciate the work all you guys
>>developing WTP are doing. I've been an Eclipse user for quite some time
>>and I really like the direction things are going. WTP seems a little bit
>>rough around the edges to me right now, however.
>>
>>(Some/all of these things are most likely the result of my specific
>>circumstances. I've managed to find workarounds for most, but not all,
>>of them.)
>>
>>1. Automatic deployment of dependency JARs. I have a web service project
>>which depends on several other Eclipse packages as well as an external
>>JAR file. Right now, it doesn't appear to be possible to satisfy the
>>runtime requirements on the Tomcat 5.5 server I'm using without manually
>>copying the JAR files over. Ideally if a web project depends on other
>>projects or JAR files to build and run all this should automatically
>>happen. At the moment, I can't seem to get it to work that way (although
>>a bug I commented on was recently fixed allowing a partial solution to
>>the problem - thanks!). This could be my fault for not configuring
>>something correctly in Eclipse.
>
>
> Do you mean on your production or development machine? For production,
> it's a pain to keep changing settings to keep my dependency jars from
> being included in the built war, because I have them deployed in the
> shared/lib folder on my production Tomcat server. On my development
> machine, there is an issue where I need to put them in the project's
> web-inf/lib folder, even when they are added to the build path dialog.
> There is certainly room for some improvement with dependency settings in
> the WTP, but I've always managed to get things to work the way I need to
> (though sometimes it took a while to get the right combination of
> settings).
>
> ...
I'm talking about development. I can get everything to go in the right
place if I'm trying to set it up on a public server, since it's a
one-time thing, but I don't want to have to fiddle with it constantly to
get it to work correctly on my development machine. I've had to do the
same thing you did: place the JAR files in the web-inf/lib manually
since it didn't seem to work when I used the GUI settings (I'm using Ant
for this now to automate it, but it certainly was nonintuitive). It
would be nice if there was some more flexibility here and better
description of what the various settings actually do. I had another
problem that was caused by WTP unjarring a signed jar file when creating
the war, and the solution to that was nonobvious from the GUI as well.
Several of the dialog boxes relating to this seem to have rather serious
bugs as well (such as portions of the settings disappearing and freezing
up when errors/exceptions are encountered). I'm hoping this gets
improved quite a bit before the final 1.0 release.
>
>
>>3. What version of the JDK and Tomcat are ideally recommended for use
>>with WTP? I'm using JDK 1.5 and Tomcat 5.5x, FWIW (Axis 1.2.1). Is this
>>configuration recommended or should I drop to older versions?
>
>
> I use WTP with two different jdk/tomcat installations, one is the same
> as yours: JDK 1.5 and Tomcat 5.5.9 (recently upgraded to 5.5.12), and
> the other is a 1.4.2_08 with the latest Tomcat 4.x. The 1.5/5.5.12
> installation is much more stable than the 1.4/4.x.
>
Good to hear that. I just upgraded to 5.5.12 also, and it does seem to
be a lot less problematic than 5.5.9. Maybe some of the issues I was
having were caused by Axis rather than WTP. Hopefully the next build of
WTP will be a bit better.
|
|
|
Goto Forum:
Current Time: Fri Apr 19 23:31:46 GMT 2024
Powered by FUDForum. Page generated in 0.02959 seconds |
] 
Search
Help
Register
Login
Home
