Mailing-List: contact dev-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Developers List" <dev@poi.apache.org>
Received-SPF: pass (nike.apache.org: domain of yaniv.kunda@answers.com
 designates 209.85.217.175 as permitted sender)
From: Yaniv Kunda <yaniv.kunda@answers.com>
References: 
 <CABeeCP364cGWWDO0KeKWnNv3r0DPdMnVNaQ9uPF5Ei39+YaHtw@mail.gmail.com>
 <53DFFC99.1070008@gmx.de> <12cd0981f36c7a8c0e27640c43849219@mail.gmail.com>
 <alpine.DEB.2.02.1408051000440.19865@urchin.earth.li>
In-Reply-To: <alpine.DEB.2.02.1408051000440.19865@urchin.earth.li>
MIME-Version: 1.0
Thread-Index: AQLggtemhPdAM2s5etQcEhHjHhqm/QJusnlmAdLt5aMCLv6qypluOEQg
Date: Wed, 6 Aug 2014 13:30:46 +0300
Message-ID: <4eaaac619e6aae343193aac30921b2c1@mail.gmail.com>
Subject: =?UTF-8?Q?RE=3A_Performanc=E2=80=8Be_issues_related_to_XMLBeans?=
To: POI Developers List <dev@poi.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The fact that you described the XMLBeans proxy objects as "leaking" through
the API says it all - they should have been encapsulated from the start.
If you add the facts that:
- the XMLBeans project is dead (in the attic for over a year, reboot is
stuck)
- we have/had so many issues with it
- it might be an overkill in regards to unnecessary (or even broken)
thread-safety The conclusion that it should be replaced at some point, but
for the shorter term be hidden and only used as an internal implementation.

The best way to do that in light of its existing exposure is to deprecate i=
t
and provide a new alternative wrapper that will eventually supersede it.

-----Original Message-----
From: Nick Burch [mailto:apache@gagravarr.org]
Sent: Tuesday, August 5, 2014 12:09
To: POI Developers List
Subject: RE: Performanc=E2=80=8Be issues related to XMLBeans

On Tue, 5 Aug 2014, Yaniv Kunda wrote:
> I'll try to have some patches out soon.

I'd suggest you pick one or two places only, pick a few documents of varyin=
g
size complexity, and post average performance before and after. No point
updating the code if it doesn't actually help much!

> In regards to XMLBeans replacement, I naturally prefer to use JAXB
> which does not require any additional libraries - Unless it poses some
> limitations on what POI needs.

We have the XMLBeans objects leaking through the API in various places, and
a whole bunch of our users needing that to do what they do. Much as I'd lov=
e
all of those people to instead submit a patch to POI which wraps that
functionality up in a nice usermodel interface with the xml handling stuff
hidden inside, I just can't see most of them bothering. Unless we could get
JAXB to be binary compatible with XMLBeans, I can't see us being able to
switch it because it'd just break too much downstream

Thanks
Nick

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

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