I personally favor using a layered approach using an ESB (Enterprise Service Bus) like Mule (http://mule.codehaus.org).
For IDE, I could use Eclipse. Next layer down, I've developed a wrapper over Mule so I could configure the end points using a configuration file. Next layer down is Mule. Next layer is a DI Container such as Spring or Seasar (http://www.seasar.org/en/). I like the layered approach because I won't be tied up to a single software and the higher layer abstracts the processes in the lower layer. I'm also able to customize the lower layers when I need to. In my current environment, I could do all of the following by setting up the configuration file: (1) I could turn a CSV into a web service, (2)change so that web service gets data from an application, (3) output the content of the service into AJax, MS Office (MS Excel, MS Word), or a database, (4) switch the output, (e.g. from AJax to MS Excel), (4) or switch the output to an application API. If I need to do something that's not yet supported, I could just add it by writing a new ESB adapter or write some logic in the DI Container. Cheers, H.Ozawa Robin wrote: > But then the question is: What's the best platform for developping > services in Java? > Is Spring a viable alternative? > > Robin > --- In [email protected] > <mailto:service-orientated-architecture%40yahoogroups.com>, "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 <*> 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/
