Sorry for repeating myself, but it would be kind of useful for me to
know the solution ;)
Does anyone know it?
My previous post was sent in HTML and was not very readable on the
sourceforge page. Sorry about that. See it for attachments. Here's the
message itself, this time in plain text.
Than
Ok. Try the below. I have not tried all your examples below - only the
first. Looks quite verbose, unfortunately.
You *could* remove the xmlns namespace to begin with, process and then
re-insert. In fact that's one option I may explore to get XMLTask to work
more nicely with the namespace grief th
Hi Michael -
Thx for the below. Sorry. I meant to reply earlier. I'm swamped at the
moment so I can't give you an ETA of a suggestion etc. at the moment.
Brian
On Tue, June 3, 2008 09:11, MichaÅ Tkacz wrote:
> Sorry for repeating myself, but it would be kind of useful for me to
> know the solut
The local-name() trick works, thanks!
Although it might get a little bit ugly if more/longer xpaths are needed.
But it's much better than nothing for me now :)
If I can suggest something, rather than stripping xml of the namespace
information in future versions, you could provide some way to def
Not really. What would you want to change it to, and why ?
Brian
On Tue, June 3, 2008 16:10, Mark Coffin wrote:
> Hi All,
>
> I've discovered that when using properties that it will only work if you
> use ${dev.property}. Is there any way to change this?
>
>
>
>Mark Coffin
>[EMAIL PROTEC
For example:
I have an ant script that sets properties based on the environment test,
prod, dev, etc. This only works if I change the property names to
dev.property and I can't change the dev.property and set it to
session.timeout or app.debug within the xmltask.
Or is there another way to acc
Can you use to call a common XMLTask target and specify
properties as elements within the ? That means you can
call the same target several times with different property values.
Brian
On Tue, June 3, 2008 16:36, Mark Coffin wrote:
> For example:
>
> I have an ant script that sets properties ba
Hi All,
I've discovered that when using properties that it will only work if you
use ${dev.property}. Is there any way to change this?
Mark Coffin
[EMAIL PROTECTED]
Phone: 905.632.0864
1.800.668.8486
Fax: 905.632.2605
www.aalsolutions.com
** CONFIDENTIALITY