Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 38315 invoked by uid 500); 1 Apr 2001 22:57:17 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 38304 invoked from network); 1 Apr 2001 22:57:16 -0000 Date: Mon, 2 Apr 2001 08:59:30 +1000 From: Jeff Turner To: cocoon-users@xml.apache.org Subject: Re: New SOAP live samples online Message-ID: <20010402085930.B14154@socialchange.net.au> Mail-Followup-To: cocoon-users@xml.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from ulim@denic.de on Sun, Apr 01, 2001 at 01:43:19PM +0200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Very cool :) All sorts of neat possibilities.. SVG -> PNG services, etc. I'm sure the SOAP and FOP people would like to hear about this. --Jeff On Sun, Apr 01, 2001 at 01:43:19PM +0200, Uli Mayring wrote: > Hello, > > under http://ulim.cocoonhost.com you can find > > a) the docs for the new version of the SOAP taglib > b) the new version as a download .tar.gz archive (complete with DocHandler > and the PDF archive) > c) the new live samples > > There is one new feature in the live samples, you can now save > generated letters to the PDF archive (no spectacular code, I just didn't > have time to complete this for the last version). > > And there's one new feature in the SOAP taglib (besides upgrading it to > work with Cocoon 1.8.2), which is illustrated by the new sample > "addressbook". It allows you to send arbitrarily complex XML fragments > (i.e. XML documents without XML declaration and root tag) to a SOAP > service. And you can retrieve these XML fragments in any XSP page using > the SOAP taglib. This is a very general technique, but I wrote with a > concrete application in mind: > > This technique enables you to call Cocoon programmatically and pass it > arbitrary XML data to work with. There is no need anymore for the XML data > being in the filesystem or a database at the remote end. All you need at > the remote end is a static stub file and the XML fragments you pass along > will be inserted into it. No great achievement in a technical sense, but > it makes workflows possible a la "send us your XML data via SOAP and we'll > send you a PDF". The frontend (i.e. the one, who sends the XML data) can > either be an XSP page (as in the addressbook sample) or an arbitrary > program (as in the DocHandler). > > The addressbook sample actually uses both frontends: first an XSP page to > pass the address data as XML fragments to a SOAP service (the DocHandler). > Then the DocHandler asks Cocoon to make a PDF from this XML data by > passing the XML fragments to a (remote or local) XSP page and returns > the generated PDF to the original requester. > > This technique is not limited to PDF, but that's all I implemented > (besides XML, which is of course "naturally" supported). > > Ulrich > > -- > Ulrich Mayring > DENIC eG, Softwareentwicklung --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: