axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Brandow (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2418) Unable to find Java method when method isn't allowed
Date Wed, 01 Mar 2006 00:58:40 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2418?page=comments#action_12368193 ] 

David Brandow commented on AXIS-2418:
-------------------------------------

Well, presumably the question is "why do you want to define echoFloat as a method on a web
service, but not allow it?"

The answer is that I want to write my WSDL with all the methods the web service could possibly
support and then choose after the fact whether to allow or disallow those methods.  If I have
to take out the definition of the method from the web service in order to disallow it (and
then add it back in again in order to re-allow it), thats a real pain, and its not how I read
the spec, nor how it used to work.

> Unable to find Java method when method isn't allowed
> ----------------------------------------------------
>
>          Key: AXIS-2418
>          URL: http://issues.apache.org/jira/browse/AXIS-2418
>      Project: Apache Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.3
>     Reporter: David Brandow
>     Priority: Critical
>  Attachments: echo.jar, server-config.wsdd
>
> I have a service that works fine when all the methods are allowed, either by listing
them all explicitly or by using an asterisk, but if one of those methods is not in allowedMethods
(whether its in disallowedMethods is irrelevant), the service won't work. This is the exception
I'm getting:
> Caused by: java.lang.Exception: Couldn't find a matching Java operation for WSDD operation
"echoFloat" (1 args)
>     | at org.apache.axis.InternalException.<init>(InternalException.java:71)
>     | at org.apache.axis.description.JavaServiceDesc.loadServiceDescByIntrospection(JavaServiceDesc.java:902)
>     | at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:477)
>     | at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(SOAPService.java:285)
>     | at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:500)
>     | at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
>     | at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
>     | at org.apache.axis.deployment.wsdd.WSDDDeployment.getService(WSDDDeployment.java:427)
>     | at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:231)
>     | at org.apache.axis.AxisEngine.getService(AxisEngine.java:311)
>     | at org.apache.axis.MessageContext.setTargetService(MessageContext.java:755)

-- 
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


Mime
View raw message