The Java/.NET integration story keeps getting better and better every day–two tidbits in particular stand out thus far.
From Eduardo Pelegri-Lopart’s weblog,
I knew MTOM support was already implemented in recent JAXB 2.0 builds but I had missed that the full integration with JAX-WS 2.0 was also working. I just talked with Rajiv and he tells me that last night Simon and Rags got it working between the Indigo Beta RC and the JAX-WS 2.0 EA2 released last week. I hope I won’t jinx by talking about it, but Simon and Rags will demo it during their session this afternoon. … The session is TS-9866, "Advanced Web Services Interoperability", 2:45-3:45 in the Yerba Buena Theater.
And Simon echoes a similar story (though he did it with WSE 3, not Indigo) on his weblog:
In my JavaOne session yesterday I showed (what I believe to be) the first MTOM Interop demo between .NET and Java using publicly available toolkits. For those that don’t know MTOM (Message Transmission Optimization Mechanism) is the new specification for optimizing the transmission and/or wire format of SOAP messages. Primarily this means that we have a new standard that allows the sending of attachments over Web Services – one that the industry agrees on, and one that is composable with the other WS-* specifications.
I still have to touch base with Simon to find out if there’s also an Indigo demo with JAX-WS* that he and Rajiv did, as I’ll want to steal… um, I mean leverage… it for my Indigo/Java talk for TechEd Europe in a week or two. 🙂
Better yet, in other news,
You know who you are. We have finally publicly announced it; we will have a new JDBC driver for Sql Server 2005.