Out of memory

[Knuplesch, Juergen]

Hello,

My build runs now with -Xmx1500m and still out of memory.

It seems that the memory of big tasks I use is not garbage collected after I used them.
(e.g. XSLT with saxon on the classpath, junit with 2200 tests...)

The machine I use has not much more memory, so starting with -Xmx2000m failed.

What can I do?

Greetings Jürgen

--
Jürgen Knuplesch

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

[Stefan Bodewig]

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> My build runs now with -Xmx1500m and still out of memory.

> It seems that the memory of big tasks I use is not garbage collected
> after I used them.  (e.g. XSLT with saxon on the classpath, junit with
> 2200 tests...)

Ant 1.7.1 has a few classloader leaks that have been plugged in trunk -
one affected <junit>[1] - so you could try a trunk build of Ant to see
whether this helps.

I'd first try to fork the junit tests into a new VM so the memory used
by the tests themselves is not used by Ant's VM and gets reclaimed once
the tests are done.

Stefan

[1] http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTask.java?r1=808350&r2=811435

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

[Knuplesch, Juergen]

Hello,

Thanks for your answer!
Good to know, that there are known problems.

I already fork the junit tests. I even have parted the tests into three parts, because of earlier challenges.
Memory eater is also junitreport (especially for 2200 tests) etc., all the XSLT stuff needs a lot of memory and of course
Tasks like jar.

I hopefully (the build is running in the moment I write this) solved the problem by using a 64Bit Java on a 64Bit Windows machine and increasing the memory. This is of course no solution, but it will probably work.

So I have to wait for Ant 1.7.2 or create one out of the trunk...

Juergen

--
Jürgen Knuplesch
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [mailto:bodewig@...]
Gesendet: Dienstag, 6. Oktober 2009 09:33
An: user@...
Betreff: Re: Out of memory

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> My build runs now with -Xmx1500m and still out of memory.

> It seems that the memory of big tasks I use is not garbage collected
> after I used them.  (e.g. XSLT with saxon on the classpath, junit with
> 2200 tests...)

Ant 1.7.1 has a few classloader leaks that have been plugged in trunk - one affected <junit>[1] - so you could try a trunk build of Ant to see whether this helps.

I'd first try to fork the junit tests into a new VM so the memory used by the tests themselves is not used by Ant's VM and gets reclaimed once the tests are done.

Stefan

[1] http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/optional/junit/JUnitTask.java?r1=808350&r2=811435

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


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

[Stefan Bodewig]

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> Hello,

> Thanks for your answer!
> Good to know, that there are known problems.

Unfortunately they may not be.

> I already fork the junit tests.

Then the change I pointed at won't affect you since the classloader leak
only applies to non-forked tests.

> Memory eater is also junitreport (especially for 2200 tests) etc.,

Ouch.  I don't think we have any means to address that.

> all the XSLT stuff needs a lot of memory

that should be eligible to be garbage collected once the task are done.
If you had any way to attach a memory profiler to it so we could see
what is occupying the memory, that would be great.

> and of course Tasks like jar.

which shouldn't keep too much memory around once it is done either.

> So I have to wait for Ant 1.7.2 or create one out of the trunk...

That would be 1.8.0 and I'm afraid it wouldn't help.

Stefan

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

[Steve Loughran]

Knuplesch, Juergen wrote:

> Hello,
>
> Thanks for your answer!
> Good to know, that there are known problems.
>
> I already fork the junit tests. I even have parted the tests into three parts, because of earlier challenges.
> Memory eater is also junitreport (especially for 2200 tests) etc., all the XSLT stuff needs a lot of memory and of course
> Tasks like jar.
>
> I hopefully (the build is running in the moment I write this) solved the problem by using a 64Bit Java on a 64Bit Windows machine and increasing the memory. This is of course no solution, but it will probably work.

It's junitreport that is killing you : the post-run transform, not the
tests themselves.

* switch to Xalan, not Sun's built in xsl engine
* In a 64 bit Java 6u15 and up, you can ask for half-sized pointers,
XX:+UseCompressedOops
  That cuts the memory footprint of every java instance down to almost
that of 32 bit jvms,

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

[Knuplesch, Juergen]

 Hello,

I have two memory problems:

1.In the XSLT task I get:
java.lang.OutOfMemoryError: PermGen space

I increased MaxPermSize
In a few hours I will know if this helped, but it is not a real solution.


2.The second problem disappeared, after increasing the memory to 2000m.
It happened this time (I earlier had to increase the memory) in the non standard pack200 Task:

