ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Dougherty <mdoughe...@xifin.com>
Subject [Fwd: XSLT task question]
Date Fri, 04 Jul 2003 01:03:24 GMT
I'm very new to this whole process and am not really sure how it all
works. So I'll just throw this out at you all and see what you think.

A few weeks ago I asked the attached question on the users list. I am
going to have to build this anyway. So I am wondering if you think the
general Ant community would find it useful, and therefore I should
enhance the exisitng <xslt> task. Or if you don't think anyone else
would find this feature useful, I would just build our own in-house task
and leave it at that.

What I'm thinking about adding is something like:

    <style extension=".xml" dest="${build.dir}/datasets" naming="xsl">
      <xsl dir="${src.dir}">
        <include name="**/*.xsl" />
      </xsl>
      <xml dir="${src.dir}">
        <include name="data.xml" />
      </xml>
    </style>

So the Style task would take one or more filesets of XSL documents and
one or more filesets of XML documents. The name of the resulting files
would be derived from the naming attribute (either "xsl" or "xml").

What do you think?
Mike


--Forwarded Message-- 

> From: Mike Dougherty <mdougherty@xifin.com>
> To: Ant Users List <user@ant.apache.org>
> Subject: XSLT task question
> Date: 16 Jun 2003 15:33:22 -0700
> 
> In looking at the documentation for the <xslt> it appears as though the
> task is intended to process multiple XML documents with a single XSL
> stylesheet. I can't seem to find any way to get the opposite behavior
> (process a single XML document with multiple stylesheets). Is there any
> way to do this with the existing implementation? Or do I need to extend
> it to get this behavior?
> 
> Thanks,
> Mike
> 


-- 
Mike Dougherty
Sr. Software Engineer   | mdougherty@xifin.com 
XIFIN, Inc.             | http://www.xifin.com
Ph: 760.804.0770 x47    | Fax: 760.804.0851

This message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender and destroy all copies
of the original message.


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message