It is raising new perspectives for services containers which is a consequence of the implementation language neutrality of Web service.
First of all, I do not think that J2EE end-users will be interested to drop their infrastructure so fast and build a second PHP or Ruby infrastructure aside of it. Some Java EE vendors are already supporting additional containers for PHP, I think this trend will continue. Advantage here is that PHP, Java and maybe other language-based applications are integrated under a single operational platform. I will expect a shared management console, security systems and monitoring tools for all these languages allowing a company to select the best language for the job. Next, the use of Java is maybe overkill in some simplistic applications but I am convinced Java makes really sense for implementing complex services. The Enterprise Architecture Pattern selected to build the service will influence the framework and eventually the language used. It does not make sense to build an financial order brokering service in PHP the same way it does not make sense to use a full Java EE stack with a complete OO Domain Model for a simple data retrieval service. Robin --- 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/
