Well, do you not think that this scenario can be made to work? Not sure
why Axis2 cannot read the wsdl and remove the operations from the WSDL
file. I assume the WSDL is then kept in memory? Since Axis2 does update
the host/port in a static WSDL, I do not see why it could not remove the
operations that are excluded. Is this not possible?
Nadir Amra
From:
"Deepal Jayasinghe (JIRA)" <j...@apache.org>
To:
axis-dev@ws.apache.org
Date:
07/25/2009 10:19 AM
Subject:
[jira] Resolved: (AXIS2-4440) excludeOperations with static WSDL does not
work
[
https://issues.apache.org/jira/browse/AXIS2-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4440.
--------------------------------------
Resolution: Invalid
I am sorry I did not understand the question properly, Excluding an
operation does not prevent someone accessing that. Rather we exclude those
operation from auto generated WSDL
> excludeOperations with static WSDL does not work
> ------------------------------------------------
>
> Key: AXIS2-4440
> URL: https://issues.apache.org/jira/browse/AXIS2-4440
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.5, 1.4, 1.3
> Reporter: nadir amra
>
> A have a static WSDL file for my service. When I use excludeOperations
in services.xml i am still able to invoke the operation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
