Note that there are some explanatory texts on larger screens.

plurals
  1. POCalling Java WS from .NET - Java way uses Apache Rampart, .NET equivalent
    primarykey
    data
    text
    <p>A vendor we're integrating with provides some web-service functions... They developed it in Java, and also gave us an example client project (in Java) that shows the consumption of those web-services. We actually want to implement the consumption/interface of the web-services with .NET, but we're not able to figure out how the security should work.</p> <p>In their Java client example, they appear to be using something called "Apache Rampart". They have code within that looks like this: </p> <pre><code>public static void initSecurityPolicy(ServiceClient client) throws Exception { Options options = client.getOptions(); options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, loadPolicy("policy.xml")); options.setUserName(USERID); options.setPassword(PASSWD); options.setTimeOutInMilliSeconds(READTIMEOUT); client.engageModule("rampart"); } </code></pre> <p>Could someone help me in what I should be looking for, in the .NET world, to do the equivalent of this? Currently, in my .NET project.. I can consume their WSDL fine, and it generates the proxy objects perfectly fine, but if I try to run/invoke any function, it tells me "missing SOAP header" and I believe it's security-related. </p> <p>They also provide me the policy.xml file. I'm a novice .NET programmer and I usually rely on the proxies that VStudio generates to handle any WS-related programming, so I'm not sure what to do with that policy.xml file, nor do the equivalent of what they do in the code above in the .NET world. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload