<br><font size=2 face="sans-serif">I would be very interested in this ability to control the initial size, I am working repeatedly with documents I know a lot about.</font>
<br>
<br><font size=2 face="sans-serif">I have an en_en.xml which I know has about 4000 children, I also have a usd.xml which has about a 1000 and a config.xml which averages about 10 and I have one which only has a few children but is very nested so I assume setting to 1 would be quite slow but very compact (but then this one is loading when the servlet starts so space is more important than time)</font>
<br>
<br><font size=2 face="sans-serif">A setting to control these before I build a document would be welcome.</font>
<br>
<br><font size=2 face="sans-serif">Any help of creating a faster, non validating parse would be helpful as the documents I am parsing in are the ones I created (persistence) so there is no point in validating them as JDOM created them.<br>
<br>
/Phill<br>
IS Dept, Software Engineer.<br>
phill_perryman@mitel.com<br>
http://www.mitel.com<br>
Tel: +44 1291 436023</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Bradley S. Huffman" <hip@cs.okstate.edu></b></font>
<br><font size=1 face="sans-serif">Sent by: jdom-interest-admin@jdom.org</font>
<p><font size=1 face="sans-serif">18/02/2004 17:08</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: phil@triloggroup.com</font>
<br><font size=1 face="sans-serif"> cc: jdom-interest@jdom.org</font>
<br><font size=1 face="sans-serif"> Subject: [jdom-interest] Re: [jdom-announce] JDOM Beta10 released</font></table>
<br>
<br>
<br><font size=2 face="Courier New">phil@triloggroup.com writes:<br>
<br>
> I'm very pleased to see that JDOM is being officially released soon. Mo=<br>
> reover, it features new capabilities like Content class that will make =<br>
> our work easier!<br>
><br>
> I still have just one concern with the API, that forces us to provide o=<br>
> ur own build to customers. It's about optimization, when you want to co=<br>
> nstruct a DOM without going through any validation stuff, because you p=<br>
> erfectly know that your DOM is valid. Typically, we currently do this w=<br>
> hen building an HTML tree programmatically (the build class is machine =<br>
> generated from HTML source). <br>
> We already spoke about this earlier, and I want to reanimate the debate=<br>
> because it may gain up to 20/25% execution speed. <br>
><br>
> You'll find a copy of the changes I made and now working with Beta 9 in=<br>
> production. To please Eliott and prevent people from doing something b=<br>
> ad, all these &quot;unverified&quot; methods must be called as static m=<br>
> ethods from UnverifiedFactory class. I joined to the mail the pieces of=<br>
> code that does the trick. Nothing changed in the API, it is just an a=<br>
> dd-on.. Because of class scopes, there is now way to make it running wi=<br>
> thout providing a custom build. <br>
<br>
Jason just moved JDOMFactory out of package org.jdom.input and into<br>
org.jdom so users can have a custom factory to skip verification from<br>
trusted sources, so that pretty much eliminates the need for the extra<br>
createElement, etc. methods. And since it has moved, putting a "fast"<br>
version of JDOMFactory in contrib would probably be a good idea at this<br>
point.<br>
<br>
But I don't see how the static addContent methods help. Elements can have<br>
anything as children except a DocType so all your skipping is one instanceof<br>
test and a check for a null parent. But the potentially biggest time waster,<br>
reallocation of the content array, remains intact. But that assumes the<br>
number of children in most of a document's elements greatly exceeds the<br>
INITIAL_ARRAY_SIZE and causes excessive array reallocation. Something only<br>
profiling can support or disprove, and then only on a case by case bases.<br>
<br>
One problem I do see, which falls under the TODO item "ensure JDOM is<br>
appropriately tweaked for subclassing", is if your problem would benefit<br>
from a larger INITIAL_ARRAY_SIZE, I don't see a easy to do it currently.<br>
<br>
Brad<br>
_______________________________________________<br>
To control your jdom-interest membership:<br>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com<br>
</font>
<br>
<br>