InteropBlog: Beyond Web Services, a look at a Java/.NET bridge

Discussions

News: InteropBlog: Beyond Web Services, a look at a Java/.NET bridge

  1. While the JNBridgePro interoperability tool does support SOAP and XML, there is a distinct effort here to formulate an approach that 'lets the Java do java, and the .NET do .NET.' JNBridgePro builds its bridge by generating a set of proxies that expose classes’ APIs and manages communications between .NET and Java classes. Now that Web services' pros and cons are more known, developers may find favor with these somewhat more programmatic approaches. The company has recently added improved support for Winforms on one side and AWT and Swing on the other. From the story:
    Web services are ‘'tied to text messages - tied to ASCII, and ASCII is very verbose,” said Wayne Citrin. “You throw in XML and these extra words and constructs.” That is one problem with XML. “The whole service-oriented approach is really very narrow,” said Citrin. ''You are, by design, exposing a narrow view - like peaking through a keyhole. What happens is that developers and customers sometimes really want to access an API, not a service.'' ''You have rich APIs like EJB or JMS. They are complex. These are not just a single service that you just access''
    http://tssblog.techtarget.com/index.php/xmlweb-services/beyond-web-services-a-look-at-bridging-javanet-apps/

    Threaded Messages (1)

  2. NO MORE ... YAR[ Go to top ]

    Why is everyone always trying to reinvent the wheel. Focus on making what's exists better and stable. Fabulous a protocol fpr Java/.NEt but what if your consumer is in PHP, RPG or any other of the hundreds of diffrent languges out there. Waste of time