JBoss and Microsoft have announced plans to enhance interoperability between their product lines, committing to web services and security interoperability, manageablility of JBoss environments using Microsoft's Operations Manager, and optimized use of SQL Server for users of Hibernate 3 and EJB 3.

While commitment to interoperability of web services may be obvious (and highly beneficial to the entire development community), JBoss feels that since nearly half of their userbase deploys on Windows, security interoperability and manageability provides a distinct advantage to their platform.

Both companies will continue to compete vigorously, even while providing what they term an "optimized experience" for Jboss customers on the Windows Server platform.

They have not stated when the features will be implemented.

Attempt # 3

What is the source of this article? URL please.

Attempt # 3What is the source of this article? URL please.

Here it is:

  PR: http://www.jboss.com/pdf/press/microsoft.pdf

  FAQ: http://www.jboss.com/partners/microsoft


Cheers,


Sacha


JBoss, Inc.
GM EMEA

some wishes
1) Publish a JMS provider for the MS SQL Service Broker
2) Allow for the use of the MS transaction coordinator across JDBC, JMS, and SOAP
3) ws-management

this is a step in the right direciton, keep it up

Some people say you can judge the character of a person by the company they choose.

Does the same apply for companies?

Some people say you can judge the character of a person by the company they choose.Does the same apply for companies?

Yes, you should now address us as JBo$$ if you don't already. ;-)

Some people say you can judge the character of a person by the company they choose.

Does the same apply for companies?

Don't judge Microsoft so harshly.

