That's interesting now, I guess my pad answer will be "imitation is the sincerest form of flattery." I think what BEA has done is recognized two facts. Actually three things. First development should be easy. When an enterprise developer sits down at his or her tool, developing components, developing web services should be an easy operation. You shouldn't have to go through a whole host of different steps in order to an essence to solve a very simple problem. So as Einstien said "simple things should be simple and complex things should be possible." So I think BEA has recognized that and we're happy that they've done that. We've recognized that for many many many years. The next thing I think is interesting is that BEA has understood that attributal programming is very important. The ability to annotate types and the ability to annotate methods with meta data in order to change the compile time or run time behaviour is an important program in paradigm. It's one that we've really adopted instead of the .NET framework and that we've been utilizing for many many years. It started back in the COM days doing attributal programming. And the third piece is the importance of a web services. So web services should be the core of how we do interop and how we do RPC moving forward. So from that perspective BEA's technology is very interesting and in fact it buttresses our whole development model. It should be easy, it should be attributal and declaritive and it should be web services oriented. To answer your question directly to they are competition, certainly they are. Now we'd welcome them to come over and take a look at the CLI and take a look at Csharp and perhaps they could move their product over to support the .NET framework and we'd certainly welcome having that conversation but for the time being they certainly are.