Hey Wolfgang, It's great that you are weighing in with questions and suggestions.
When I started looking at the 181 spec I had the impression that the omission of the WebResult was identical to having a Oneway annotation thus making the use of Oneway somewhat redundant. After further review and discussion, I am thinking that there are in essence two types of Annotations in the 181 spec, decorative and indicative. The indicative annotations such as WebService, WebMethod and Oneway mean something special simply by existing. The decorative annotations like WebParam, WebResult and SOAPBinding will customize behavior if they specify any values for the annotation members but will revert to the default values if empty or absent. Does this view sound reasonable to you? It makes the Oneway useful as an indicator that the method should not return a value and WebResult would only be used to provide a custom name for the value. Thanks again for jumping into the discussion and if you have questions or suggestions regarding the WSM implementation put together so far, don't hesitate to holler. cheers, Jonathan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, September 19, 2004 9:33 PM To: Beehive Developers Subject: Re: Proposal for continously testing JSR-181 functionality Hi Michael, Jonathan > My suggestion is that the WebResult annotation must appear with the WebMethod annotation. > or at least warn "you'd better to add WebResult" or something like > that during the development stage.. I said above in my previous mail, but there's the Oneway annotation as well , so how about either the WebResult or Oneway annotation must appear with WebMethod ? Otherwise, an exception will be thrown. Thanks in advance. wolfgang
