Return-Path: 
 <dev-return-52223-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 57848 invoked from network); 22 Oct 2003 17:32:48 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 22 Oct 2003 17:32:48 -0000
Received: (qmail 54448 invoked by uid 500); 22 Oct 2003 17:32:37 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 54419 invoked by uid 500); 22 Oct 2003 17:32:37 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 54406 invoked from network); 22 Oct 2003 17:32:37 -0000
Received: from unknown (HELO mail2.gfs.com) (208.240.15.6)
  by daedalus.apache.org with SMTP; 22 Oct 2003 17:32:37 -0000
Received: from GFS-MTA by mail2.gfs.com
	with Novell_GroupWise; Wed, 22 Oct 2003 13:32:30 -0400
Message-Id: <sf9686ee.043@mail2.gfs.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.3
Date: Wed, 22 Oct 2003 13:32:14 -0400
From: "Kyle Adams" <kadams@gfs.com>
To: <dev@ant.apache.org>
Subject: XML, XSL, and Ant
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

This is an extension of a thread that originally began in users (http://mar=
c.theaimsgroup.com/?t=3D106676425600008&r=3D1&w=3D2), but is moving more =
towards a dev-type discussion.

I've noticed some odd behaviors in how <style> utilizes <xmlcatalog> - I'm =
not sure if they're bugs, or just the way things work.

1) <xmlcatalog> only applies to source XML document - if there are =
entities/dtds in the stylesheet, these can't be resolved by <xmlcatalog>.  =
Confirmed on Ant 1.5.3/Xalan 2.2, D11/Xerces 2.3.0 and Ant 1.6, B2/Xalan =
2.5.1/Xerces 2.5.0/10-22-2003 snapshot of commons-resolver.

2) Any XML documents accessed via the document() function in the XSL will =
not have their entities/dtds resolved.  Confirmed on Ant 1.5.3/Xalan 2.2, =
D11/Xerces 2.3.0

Are these just "the way things are" with resolvers, or should the resolver =
be catching entities/dtds in the XSL and/or any XML documents validated =
during a transformation?

Thanks,
Kyle

_____

Kyle Adams | Java Developer  |  Gordon Food Service  |  616-717-6162


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org