[jbpm-dev] [Design of JBoss jBPM] - Re: oryx and jbpm

[eikish]

Hi, I'm that "Eiki" :)

We are also using Chiba for our display needs (modified a little) but we have already a working but not polished XForms browser based editor we developed in house and we connect that to JBPM. We can for example see all tasks in a process version as xforms and edit them even for running processes (older versions) and add and remove variables (set access (read,write,required)) and easily map them to inputs. This is part of our CeSM platform (Customer eServices Management , a new buzzword you heard it here first :p )

Unlike the Orbeon editor ours isn't itself based on xforms just web2.0 magic and right now it's closed source although we are planning to make our platform available for other developers and are open to suggestions ;) The oryx xforms editor is a little strange to me as well as many of the other editors out there. It seems that developers are mostly creating visual XForms syntax editors but not form editors that use XForms underneath if you know what I mean....anyway that's off topic
 
About Oryx, it's very well made but I agree with kukeltje the built in repository and even openid support is something we probably won't use because we already have our own authentication and repo. Also we want to build a jpdl designer with handy extensions for our custom actionhandlers to make it truly possible for a newbie (non programmer) to design and test a complete process.

The requirements in our case in other words are being able to draw and export the xml. But when we have that we will integrate it with our form designer so we can jump right to a task and edit it.

Looking at the JPDL4 editor (only seen the alpha1) I see jboss is taking the road of integrating the positioning of the elements into the xml instead of the gpd.xml file. This is a smart move in my view and will make it easier to create designers/exporters for jpdl. I think with Oryx this strategy would be best as well but I'm worried about backward compatability. We are using jBPM 3.3 and don't see that v.4 will be out any time soon so I need to make sure we build (or you as well?) a jpdl extension to oryx that will work on jBPM 3.3 as well...

Will JPDL4 work on 3.3?



cheers
Eirikur Hrafnsson, eiki at idega.com
Chief Software Engineer
Idega Software
http://www.idega.com



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210712#4210712

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210712