Yaron Naveh

Greenhorn
+ Follow
since Oct 26, 2008
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Yaron Naveh

Example for interoperability between WSIT and Wcf using X.509 security:

http://webservices20.blogspot.com/2010/01/axis2-wcf-interoperability.html
10 years ago
I assume they mean that with RPC there are a few constraints on the message structure, e.g. the root element is the operation name and etc. In doc/lit you have more freedom. But I agree the statement in the link is a little vague.
11 years ago
Not sure. The security stuff may be ok under some configuration, but I don't know if Axis supports the correct WS-Addressing version.
11 years ago
It depends how you configure the WsHttpBinding.
The default setting of negotiateServiceCredentaial=true is not supported even by Axis2.
If you have changed this setting in WCF it is possible but I havn't tried it and I guess it can be very hard (even with Axis2)
11 years ago
The client needs to get something in order to know a fault has not occured.

If this is really important you can have a mini "service" on the client which the server can send faults to and make the original operation to one way, but I think you should leave it as is.
11 years ago
Maybe the original wsdl reference some other wsdl/xsd files which you didn't copy locally.
Check any <import /> <include /> elements.
11 years ago
Historically RPC style was used but it was found to hurt interoperability and some other concerns.
Today you should use document style. The biggest difference is that with document style the messages are valid according to some XML schema.
11 years ago
I think you are using a relatively old version of Axis.

With newer versions you should use the web service wsdl (on /WebSite3/Service.asmx?WSDL) to generate a client side proxy (using wsdl2java.bat for example). This should also be possible with your current version.

What you are doing in your code is ignoring the WSDL. The WSDL contains some important information with regarding to how request should look like. It might be possible to configure Axis to send correct message even in the way you do it but it is harder.
11 years ago
Use a tool like Fiddler or tcpMon to see what is the difference between the request SOAP that Axis and c# clients send
11 years ago
Dan

What is exactly your question? I think this sentence correctly describe the encryption process.
The url of the request is something you can control from the client.

Generally for classic web services the personId should not be in the url but inside the HTTP body. If you are doing something like a web service over GET then I'm not sure the .Net client can handle it directly, maybe you can just send HTTP requests from .Net.
11 years ago
I'm not sure about that, I suggest you will open a new thread
One's public key is known to everybody but his private only to him,

Everybody should be able to encrypt a message and only one person should be able to decrypt it. So everybody will use the receiver public key to encrypt and he will use his key to decrypt (only he should be able to do it).

A signature proves someones identity. With signature only the sender should be able to sign (so others will not be able to impersonate her). Since only she knows here private key she will use it for signing. Everybody should be able to authenticate the signature. So they use the public key which is the only one they know.
For Qa 1&4 are correct

For Qb 2&3 are correct

I think the way Qb is phrased is misleading somehow but technically 2&3 are correct.