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 Tue, 28 Feb 2006 14:48:42 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2418?page=comments#action_12368107 ] 

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

I'm afraid I can't agree. Perhaps I'm missing something but there appears to be no way of
setting the allowedMethods and disallowedMethods properties so that I can have echoFloat be
disallowed (or not explicitly allowed, either way or even both) without it throwing an exception
when it tries to initialize the service. If it throws an exception on initialization when
you try to disallow a method, then disallowing a method isn't really a viable option.

> 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