(It's a joke. Just a joke. ;-)

Peace,

Cameron Purdy
Tangosol Coherence: This space available.

0x02

Nonsense WS-I already exists !!!

Nonsense WS-I already exists !!!

Sun should have been working along these lines a long time ago. Many environments have .NET and Java. Sure ws-1 allows you to communicate between the two, but when you want two systems to be tightly integrated you should have more in your toolkit then just WebServices. Borland builds a product that allow tight high performance integration between .NET and Java, but it is the only product of its kind that I know of.

Like I said Sun has had open agreements with Microsoft for a while now, and should have been addressing some of these integration issues. But lets be honest Sun seems to have no interest in tight integration with anything outside of the JVM.

I hate to bring up the whole JNI issue, but I think it is a related example of how Sun can not see past their own product, and is in denial about some customer needs. I love it when vendors tell me how I should (and should not) use their product ;(

I guess it is good that we are going to get better SQL Server support from some of the Java community. I personally don't like SQL Server, but seems to have progressed past the toy it once was.

This artical could be a joke, but I hope it isn't.

Like I said Sun has had open agreements with Microsoft for a while now, and should have been addressing some of these integration issues. But lets be honest Sun seems to have no interest in tight integration with anything outside of the JVM.

Come on now, it's a two way street. I'm quite sure Microsoft also has no interest in it, especially if said technology is enroaching in their target market.

Microsoft knows full well that the big players in the J2EE space offers the full stack (eq. IBM, DB2, Tivoli Products) and that it's hard for them to crack said market.

MS products are like viruses, once they are able to breach the tech stack, said products start replicating (usually w/ underlying dependencies eq. SQL Server -> MS Active Directory -> MS Active Directory -> Windows OS, on and on).

I always felt that the MSSQSL JDBC drivers were deliberately bad, because if they were good you could do a good EJB system without having to pay Oracle so much money.

If this agreement leads to improved MSSQL stuff, this is a good thing. Some people may also like better JNDI bridging to ActiveDirectory though I fail to see the point there myself, as ActiveDir does suck.


JBoss's rationale for this is obvious: better products, better interop, better legitimacy. But I have to speculate why MS are doing this?

(a) because JBoss have the mass market, and they want that market to work on windows

(b) because helping JBoss hurts IBM and oracle

One thing I do know, it aint because MS like open source :)

I always felt that the MSSQSL JDBC drivers were deliberately bad, because if they were good you could do a good EJB system without having to pay Oracle so much money.

Well if that's your criteria for purchasing a database product or the other...

I always felt that the MSSQSL JDBC drivers were deliberately bad, because if they were good you could do a good EJB system without having to pay Oracle so much money.

Why would Microsoft want you to pay Oracle money...?

(Take 2)

MS products are like viruses, once they are able to breach the tech stack, said products start replicating (usually w/ underlying dependencies eq. SQL Server -> MS Active Directory -> MS Active Directory -> Windows OS, on and on).

True I have seen that, but I have also seen the inverse. One of the companies I'm contracting for right now wanted to use Java because they were having so many issues with .NET (as a whole). There was always permission problems, AD issues, security patches breaking things, administrators changes profile and GPOs that were breaking the apps, etc... They wanted their newest web app written in Java so that they specifically didn't have to deal with it being wrapped into the mess, that their existing application server env was starting to become. Over the last 6 months the Java apps have been proving themselves in the uptime catagory, and the company has been moving more and more to Java.

This artical could be a joke, but I hope it isn't.

Nope. Not a joke. JBoss sent it out this morning.

I love it when vendors tell me how I should (and should not) use their product.

I find it a pleasant change from the Microsoft attitude, which is frequently to give the developer full range to produce unsafe code of the lowest quality. Having had to salvage the results of such development, I would rather have restrictions.

However, better Java/.NET integration would definitely be a benefit.

(try 5)

I find it a pleasant change from the Microsoft attitude, which is frequently to give the developer full range to produce unsafe code of the lowest quality.

I guess it is a matter of perference then. I perfer to use things as they were indended. I perfer to use best practices, when it makes sense. I also don't like it when developers feel that it ok to produce garbage, just because it is easier to write junk then do the job right.

That being said, when it comes to having options or not having options I perfer to have options. And I think that Sun can do a better job of giving me better options, when it comes to .NET integration and JNI.

But lets be honest Sun seems to have no interest in tight integration with anything outside of the JVM.

Why should they? Sun seems to be the only one caring about robustness and backwards compatibility. They act strange sometimes but do a right job IMO. What would there be now without them?

Why should they? Sun seems to be the only one caring about robustness and backwards compatibility. They act strange sometimes but do a right job IMO. What would there be now without them?

I'm just bitter because I think JNI sucks, and I can't seem to stop complaining about it. Just ignore me....

Like I said Sun has had open agreements with Microsoft for a while now, and should have been addressing some of these integration issues. But lets be honest Sun seems to have no interest in tight integration with anything outside of the JVM.

Sun and Microsoft have been working together for some time now under the announced agreement. Though you may not have seen any significant progress - that doesn't mean progress isn't being made; nor does it mean that Sun isn't commited to delivering some significant advancements in interop. between Java & .NET.

Here are a few articles here that outline the Sun and Microsoft agreement:

http://developers.sun.com/foryourbusiness/sun-msft/index.html

Also could someone actually state what JBoss are doing that *any* other vendor doesn't already do with Microsoft ?

Rich Sharples
Sun Microsystems

Just wondering. Seen the usual suspects hanging out on the usual lists ;) IKVM would indeed provide a good chunk of something that no other vendor is doing.

cheers,
dalibor topic

WS-I never came off the fence and declared which subset of XML Schema datatypes everyone should implement.

There is no guarantee that two WS-I compliant systems can interoperate, other than unit testing and regression testing.

It´s a joke ???

Please see: http://www.jboss.com/partners/microsoft

The announcement coming from both JBoss and Microsoft will be hitting the wires shortly (if not already).

Ouch. .Net gets dissed! J2EE gets forked! IBM still wins! MS tries to manage the bleeding from a low end competitor. IBM still eating away from high end. JBoss/Windows vs. JBoss/Linux perf race to follow.

If company's adopt JBoss on Windows over JBoss on Linux doesn't Java own mindshare. OS gets commoditized in manager's eyes. They see Linux as a lower cost solution and switch to save money.