On Apr 15, 2011, at 17:49, Steve Ebersole wrote:
What causes the bad performance? You do realize there are 3 aspects
to performing jaxb right? You have the actual jaxp parsing, the validation and then
finally the binding.
Conversely, with DOM you have jaxp parsing, validation and DOM model binding.
So what is the big difference?
I'm not an expert on it but what I understood from Jason on why they (as I understood
it) removed all JAXB parsing was that
a) it was too slow b) not flexible c) the code got very messy to support multiple
versions/variations (probably related to b)
This was in comparison to the stax(?) parsers they moved to as far as I understood it.
On 04/15/2011 10:45 AM, Max Rydahl Andersen wrote:
> im confused - are we seriously looking at using jaxb for parsing the xml
configurations even though
> they are doing what they can to remove any jaxb stuff from AS7 codebase because of
the bad performance
> and maintenance overhead (especially when its part of the server) ?
> On Apr 13, 2011, at 11:15, Hardy Ferentschik wrote:
>> On Tue, 12 Apr 2011 21:26:01 +0200, Steve Ebersole<steve(a)hibernate.org>
>>> Do we want to make caching of files a flag for processing all of the xml
>>> Currently we have methods:
>>> addFile(String path)
>>> addFile(File file)
>>> addCacheableFile(String path)
>>> addCacheableFile(File file)
>>> Could we instead condense these and allow configuration of whether to
>>> try and cache xml files?
>> Besides my other comments regarding low priority and xml maybe not being
>> the right
>> level of caching, I would also prefer a configuration approach.
>> hibernate-dev mailing list
Steve Ebersole <steve(a)hibernate.org>