Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change 
notification.

The following page has been changed by JohnKaputin:
http://wiki.apache.org/ws/FrontPage/Woden/TaskList

The comment on the change is:
Closed a completed task.

------------------------------------------------------------------------------
  Documented use cases covering the various usage scenarios for Woden would 
help to clarify our collective understanding of the total requirements to be 
met by Woden and why certain design or implementation choices are necessary. So 
far, development has focussed on parsing and validation (i.e. read-only at 
runtime), but we need a better understanding of the WSDL creation / editing / 
writing requirements (e.g. re-validation after modification, preserving 
whitespace, etc).
  ==== Status ====
  Initial attempts at identifying actors and use cases by John Kaputin and 
Jeremy Hughes. Will post work-in-progress to wiki or web site when we have 
something documented. Will need broader input from others on this.
- -----
- == element=union of xs:QName, xs:token ==
- The ''element'' attribute of interface operation <input> and <output> can be 
a QName or a token. Currently just implemented as type QName. Need to model 
this with inheritance and change the implementation to handle either.
- ==== Status ====
- Not started.
  -----
  == Message label ==
  The ''messageLabel'' attribute of the message reference or fault reference 
elements is currently implemented as a type-safe enumeration with the values 
'In' and 'Out'. This needs to be implemented either as an extensible enum or 
perhaps just as an NCName.
@@ -175, +170 @@

  02Feb06: Unit tests completed for {{{ServiceElement}}}, {{{EndpointElement}}} 
(in SVN, but did not make M3 build).[[BR]]
  Unit test reqs captured by JIRAs WODEN-49,50,51,53,54,55
  -----
+ == element=union of xs:QName, xs:token ==
+ The ''element'' attribute of interface operation <input> and <output> can be 
a QName or a token. Currently just implemented as type QName. Need to model 
this with inheritance and change the implementation to handle either.
+ ==== Status ====
+ Implemented in M6 or earlier
+ -----
  
  == END of Closed Tasks ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to