Hi,
Right, so as for 1) this would be more for doing selections and trasformations
that are quick and trivial and that can't be done using something like
XmlProperty to extract values.
2) is a bit trickier, so that would be details I'd look into. I'm a bit swamped
with other work but I'm going to poke around and see what I can see.
Thanks,
Andrew
Dominique Devienne <[EMAIL PROTECTED]> wrote: > how would people feel about
having inline XSLT
> in the ant file under the xslt task?
Yes, I thought about this too, but I don't think it's either practical nor easy.
(1) Not practical because XSL stylesheet tend to be rather big. Mixing
more than a minimal XSL with a build file will rapidly become unwieldy
IMHO.
(2) Not easy because XSL makes heavy use of XML namespaces, and this
will (a) either clash with Ant processing of XML NS, or (b) require
the use of a CDATA section of the XSL code, which would be ugly.
Maybe there's an XML NS-aware version of XmlFragment, I don't recall.
Stefan uses it I believe to have in-Ant NAnt builds, or something of
the like, so it might work and prove me wrong on (2), yet (1) remains.
That said, if you feel like doing it, go for it! ;-) --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail.
