Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Down to the wire?

David et al,
here's the current status on Web services.

1. "P1" functional items complete

All high priority items and some medium priority items in the wst.command [1], [2] and [3] milestone plans are complete. Axis 1.1 Java Web services (bottom-up and top-down) and clients are running. Axis EJB Web services in the Web service milestone plans were positioned as medium and could not be contained in M3. On the brighter side, the Web Service Explorer, lower priority for M3, is in. This seemed an appropriate exchange to make in the interest of having well-rounded Web services scenarios in M3.

2. running unit tests pass

There are no JUnit tests yet for the Web services scenario wizards. These are also under development. We would appreciate help from anyone willing to contribute testcases.

3. released map files can be imported to dev. environment

       a. with no compile errors
       All's well.
      b. and no PDE schema errors

       There were errors, but not any more. I just committed and released changes to fix several plugin.xml manifest compilation errors [4]

4. test tutorials can be performed without major bugs or work-around for "P1" items

There are four Web services tutorials available now from the "WTP Community" Web page [5]. We've been verifying them on an ongoing basis, and will keep doing so as integration builds appear.

5. posted test plans executed

Test plans written by Kathy Chan are posted [6]. We plan to run thru them on Wednesday.

6. all defects of 'major' or greater have at least been addressed (answered, if not fixed)

Most major defects resolved. At last count, one remained [7] which we will continue to chase, but is not severe enough to hold the milestone (IMHO). A few other defects / enhancements have been committed lately that merit a few words (literally - gory details are in the bugs).
The Web Service wizard launched from WSDL was defaulting to Skeleton EJB instead of Skeleton Java Bean. The default is fixed.
The behaviour of the WS-I Simple SOAP Binding Profile and Attachment Profile preferences did not match the behaviour of the WS-I test tools. Now it does.
There are several so-called "third party" jars and files that are not currently maintained in the Eclipse webtools repository or the WTP builds. There is an ANT task to help automate the process of downloading the necessary files into your PDE or WTP installation, however, it's easy to miss. Bug 85324 introduces a new plugin that checks for the presence of these third party files and, if any are absent, barks out a handy dialog early during Eclipse startup.


Cheers - CB.

Chris Brealey
Rational Studio Java Web Services, IBM Canada Ltd.
D3-275, D3/ENX/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
cbrealey@xxxxxxxxxx, 905.413.6038, tieline:969.6038, fax:905.413.4920

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-dev-admin@xxxxxxxxxxx

02/22/2005 11:15 AM

Please respond to

[wtp-dev] Down to the wire?

Its Tuesday already! Unfortunately some of the fixes put in head late last night did not make it to this
morning's I-build, but I think all dev. teams can continue testing with posted fixes/workarounds
until the next I-build, on Wednesday (preferably with this mornings I-build, but yesterday's or today's

is up to each team).

At this morning's PMC call the commitment to quality was (re)affirmed, so the milestone will

be delayed, probably by one full week, if we can not make our quality target for a milestone

build. To be explicit, I've listed the quality criteria below.

1. "P1" functional items complete

2. running unit tests pass

3. released map files can be imported to dev. environment

      a. with no compile errors

      b. and no PDE schema errors

4. test tutorials can be performed without major bugs or work-around for "P1" items

5. posted test plans executed

6. all defects of 'major' or greater have at least been addressed (answered, if not fixed)

7. component leads all vote "yes" and no substantial objections from contributors

Final countdown:

    expecting a "good and final" I-build on Wednesday.

    re-test on Wednesday's build

    last opportunity for critical fixes by Wednesday evening.
    re-test final build from Thursday morning

    vote on Thursday, by end of day, for your component. (state status, or reason of "no" votes).
    promote to "M" build on Friday, if appropriate, or decide by how much to delay.

If anyone has questions, knows now they can't make targets, or needs help, please let us know.

Thanks everyone for all the hard work!

Back to the top