You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org> on 2005/08/09 16:00:35 UTC
[jira] Created: (BEEHIVE-877) WebService / WebMethod rules changed in latest spec
WebService / WebMethod rules changed in latest spec
---------------------------------------------------
Key: BEEHIVE-877
URL: http://issues.apache.org/jira/browse/BEEHIVE-877
Project: Beehive
Type: Bug
Components: Web Services (181)
Versions: v1m1
Environment: dist built from SVN
Reporter: Jeremiah Johnson
Assigned to: Eddie O'Neil
Fix For: TBD
The JSR-181 specification has a change that defines the rules for when a method should be exposed as a Web method.
--- JSR-181 v0.9.2 (Dec '04)
If the implementation bean does not implement a service endpoint
interface, it must include @WebMethod annotations on each method that is
to be exposed as a Web Service operation. More information on the
@WebMethod annotation may be found in section 5.2.
--- JSR-181 v1.0 (June '05)
If the implementation bean does not implement a service endpoint
interface, all public methods other than those inherited from
java.lang.Object will be exposed as Web Service operations. This
behavior can be overridden by using the WebMethod annotation to specify
explicitly those public methods that are to be exposed. If a WebMethod
annotation is present, only the methods to which it is applied are
exposed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-877) WebService / WebMethod rules changed in latest spec
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-877?page=all ]
Jeremiah Johnson updated BEEHIVE-877:
-------------------------------------
Attachment: BEEHIVE-877-patch.txt
BEEHIVE-877-patch.txt is a patch that I would suggest for use in implementing the JSR-181 change. 9 tests are added in the WSM DRT suite to validate functionality defined in section 3.1 of the JSR-181 v1.0 spec. If this patch is applied, you will need to issue 'svn add' on the following 3 files:
wsm/drt/tests/org/apache/beehive/wsm/test/axis/wsdl/WebMethodOverrideTest.java
wsm/drt/webapp/WEB-INF/src-ws/webservice/AllPublicMethods.java
wsm/drt/webapp/WEB-INF/src-ws/webservice/WebMethodOverride.java
IMPORTANT: don't apply this patch without changing the WSM implementation because it would break the build. The AllPublicMethods Web service has non-public methods in it and even though they don't use the WebMethod annotation, the build breaks.
> WebService / WebMethod rules changed in latest spec
> ---------------------------------------------------
>
> Key: BEEHIVE-877
> URL: http://issues.apache.org/jira/browse/BEEHIVE-877
> Project: Beehive
> Type: Bug
> Components: Web Services (181)
> Versions: v1m1
> Environment: dist built from SVN
> Reporter: Jeremiah Johnson
> Assignee: Eddie O'Neil
> Fix For: TBD
> Attachments: BEEHIVE-877-patch.txt
>
> The JSR-181 specification has a change that defines the rules for when a method should be exposed as a Web method.
> --- JSR-181 v0.9.2 (Dec '04)
> If the implementation bean does not implement a service endpoint
> interface, it must include @WebMethod annotations on each method that is
> to be exposed as a Web Service operation. More information on the
> @WebMethod annotation may be found in section 5.2.
>
> --- JSR-181 v1.0 (June '05)
> If the implementation bean does not implement a service endpoint
> interface, all public methods other than those inherited from
> java.lang.Object will be exposed as Web Service operations. This
> behavior can be overridden by using the WebMethod annotation to specify
> explicitly those public methods that are to be exposed. If a WebMethod
> annotation is present, only the methods to which it is applied are
> exposed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira