Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 8795 invoked by uid 500); 19 Jul 2001 15:44:54 -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 8784 invoked from network); 19 Jul 2001 15:44:54 -0000 Message-ID: <4341EF5F8B4AD311AB4B00902740B9F208680711@xcup02.cup.hp.com> From: "HALLOWELL,KARL (HP-Cupertino,ex1)" To: "'cocoon-users@xml.apache.org'" Subject: RE: The order of battle Date: Thu, 19 Jul 2001 08:37:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > -----Original Message----- > From: Marks local account [mailto:millerm@logica.com] >=20 > I have a pipeling that has the following pattern: >=20 > > > > > >=20 > I though what happened her was that a file 'login_xsp.java' was > generated from 'login.xsp' which would fire SAX events that are then > transformed by 'login-page2html.xsl'. >=20 > But in tracking down a bug it looks more like the login.xsp=20 > page has the > login-page2html.xsl applied, and then it is compiled into a=20 > .java file. > I concluded this because the problem was that the root tag=20 > was not being > matched, and the java file only had a few tags in it. When I=20 > go the name > of the tag right in login-page2html.xsl then the resulting java file > produced had all the bits and pieces. I don't follow your conclusion. This fits with the scenario that the stylesheet inserts by default some html tags, and skips the XML which = it can't match. This is expected behavior, FAIK. Karl Hallowell=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = karl_hallowell@hp.com =20 --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: