Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail NNTP-Posting-Date: Sun, 06 Jan 2013 11:10:33 -0600 Date: Sun, 06 Jan 2013 17:10:31 +0000 From: lipska the kat User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: Java servlet on browsers: dying or kicking ? References: <50d892e5$0$282$14726298@news.sunsite.dk> <50dbf6d1$0$80176$742ec2ed@news.sonic.net> <50dcfecc$0$292$14726298@news.sunsite.dk> <50dd5b51$0$80184$742ec2ed@news.sonic.net> <50de2260$0$293$14726298@news.sunsite.dk> <50df9c4b$0$284$14726298@news.sunsite.dk> <50e99980$0$294$14726298@news.sunsite.dk> In-Reply-To: <50e99980$0$294$14726298@news.sunsite.dk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Message-ID: Lines: 33 X-Usenet-Provider: http://www.giganews.com X-AuthenticatedUsername: NoAuthUser X-Trace: sv3-4Kkx2R42LVmNyME0RkFDJQlcIDPjpxIgd7ZUYOfyeXBwZl1bWdjhA0hpt9n6NxiBqaFww5oWHV7XoEW!FfB2Kq4MvlqXY2Epj00nO+4kn5rrWXGxOFMRKTXiUrrd3xvV8HWxx0JsBJytLq82WR+tepBu+/g= X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2975 Xref: csiph.com comp.lang.java.programmer:21040 On 06/01/13 15:34, Arne Vajhøj wrote: > On 1/6/2013 5:27 AM, lipska the kat wrote: >> On 05/01/13 00:22, Richard Maher wrote: >>> "Arved Sandstrom" wrote in message >>> news:nUoEs.1$Z03.0@newsfe23.iad... [snip] > In a SOA world each service will be responsible for its > own business logic. One definition of an SOA is that Services are unassociated, loosely coupled units of functionality that have no calls to each other embedded in them This being the case then it will be even more important to manage the possible combinations of what will effectively be calls on your business logic. You can't simply allow your various departments to publish a random collection of services and let anyone combine them in any way they like. As I see it a SOA while providing maximum flexibility clientside will be even more dependent on some central repository of rules that will need to be applied at some stage in the interaction lifecycle. Allowing different interpretations of critical business process will surely be an invitation to chaos and disaster. Or maybe I'm being over cautious. lipska -- Lipska the Kat©: Troll hunter, sandbox destroyer and farscape dreamer of Aeryn Sun