Path: csiph.com!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Web services/SOA - The right way
Date: Tue, 23 Aug 2016 19:17:15 -0400
Organization: Aioe.org NNTP Server
Lines: 29
Message-ID: <npilhr$1bbs$1@gioia.aioe.org>
References: <aa1331d1-623a-4d8a-9812-ceccf9f72c19@googlegroups.com> <b92073ee-24b3-4667-a938-bf5395977e7b@googlegroups.com> <npf7s1$1k5$1@gioia.aioe.org> <npiifg$1791$1@gioia.aioe.org>
NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:35429

On 8/23/2016 6:24 PM, Richard Maher wrote:
> On 23-Aug-16 12:05 AM, Arne Vajhøj wrote:
>>   JAX-WS or JAX-RS - and if you need to support mobile then go for
>>   JAX-RS
>
> Why is mobile relevant? Why does the server-tool choice dictate/restrict
> the client?
>
> JSON in JSON out; what is JAVA trying to do?

It is the other way around. The client is "strongly suggesting"
to the server.

JAX-WS is SOAP XML.

JAX-RS is RESTFul JSON (or simple XML).

If you are integrating with an ESB in the 100K$ per CPU license
class then they love contract first WSDL and SOAP with lots of
extra WS-* standards.

If you are integrating with mobile then SOAP will waste
bandwidth and the developers will revolt due to poor
tool support. RESTFul JSON (or simple XML) is the only
good choice.

Arne