Well, why don't you explain to me what .NET is then, because I'd like to know.
My feeling based on the few articles I have read, is that this is a technology initiative based in some part on the useless msft biztalk server, which has no hooks into any existing enterprise platforms (where the demand for this tech is coming from, primarily).
I am very interested in the new XML/workflow technologies evolving now which promise to be sort of transaction routers into misc. enterprises. There are a number of companies working on this and usually ejbs are the technology of choice... I'll let the sun people here comment on the java component. But if msft is doing this, and NOT using ejb's then it is going against the trend.
Of course it could be .net has nothing to do with connectivity and adapters. Its hard to know based on the limited info I have seen, but if this IS what they are doing then they are already pretty far behind, fwiw.
edit - oh look here is an article on .net
In many ways, these vertical initiatives were meant to be industry-specific electronic data interchange (EDI) blueprints. In manufacturing, for example, such a blueprint would provide standards and plumbing guidelines to link shop-floor equipment with back-room servers.
zdii.com
Let me list ALL THE COMPANIES I think can do this much, much better than msft right now and most are shipping products: orcl, itwo, manu, arba, cmrc, webm, tibx, vitr, beas (integration product), mctr... I could go on but why bother... |
