.net - Better solution for WCF service(s) that talk to 3rd party Java services? -
I am in a scenario where I have to integrate with my work on a third party system that works with Java-based web services Displays. I can parse the service WSDL definition and generate a proxy class and work with them in the NAT world. However, services are not called "clean" in such a way that the name of property in the Java application's object model is extremely complex, and the servers hosting the Java environment will sometimes go down and point-to-point, when the mine client The URI is not responding, so the apps do not strengthen it. I did not even want to include service implementation logic in my web app because these Java services reuse multi use The possibilities are because businesses often use the same data, which asks for new things.
What I did some time ago, some "cover" WCF services that handle property mapping and provide a better interface for our developers to develop against it. However, this solution does not look great because I want to apply some routing and some other features and want to remove Java service from 1: 1 rapper WCF. Is there a good way to handle this slightly more dynamically using WCF 4 features? I think the biggest hurdle is that I have no access to Java services changes and developers who support that side are not much familiar with Java. Even trying to explain the EOS / SOA concepts is usually a lost cause.
Any person using WCF as a proxy service gateway for third-party services? If so, how do you manage the mapping of fields from your WCF data object to a more dynamic 3-party service? Are you using WSDL from third party service to generate binding contracts and proxy classes in your WCF layer?
Thank you. I know this is a very comprehensive question and 100% is not the right or wrong solution. Just looking for some feedback on this architecture I get a lot of information about a WCF service, which is the routine service of other WCF services Interacted with, but often works as a Gateway for WCF routes or Java-based services.
Then, this is my current architecture.
.NET Client -> WCF Service (mapping, property cleanup, and some minor biz logic) -> Java-based web service - > Source data (Big Asset Management System)
If you need 3rd party integration, service reuse, routing, mapping, etc. are required, then you need an ESB that provides you with Will do There are many features 'out of the box' and you will save your custom mediator while not developing, you can try with the WSO2 (Open Source).Regards, Jose
Comments
Post a Comment