From dev-return-30414-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Fri May 15 23:35:57 2009 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 43760 invoked from network); 15 May 2009 23:35:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 May 2009 23:35:57 -0000 Received: (qmail 90792 invoked by uid 500); 15 May 2009 23:35:57 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 90687 invoked by uid 500); 15 May 2009 23:35:57 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 90679 invoked by uid 99); 15 May 2009 23:35:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 May 2009 23:35:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ross.gardler@googlemail.com designates 209.85.219.175 as permitted sender) Received: from [209.85.219.175] (HELO mail-ew0-f175.google.com) (209.85.219.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 May 2009 23:35:45 +0000 Received: by ewy23 with SMTP id 23so3253142ewy.39 for ; Fri, 15 May 2009 16:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=JXXWQTmjHQOir0CkvQsBwioOJqkFcLcUXGAOaGCY2eo=; b=sbFCJ2xL0gNuCylscbxwMNQGRWjdLjVDzP0LpI+D+uotrst5vfML1INrfycszK1iwU KEH2TeUNjHgTTrUqsqcE6c8FgwCfIIdvrqo9/tZ3ZaPeJ9a4JZar/j7SUKLLBReQvQz1 ChVt9AZ60/ThUalLf4uqw7cW+UV/WxXXZyDqI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=LSeKLzgibcAssmeUI0DvyrbiNBUyfONjyco1EikBaZDVCelqIgan4O1iCs0Ny41Mh/ +MJ12hSl0EspvdEE1jRoyb+STZsQqfzsu9qNf51hxpQNLWRoHKrRCbYiO2nFqRCOwbrL eIY2zSfvNA27PvZt1Fil3PdxnAyNFM7F/ZTHM= MIME-Version: 1.0 Sender: ross.gardler@googlemail.com Received: by 10.216.26.201 with SMTP id c51mr1370164wea.228.1242430525352; Fri, 15 May 2009 16:35:25 -0700 (PDT) In-Reply-To: References: Date: Sat, 16 May 2009 00:35:25 +0100 X-Google-Sender-Auth: 13c4310525fb5a7c Message-ID: <61c9bc470905151635w69af58aeo47846e4bebeb3d4e@mail.gmail.com> Subject: Re: class attribute of body element in XDocs source is not included in generated HTML From: Ross Gardler To: dev@forrest.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2009/5/15 Brolin Empey : > I asked about this months ago, but will ask again because the issue still > exists in the current version of Forrest.=A0 The last time I asked, I was > using a release version. > > Here is the body element of my XDocs source file: > > > > The generated HTML does not include the class attribute.=A0 Is there any = way > to get the class attribute included in the generated HTML? > > I guess this is a Cocoon issue.=A0 It is annoying because I have to hack = the > generated HTML to add the class attribute. This is not a Cocoon issue. It will be stripped by one of our XSLT files. The question is, which one... To narrow the possibilities request http://localhost:8888/foo.xml This will return the intermediate format used by forrest (i.e. what we have after all input side plugins have been executed). Does the class attribute exist? If not then it is the input side XSLT that is stripping it, since you indicate your source is in XDoc I assume you are not using an input plugin and therefore it is in the core stylesheets, see http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/resources/stylesh= eets/ It would really help you in tracking this problem if you familiarise yourself with the Forrest processing pipelines, but brute force examination of likely looking stylesheets may get you there. If the class information appears in the intermediate format then the problem is on the output side. Since you are talking about HTML then the issue wll be somewhere in the skin stylesheets. Sorry I can't be more specific, I don't have the time to track the problem myself, I hope this info helps get you started debugging. Ross > > -- > Sometimes I forget how to do small talk: > > =93What if there were no hypothetical questions?=94 =97 George Carlin > --=20 Ross Gardler OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk