irmis-devel Mailing List for IRMIS

Hi all,

 

Big release with a few changes that break compatibility.

 

First of all: from now on IRMIS will come in different modules. There
are several reasons behind this push:

* different parts of IRMIS are at a very different level of maturity, so
it makes it impossible to have a non-alpha release for the whole
project. This will allow to tag stable the parts that are indeed so.

* one may be interested in only a piece of IRMIS, and now he/she will be
able to pick and choose what to get

* it will be easier to for different maintainer to contribute separate
modules, as the release schedule will be different for each, and so can
be the choice of underlying technologies.

 

So, each module will come in a separate tarball. All tarballs can be
installed in the same directory (can be put one on the other).

 

As of today, I will be responsible for only the IRMIS Components module.
The IRMIS Lattice module is released "as is" and I will not support it
in the near future (I'd rather concentrate to push IRMIS Components to a
final release and have other commitments in other projects).

 

For someone upgrading, there are a few key compatibility breaking items
you have to keep in mind:

* Only Glassfish 3.x will be supported going forward (I am starting to
use EJBs in a web container, which is not supported in the old
distributions) 

* The database script will move the IRMIS components tables to
irmis3-components, so make sure your db authorization is setup correctly

* The JDBC resource is renamed from irmisDB to irmis3-components, so the
glassfish setup needs to be updated

* All classes in the IRMIS Components API have moved

That should be all.

 

As for new functionality:

* attachment crawler: bundled a script that can crawl a directory and
add component type/component properties based on the content of the
directory. This allows to have a webdav share in which one can drop
files (manuals, reports, images, ...) that relate either to a component
type or to a specific instance and a property with a link to the
corresponding document will appear in the database.

* Better support for keyboard shortcuts in applications

* Reviewed Component Type Editor and Component Inventory to have a more
consistent UI

* Few bug fixes and addition to the Component Type Editor (highlights
which types have changes, new component type always shown regardless of
filter, ...)

* Service now keeps better usage information, including: a directory in
the home directory (of the user running the service) that will contain
each xml transaction and each client application log; a database table
with performance/usage data.

 

Full log at:

https://sourceforge.net/apps/trac/irmis/query?status=closed&group=compon
ent&order=summary&col=id&col=summary&col=owner&col=type&col=priority&col
=component&col=version&milestone=components-3.0.24-alpha%20(r1470)

 

Gabriele

Hi all,

 

Just a heads up: next release will require glassfish 3.x.

 

I am reorganizing the code on the server side, and I am making use of
EJBs to better break up the code. Glassfish 3.x allows EJBs to be
defined inside a web module, without having to define an extra separate
archive.

 

Gabriele