Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 28167 invoked from network); 17 Nov 2003 12:03:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 17 Nov 2003 12:03:53 -0000 Received: (qmail 78910 invoked by uid 500); 17 Nov 2003 12:03:49 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 78869 invoked by uid 500); 17 Nov 2003 12:03:48 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 78845 invoked from network); 17 Nov 2003 12:03:47 -0000 Received: from unknown (HELO kerberos) (62.116.51.59) by daedalus.apache.org with SMTP; 17 Nov 2003 12:03:47 -0000 Received: From mail.at.efp.cc ([62.116.51.60]) by kerberos (WebShield SMTP v4.5 MR1a); id 106907062599; Mon, 17 Nov 2003 13:03:45 +0100 Received: from WRPO (wrpo.at.intra.efp.cc [194.107.80.156] (may be forged)) by mail.at.efp.cc (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hAHC3hX29096 for ; Mon, 17 Nov 2003 13:03:44 +0100 From: "Reinhard Poetz" To: Subject: RE: Web Service Transformers in Cocoon (Re: [article] XML.com: EAI using Apache Cocoon 2.1) Date: Mon, 17 Nov 2003 13:02:58 +0100 Message-ID: <000401c3ad02$bed5fa60$1e01a8c0@WRPO> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3FB89B49.6010205@nada.kth.se> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Okay, I think it is time to find the 'official' way how to=20 deal with WebServices in Cocoon. There are many implementations=20 around and this is rather confusing (at least for me).=20 I summarized all available implementations that I know and=20 added them to a new Wiki page:=20 http://wiki.cocoondev.org/Wiki.jsp?page=3DWebServices Please add your usecases and what you need (use) in Cocoon to implement it. Take this as starting point in order to get a 'official' web service integration in Cocoon and to give our users clear advice what to take. -- Reinhard > -----Original Message----- > From: Daniel Fagerstrom [mailto:danielf@nada.kth.se]=20 > Sent: Monday, November 17, 2003 10:56 AM > To: dev@cocoon.apache.org > Cc: steve@candlelightsoftware.com; tony@cultech.com.au > Subject: Web Service Transformers in Cocoon (Re: [article]=20 > XML.com: EAI using Apache Cocoon 2.1) >=20 >=20 > It seem popular to write web service transformers these days. I have=20 > written one that can be found in=20 > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D24402, after that = I=20 > implemented it I have found two other implementations: the=20 > one described=20 > in the article: http://xml.com/pub/a/2003/11/12/cocoon-eai.html, that=20 > can be found in=20 > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D24391,=20 > and still another one described in=20 > http://webservices.xml.com/pub/a/ws/2003/03/18/cocoon.html. The later=20 > one is AFAIK not submitted to Cocoon and only works for Cocoon 2.0.3,=20 > although it probably should be easy to port it to 2.1. >=20 > There is also an XSP implementation of web service calls within the=20 > current Cocoon distribution. There are also a number of=20 > components that=20 > provide functionality for request parameter based web services:=20 > HttpProxyGenerator, WebServiceProxyGenerator and possibly=20 > GenericProxyGenerator in the Proxy block as well as the=20 > CIncludeTransformer. >=20 > There is a lot of overlapping functionality in the different=20 > web service=20 > client components in Cocoon. >=20 > IMO it would be a good idea to merge at least the different=20 > web service=20 > transformer proposals. I would prefer to put as much functionality as=20 > possible in the HTTPClientSource as in my proposal, as it seem to be=20 > better to focus the functionality in one reusable place than=20 > having it=20 > reproduced in various places. The web service enabled=20 > HTTPClientSource=20 > can then be used from generators and transformers as well as from=20 > flowscripts. I have not studied Tonys and Steves proposals in any=20 > detail, but at least in Tonys variant there is some login=20 > handling that=20 > my implementation lacks, it would be nice to transfer that=20 > functionality=20 > to the HTTPClientSource. >=20 > For the transformer part I have no strong opinions, I put the=20 > functionality in the SourceWritingTransformer, as it already=20 > contained=20 > various operation on modifyable sources. But it probably=20 > makes sense to=20 > have it in a specialized transformer instead. >=20 > What do you think? >=20 > /Daniel >=20 > Velle Andr=E8 wrote: > > The article mentions a web service transformer that seems=20 > superior to=20 > > the one in 2.1.3, and states that it has been submitted to the=20 > > cocoon-dev list. I haven't been able to find anything like=20 > this, and=20 > > it seems interesting. Anyone know anything about it? > >=20 > > Regards, > > Andr=E9 > >=20 > >=20 > >>-----Original Message----- > >>From: Andreas Hochsteger [mailto:e9625392@student.tuwien.ac.at] > >>Sent: 15. november 2003 09:11 > >>To: dev@cocoon.apache.org > >>Subject: [article] XML.com: EAI using Apache Cocoon 2.1 > >> > >> > >>I just got a newsletter from XML.com promoting this article: > >>http://xml.com/pub/a/2003/11/12/cocoon-eai.html > >> > >>It's about "Enterprise Application Integration using Apache > >>Cocoon 2.1". > >=20 > >=20 >=20