Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Crazy Fools Chasing Crazy CyberNews -- Ignore unavailable to you. Want to Upgrade?

To: ms.smartest.person who wrote (703)	11/8/2001 9:49:23 PM
From: ms.smartest.person	Read Replies (1) \| Respond to of 5140

Graphic: How Sun Software Works (Subscription may be required. If you cannot access the graphic, try the next 2 links) businessweek.com@@pnUbumYQ8*XHrQUA/premium/content/01_47/b3758003.htm Link to the Graphic, which is totally contained in a gif: businessweek.com If all else fails, try this profile page - I embedded the image and just maybe this will be failsafe: Member 8849888 Used with permission of businessweek.com

To: ms.smartest.person who wrote (703)	11/9/2001 1:16:18 PM
From: rudedog	Respond to of 5140

One problem with this analysis on the web services sector comes to mind - although the article is pretty good overall. Web services is an architecture, not an infrastructure. Microsoft has tried to blur the distinction by painting everything with the .NET brush, and then equating .NET with web services. That's to be expected - they have achieved the magic "architectural leadership" position, but have not tied that to their products (or revenue!), so they want to get some present benefit from the clean sweep they got on the web services initiative. But java, and J2EE, are execution components, and tightly coupled ones at that. J2EE has gotten traction for exactly that reason - it is currently the most flexible and platform independent mechanism for creating process building blocks. But that strength as an execution engine is a huge weakness as a web services integration platform. J2EE is great for creating the business functionality that web services would expose, but it is completely inappropriate for integrating those functions into a web services based business process. Sun needs to create a new, independent framework for web services integration. As it happens, I spoke to some people from Sun earlier this week on this topic - they are aware of what they need to do, and that claiming that java or J2EE are appropriate web services platforms is just wrong - it's not what java does. They also mentioned that they would not say that in public, since the general public and the industry are not particularly aware of the issue and it would not serve Sun to highlight it. Even though the web services integration story in WebSphere is mostly Marketecture (and an opportunity for IBM to sell services), IBM has taken the bull by the horns, at least in architectural discussions with customers, and their architects correctly position J2EE. I see this as an important issue for Sun to address quickly, before people start to look to carefully at SunONE. Without a web services integration story, SunONE is just old wine in new bottles. But it is beginning to get visibility from some players who are not exactly in the Microsoft camp and are supporters of J2EE for process implementation, including influential Systems Integrators like KPMG and PWC.