I'm curious, does anyone know the rationale for closing down the XMLBeans product in the first place? It doesn't seem to be stated on the XMLBeans website. I seem to recall the last time I played with XMLBeans/JAXB (maybe 2 or 3 years ago?) that XMLBeans seemed to be easier to use, though I don't recall precisely why.
Dustin On 11/08/2017 09:13 AM, Murphy, Mark wrote: > This actually seems to be an optimal solution as we wouldn't need to worry > about refactoring in a new XML binding scheme, and as Java and technology > moves forward, other users of XMLBeans are likely to be affected by the same > bugs that we are having issues with. > > -----Original Message----- > From: Upayavira [mailto:u...@odoko.co.uk] > Sent: Tuesday, November 07, 2017 12:16 PM > To: Javen O'Neal <one...@apache.org>; POI Developers List <dev@poi.apache.org> > Cc: gene...@attic.apache.org; d...@xmlbeans.apache.org > Subject: Suspected Spam:Re: Non-maintainer upload of bugfixes for the > XMLBeans library in the Attic > > Could POI take on XMLbeans as a second product? If they intend to maintain > it, and can provide 3+ PMC members who will vote on releases, then presumably > the POI project could make releases of the Apache XMLBeans product? > > Then there's no naming issues, everyone benefits from public releases. > At such a point as there is enough interest, it can fork back into its own > community. POI committers would gain commit rights on an XMLBeans repo. > > Upayavira > > On Tue, 7 Nov 2017, at 04:59 PM, Javen O'Neal wrote: >> Any other project using XMLBeans on Android would likely be affected >> by the same issue. Making the XMLBeans update within the POI source >> code or POI maven coordinates would make it more difficult for others >> to find this update. >> >> If we had to change the Java package name to >> org.apache.poi.internal.xmlbeans, it would take a bit of trickery to >> allow users to continue using the official releases, XMLBeans 2.3.0 or >> 2.6.0 if the bug doesn't affect them. >> >> On Nov 7, 2017 03:41, "sebb" <seb...@gmail.com> wrote: >> >> On 7 November 2017 at 07:20, jan iversen <jancasacon...@gmail.com> wrote: >>> >>> Sent from my iPad >>> >>>> On 6 Nov 2017, at 21:47, Dominik Stadler <dominik.stad...@gmx.at> wrote: >>>> >>>> Hi, >>>> >>>> The Apache XMLBeans library was moved to the Attic a few years ago >>>> (05/2014), however Apache POI still uses the library as it's core >>>> XML binding framework. >>>> >>>> While the Apache POI PMC and the development community is already >>>> discussing possible replacements for some time, use of XMLBeans is >>>> still deeply rooted and thus hard to replace quickly. >>>> >>>> Over time, we discovered a few grave bugs in XMLBeans which lead to >>>> bug-reports that we cannot fix ourselves. >>>> >>>> Therefore we would like to start discussion about an NMU of >>>> XMLBeans to >> get >>>> a fix for the most pressing issues. >>>> >>>> See https://bz.apache.org/bugzilla/show_bug.cgi?id=59268 for the >>>> full discussion,and https://github.com/pjfanning/xmlbeans for a >>>> fork with initial bugfixes. >>>> >>>> Among others, we would like to fix the following, changes for these >>>> are already applied and verified in the github fork: >>>> * the official XMLBeans-JAR contains duplicate classes, making it >>>> impossible to use it on Android as the Android build fails due to >>>> this >>>> * cannot use Unicode surogates, thus affecting use of Apache POI in >>>> non-latin-script areas >>>> * Remove W3C and JAVAX classes which are not needed any more since >>>> Java 6 (current Apache POI development is on Java 8) >>>> >>>> >>>> So is there a precedent for something like this? What steps do we >>>> need to make to get an updated version of XMLBeans published? >>> Others might have examples of how it was done in the past. Making a >>> fork >> on e.g. github with a new non-apache name is the simplest way. >>> However if I understand it correct your intention is only to >>> maintain >> XMLbeans for the benefit of POI. That gives you (as I see it) another >> option, you can include the source code in your project and do the >> patches as part of your project. >> >> I think it would need to be in a different package to avoid possible >> confusion with the original. >> And it should be obvious that it is not intended for external use. >> >> e.g. org.apache.poi.internal.xmlbeans >> >>> rgds >>> jan i >>>> >>>> Thanks... Dominik >>>> >>>> On behalf of the Apache POI PMC >>>> >>>> >>>> About Apache POI >>>> ----------------------- >>>> >>>> Apache POI is well-known in the Java field as a library for reading >>>> and writing Microsoft Office file formats, such as Excel, >>>> PowerPoint, Word, Visio, Publisher and Outlook. It supports both >>>> the older (OLE2) and new (OOXML - Office Open XML) formats. >>>> >>>> See https://poi.apache.org/ for more details >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional >> commands, e-mail: dev-h...@poi.apache.org > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional > commands, e-mail: dev-h...@poi.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
