Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 135167 - Expecting error msg if creating a Java bean Web service from a bean containing NO valid methods
Summary: Expecting error msg if creating a Java bean Web service from a bean containin...
Status: CLOSED DUPLICATE of bug 132905
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: jst.ws (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: jst.ws CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-05 18:22 EDT by Seng Phung Lu CLA
Modified: 2006-06-19 10:40 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Seng Phung Lu CLA 2006-04-05 18:22:39 EDT
Running bottom up Java bean Web services with no methods does not produce any error or warning messages with Axis/Tomcat. I was expecting a warning or error message.

ie. public class Echo() {}
Comment 1 Seng Phung Lu CLA 2006-04-05 18:24:23 EDT
Forgot to mention that "public static" methods are allowed by Axis/Tomcat configuration.  This doesn't seem correct to me.  The wizard should constrain for only "public" methods.
Comment 2 Chris Brealey CLA 2006-04-05 23:27:48 EDT
Referring to classes with no public methods, this is a good example of a condition to catch under bug 132905, therefore, returning as a duplicate.

JSR-109 does not allow public static methods, however, JAX-RPC has nothing to say about the matter. Apache Axis, which is JAX-RPC but not JSR-109 compliant, handles public static methods just fine, and the semantics seem fairly clear. Why do you feel public static methods should not be allowed, at least for Axis?

*** This bug has been marked as a duplicate of 132905 ***
Comment 3 Seng Phung Lu CLA 2006-06-19 10:40:26 EDT
Closing