+1.
I think it would be useful to define a set of SOA scenarios that Tusany is
developed to support. Overtime, these senarios can be implemented using
Tuscany and become part of the integration suite. We can use them as one way
to measure the functional completeness for Tuscany.
FYI: There are some initial efforts documented at the following wiki page:
http://wiki.apache.org/ws/Tuscany/TuscanyJava/Scenarios
Thanks,
Raymond
----- Original Message -----
From: "Dan Murphy" <[EMAIL PROTECTED]>
To: "Tuscany Developers" <[email protected]>; "Tuscany Users"
<[email protected]>
Sent: Monday, January 15, 2007 4:39 AM
Subject: SOA Scenarios
Hi,
There have been a number of postings about scenarios. For example:
- In July
http://www.mail-archive.com/[email protected]/msg04490.html
about JSF using Tuscany
- In Nov
http://www.mail-archive.com/[email protected]/msg00319.htmlas
part of the what next for C++
- More recently
http://www.mail-archive.com/[email protected]/msg00416.htmland
- http://www.mail-archive.com/[email protected]/msg12818.html
Would it be useful to document and maintain a set of scenarios that
Tuscany
does/will support?
These could be used to validate and help guide what get developed, rather
than relying "what next ?" postings (more permentant record). It could
also
be used to help identify complexity and completeness. Lastley it might
also
make it clearer to differenticate Tuscany from similar projects. Perhaps a
way to kick off would be to start gathering some user stories (rather than
more abstract scenarios)
WDYT ?
Cheers,
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
