Return-Path: 
 <user-return-41175-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 44630 invoked from network); 18 Feb 2004 20:43:19 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 18 Feb 2004 20:43:19 -0000
Received: (qmail 35910 invoked by uid 500); 18 Feb 2004 20:42:59 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 35878 invoked by uid 500); 18 Feb 2004 20:42:59 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:user-subscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 35864 invoked from network); 18 Feb 2004 20:42:58 -0000
Received: from unknown (HELO tierw.net.avaya.com) (198.152.13.100)
  by daedalus.apache.org with SMTP; 18 Feb 2004 20:42:58 -0000
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
 i1IKdDjG023161
	for <user@ant.apache.org>; Wed, 18 Feb 2004 15:39:13 -0500 (EST)
Received: from cof110avexu4.global.avaya.com (h135-9-6-19.avaya.com
 [135.9.6.19])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
 i1IKdBjG023105
	for <user@ant.apache.org>; Wed, 18 Feb 2004 15:39:11 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: One-to-one file mapping
Date: Wed, 18 Feb 2004 13:43:01 -0700
Message-ID: 
 <BCB88E2C87736145BC9A5FCA9E2D72A601F90F3E@cof110avexu4.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: One-to-one file mapping
Thread-Index: AcP2TXTB4cTf0NZaTCC0M8Q0Q5nVYgADLz+A
From: "Holbrook, R Cody (Cody)" <rch7@avaya.com>
To: "Ant Users List" <user@ant.apache.org>
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

Matt,

Thanks for the interest in the problem.  I apologize for overlapping. =
Essentially, here's what I'm currently doing.  A XML file (containing =
documentation) is passed through a stylesheet (XSL) to create a new XSL. =
 The XSDs are run through the new stylesheet and result in XSDs with =
documentation.  The XSDs run through the castor target generate java =
code.  The java also has the documentation. Simply run javadoc against =
the newly generated java and you've got product documentation in HTML =
format. =20

That's all well and good, but as the code base has grown, the original =
documentation has grown into something that will soon be unmanageable.

So here's what I'm looking to do.  Let's say that I have 10 XSDs.  I =
know each one's name and will not change them.  Originally, one XML was =
used to hold the documentation for all 10 XSDs, but now, I want to break =
the file up into 10 pieces.  Each XML filename will look exactly like =
it's XSD counter part (a.xml contains documentation only for a.xsd, same =
with b.xml:b.xsd, etc.).  These XML files have already been created. =20

What I need ant to do is match these files up correctly.  So using the =
process I've established, here's what will happen:

b.xml goes through stylesheet to become b.xsl (this already happens to =
all XML in ${documentation})

b.xsd is passed through a.xsl to become a new a.xsd containing the =
documentation from b.xml.

Here's what a single target would look like:

	<target name=3D"create-xsl" depends=3D"create-src" =
description=3D"Create xsl from xml">
		<xslt basedir=3D"${documentation}" destdir=3D"${xsl.gen}" =
style=3D"${xsl}/stylesheet.xsl" extension=3D".xsl">
		</xslt>
	</target>
=09
	<target name=3D"create-xsd" depends=3D"create-xsl" =
description=3D"Create xsd using xsl">
		<xslt basedir=3D"${xsd}" destdir=3D"${xsd.gen}" =
style=3D"${xsl.gen}/b.xsl" extension=3D".xsd"
			includes=3D"b.xsd"></xslt>
	</target>

So here you can see that the create-xsl target isn't interested in file =
names.  It simply passes all XML files in ${documentation} through =
stylesheet.xsl to create more XSL files.

Target create-xsd, however, needs to be told exactly what XSL and XSD to =
use.  This works, and I could just make a create-xsd target for each XSD =
I need processed.  But there are several 100 and that makes for a big =
build.xml.  Also, new XSDs are added every week or so, making =
maintenance of the build file frequent and tedious work.

What I don't understand how to do is how to change the create-xsd target =
to make it do perfect matches of the XSL identified in style and the XSD =
identified in includes.  Wildcards don't work (ie *.xsl, *.xsd) because =
each XSL runs against each XSD and it's a messy and long process!  Any =
ideas?

Thanks,

Cody Holbrook



--- "Holbrook, R Cody (Cody)" <rch7@avaya.com> wrote:
> Is there a good way, without making a bevy of
> targets to cover all the xml files, to match 1-to-1
> XML-to-XSD (a.xml only interacts with a.xsd, etc.)?


Cody:

Without my having any experience working with the xslt
task, can you elaborate a little on what you want to
happen per a,b,...,z file pair?

Thanks,
Matt

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