[GeoNetwork-devel] No more DTM IDs are available

Hi all,

            I am getting some exceptions thrown from Geonetwork with this
exception:

No more DTM IDs are available

My research tells me that this is caused by an old version of Xalan and
apparently the newer versions fix this (2.6.0 onwards I think). I have
managed to get around it a number of times by limiting the number of XSL
templates with the same mode. Ie. Creating sub modes. But I am now getting
this when I use the add element button on the edit form. It doesn't seem
logical to me that this is caused by the XSL, but I could be wrong. It looks
like this is being thrown from the Jeeves code so my question is when do you
think you will update to a newer version of Jeeves, if there is one
available, which hopefully uses the new version of Xalan.

--
Steven Smith <steven.smith@anonymised.com>
Software Developer / Analyst

Geometry Pty Ltd

Telephone

:

03 6223 1999

Facsimile

:

03 6223 1988

Web

:

www.geometryit.com
<file:///C:\Documents%20and%20Settings\ssmith.GEOMETRY\Application%20Data\Mi
crosoft\Signatures\www.geometryit.com>

Address

:

31 Salamanca Square, Battery Point, TAS 7004, Australia

Postal

:

PO Box 844, Sandy Bay, TAS 7006, Australia

Building Intelligent Business through the Power of Spatial

Hi Steven,

Jeeves uses the default transformer (the one provided with Java 1.5). If you
wanto to use another one, you have to pass a system property to the
java executable.

Cheers,
Andrea

Hi all,

            I am getting some exceptions thrown from Geonetwork with this
exception:

No more DTM IDs are available

My research tells me that this is caused by an old version of Xalan and
apparently the newer versions fix this (2.6.0 onwards I think). I have
managed to get around it a number of times by limiting the number of XSL
templates with the same mode. Ie. Creating sub modes. But I am now getting
this when I use the add element button on the edit form. It doesn't seem
logical to me that this is caused by the XSL, but I could be wrong. It looks
like this is being thrown from the Jeeves code so my question is when do you
think you will update to a newer version of Jeeves, if there is one
available, which hopefully uses the new version of Xalan.