D:\DopeBuildBase\Build\DopeBuildServer\dopebuildwar.xml:356: java.lang.OutOfMemoryError

This task made also a few problems, when I used it first.
I check the documentation for help, or is pack200 also included in the next Ant version?

Thanks for your help!

I'm not sure if I can profile this, but maybe I try.


Greetings Jürgen

--
Jürgen Knuplesch
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [mailto:bodewig@...]
Gesendet: Dienstag, 6. Oktober 2009 11:59
An: user@...
Betreff: Re: Out of memory

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> Hello,

> Thanks for your answer!
> Good to know, that there are known problems.

Unfortunately they may not be.

> I already fork the junit tests.

Then the change I pointed at won't affect you since the classloader leak only applies to non-forked tests.

> Memory eater is also junitreport (especially for 2200 tests) etc.,

Ouch.  I don't think we have any means to address that.

> all the XSLT stuff needs a lot of memory

that should be eligible to be garbage collected once the task are done.
If you had any way to attach a memory profiler to it so we could see what is occupying the memory, that would be great.

> and of course Tasks like jar.

which shouldn't keep too much memory around once it is done either.

> So I have to wait for Ant 1.7.2 or create one out of the trunk...

That would be 1.8.0 and I'm afraid it wouldn't help.

Stefan

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


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

[Redmond, Nicole]

Sometimes you need a combination...

-Xms128m -Xmx768m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC

-Xms should be set to 1/64 of your memory size, -Xmx should be set to 1/4 as a max....

Nicole Redmond

-----Original Message-----
From: Knuplesch, Juergen [mailto:Juergen.Knuplesch@...]
Sent: Tuesday, October 06, 2009 7:10 AM
To: Ant Users List
Subject: AW: Out of memory

 Hello,

I have two memory problems:

1.In the XSLT task I get:
java.lang.OutOfMemoryError: PermGen space

I increased MaxPermSize
In a few hours I will know if this helped, but it is not a real solution.


2.The second problem disappeared, after increasing the memory to 2000m.
It happened this time (I earlier had to increase the memory) in the non standard pack200 Task:

D:\DopeBuildBase\Build\DopeBuildServer\dopebuildwar.xml:356: java.lang.OutOfMemoryError

This task made also a few problems, when I used it first.
I check the documentation for help, or is pack200 also included in the next Ant version?

Thanks for your help!

I'm not sure if I can profile this, but maybe I try.


Greetings Jürgen

--
Jürgen Knuplesch
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [mailto:bodewig@...]
Gesendet: Dienstag, 6. Oktober 2009 11:59
An: user@...
Betreff: Re: Out of memory

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> Hello,

> Thanks for your answer!
> Good to know, that there are known problems.

Unfortunately they may not be.

> I already fork the junit tests.

Then the change I pointed at won't affect you since the classloader leak only applies to non-forked tests.

> Memory eater is also junitreport (especially for 2200 tests) etc.,

Ouch.  I don't think we have any means to address that.

> all the XSLT stuff needs a lot of memory

that should be eligible to be garbage collected once the task are done.
If you had any way to attach a memory profiler to it so we could see what is occupying the memory, that would be great.

> and of course Tasks like jar.

which shouldn't keep too much memory around once it is done either.

> So I have to wait for Ant 1.7.2 or create one out of the trunk...

That would be 1.8.0 and I'm afraid it wouldn't help.

Stefan

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


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


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

[Knuplesch, Juergen]

Hello Steve,

I had my problems with junitreport before....

This time the PermGenSpace error happens with saxon.
For this XSLT I had to use saxon.
In my build I use Saxon and for junitreport the standard VM xsl processor,

How do I tell junitreport to use Saxon or Xalan?
I did not find an option (in your book for ANT 1.6.5) as in XSLT.
I thought xalan is the standard xsl processor in ANT?

Greetings Jürgen


--
Jürgen Knuplesch
-----Ursprüngliche Nachricht-----
Von: Steve Loughran [mailto:stevel@...]
Gesendet: Dienstag, 6. Oktober 2009 13:02
An: Ant Users List
Betreff: Re: AW: Out of memory

Knuplesch, Juergen wrote:

> Hello,
>
> Thanks for your answer!
> Good to know, that there are known problems.
>
> I already fork the junit tests. I even have parted the tests into three parts, because of earlier challenges.
> Memory eater is also junitreport (especially for 2200 tests) etc., all
> the XSLT stuff needs a lot of memory and of course Tasks like jar.
>
> I hopefully (the build is running in the moment I write this) solved the problem by using a 64Bit Java on a 64Bit Windows machine and increasing the memory. This is of course no solution, but it will probably work.

