Binary or source?
Most users will want to download a binary release of XMLBeans. If you're interested in contributing or like to live on the bleeding edge, you may want to compile the source for yourself.
XMLBeans requires JDK 1.6. Last version to work with JDK 1.4 is 2.6.0 which has not been updated in a while.
Once you've downloaded the distribution or checked out the source, you should:
28 October 2018 - XMLBeans 3.0.2 available
The Apache POI team is pleased to announce the release of XMLBeans 3.0.2. Featured are a handful of bug fixes.
A summary of changes is available in the Release Notes. A full list of changes is available in the change log or the corresponding Jira ticket. People interested should also follow the dev list to track progress.
The XMLBeans source release as well as the pre-built binary deployment packages are listed below. Pre-built versions are available in the central Maven repository under Group ID "org.apache.xmlbeans" and Version "3.0.2".
SHA256 checksum: 520866defedb0251713573d4ceaea33601d33b575039cdea1f74d53b946a7238
SHA512 checksum: 3819f6b108e564d8393a28b289aa9141c62f019c883f9a74483a96f36ea1acf3fed979055f13e2b33edd8f3d4518576a171902ba3396ced3276f38783be9cb5a
SHA256 checksum: 8aaef24b17e4d8a64ffedaf0a998291fba1ff983a93c3be030fcdf8470cfee0f
SHA512 checksum: 12c9827901cb4eff1c7665a426792af7fe7a7a9d349b3fc3e2054e6be79ce93fa47ea879bb1fe96f098c87f349e04d9979755484bc2eac52c525a9a75da58795
SHA256 checksum: 4869678e4de642eec283f35d66e7d4078d1d3024bde2ae677cf027a307bf427f
SHA512 checksum: 2f109fe4e65ed220d257f4372290925faf996e31d8c5397615067cda456b0fefaa9d4283a7c74b40059c4d09c569c101837c61ba6160f14f42e3aede0f052f9a
SHA256 checksum: a10bb823b147bc466f4947188f9397ca2f787ef7155b002b306c451fd5468c3c
SHA512 checksum: c32e603fb07c3352b9fd13f592ec57ca7010aa272d3e6d796a78e7832de91bad8f3b77587769396b777a43d12820774c9ea995fbd07daa386c5aab4ca72a7448
It is essential that you verify the integrity of the downloaded files using the PGP and SHA signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases. This page provides detailed instructions which you can use for POI artifacts.
The PGP signatures can be verified using PGP or GPG. First download the KEYS file as well as the .asc signature files for the relevant release packages. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures.
As an example:
% pgpk -a KEYS % pgpv xmlbeans-X.Y.Z.jar.asc
% pgp -ka KEYS % pgp xmlbeans-X.Y.Z.jar.asc
% gpg --import KEYS % gpg --verify xmlbeans-X.Y.Z.jar.asc xmlbeans-X.Y.Z.jar
Sample verification of xmlbeans-bin-3.0.2-20181028.tgz
% gpg --import KEYS gpg: key 38DAC8E212DAE9BE: "Glen Stampoultzis <glens at apache.org>" not changed gpg: key F5C260164CEED75F: 32 duplicate signatures removed gpg: key F5C260164CEED75F: 108 signatures not checked due to missing keys gpg: key F5C260164CEED75F: 1 signature reordered gpg: key F5C260164CEED75F: "Nick Burch <nick at gagravarr.org>" not changed gpg: key 8AAF88D6D84E41AE: 1 duplicate signature removed ... % gpg --verify xmlbeans-bin-3.0.2-20181028.tgz.asc gpg: assuming signed data in 'xmlbeans-bin-3.0.2-20181028.tgz' gpg: Signature made Tue 23 Oct 21:51:09 2018 IST gpg: using RSA key 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13 gpg: Good signature from "PJ Fanning (http://www.apache.org/) <fanningpj at apache.org>" [ultimate] gpg: aka "PJ Fanning <fanningpj at yahoo.com>" [ultimate] % gpg --fingerprint 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13 pub rsa2048 2018-05-02 [SC] [expires: 2020-05-01] 6BA4 DA8B 1C88 A494 28A2 9C3D 0C69 C1EF 4118 1E13 uid [ultimate] PJ Fanning (http://www.apache.org/) <fanningpj at apache.org> uid [ultimate] PJ Fanning <fanningpj at yahoo.com> sub rsa2048 2018-05-02 [E] [expires: 2020-05-01]
Using XPath/XQuery requires an additional download of saxonb9-0-0-4j.zip and placing on the classpath of the files saxon9.jar and saxon9-dom.jar that it contains. The zip is available here. We cannot distribute this zip in a binary distribution due to licensing issues.
There are a few ways to get the XMLBeans source code. You can download the source for a particular release, browse the source using ViewSVN/CVS, or check the source out from SVN.
Source via ViewSVN/CVS
You can browse the XMLBeans source via ViewSVN/CVS
Source via SVN checkout
In SVN, you will find the actively developed version of XMLBeans under "trunk". Under "tags" there are a number of tags corresponding to the released versions of XMLBeans, as an alternative to downloading the source distribution (there are additional things like tests, which are not included in the distribution as well).
If you have SVN installed on your machine you can issue the following commands to get XMLBeans source:
# get the version of XMLBeans under development svn co https://svn.apache.org/repos/asf/xmlbeans/trunk/ xmlbeans # or, just get the samples for XMLBeans svn co https://svn.apache.org/repos/asf/xmlbeans/trunk/samples/ xmlbeans-samples
Source via Git
Please see the Git at Apache page for details. As of this writing the Git acess is read-only.
Git Clone URL: git://git.apache.org/xmlbeans.git
Http Clone URL: http://git.apache.org/xmlbeans.git
XMLBeans requires that you have Ant installed (1.6.5 works fine).
After the steps above you should see an "xmlbeans" directory (or you can choose a different name in the previous step, of course):
cd xmlbeans\ xbeanenv ant
This will create a build directory containing the executables. The xbean.jar is in the xmlbeans\ar directory. Try ant -projecthelp to see other build options.
Building on Unix or Cygwin is essentially the same as for Windows:
cd xmlbeans/ ./xbeanenv.sh ant