EDN Admin
Well-known member
Background: Ive been tasked with rewriting a Java web services client in .NET. I chose C# because a) Im more familiar with it than VB and b) its more similar in syntax/structure to Java than VB. My office does not have any Java "experts",
only one guy whos familiar with Java but could not accomplish in a year what I accomplished in 45 minutes with figuring out the structure of the client. Nevertheless, Im struggling to conceptualize the structure of the new C# client because of the use of
a number of Java libraries that Im not familiar with.
Current situation: Ive received the Java clients source code from its original developers. A lot of it used custom classes that I havent had any trouble rewriting in C# (though the Java enum type is substantially different from C# enums
that I had to figure out a way to rewrite those as classes). Ive also been able to use Java Decompiler to crack open the jar files for a number of the libraries that were used so I could have a look at their source code. The Java client is using the Axis2
library to set up the communications with the web service, and Ive now got both the Java and C source code for it. While Id love to find that there is some sort of 1:1 or at least 1:0.9 equivalency with a C# library for it, I can dig up the info I need on
C# libraries to construct general equivalencies on my own.
The problem: This is my first foray into writing anything for Web Services. My primary field of experience has been back-end application programming, working with data models and an old Pick database. As such, I dont know how to implement
the certificates that are needed in order to communicate with the web service (two X509.3 certs), nor how to work with the XML/SOAP/MTOM models that are the required communication structure for the web service.
What Ive done so far to solve this on my own: Ive done a number of searches on the general internet, on the MS KB, on here, and on CodeProject. Ive found a large number of articles that touch on WS in general and on using certificates,
but partly due to the challenge of coalescing so many different information sources and partly due to my inexperience, I havent yet gleaned enough knowledge to be able to create a basic test client to verify that I can communicate with the WS through C#.
Im sure its possible, but neither I nor the rest of the people in my office have ever been successful with exactly that challenge.
What I need: Please explain to me the basic structure in C# (or in general) for calling a web service using SOAP and MTOM as the protocols, using existing installed certificates to ensure that the web service is willing to talk. I dont
need the code written for me; I just need a single source that says "This is how you do it." Even a collection of links described as "Do this first <link>, then do this <link>" would be great. Thank you in advance for any help, and of course if
you need more information about whats going on in the client I will try to give you a useful answer.
View the full article
only one guy whos familiar with Java but could not accomplish in a year what I accomplished in 45 minutes with figuring out the structure of the client. Nevertheless, Im struggling to conceptualize the structure of the new C# client because of the use of
a number of Java libraries that Im not familiar with.
Current situation: Ive received the Java clients source code from its original developers. A lot of it used custom classes that I havent had any trouble rewriting in C# (though the Java enum type is substantially different from C# enums
that I had to figure out a way to rewrite those as classes). Ive also been able to use Java Decompiler to crack open the jar files for a number of the libraries that were used so I could have a look at their source code. The Java client is using the Axis2
library to set up the communications with the web service, and Ive now got both the Java and C source code for it. While Id love to find that there is some sort of 1:1 or at least 1:0.9 equivalency with a C# library for it, I can dig up the info I need on
C# libraries to construct general equivalencies on my own.
The problem: This is my first foray into writing anything for Web Services. My primary field of experience has been back-end application programming, working with data models and an old Pick database. As such, I dont know how to implement
the certificates that are needed in order to communicate with the web service (two X509.3 certs), nor how to work with the XML/SOAP/MTOM models that are the required communication structure for the web service.
What Ive done so far to solve this on my own: Ive done a number of searches on the general internet, on the MS KB, on here, and on CodeProject. Ive found a large number of articles that touch on WS in general and on using certificates,
but partly due to the challenge of coalescing so many different information sources and partly due to my inexperience, I havent yet gleaned enough knowledge to be able to create a basic test client to verify that I can communicate with the WS through C#.
Im sure its possible, but neither I nor the rest of the people in my office have ever been successful with exactly that challenge.
What I need: Please explain to me the basic structure in C# (or in general) for calling a web service using SOAP and MTOM as the protocols, using existing installed certificates to ensure that the web service is willing to talk. I dont
need the code written for me; I just need a single source that says "This is how you do it." Even a collection of links described as "Do this first <link>, then do this <link>" would be great. Thank you in advance for any help, and of course if
you need more information about whats going on in the client I will try to give you a useful answer.
View the full article