Return-Path: X-Original-To: apmail-cocoon-users-archive@www.apache.org Delivered-To: apmail-cocoon-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 06F5842A5 for ; Fri, 17 Jun 2011 11:18:55 +0000 (UTC) Received: (qmail 83032 invoked by uid 500); 17 Jun 2011 11:18:54 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 82974 invoked by uid 500); 17 Jun 2011 11:18:53 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 82944 invoked by uid 99); 17 Jun 2011 11:18:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 11:18:53 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RFC_ABUSE_POST,SPF_NEUTRAL,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [82.99.2.81] (HELO mx4.ciber-europe.com) (82.99.2.81) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 11:18:48 +0000 Received: from eusex01.sweden.ecsoft ([10.46.0.69]) by mx4.ciber-europe.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 17 Jun 2011 13:18:07 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: problem with serialization Cocoon2.2 Date: Fri, 17 Jun 2011 13:18:06 +0200 Message-ID: <7C655C04B6F59643A1EF66056C0E095EA99CEE@eusex01.sweden.ecsoft> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: problem with serialization Cocoon2.2 Thread-Index: Acws4DtbE254s0p+RSaHKbsp4+c3pQ== From: "Robby Pelssers" To: , Cc: , X-OriginalArrivalTime: 17 Jun 2011 11:18:07.0323 (UTC) FILETIME=[3BB9CAB0:01CC2CE0] Hi all, I have a strange situation I don't really understand. In my sitemap I have following patterns: = =20 = =20 =20 =20 =20 =20 =20 And configured following serializer: UTF-8 -//NXP//DTD P-Topic//EN ${p-topic-dtd} The pattern "basictype/*/*/*" generates a DITA topic by transforming the = result of an Xquery. When I invoke = http://localhost:8888/topics/basictype/PH3330L/released/pinning_informati= on?drawingExtension=3Dgif in the browser and save the result [1] to = filesystem I see that the doctype has been added correctly: ... When I invoke = http://localhost:8888/topics/topic2xhtml/basictype/PH3330L/released/pinni= ng_information I would expect the topic to get transformed correctly = into XHTML. This does not work however. Just for testing purpose I = added [1] in my app into /data/pinning_information.xml and created a new = match pattern which reads [1] from disc But when i now try to invoke = http://localhost:8888/topics/topic2xhtml/test the DITA topic does get = transformed correctly. Is there a difference between=20 a) calling a pipeline that generates a DITA topic on the fly and = serializes it using my custom serializer which is used as input for the=20 topic2xhtml/** pattern b) reading the DITA topic from filesystem which is used as input for = the topic2xhtml/** pattern It looks like the class attributes which should be added by the DTD are = not added in use-case (a) which is why the transform fails. Any insight is appreciated. Kind regards, Robby Pelssers --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org