I am not a fan of kicking Java, not due to my 10 years of investment in Java but because I am against kicking at all, including C#. Every successful OO language will get its niche in implementation of SOA Services. It is obvious to me that Java / EE 5 is not a panacea for SOA because of many reasons, one of which is that SOA is not OO environment.
SOA itself, probably, needs some kind of descriptive language to define not only interfaces like Web Services / WSDL but also Service Provider behavior and related SLA. I do not credit SOAP for this role. Latter can cause a "CORBA syndrome" of the 21st century, if you wish, - the descriptive language has to be recognized and supported by all SW development camps, which is not a trivial goal to achieve. If Java gets the first place in implementation of such descriptive language (probably, via mapping, like it is in CORBA), it might occupy a space beyond Service implementation. If it get the second or the third place, I do not think this will constitute a collapse for Java. - Michael Poulin --- In [email protected], "Gervas Douglas" <[EMAIL PROTECTED]> wrote: > > I have just received this in an e-mail newsletter from Michael Meehan > of SerachWebServices.com: > > Gervas > > ===================================================================== > > Is it time to kick the Java? > [Michael Meehan] > > We've known for a long time that service-oriented architecture posed a > stiff challenge for Java. Java was built in a pre-SOA world and while > the Java Community Process has churned out plenty of standards > designed to make Java SOA and Web services friendly, there's always > been the nagging notion that it's being done as patchwork rather than > as an organic fit. > > A year ago we at SearchWebServices.com were writing about whether Java > could find its place within the SOA universe. > > Well, the word coming out of some analyst houses these days is no, the > Java EE platform is becoming too bloated, "the CORBA of the 21st > Century" as one analyst calls it. The analysts don't expect the Java > programming language to disappear, but they do think that Java EE 5 is > the beginning of the end of the Java platform. > > The reason why? Because SOA doesn't rely on a common programming > model. In fact, it eschews it. Just like Java once carried the banner > for operating system independence, SOA carries it for platform > independence. > > How well you interface with others is what matters in the SOA world > order. In fact, we've got news this week about the latest on the > vendors who joined to form the SOALink group back in May. > > And august Java vendors like BEA continue to branch out far beyond the > Java EE platform. We'll have news about that as the week progresses as > well. > > Yet the Java EE platform may be racing toward a moment of truth with > Web services and SOA implications abound. It might be the biggest > story in the software industry this year because Java EE, and J2EE > before it, really has become part of the industry's foundation. > > As this moves forward you're likely going to have to ask yourself, how > much Java is good for me? > ------------------------ Yahoo! Groups Sponsor --------------------~--> Something is new at Yahoo! Groups. Check out the enhanced email design. http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
