Woden-49 to Woden-55:
My idea for these JIRAs was, as you say, a test case for each API method
and I do think this could/should be contained within M7. These are just
method signature tests. The full functional tests, which I suggest should
be provided by the W3C WSDL 2.0 test suite, will test in more details the
type of information contained in those elements and attributes - they
should fully test the spec and in doing so, will test the implementation of
these Woden methods.
Woden-108:
I think this JIRA needs to be dealt with for M7 - whether we implement a
solution in Woden or close Woden-108 and open a JIRA against Axis2 is to be
determined.
John Kaputin
Lawrence Mandel
<[EMAIL PROTECTED]
om> To
[email protected]
07/12/2006 04:58 cc
Subject
Please respond to Re: [VOTE] JIRAs flagged for M7
[EMAIL PROTECTED]
he.org
I'm +1 on all the Jiras except those I've listed in this e-mail. For those
I've listed I'd like some more information before giving my +1.
Woden-49 to Woden-55
John, I seem to recall you saying that these unit test Jiras would be
solved by the improved WSDL working group test suite. As your comment in
each of the Jiras states,
"The objective here is simply to test the Woden API. Complete functional
tests for service and endpoint should be provided by the W3C WSDL 2.0 Test
Suite. "
I agree with this comment that the tests in the WSDL working group test
suite are functional tests and the unit tests identified in these Jiras
should focus on testing individual methods. If this is the case I'd like
to see these Jiras resolved by creating method level tests rather than
simply relying on the WSDL test suite. Can this work be contained in M7?
Woden-108
I'm not sure this Jira should be handled by Woden. This seems like an
Axis2 problem to me.
Thanks,
Lawrence
John Kaputin <[EMAIL PROTECTED]>
12/01/2006 11:41 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
[VOTE] JIRAs flagged for M7
Of the 49 outstanding JIRAs, 33 are now flagged for the M7 release. When
I
went through the list I commented in some of the non-M7 JIRAs why they
shouldn't be flagged for M7 - that doesn't exclude them from being done
for
M7, it just means they are no 'show stoppers' for M7.
Before next Tuesday's Woden call/chat can you please review the M7 list
and
the non-M7 outstanding JIRAs and comment on the JIRA or mailing list if
you
think any JIRAs should/shouldn't be on the M7 list.
If you are happy with the M7 list please vote your acceptance to
woden-dev,
so that hopefully by Tuesday we can agree the scope for M7 and then think
about effort, time and a likely release date.
Here's my +1 for the current M7 JIRA list.
regards,
John Kaputin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
