You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by John Kaputin <KA...@uk.ibm.com> on 2007/05/02 19:22:06 UTC

Sriram, getting started

Hi Sriram,
I have a couple of JIRA suggestions to get you started on Woden 
development. The JIRAs themselves are fairly straightforward, but they 
will give you some exposure to the Woden code base and to our testing 
procedures, which include creating junit tests for any new code and 
running the existing Woden junit test suite and the W3C WSDL 2.0 test 
suite for regression testing.  I can provide more info on how to do this 
and on any setup you might need to do in your development environment 
(will probably create a short Developer's Guide web page with info that 
will be useful to you).

WODEN-3: This JIRA is a simple change to an assertion error message, 
adding another parameter to the message template in messages.properties 
and modifying the method that formats this error message to include the 
new parameter.

WODEN-32: This JIRA is more work, but will touch all of the Woden 
component model giving you good code coverage. It involves implementing 
toString() methods for each of the WSDL components using the fragid syntax 
defined in the WSDL 2.0 spec.  I have attached a WSDL example to the JIRA 
showing what the component fragids would look like for this WSDL. You'd 
need to read the spec references in the JIRA to understand the requirement 
a bit more, then we can discuss any questions/issues via the woden-dev 
list and capture any decisions in the JIRA.

WODEN-149: Changing Woden to use the new WSDL 2.0 Assertion numbers 
created for Proposed Recommendation. This is a possibility for you too, 
but I first need to locate and review some scripts Arthur created for this 
change and have a think about testing.

I'd suggest you try WODEN-3 to get familiar with the development 
environment and testing, then move on to WODEN-32. Let me know what you 
think of these suggestions.

regards,
John Kaputin





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU







---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


Re: Sriram, getting started

Posted by Arthur Ryman <ry...@ca.ibm.com>.
Sriram,

If you'd like to work on WODEN-32, I can explain the fragids to you. [1]

[1] http://www.w3.org/TR/2007/WD-wsdl20-20070326/#frag-ids

Arthur Ryman, PhD, AoT, DE
Process and Portfolio Management, Rational Division

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-3831 (T/L: 318-8867)
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



John Kaputin <KA...@uk.ibm.com> 
05/02/2007 01:22 PM
Please respond to
woden-dev@ws.apache.org


To
woden-dev@ws.apache.org
cc
"sriram m" <sr...@gmail.com>
Subject
Sriram, getting started






Hi Sriram,
I have a couple of JIRA suggestions to get you started on Woden 
development. The JIRAs themselves are fairly straightforward, but they 
will give you some exposure to the Woden code base and to our testing 
procedures, which include creating junit tests for any new code and 
running the existing Woden junit test suite and the W3C WSDL 2.0 test 
suite for regression testing.  I can provide more info on how to do this 
and on any setup you might need to do in your development environment 
(will probably create a short Developer's Guide web page with info that 
will be useful to you).

WODEN-3: This JIRA is a simple change to an assertion error message, 
adding another parameter to the message template in messages.properties 
and modifying the method that formats this error message to include the 
new parameter.

WODEN-32: This JIRA is more work, but will touch all of the Woden 
component model giving you good code coverage. It involves implementing 
toString() methods for each of the WSDL components using the fragid syntax 

defined in the WSDL 2.0 spec.  I have attached a WSDL example to the JIRA 
showing what the component fragids would look like for this WSDL. You'd 
need to read the spec references in the JIRA to understand the requirement 

a bit more, then we can discuss any questions/issues via the woden-dev 
list and capture any decisions in the JIRA.

WODEN-149: Changing Woden to use the new WSDL 2.0 Assertion numbers 
created for Proposed Recommendation. This is a possibility for you too, 
but I first need to locate and review some scripts Arthur created for this 

change and have a think about testing.

I'd suggest you try WODEN-3 to get familiar with the development 
environment and testing, then move on to WODEN-32. Let me know what you 
think of these suggestions.

regards,
John Kaputin





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU







---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org