Now, this is a really interesting question..... Robin wrote: > But then the question is: What's the best platform for developping > services in Java?
For me the best platform is what suits my design/customer requirements best. It's a fluid thing that changes all the time. What requirements do you have of your platform? Is it to use "standard" API's so you can switch it for something else (when it is no longer the best)? Selecting one platform makes some things easier and others harder which is, for me, the reason why there is no best platform unless everything you do is always the same. Ultimately, this is why we have "legacy" - the best choice at one time is no longer the best later. Trying to select the best leads to dry theoretical, unresolved debate. Discussion of tradeoffs/suitability for purpose in some specific scenarios is more informative. Someone actually did something like that for web frameworks recently...... > Is Spring a viable alternative? > Is Spring a platform? Is Weblogic a platform? I think they are containers offering a set of API's and a deployment model (with Spring arguably being significantly more configurable). But are containers the only way to do things? Are they always what you want? Best wishes, Dan. > Robin > --- In [email protected], "Anne Thomas > Manes" <[EMAIL PROTECTED]> wrote: >> Please note that the report cited in this article is talking about > Java EE, >> not about Java in general. Burton Group predicts that Java will remain >> strong and healthy for a long time. >> > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > 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/
