You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2006/03/20 05:39:30 UTC
[jira] Resolved: (AXIS2-397) allowedMethods in services.xml
[ http://issues.apache.org/jira/browse/AXIS2-397?page=all ]
Deepal Jayasinghe resolved AXIS2-397:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
done
> allowedMethods in services.xml
> ------------------------------
>
> Key: AXIS2-397
> URL: http://issues.apache.org/jira/browse/AXIS2-397
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
> Fix For: 0.95
>
> We need to add an allowedMethods parameter in services.xml just like Axis1 has.
> Quoting Deepal:
> Service Operations
> There was a mail thread in the mailing list about that topic and we came to
> conclusion that , we are going to display all the public method in the
> service impl class. And using services.xml user can override or add
> parameters to those operation. IF there is a wsdl in META-INF then all the
> operations in the portType will be published and user can override them
> using services.xml.
> its implemented . So if the service impl class is implement in Java then it
> is not require to have any operation tag in services.xml unless user want to
> override something.
> But I think we need to improve that , meaning user should be able to control
> the operation that he need to expose , currently user dose not have any
> control over that and all the public methods in service impl class will be
> 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