It's junitreport that is killing you : the post-run transform, not the tests themselves.

* switch to Xalan, not Sun's built in xsl engine
* In a 64 bit Java 6u15 and up, you can ask for half-sized pointers, XX:+UseCompressedOops
  That cuts the memory footprint of every java instance down to almost that of 32 bit jvms,

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


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

[Stefan Bodewig]

On 2009-10-06, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> It happened this time (I earlier had to increase the memory) in the
> non standard pack200 Task:

> D:\DopeBuildBase\Build\DopeBuildServer\dopebuildwar.xml:356: java.lang.OutOfMemoryError

> This task made also a few problems, when I used it first.  I check the
> documentation for help, or is pack200 also included in the next Ant
> version?

No, it is not developed by Ant developers.  Actually I'm aware of more
than one pack200 task, neither of which is developed by Ant devs, so I'm
not even sure which one you talk about 8-)

Stefan

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

[Steve Loughran]

Knuplesch, Juergen wrote:

> Hello Steve,
>
> I had my problems with junitreport before....
>
> This time the PermGenSpace error happens with saxon.
> For this XSLT I had to use saxon.
> In my build I use Saxon and for junitreport the standard VM xsl processor,
>
> How do I tell junitreport to use Saxon or Xalan?
> I did not find an option (in your book for ANT 1.6.5) as in XSLT.
> I thought xalan is the standard xsl processor in ANT?

If Xalan is on the classpath, it gets picked up, otherwise on java1.5+
the default XSL engine is the variant of xalan that comes in the JVM,
and it is very memory hungry.

If you run ant -diagnostics you will see which engine you get; if it is
the one in the JVM, stick a xalan-2.7.x into your ANT_HOME/lib

PermGen heapspace is a separate problem. On the BEA/Oracle JRockit JVM,
it never occurs, they just have one big heap, instead of a separate heap
for class information. But you can't download that for free any more.

Try the 64 bit jvm with compressed pointers; its got a big heap with
small pointers, not as good as JRockit, but a good second best.


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

[Knuplesch, Juergen]

Hello,

I got now the Java profiler on. Maybe I will find out, whats going on.
But now javadoc ran outofmemory, probably because of my change from 32Bit to 64Bit java.

I will try Xalan. If I find sth. out or become despaired, i will post again

Juergen

--
Jürgen Knuplesch                    
-----Ursprüngliche Nachricht-----
Von: Steve Loughran [mailto:stevel@...]
Gesendet: Dienstag, 6. Oktober 2009 14:21
An: Ant Users List
Betreff: Re: AW: AW: Out of memory

Knuplesch, Juergen wrote:

> Hello Steve,
>
> I had my problems with junitreport before....
>
> This time the PermGenSpace error happens with saxon.
> For this XSLT I had to use saxon.
> In my build I use Saxon and for junitreport the standard VM xsl
> processor,
>
> How do I tell junitreport to use Saxon or Xalan?
> I did not find an option (in your book for ANT 1.6.5) as in XSLT.
> I thought xalan is the standard xsl processor in ANT?

If Xalan is on the classpath, it gets picked up, otherwise on java1.5+ the default XSL engine is the variant of xalan that comes in the JVM, and it is very memory hungry.

If you run ant -diagnostics you will see which engine you get; if it is the one in the JVM, stick a xalan-2.7.x into your ANT_HOME/lib

PermGen heapspace is a separate problem. On the BEA/Oracle JRockit JVM, it never occurs, they just have one big heap, instead of a separate heap for class information. But you can't download that for free any more.

Try the 64 bit jvm with compressed pointers; its got a big heap with small pointers, not as good as JRockit, but a good second best.


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


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

[David Leangen-12]

> -Xms128m -Xmx768m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC
>
> -Xms should be set to 1/64 of your memory size, -Xmx should be set  
> to 1/4 as a max....

How did you arrive at these "rules"?



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

[Steve Loughran]

Knuplesch, Juergen wrote:
> Hello,
>
> I got now the Java profiler on. Maybe I will find out, whats going on.
> But now javadoc ran outofmemory, probably because of my change from 32Bit to 64Bit java.

Use -XX:+UseCompressedOops  -best feature of Java 6u15.


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

[Redmond, Nicole]

http://java.sun.com/performance/reference/whitepapers/tuning.html

