InfoQ Homepage Interop Content on InfoQ
-
Lisp on the .NET Runtime
Continuing our coverage of Lisp, we present some of the efforts underway to port the venerable language to the .NET runtime. Variants we look at include IronLisp, LispSharp, and Common Larceny.
-
Article: 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.
-
ColdFusion as an Integration Platform
Facing stiff competition in the web server market, Adobe has added .NET support to ColdFusion 8. This sets it up to be perhaps the most connected platform out of the box.
-
.NET to Ruby connector available
The Ruby Connector allows communication between .NET and Ruby. This brings the power of .NET to Ruby, and allows to use Ruby to power Visual Studio generated GUIs.
-
Call .NET Libraries from Lisp Using RDNZL
A long standing complaint about Lisp is the lack of high quality libraries. While the truth of this is disputed, there is certainly value in having access to the wide array of libraries found in the .Net platform.
-
Perl/.NET Interoperability Using Web Services
Web services were supposed to enable cross-application integration regardless of the underlying platform or language. While the promise is still there, today we still need tricks to make it work.
-
WSO2 Releases Web Service Framework/C v1.0 and announces Mashup Server
WSO2 announced the release of WSF/C which is a C library used for producing and consuming web services in C. Similar releases exist for Java and PHP. They also announced a new product, the Mashup Server which will be a platform for creating, deploying, and consuming Web services Mashups.
-
XACML finally ready for prime time?
XACML, the eXtensible Access Control Markup Language, an Oasis standard approved more than 2 years ago, has been demonstrated to work cross vendor platforms on Burton's Catalyst Conference last week.
-
Gardens Point Ruby.NET internals interview
An option for running Ruby on the CLR today is the Gardens Point Ruby.NET compiler. A lot of work has gone into compatibility with Ruby and, recently, interoperability with other languages on the CLR. We talked to John Gough, of the Ruby.NET team, about technical details, compatibility and future plans for community participation in the project.
-
Ted Neward on Interop & Office Integration interview & whitepaper
Ted Neward has published a detailed whitepaper on Java and .NET integration with samples showing Office clients over Spring-based Java systems, SQL Server & JSP. At the same time InfoQ has published a video interview with Ted that talks further about Office integration possibilities as well as various interop approaches (in-proc, messaging, web services) work and when to use them.
-
In Case You Missed It: A .NET OpenID Library
For those of you looking at using OpenID, there is a .NET compatible library available. The Library was written in Boo, a .NET language inspired by Python. It also leverages a library from the Mono project.
-
Red Hat joins Interoperability Vendor Alliance
Red Hat announces it has joined the Interoperability Vendor Alliance, with IBM, Microsoft, BEA, Oracle and others.
-
InfoQ Article: In-Process JVM & CLR Interop
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; in this new article, Ted Neward shows how and why.
-
Fire and Motion: What OpenXML Means to IBM and Lotus Notes
In the on going debate between ODF and OpenXML, two things are becoming clear. The first is that both ODF and OpenXML are essentially proprietary formats dressed up to be open standards. The second is neither IBM nor Microsoft is going to back down.
-
OASIS WS-Transaction (almost) a standard
The OASIS WS-TX technical committee held a face-to-face meeting last week at IBM Hursely. This is likely the last such meeting prior to final standardisation of WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity.