From dev-return-87601-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Dec 03 01:03:21 2010 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 13289 invoked from network); 3 Dec 2010 01:03:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Dec 2010 01:03:20 -0000 Received: (qmail 46826 invoked by uid 500); 3 Dec 2010 01:03:19 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 46722 invoked by uid 500); 3 Dec 2010 01:03:19 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 46715 invoked by uid 99); 3 Dec 2010 01:03:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 01:03:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirunhua@gmail.com designates 209.85.161.182 as permitted sender) Received: from [209.85.161.182] (HELO mail-gx0-f182.google.com) (209.85.161.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 01:03:13 +0000 Received: by gxk8 with SMTP id 8so4752140gxk.13 for ; Thu, 02 Dec 2010 17:02:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KtnjgkdYw3GF3zc+LgHJStKDuwokJd6+SuTBLKqXryw=; b=X8HuMclDHEff5fpHQeTtgvtvgjSGbmLJ2EaWFkSFc2sjpjF62uHpxHyHyDgnLTxV67 JHbdQDmhT4v7jxzJeu0pigXxCTn2mwHndRTSJ0SJPvFp+6EgtAITTNwvZQHjTWHg8JNr +izP/K9uv5LhMPZNnb8dkAhrv1bUzQdnRo/1M= 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; b=NLr3Y5wdj9Y4lR08aHcwXMvYVFydXTQYYgGFoTRFZOUiRIZnmH2kDQwYssZN6QKoJ0 PShw1BArYKRu1mWFkJ/jcf0ic2eCQj3MbVeXAnJpqBtPgiDQXreYr804cBc4JAVoOv7l MVGVdYG4zq6jhkwFSUoyKRL5Tt/ncDZUlR/a8= MIME-Version: 1.0 Received: by 10.90.75.18 with SMTP id x18mr2288235aga.5.1291338172592; Thu, 02 Dec 2010 17:02:52 -0800 (PST) Received: by 10.90.106.6 with HTTP; Thu, 2 Dec 2010 17:02:52 -0800 (PST) In-Reply-To: References: Date: Fri, 3 Dec 2010 09:02:52 +0800 Message-ID: Subject: Re: Incorrect schema docs on Geronimo website From: chi runhua To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=0016361e7cf80ff45f049677198d --0016361e7cf80ff45f049677198d Content-Type: text/plain; charset=ISO-8859-1 Thanks Shawn. That's really helpful. I thought those .xsd.html files under /schema-2.1/docs/ directory were generated automatically, actually they're not. Looks like Hernan or some other committers did the conversion using oXygen XML editor and then committed those files. I also noticed that the copyright information on the bottom of each page is not correct, which should be copyright(C)2005-2010. Another thing I didn't figure out yet is that how those .xsd.html files were generated using the same template as other pages on Geronimo homesite, because those schema files are not from Confluence wiki thus the .html files can't be generated using the auto-export plugin. Does this means we have to update each page manually? If anyone could shed a light on me, that would be great. Another thought is we don't generate .html pages for the schema files any more, we only provide the raw data for the users just like we did for 2.0 version. see https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/schemas-1.1/ Any thoughts? Jeff C On Thu, Dec 2, 2010 at 5:38 PM, Shawn Jiang wrote: > Just take a look at the source tree, [1] might be the place to add. > > [1]https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/ > > On Thu, Dec 2, 2010 at 5:35 PM, chi runhua wrote: > > Hi, looked like that the schema docs are not correct for Geronimo 2.2 on > the > > Geronimo website, because G2.2 schema docs[1] still link to G2.1 schema > > pages under a /schema-2.1/docs directory, see [2]. And the oXygen XML > > Editor do the real-time transforming to the .xsd files and publish the > > result files to Geronimo Website. > > > > [1]. http://geronimo.apache.org/apache-geronimo-v22-xml-schemas.html > > [2]. > http://geronimo.apache.org/schemas-2.1/docs/geronimo-web-2.0.1.xsd.html > > > > IIUC, we might need to create a folder for each major release such as > 2.*, > > 3.*, and then promote corresponding schema files into the folder, so that > > they could be converted and published by the oXygen tool successfully. > Does > > anyone know where and how to create the folder? > > > > > > Jeff C > > > > > > > > -- > Shawn > --0016361e7cf80ff45f049677198d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Shawn.=A0 That's really helpful.

I thought those .xsd.htm= l files under /schema-2.1/docs/ directory were generated automatically, act= ually they're not. =A0Looks like Hernan or some other committers did th= e conversion using oXygen XML editor and then committed those files.

I also noticed that the copyright information on the bottom = of each page is not correct, which should be copyright(C)2005-2010.=A0
<= div>
Another thing I didn't figure out yet is that how th= ose .xsd.html files were generated using the same template as other pages o= n Geronimo homesite, because those schema files are not from Confluence wik= i thus the .html files can't be generated using the auto-export plugin.= Does this means we have to update each page manually? If anyone could shed= a light on me, that would be great.

Another thought is we don't generate .html pages fo= r the schema files any more, we only provide the raw data for the users jus= t like we did for 2.0 version. see=A0https://svn.apache.org/repos/a= sf/geronimo/site/trunk/docs/schemas-1.1/

Any thoughts?

Jeff C

On Thu, Dec 2, 2010 at 5:38 PM, Shawn Jiang <ge= nspring@gmail.com> wrote:
Just take a look at the= source tree, [1] might be the place to add.

[1]https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/=

On Thu, Dec 2, 2010 at 5:35 PM, chi runhua <chirunhua@gmail.com> wrote:
> Hi, looked like that the schema docs are not correct for Geronimo 2.2 = on the
> Geronimo website,=A0 because G2.2 schema docs[1] still link to G2.1 sc= hema
> pages under a /schema-2.1/docs directory, see [2].=A0 And the oXygen X= ML
> Editor do the real-time transforming to the .xsd files and publish the=
> result files to Geronimo Website.
>
> [1]. http://geronimo.apache.org/apache-geronimo-v22= -xml-schemas.html
> [2]. http://geronimo.apache.org/schemas-2.1= /docs/geronimo-web-2.0.1.xsd.html
>
> IIUC, we might need to create a folder for each major release such as = 2.*,
> 3.*, and then promote corresponding schema files into the folder, so t= hat
> they could be converted and published by the oXygen tool successfully.= =A0 Does
> anyone know where and how to create the folder?
>
>
> Jeff C
>
>



--
Shawn

--0016361e7cf80ff45f049677198d--