Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Fw: [wtp-dev] Testing Web services tools in WTP M3 candidate I-build 200502230727

Hi Adam,

We don't plan to support Axis 1.2 in WTP M3.  We had been testing with Axis 1.1 for M3.

As the Axis 1.2 release becomes available (the latest available driver is Axis 1.2RC2), we plan to move our support to it.  Since different user would likely have requirements for different levels of Axis, we plan to architect a design that would support generating Web service that can target different Axis releases (similar to how server tooling is supporting multiple Tomcat servers).

For the time being in M3, you could try modifying the instruction for copying third party JARs in the URL:

to change Axis1.1 to Axis1.2RC2 (which means copying the Axis 1.2RC2 JARs to the directory).

I tried driving the Axis 1.2RC2 emitter with a slightly different Web services tools code base a few weeks ago and had some initial success.  We had not pursue that further and had concentrated on testing the Axis 1.1 support.

If you run into problems, we could look into it and see if it can be easily solved by a patch.  Of course, you are more than welcome to submit a patch to enable this support.


Kathy Chan

----- Forwarded by Kathy Chan/Toronto/IBM on 23/02/2005 04:39 PM -----
Adam Kruszewski <spambox@xxxxxxxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx

23/02/2005 03:23 PM

Please respond to

Re: [wtp-dev] Testing Web services tools in WTP M3 candidate I-build 200502230727

Kathy Chan wrote:
> We are currently running FVT on the Web services tools in the WTP M3
>  driver on Windows and Linux.  Here's the link to the test plan:
> If there's anyone in the community interested in helping out the
> testing of the Web services tools to identify problem areas that
> needs to be addressed, you're more than welcome to do so.  If you
> find any defect that you think is critical to be addressed in M3,
> please let us know.

Is Axis 1.2 planned to be supported by M3 build? Axis1.1/Apache Soap in
version from first Eclipse 3.1M5a build are not really useful for those
working with J2SE5.0 (all autogenerated client proxies have imports of
packages named org.apache.<something>.*enum*)

Running Eclipse on J2SE5.0 when I tried to generate a bean based web
service I have got a nice bunch of exceptions (from
ClassNotFoundException claiming that my javabean was not found, to NPE
in axis core) but those are probably caused because Axis 1.1 is somewhat
not working right in J2SE5.0 environment.

wtp-dev mailing list

Back to the top