NeXML: a UML-driven XML Schema with Java bindings for the NeXus format
Served: Mon Jan 05 20:24:27 PST 2009
NeXus Home ||  NeXML home |  MetaDTD(XML)->XMLschema(XSD) |  XSD->EMF(Java) |  XSD->UML ||  MetaDTD->NeXusBeans(Java) |  NeXusBeans->UML |  MetaDTD->HTML ||  Thanks

NeXusBeans: beta release including new NeXusBeans Java generator tool

This is the beta release of NeXusBeans, as developed by Dr Darren Kelly from 2005 - 2007 for the Bragg Institute, ANSTO (under project management of NIAC member Dr Nick Hauser, and initially within the Data Analysis Team lead by Paul Hathaway).

Java NeXusBeans bring true Java component engineering, UML graphical engineering, and XML Schema validation (under development) to the NeXus neutron science data format. A prototype of the system was presented to to the NeXus International Advisory Committee (NIAC) in Feb 2006 at Grenoble, France.

The beta release will only be "supported" within the Bragg Institute at ANSTO for trials, and may be subject to frequent change (with post-beta versioning). The planned 1.0 release will be supported by the Bragg Institute for the benefit of the wider NeXus community.

In order to use this release of NeXusBeans you will need:

You may also like to inspect:

Notes on this release

The NeXusBeans provided with this release:

The base package is only partially documented, as there are still many issues concerning handling of dimensioned data. The UML overview of the base package is out-of-date, yet nevertheless quite informative.

The metamodel-driven Java forward-engineering system is extensively documented in UML, and will be released as a separate educational demonstration project for the Magicdraw UML tool.

How to generate fresh NeXusBeans using the provided tool

The class NeXusXmlTemplateToNeXusBean_ generates NeXusBeans from remote NeXus SVN repository of XML Meta-DTD templates to a project base directory of your choice. The base directory for project output must already exist, and so must all directories under it with the following deliberately fixed structure reflecting the enforced Bragg Institute package structure:

$base/src/au/gov/ansto/bragg/nexus/auto

The current policy is to deliberately NOT create the directory structure for you, automatically in the tool, you must create it by hand first !

To execute from the command line use:

java au.gov.ansto.bragg.nexus.tool.NeXusXmlTemplateToNeXusBean_ $base

Where $base is something like:

/home/somebody/project/nexus/

You must have the following libraries in your classpath (or versioned equivalents):

In order to compile and use the generated NeXusBeans you will then need only:

Please BEWARE that if you have the distributed NeXusBeans in au.gov.ansto.bragg.nexus.auto AND your newly generated and compiled NeXusBeans in au.gov.ansto.bragg.nexus.auto with the same packaging on the same classpath you WILL get a strange clash.

NeXus Home ||  NeXML home |  MetaDTD(XML)->XMLschema(XSD) |  XSD->EMF(Java) |  XSD->UML ||  MetaDTD->NeXusBeans(Java) |  NeXusBeans->UML |  MetaDTD->HTML ||  Thanks
This dynamic web site and software © 2008 Darren R C Kelly. All rights reserved.
Content streamed from the NeXus home site is available under the GNU Free Documentation License 1.2.
Developer: Darren Kelly.    Project site hosted by: webel.com.au