Re: [jbpm-dev] Removed Timer/autosave in Revision 4006?
by Ronald van Kuijk
Might be related to
https://jira.jboss.org/jira/browse/JBPM-2036
(somebody did not make a test for 1015? :-))
2009/2/27 Bernd Rücker <bernd.ruecker(a)camunda.com>
> Hi Alex!
>
>
>
> With Revision 4006 you removed the fix for
> https://jira.jboss.org/jira/browse/JBPM-1015 from the Timer class,
> basically this code:
>
>
>
> public boolean execute(JbpmContext jbpmContext) throws Exception {
>
> // add processInstance to autoSave field (For details refer to
>
> // https://jira.jboss.org/jira/browse/JBPM-1015)
>
> jbpmContext.addAutoSaveToken(token);
>
>
>
>
>
> Was this by accident? Or what rational was behind this? Can I re-include
> it?
>
>
>
> Because now, Bug 1015 would occur again with jbpm 3.2.6…
>
>
>
> Thanks
>
> Bernd
>
>
>
> EJB-3-Buch: http://www.ejbbuch.de/
>
> Unsere Seminare: http://www.camunda.com/seminare/
>
> Blog: www.bpm-guide.de
>
> ---------------------------------------------
>
> camunda services GmbH - The Business Process Company
>
> Werastraße 18 - 70182 Stuttgart
>
> www.camunda.com - info(a)camunda.com
>
> ---------------------------------------------
>
> Bernd Rücker
>
> Geschäftsführer
>
> Telefon +49 711 3278645
>
> Mobil +49 171 1473461
>
> bernd.ruecker(a)camunda.com
>
> ---------------------------------------------
>
> Amtsgericht Charlottenburg: HRB 113230 B
>
> Geschäftsführer: Jakob Freund, Bernd Rücker
>
> ---------------------------------------------
>
>
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
>
15 years, 9 months
Re: remaining 3.2.6 issues
by Thomas Diesler
Yes, after talking with Julian and Trevor we agreed to release and use
3.2.5.SP2
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?projectId=10052&style...
Burr Sutter wrote:
> I concur.
>
> Did we resolve which version of jBPM makes it into SOA-P 4.3 CP01?
>
> You know the backward compatible with the 3.2.2 DB issue... :-)
>
>
>
> Alejandro Guizar wrote:
>> Hey Thomas,
>>
>> (Burr in CC)
>>
>> JBPM-1952: use JMS instead of DBMS for the store of jobs.
>>
>> * Current status: JMS is already used in the enterprise jbpm.cfg.xml.
>> * Proposed resolution: add test case to enterprise module.
>>
>> JBPM-1953: select the lock strategy in jbpm.cfg.xml.
>>
>> * Current status: request is not feasible. Pessimistic locking would
>> require a separate set of mapping files with version columns removed.
>> Furthermore, as discussed with Burr, if JMS is used then pessimistic
>> locking becomes unnecessary.
>> * Proposed resolution: reject
>>
>> Let me know if you agree with the proposed resolutions so I can close
>> the issues in JIRA.
>>
>> -Alejandro
>>
>> El jue, 26-02-2009 a las 12:26 +0100, Thomas Diesler escribió:
>>
>>> Hi Alejandro,
>>>
>>> could you please give me a quick update on
>>>
>>> https://jira.jboss.org/jira/browse/JBPM-1952
>>> https://jira.jboss.org/jira/browse/JBPM-1953
>>>
>>> We have the release scheduled for Sun,1-Mar-2009. Will you be able to
>>> resolve these in time?
>>>
>>> cheers
>>> -thomas
>>>
>>
>>
15 years, 9 months
Rolled back changes
by Bernd Rücker
Hi Thomas,
could you please send a short mail in future if you rollback changes?
Somehow the notification in JIRA doesnt work for me, so I just saw this
today by accident
BTW: Is there a way to get notified about SVN commits?
Cheers
Bernd
15 years, 9 months
Re: remaining 3.2.6 issues
by Alejandro Guizar
That must be 3.2.5.SP2.
El jue, 26-02-2009 a las 16:33 -0500, Burr Sutter escribió:
> I concur.
>
> Did we resolve which version of jBPM makes it into SOA-P 4.3 CP01?
>
> You know the backward compatible with the 3.2.2 DB issue... :-)
>
>
>
> Alejandro Guizar wrote:
> > Hey Thomas,
> >
> > (Burr in CC)
> >
> > JBPM-1952: use JMS instead of DBMS for the store of jobs.
> >
> > * Current status: JMS is already used in the enterprise jbpm.cfg.xml.
> > * Proposed resolution: add test case to enterprise module.
> >
> > JBPM-1953: select the lock strategy in jbpm.cfg.xml.
> >
> > * Current status: request is not feasible. Pessimistic locking would
> > require a separate set of mapping files with version columns removed.
> > Furthermore, as discussed with Burr, if JMS is used then pessimistic
> > locking becomes unnecessary.
> > * Proposed resolution: reject
> >
> > Let me know if you agree with the proposed resolutions so I can close
> > the issues in JIRA.
> >
> > -Alejandro
> >
> > El jue, 26-02-2009 a las 12:26 +0100, Thomas Diesler escribió:
> >
> > > Hi Alejandro,
> > >
> > > could you please give me a quick update on
> > >
> > > https://jira.jboss.org/jira/browse/JBPM-1952
> > > https://jira.jboss.org/jira/browse/JBPM-1953
> > >
> > > We have the release scheduled for Sun,1-Mar-2009. Will you be able to
> > > resolve these in time?
> > >
> > > cheers
> > > -thomas
> > >
> >
> >
15 years, 9 months
[Design of JBoss jBPM] - Re: oryx and jbpm
by eikish
Ronalds description of the XForms editors is right on the money. Our own form editor is built from the perspective of an end user not a developer.
However when we edit "process" forms which basically are jbpm tasks the only added complexity is that the developer must bind process/task variables to the inputs. But everything is done visually so that's not hard to do. We haven't released it to other developers other than our partners yet because we want to improve it substantially but it's used in production already.
Just for fun here are some screenshots:
The list of deployed jBPM processes and their "human" tasks
[img]http://www.idega.is/content/files/public/formbuilder/80.png[/img]
One jBPM process opened (in that particular version) and we see the editable tasks (forms are also versioned so we can change old running tasks and variables)
[img]http://www.idega.is/content/files/public/formbuilder/81.png[/img]
"Start task" in the design mode (also have source and preview).
On the right are the used and unused variables from jbpm.
[img]http://www.idega.is/content/files/public/formbuilder/83.png[/img]
You can have sections as well
[img]http://www.idega.is/content/files/public/formbuilder/84.png[/img]
Binding a variable and setting its access attribute (changing the definition and running process instances).
[img]http://www.idega.is/content/files/public/formbuilder/79.png[/img]
Final form displayed in chiba (the css is of course customisable). "Custom" component at the buttom (done in source view)
[img]http://www.idega.is/content/files/public/formbuilder/87.png[/img]
Lastly here what our "task list" looks like for one of our clients (viewed as a case handler). This mixes it all together: roles supply the tasks from jbpm (custom actor resolution), we make documents out of everything (read only xforms or generate pdf), the system auto attaches emails related to the case, we support eSignatures and we access control the contacts. The handlers can access control everything to different roles:
[img]http://www.idega.is/content/files/public/formbuilder/case.png[/img]
Our reason for doing an Oryx extension is so we can visually reuse our reusable (sub)processes that we are using all the time in new processes for clients. As well as to be able to control some metadata about the process for example if a task should become a document or not and if it is signable or not. We then want to automatically jump to the xforms editor while developing processes to make it faster to develop solutions.
We would be happy to work on a jboss hosted extension of Oryx. So go ahead and set it up. We have planned to start in march/april on it.
A side note about the forms:
We are a little dependant on Chiba at the moment but in the future I can see supporting other "renderers" like this new Google project:
http://code.google.com/p/ubiquity-xforms/
Especially because Chiba is heavy on the memory resources in the current production version.
Cheers
Eiki, Idega.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213450#4213450
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213450
15 years, 9 months
