You are viewing a plain text version of this content. The canonical link for it is here.

Posted to rampart-c-dev@ws.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2008/02/27 04:18:53 UTC

[jira] Assigned: (RAMPARTC-71) Rampart does not work unless the operation name is in the URL

     [ https://issues.apache.org/jira/browse/RAMPARTC-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar reassigned RAMPARTC-71:
----------------------------------------

    Assignee: S.Uthaiyashankar  (was: Glen Daniels)

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