BT

InfoQ Homepage Interop Content on InfoQ

Articles

RSS Feed
  • Fighting Developer Fatigue with JNBridge

    Developer fatigue is the overwhelming frustration felt by developers who are under pressure to keep current with a flood of new languages, libraries, frameworks, platforms and programming models. JNBridge offers a way to help alleviate developer fatigue by allowing you to mix the libraries you know with code written in the language you are learning.

  • Getting Started With SharePoint Web Services

    Programmatic access to SharePoint is limited to .NET based languages unless a developer utilizes web services. Trent provides examples of how to extend the out of the box web services and how to consume them from both .NET and Java.

  • Open Source WS Stacks for Java - Design Goals and Philosophy

    InfoQ's Stefan Tilkov questioned lead developers of Apache Axis2, Apache CXF, Spring Web Services, JBossWS and and Sun’s Metro about their design goals, their approach towards Java and Web services standards, data binding, accessing XML, interoperability, REST support, and framework maturity. The results revealed many similarities and some noteworthy differences.

  • Interview: Dino Chiesa on Microsoft's SOA strategy

    Microsoft has intensified its marketing efforts on SOA with the launch of a new web site, a series of webinars, an ebook, “SOA in the Real World” and the “SOA & Business Process Conference 2007”. In the next couple of months Microsoft will also be releasing .Net 3.5 and an ESB Guidance. InfoQ talked to Dino Chiesa, Director of Marketing for .Net to better understand Microsoft's SOA strategy.

  • Messaging Interop with JMS & Spring.NET

    Message oriented middleware has long been a popular choice to integrate diverse platforms. Using MOM as a basis for communication between .NET and Java this article demonstrates interoperability between a .NET client and a Java middle tier using the JMS support in the Spring framework, available for .NET as well as Java, to provide a common programming model across both tiers of the application.

  • In-process Interoperability

    The two most popular managed environments (the JVM and the CLR) are in fact, nothing more than a set of shared libraries, each providing services to executing code such as memory management, thread management, code compilation (JIT), etc. Using both the JVM and the CLR inside the same operating system process is easy, since any process is capable of loading just about any shared library.

  • Eclipse RCP & OSGi on the Client & Server

    RPC software provides ERP and project planning solutions to the contract furniture industry. This case study takes a look at how they are using Eclipse RCP and other Eclipse technology to respond to customer needs at a rapid pace while continuing to providing a first class user experience.

  • WPF as a Rich Client Technology

    WPF makes it easy to create visually impressive app, but WPF also has other talents which make it a compelling choice as a rich client over back-end services written in any technology such as Java, Ruby, or .NET. This article compares WPF to alternatives such as Ajax/DHTML, Swing, and Flash; it will also look at some scenarios where a WPF client makes sense, using Java as the back-end example.

  • Casestudy: IP Telephony Integration

    This case study takes at Litescape's IP telephone integration solution, from requirements through an architectural overview of their Java and .NET implementation, and then zooming in some interesting technical aspects of their project including phone integration with WebEx/LiveMeeting, integration between Java/.NET interop, HTTP vs. IPC communication between systems installed on the same machine.

  • Java, .NET, But Why Together?

    The Java vs. NET war is over. In this article, Ted Neward looks at how we can leverage the strengths of each together, such as using Microsoft Office to act as a "rich client" to a Java middle-tier service, or building a Windows Presentation Foundation GUI on top of Java POJOs, or even how to execute Java Enterprise/J2EE functionality from within a Windows Workflow host.

  • Evolutionary integration with ESBs

    ESB Programming experts provide simple working examples and clearly communicated ideas and patterns using the open source Mule ESB tool set. These examples provide both working code as well as suggest a methodology of evolutionary integration which can be used to dramatically simplify and accelerate SOA integration.

  • Simple JAVA and .NET SOA interoperability

    .NET and Java interop can be made really simple using a REST documentcentric approach. This article compares a REST and SOAP approach to interop as well as the advantages of using HTTP POST vs. GET for REST invocations.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.