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? 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) ? > > /max > > On Apr 13, 2011, at 11:15, Hardy Ferentschik wrote: > >> On Tue, 12 Apr 2011 21:26:01 +0200, Steve Ebersole<st...@hibernate.org> >> wrote: >> >>> Do we want to make caching of files a flag for processing all of the xml >>> files? >>> >>> 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. >> >> --Hardy >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > /max > http://about.me/maxandersen > > > -- Steve Ebersole <st...@hibernate.org> http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
