Bugzilla – Full Text Bug Listing
| Summary: | Expecting error msg if creating a Java bean Web service from a bean containing NO valid methods | ||
|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Seng Phung Lu <sengpl> |
| Component: | jst.ws | Assignee: | jst.ws <jst.ws-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
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. 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 *** Closing |
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() {}