Return-Path: X-Original-To: apmail-cxf-users-archive@www.apache.org Delivered-To: apmail-cxf-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8937F2273 for ; Thu, 21 Apr 2011 11:01:57 +0000 (UTC) Received: (qmail 7810 invoked by uid 500); 21 Apr 2011 11:01:56 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 7761 invoked by uid 500); 21 Apr 2011 11:01:56 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 7753 invoked by uid 99); 21 Apr 2011 11:01:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2011 11:01:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bw0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2011 11:01:50 +0000 Received: by bwz17 with SMTP id 17so1669569bwz.0 for ; Thu, 21 Apr 2011 04:01:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=IwM28tjXf6JAP7qMe9oVy6BBmsJArY48wCoJ63vm8cc=; b=Ao95uhGMN9H4gREjkSUTf9VboSCnJZLJtS5UEG1hE7VGbrT903i6shiuTW0yCAaV0y EAy50mRwfDooL9FL2DNT84PC2Gbr9bRvXm6Qc6O/WnusIuVYJMIdPqNdnpY5erfZX8uZ mMvcURP2B7BrtotPf4I4JzDqlLrr/csAjlWNk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=AhDkH6nG4RKPx/A8YQqqqsSUN3Axa/iAw1kEQOr9UKP5thyfSIE4mAYC7RLWCt1ge7 3d2POjWTsdIir5YRL0ubTMWfcPQEd/CNoYHlqxBhQ/OW9GG/tulCzHFHwveWuZIw/BO7 iCY75w+nYqWU9qMgmGK8UI26vM+PjFiRclIwg= MIME-Version: 1.0 Received: by 10.204.0.82 with SMTP id 18mr795962bka.100.1303383689347; Thu, 21 Apr 2011 04:01:29 -0700 (PDT) Received: by 10.204.60.73 with HTTP; Thu, 21 Apr 2011 04:01:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Apr 2011 12:01:29 +0100 Message-ID: Subject: Re: Generate human-readable documentation from WADL? From: Sergey Beryozkin To: users@cxf.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi On Thu, Apr 21, 2011 at 12:35 AM, KARR, DAVID (ATTSI) wrot= e: >> -----Original Message----- >> From: Sergey Beryozkin [mailto:sberyozkin@gmail.com] >> Sent: Thursday, April 14, 2011 2:26 PM >> To: users@cxf.apache.org >> Subject: Re: Generate human-readable documentation from WADL? >> >> Yes, I can see this link too: >> https://github.com/mnot/wadl_stylesheets >> >> However we will try to ship our own stylesheet, it's on the map, WADL >> work >> is one the map from now on > > If you do this, consider rendering schema information in a graphical form= , instead of plain text. =A0That means you'd have to have more than just a = stylesheet, but the resulting documentation could be higher quality than wh= at you'd get with plain text. =A0I'm sure that code to do this could be qui= te complex, but I'm going to raise the issue anyway. > Converting a given XML Schema instance into a proper graphical tree can be a very challenging task, especially if start supporting WADL-first development. Perhaps, initially, we can have a grammar section containing an external link only, which, if clicked, will lead to a pretty printed XML. When I was saying that WADL work was on the map I was implying, should've made it more explicit, that adding a WADL-first code generator was an important task - such a generator can faciliate the development of higher-level tools given that for a WADL-first approach to be more viable, a tool helping create a WADL doc (possibly indirectly) has to be available. Having a good human readable description created from a generated WADL is also an important task, but I'd put it after the code generator task, as far as priorities are concerned. We actually have the WADL-first code generator done - the initial code is there, but it only can be used for auto generating the code on request. That code-generator related code has to be also wrapped by a command-line tool and maven plugin... Cheers, Sergey