Skip to content

Releases: floscher/jGridShift

Version 2.1.0 (JOSM flavour)

21 Jun 19:21
v2.1.0-josm
c2eb8d2

Choose a tag to compare

Same as version 2.1.0, but modified for the use with JOSM. The functionality is cut down to only the necessary.

Version 2.1.0

21 Jun 19:15
v2.1.0
088ac6a

Choose a tag to compare

  • code style has been improved (credit to the JOSM-developers)
  • improved reading from input streams
  • added first unit test for the new functionality
  • use Gradle wrapper 2.4 for building

Version 2.0.0 (JOSM flavour)

05 May 13:44
v2.0.0-josm
aaba328

Choose a tag to compare

Version 2.0.0-josm

The project has been modified for use with JOSM.

Version 2.0.0

05 May 12:56
v2.0.0
c98db26

Choose a tag to compare

Several bugs have been fixed and the API changed (classes are now prefixed with NTv2).

Version 1.0.1

05 May 09:16
v1.0.1
32110ab

Choose a tag to compare

jGridShift has been restructured and is now built with Gradle.

jGridShift 1.0

04 May 14:53

Choose a tag to compare

This release contains no significant changes to the core API.
A J2EE JCA adapter has been added, along with a web service sample app.

The contents are:

  • an API only jar
  • a JCA adapter rar with a sample service descriptor for JBoss
  • a J2EE ear including a sample deployment descriptor for JBoss
  • a GUI sample tool packaged in an executable jar.
  • full source
  • core API, JCA and samples released under the GNU
    Lesser General Public License.

The API jar can used in any application and has no dependencies.

The GUI tool is a Swing app and the executable jar contains all the classes
needed. Just run the jar and tell it where your grid shift binary is
(refer to http://jgridshift.sourceforge.net for info on where to get
gridshift binaries).

The JCA adapter contains the resource adapter xml, but needs a service
descriptor to be deployable. A sample for JBoss is included. Just edit
the jgridshift-service.xml to identify where your gridshift binary is,
drop the xml file and the jgridshift.rar into your deployment directory
and away you go. Refer to the SessionBean sample for how you acquire
and use a JCA connection.

The web service sample is pretty specific to JBoss. It requires JBoss-Net,
which is not part of the default server (in 3.2 at least). The easiest
option is to make the full server the default. The JCA adapter must be
deployed, then just drop the ear into your deployment directory.