Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Message-ID: <00a101c36105$51a2cb60$7501a8c0@TPX21>
From: "Anne Thomas Manes" <anne@manes.net>
To: <axis-user@ws.apache.org>
References: <3F2E62790250AF4485864348F7E9F6B0D76E68@stingray.tnow.net>
 <3F391ADA.5040507@yale.edu>
Subject: Re: Document vs. RPC
Date: Tue, 12 Aug 2003 14:54:56 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

See BPWS4J: http://alphaworks.ibm.com/tech/bpws4j

----- Original Message ----- 
From: "remko de knikker" <remko.deknikker@yale.edu>
To: <axis-user@ws.apache.org>
Sent: Tuesday, August 12, 2003 12:50 PM
Subject: Document vs. RPC


> Often, one makes a decision to develop RPC or Doc oriented services. 
> That's what I did. Since interoperability and uniform data format was a 
> key factor, I chose DOC.
> 
> But now I am trying to develop choreographies, I discover that there not 
> a lot (none?) (open source/free) choreography engines that support DOC 
> oriented choreographies and use choreography standards 
> (BPEL4WS/BPML/WSCI). (Although I think that the whole purpose of the web 
> services concept is defeated by RPC style, but anyway...)
> 
> Does anyone know of such tools??
> 
> In any case, it might be worth while considering, for people who are 
> weighing one against the other..
> 
> remko
> 
> 
> 
>