jinFORM / News: Recent posts

http://ddossot.blogspot.com/2006/10/16-months-iteration.html

Thanks to its partial support of XForms 1.1, Orbeon Presentation Server (OPS, cf. http://www.orbeon.com/\) will become the rendering engine of jinFORM.

The XSLs commited to CVS today support XForms 1.1 insertion and deletion of repeatable elements in a very smooth way (OPS 3.5 must be used, not an earlier version).

Next steps for jinFORM:

- clean the code base of Chiba related stuff,
- make jinFORM a fully stateless engine (as all the state will be handled by OPS),
- integrate jinFORM in OPS (with dedicated XML Pipeline and portlet configurations),
- add submission handling features in jinFORM.

While waiting for either a browser plugin that support XForms 1.1 or a rendering engine that does it (Chiba? OPS?), you can give a little try to jinFORM like this:

- configure the folder location that contains your Infopath forms,

- deploy the war on your application server,

- if your logger is on DEBUG, you should see the names of the forms jinFORM has correctly loaded,

- ask an XForm rendering of a particular form with this kind of contruct:... read more

XForms 1.1 will bring to the insert action a feature that is really missing in 1.0, i.e. the ability to copy from a specific instance location.

This will allow jinFORM to use Infopath template as the source of tree fragments for the repeating sections (instead of duplicating the latest fragment of a reapeat block, which is cumbersome to death).

see. http://www.w3.org/TR/xforms11/#insertAndDelete-action

jinFORM is not dead, simply on standby, waiting for Chiba to knock-off some blocking bugs.

To tease you a little, some screenshots have been uploaded. You can easily run them by checking the code out of CVS HEAD.

jinFORM has been migrated from MyEclipseIDE to WTP (from Callisto) in order to allow development on a free (as in beer) platform.