Is just one of numerous locations for these "rules".  By the way, they are not rules, they are best practices...

Nicole Redmond

-----Original Message-----
From: David Leangen [mailto:apache@...]
Sent: Tuesday, October 06, 2009 8:36 PM
To: Ant Users List
Subject: Re: Out of memory


> -Xms128m -Xmx768m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC
>
> -Xms should be set to 1/64 of your memory size, -Xmx should be set  
> to 1/4 as a max....

How did you arrive at these "rules"?



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


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

[Knuplesch, Juergen]

Hello,

After taking xalan 2.7.1 into Ants lib path, my XSLT using saxon dont work anymore:

dsf.comparedsffiles:
     [xslt] Processing ...
     [xslt] Loading stylesheet D:\DopeBuildBase\Build\DopeBuildServer\XSLT\compare-dsf.xsl
     [xslt] compare-dsf.xsl:113:104: Fatal Error! java.lang.ClassCastException: org.apache.xpath.objects.XRTreeFrag Cause: java.lang.ClassCastException: org.apache.xpath.objects.XRTreeFrag
     [xslt] Failed to process ....

This worked beforehand.

So saxon can't cope with the new jars. What I did was:

 <xslt style="${dsf.comparedsffiles.xsltfile}"
          in="${dsf.comparedsffiles.in}"
          out="${dsf.comparedsffiles.out}" >
        <classpath>
          <pathelement location="${ant.xslt.saxonjar}" />
        </classpath>
        <param name="filename.1" expression="${dsf.comparedsffiles.file1}"/>
        <param name="filename.2" expression="${dsf.comparedsffiles.file2}"/>
        <param name="errorfilename" expression="${dsf.comparedsffiles.error}"/>
 
    </xslt>

Any idea?

Juergen
-----Ursprüngliche Nachricht-----
Von: Steve Loughran [mailto:stevel@...]
Gesendet: Dienstag, 6. Oktober 2009 14:21
An: Ant Users List
Betreff: Re: AW: AW: Out of memory

Knuplesch, Juergen wrote:

> Hello Steve,
>
> I had my problems with junitreport before....
>
> This time the PermGenSpace error happens with saxon.
> For this XSLT I had to use saxon.
> In my build I use Saxon and for junitreport the standard VM xsl
> processor,
>
> How do I tell junitreport to use Saxon or Xalan?
> I did not find an option (in your book for ANT 1.6.5) as in XSLT.
> I thought xalan is the standard xsl processor in ANT?

If Xalan is on the classpath, it gets picked up, otherwise on java1.5+ the default XSL engine is the variant of xalan that comes in the JVM, and it is very memory hungry.

If you run ant -diagnostics you will see which engine you get; if it is the one in the JVM, stick a xalan-2.7.x into your ANT_HOME/lib

PermGen heapspace is a separate problem. On the BEA/Oracle JRockit JVM, it never occurs, they just have one big heap, instead of a separate heap for class information. But you can't download that for free any more.

Try the 64 bit jvm with compressed pointers; its got a big heap with small pointers, not as good as JRockit, but a good second best.


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


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

[Stefan Bodewig]

On 2009-10-07, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> After taking xalan 2.7.1 into Ants lib path, my XSLT using saxon dont
> work anymore:

Are you sure Ant is using Saxon at all after your change?  I don't see
any explicit configuration for saxon here

>  <xslt style="${dsf.comparedsffiles.xsltfile}"
>           in="${dsf.comparedsffiles.in}"
>           out="${dsf.comparedsffiles.out}" >
>         <classpath>
>           <pathelement location="${ant.xslt.saxonjar}" />
>         </classpath>
>         <param name="filename.1" expression="${dsf.comparedsffiles.file1}"/>
>         <param name="filename.2" expression="${dsf.comparedsffiles.file2}"/>
>         <param name="errorfilename" expression="${dsf.comparedsffiles.error}"/>
>     </xslt>

Does it help if you add a <factory> nested element to the task?

Stefan

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

[Knuplesch, Juergen]

Hello,


I did put saxon on the classpath as some docu told:

>         <classpath>
>           <pathelement location="${ant.xslt.saxonjar}" />
>         </classpath>

Afterwards it worked without xalan on the classpath.
When I put xalan into Ants libpath it fails.
Probably Ant is using now xalan.

I wanted to try factory, but there is a jar missing.
I did not find out which jar is missing.
Maybe I try this later...

