Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4BDBD45D.9030506@sosnoski.com>
Date: Sat, 01 May 2010 19:12:29 +1200
From: Dennis Sosnoski <dms@sosnoski.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090822)
MIME-Version: 1.0
To: commons-dev@ws.apache.org
CC: Amila Suriarachchi <amilasuriarachchi@gmail.com>,
 java-dev@axis.apache.org,
        wss4j-dev@ws.apache.org
Subject: Re: Performance Comparison
References: <y2n1e8c1ed41004281554hd28bda8p70093dc691c1c4e4@mail.gmail.com>
 <s2yb67458761004291523rcba59b76qfae738a300019561@mail.gmail.com>
 <o2s60708f4b1004300123pa53bb104s9dd2e2243b1ac140@mail.gmail.com>
 <201004300727.50854.dkulp@apache.org>
In-Reply-To: <201004300727.50854.dkulp@apache.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Yes, I think it'd make much more sense to base a build-on-demand 
document model on the DOM API than to try to modify all the WSS4J and 
related code to use Axiom. Especially since Axiom is a mess and has had 
performance issues from the beginning (including using way too much 
memory as the model is expanded).

As a radical suggestion, how about just implementing a build-on-demand 
DOM subset suitable for use by WSS4J and other tools? This wouldn't need 
to support all the DOM operations (including those using NodeList).

Daniel Kulp wrote:
>
> The "normal" way to traverse a DOM doesn't use the NodeList thing.   The 
> NodeList stuff isn't even threadsafe in Xerces.

Actually, *no* access operations are threadsafe in Xerces. As far as I'm 
concerned that's a really bad design for general purpose use, ironically 
going back to the deferred node expansion feature that Xerces has on by 
default. It's always irked me that I have to use a synchronization lock 
around read-only operations with a (Xerces) DOM.

That said, any form of build-on-demand document model is probably not 
going to be threadsafe. But for our purposes in using it with web 
services there's not much need for threadsafety.

  - Dennis

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org