Hello Stefan,
Thanks again for the helpful hint.
Stefan Bodewig writes:
> On 2010-05-11, Susanne Wunsch wrote:
>
>> How to use catalog entity with XML Schema?
>
> I must admit I've never tried that. Looking at the documentation of
> [1] - which really just is with sensible
> defaults for XSD
Hi Stefan,
eight backslashes, wow! That means four intermediate steps to get from
to \
I'll probably just go with the forward slashes in the property file
and pathconvert them to backslashes.
thanks a lot,
Jakob.
On Tue, May 11, 2010 at 17:29, Stefan Bodewig wrote:
> On 2010-05-11,
On 2010-05-11, Jakob Fix wrote:
> Hi, looked through the archive, but I don't think pathconvert can be
> used in this case.
> property file:
> prop=E:\\foo\\bar
property files and backslahes are a pain.
> build file:
>
>
>
>
> I also tried double escaping i.e.
> prop=E:foobar
Hi Mike,
Add value and else properties to condition and set values.. it will
work.
.
.
.
--
View this message in context:
http://old.nabble.com/D
On 2010-05-11, Susanne Wunsch wrote:
> Thanks for the link. Now the resolver is loaded, but the catalog
> entities doesn't really fit.
> How to use catalog entity with XML Schema?
I must admit I've never tried that. Looking at the documentation of
[1] - which really just is with sensible
defa
Hi Jacob
try this
${target.dir}/foobar.xml contents contains some well known regular expression
match criteria as in space between E: foo and bar:
Property=E: foo bar
the ${target.dir}/foobar.xml replaceregexp transforms whitespace character to /:
Property=E:/foo/bar
hth
Ma
good news indeed..post links to the source when you're ready to beta ..(i'll
try to build here and run thru as many TC's as i can)
Thanks Stefan and Graham!
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese N
Hi, looked through the archive, but I don't think pathconvert can be
used in this case.
property file:
prop=E:\\foo\\bar
build file:
actual result:
value="E:foobar"
desired result:
value="E:\foo\bar"
I also tried double escaping i.e.
prop=E:foobar
but there all backslashes dis
Well readers,
here is another update from Mike Kay just to whet your appetites
> I've now implemented a ValidatingReader that implements XMLReader and
>recognizes the Apache-defined XMLReader properties that are passed
>between Ant and Xerces, so that Saxon can now be used to implement
>both t