I tried a different plan.
I installed the Saxon Ant-xslt task.
But this task does not understand my windows full filenames.
It works when I replace all \ to / in the calling params.
Is there a way to convert in a property all "\" to "/" ?


Greetings Juergen

--
Jürgen Knuplesch                    www.icongmbh.de
icon Systemhaus GmbH                Tel. [phone]
Sophienstraße 40                    
D-70178 Stuttgart                   Fax. [phone]

Geschäftsführer: Uwe Seltmann
HRB Stuttgart 17655
USt-IdNr.: DE 811944121
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [mailto:bodewig@...]
Gesendet: Donnerstag, 8. Oktober 2009 09:39
An: user@...
Betreff: Re: Xalan hinders saxon

On 2009-10-07, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> After taking xalan 2.7.1 into Ants lib path, my XSLT using saxon dont
> work anymore:

Are you sure Ant is using Saxon at all after your change?  I don't see any explicit configuration for saxon here

>  <xslt style="${dsf.comparedsffiles.xsltfile}"
>           in="${dsf.comparedsffiles.in}"
>           out="${dsf.comparedsffiles.out}" >
>         <classpath>
>           <pathelement location="${ant.xslt.saxonjar}" />
>         </classpath>
>         <param name="filename.1" expression="${dsf.comparedsffiles.file1}"/>
>         <param name="filename.2" expression="${dsf.comparedsffiles.file2}"/>
>         <param name="errorfilename" expression="${dsf.comparedsffiles.error}"/>
>     </xslt>

Does it help if you add a <factory> nested element to the task?

Stefan

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


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

[Stefan Bodewig]

On 2009-10-08, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> Is there a way to convert in a property all "\" to "/" ?

<pathconvert dirsep="/" property="converted.property">
  <path location="original.property"/>
</pathconvert>

should work.

Stefan

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

[Knuplesch, Juergen]

Thanks, I had a look at that, but did not figure out, that it works with properties.

I wrote an AntTask that does the job, which was not necessary....

I think now the stuff is working...

Greetings Juergen


--
Jürgen Knuplesch                    www.icongmbh.de
icon Systemhaus GmbH                Tel. [phone]
Sophienstraße 40                    
D-70178 Stuttgart                   Fax. [phone]

Geschäftsführer: Uwe Seltmann
HRB Stuttgart 17655
USt-IdNr.: DE 811944121
-----Ursprüngliche Nachricht-----
Von: Stefan Bodewig [mailto:bodewig@...]
Gesendet: Donnerstag, 8. Oktober 2009 13:14
An: user@...
Betreff: Re: Xalan hinders saxon: converting property values

On 2009-10-08, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:

> Is there a way to convert in a property all "\" to "/" ?

<pathconvert dirsep="/" property="converted.property">
  <path location="original.property"/>
</pathconvert>

should work.

Stefan

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


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

[mgainty]

i *thought*
SAX is for event based XML parsing
XALAN parses the entire DOM document

in theory they are complimentary technologies
but there exist situations where a SAXSource is transformed to a DOMResult
http://www.cafeconleche.org/books/xmljava/chapters/ch09s11.html

http://xml.apache.org/xalan-j/
?
*gruss*
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

> Subject: AW: Xalan hinders saxon: converting property values
> Date: Thu, 8 Oct 2009 16:34:59 +0200
> From: Juergen.Knuplesch@...
> To: user@...
>
> Thanks, I had a look at that, but did not figure out, that it works with properties.
>
> I wrote an AntTask that does the job, which was not necessary....
>
> I think now the stuff is working...
>
> Greetings Juergen
>
>
> --
> Jürgen Knuplesch                    www.icongmbh.de
> icon Systemhaus GmbH                Tel. [phone]
> Sophienstraße 40                    
> D-70178 Stuttgart                   Fax. [phone]
>
> Geschäftsführer: Uwe Seltmann
> HRB Stuttgart 17655
> USt-IdNr.: DE 811944121
> -----Ursprüngliche Nachricht-----
> Von: Stefan Bodewig [mailto:bodewig@...]
> Gesendet: Donnerstag, 8. Oktober 2009 13:14
> An: user@...
> Betreff: Re: Xalan hinders saxon: converting property values
>
> On 2009-10-08, Knuplesch, Juergen <Juergen.Knuplesch@...> wrote:
>
> > Is there a way to convert in a property all "\" to "/" ?
>
> <pathconvert dirsep="/" property="converted.property">
>   <path location="original.property"/>
> </pathconvert>
>
> should work.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@... For additional commands, e-mail: user-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>

     
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/