In the current console, they the forms work when you give them the name of a task and put them in the 'root' of your process deployment. How they work internally can be seen in the example forms.
Retrieval is done in the console. Look in the gwt-console forum on some hints how to use/extend/replace the form implementation (ftl) with something else.
${form.action} to my knowledge is a specifically for the way the ftl forms work. If you have your own tapestry implementation, that would work differently. The form mechanism is now more loosly coupled to the console
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242540#4242540
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242540
Hi all,
I'm currently integrating jBPM4 with a tapestry 4.1.5 based web application. I've seen that there are some example task forms (.ftl files) in the src/test/resources directory of the jBPM4 trunk, but I couldn't find any test cases or documentation of the task forms that would explain how they are inteded to be used. The only thing I found is the post at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155048, but it doesn't explain how to actually deploy the templates and how to retrieve instances of the forms in a web application. Also, the ${form.action} expression is a bit of a mystery to me. Is this a process variable as we know it from jpdl files?
Any hints would be appreciated, thanks in advance! Cheers, Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242458#4242458
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242458
wow... please... a little patience ;-). This is all free (as in beer) time of others. You ask for progress in less than 9 hours from Shekarv's posting AND a little over 9 hours from your original posting. In between you already had two replies. Most would be jealous.
You could also have a look at the foreach forkhandler in jBPM 3 that is in the wiki. Yes it is for jBPM 3, but some concepts are the same. And maybe the implementation of the taskactivity in th source of jBPM 4.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242436#4242436
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242436
