axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Davis <...@us.ibm.com>
Subject RE: cvs commit: xml-axis/java/test/MSGDispatch TestService.java
Date Thu, 26 Sep 2002 12:57:37 GMT





Actually I think it matches the RPC style very nicely.  In RPC if you
specify "*" you'll get all public methods.  In MSG is you specify "*"
you'll get all public methods that *can* be MSG services.  RPC allows more
because it doesn't have any restrictions on the signatures - MSG isn't have
that luxury.  What Rick's change allows us to do is to have classes with
lots of public methods (including possibly lots of public MSG methods) to
be deployed without the annoyance of having to list all of them in the XML.
Its just a matter of convenience and if people don't like it then they
don't have to use "*" - and you clearly would fall into this category.
Besides, this just reverts us back to the old behavior we had before the
original change that broke all of this.  :-)
-Dug


Glen Daniels <gdaniels@macromedia.com> on 09/26/2002 08:41:03 AM

Please respond to axis-dev@xml.apache.org

To:    "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
cc:
Subject:    RE: cvs commit: xml-axis/java/test/MSGDispatch TestService.java



We're now changing the semantics of what "allowedMethods='*'" means - for
RPC/Doc services, it literally means all public methods should be web
methods.  Now for Message service it means "just the ones that match these
signatures".  I think that's confusing.  ("why is it saying 'no such
method'?")

I'm very close to -1 on it.  Why is this a good idea instead of having
people just specify the legal methods?

--Glen

> -----Original Message-----
> From: dug@apache.org [mailto:dug@apache.org]
> Sent: Thursday, September 26, 2002 8:21 AM
> To: xml-axis-cvs@apache.org
> Subject: cvs commit: xml-axis/java/test/MSGDispatch TestService.java
>
>
> dug         2002/09/26 05:20:39
>
>   Modified:    java/test/MSGDispatch TestService.java
>   Log:
>   Expand the test a little to make sure we don't restrict too much.
>   From the comment in the test:
>   Adding these dummy methods to make sure that when we deploy this
>   service using "allowedMethods="*" that we don't barf on them.
>   This will ensure that people can take classes that have public
>   methods (some available thru Axis and some not) and still be able
>   to deploy them.  (We used to throw exceptions about it)
>
>   Revision  Changes    Path
>   1.2       +9 -0      xml-axis/java/test/MSGDispatch/TestService.java
>
>   Index: TestService.java
>   ===================================================================
>   RCS file:
> /home/cvs/xml-axis/java/test/MSGDispatch/TestService.java,v
>   retrieving revision 1.1
>   retrieving revision 1.2
>   diff -u -r1.1 -r1.2
>   --- TestService.java             24 Sep 2002 20:45:20 -0000
1.1
>   +++ TestService.java             26 Sep 2002 12:20:39 -0000
1.2
>   @@ -75,6 +75,15 @@
>     * @author Glen Daniels (gdaniels@apache.org)
>     */
>    public class TestService {
>   +    // Adding these dummy methods to make sure that when
> we deploy this
>   +    // service using "allowedMethods="*" that we don't
> barf on them.
>   +    // This will ensure that people can take classes that
> have public
>   +    // methods (some available thru Axis and some not) and
> still be able
>   +    // to deploy them.  (We used to throw exceptions about it)
>   +    public void testBody(int t) {}
>   +    public void testElement(int t) {}
>   +    public void testEnvelope(int t) {}
>   +
>        public SOAPBodyElement [] testBody(SOAPBodyElement [] bodies)
>                throws Exception {
>
>
>
>
>




Mime
View raw message