[
https://issues.apache.org/jira/browse/RAMPARTC-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572766#action_12572766
]
S.Uthaiyashankar commented on RAMPARTC-71:
------------------------------------------
This is because, rampart checks the policy according to operation. So, either
you have to give the operation in the URL or you have to give mapping of action
-> operation in service.xml file.
If you give the mapping, then url can be
http://localhost:9090/axis2/services/myservicename . In this case the mapping
will be as follows, where "myactionstring" is the wsa:Action of the request
<operation name="myoperation">
<parameter name="wsamapping">myactionstring</parameter>
</operation>
> Rampart does not work unless the operation name is in the URL
> -------------------------------------------------------------
>
> Key: RAMPARTC-71
> URL: https://issues.apache.org/jira/browse/RAMPARTC-71
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.1.0
> Environment: Windows XP
> Reporter: Dave Meier
> Assignee: S.Uthaiyashankar
> Priority: Critical
> Fix For: Current
>
>
> Using regular SOAP calls without rampart I can use
> http://localhost:9090/axis2/services/myservicename as the URL and axis2/c
> gets the operation name out of the XML. With rampart, it only works if I add
> the operation name to the end of the URL (e.g.
> http://localhost:9090/axis2/services/myservicename/myoperation). This adds a
> lot of complexity to the client as I have to use a different URL for each
> operation.
> I am using Visual Studio 2005 C# as the client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
