July 2008 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: Confused about infrastructure (SVN, Mailinglist, ...)

by camunda

Okay, found something in that second wiki: http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingFromSource Seems this ( svn co https://svn.jboss.org/repos/jbpm/jbpm3/trunk) is the correct SVN for all future commits in 3.x then? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161959#4161959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161959

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Confused about infrastructure (SVN, Mailinglist, ...)

by camunda

One more: Why there is a second wiki on jbpm.dyndns.org? So which one should be used? The JBoss-Wiki? Or this special wiki? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161956#4161956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161956

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jPDL 4 early feedback

by koen.aers＠jboss.com

As far as the designer is concerned: for the current implementation it is indeed very difficult to add new stock nodes. Hence also the 'quick' implementation using generic nodes for the ESB node. For the future version of the GPD, this limitation should and will be ironed out. Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161955#4161955 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161955

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Confused about infrastructure (SVN, Mailinglist, ...)

by camunda

Hi! I am still confused about what has changed in the infrastructure... I hear a lot about SVN. But my last information was: 3.x will stay in CVS, 4 will go to SVN. IN http://www.jboss.org/jbossjbpm/jpdl_sources/ the CVS is still mentioned. In the forum I didn't find a new SVn URL. Is it CVS for 3.x or SVN? Where is the SVN located then? What about that mailinglist? Why is it there? Will it really be used? I thought, the forum is the main communication channel... About Maven I will ask further as soon I got the right source control URL ;-) Would be nice to get some light in this :-) Thanks Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161954#4161954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161954

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM3 should release lock-step with jPDL4

by camunda

anonymous wrote : Another important point (apart from inter-project dependencies) is management of the workload for the whole team. Hi Thomas, but this isn't the case for the contributers. For me personally I have some backlog of stuff I want to commit but cannot plan in advance when I can do it, since it is "a hobby" and has to fit in spare times coming here and there (but are not planned). Does this schedule mean, that if I have spare time in a code freeze I cannot commit anything? Or do you branch somehow so development on head can go further on? Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161952#4161952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161952

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining a public API for jBPM

by thomas.diesler＠jboss.com

sure, will do http://jira.jboss.org/jira/browse/JBPM-1305 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161773#4161773 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161773

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining a public API for jBPM

by pete.muir＠jboss.org

Thomas, Seam consumes the jbpm API, and it would be great if you could include the methods we use as part of the stable API you are developing. http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/bpm and http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/pageflow is our integration code - ping me if you want to discuss this further offline. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161722#4161722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161722

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM3 should release lock-step with jPDL4

by thomas.diesler＠jboss.com

I aligned the even alpha releases with jBPM3. Another important point (apart from inter-project dependencies) is management of the workload for the whole team. For any given eight week period you have N projects to work on and you can schedule your workload such that everything gets done by a well defined date. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161706#4161706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161706

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Need for database compatibility between jBPM versions

by tom.baeyens＠jboss.com

"thomas.diesler(a)jboss.com" wrote : This is based on my understanding that a process definition is an immutable entity, which is defined in XML. | process definitions can be considered as immutable, correct. "thomas.diesler(a)jboss.com" wrote : | The state of running processes is persisted in the database. For many a reason It cannot be expected that jBPM can be updated for running proccess. there are two types of migration 1) migrating a process instance to a new process definition in the same jBPM installation 2) migrating the complete jBPM database to a new major version (3.x to 4) In the general case, process instance migration is too complex, as you don't know to what extend the new process definition will look like the old one. However, in the majority of use cases, the updates to the process are fairly limited. If we provide a process instance migration that takes into account an optional node-name-mapping, then I think we have covered the 80% of the migrations with 20% of the effort. Migrating the runtime state is doable IMO. The logs and history is always too complex. What I think we definitely should consider is process instance migration from 3.x to 4. Our users *will* have to do this. With our without our help. This is the feedback that we got at jBPM community day. I think that should be definitely feasible with serialization to XML. After the clean shutdown, we should be able to provide a tool that serializes a the complete process instance information to XML and load that XML file in the new DB. IMO, this is mostly a question of resources. "thomas.diesler(a)jboss.com" wrote : If this feature is required we need to see this reflected in the test suite. In other words, as long as there are no automated tests that verify that an update of jBPM from version X to version Y for a non trivial set of running processes - this feature is not there. agreed. "thomas.diesler(a)jboss.com" wrote : | | ProcessEngine.prepareForShutdown() | | | | This will allow processes to terminate, while others cannot start. A user is expected to setup a new instance of jBPM version Y that can receive new process requests. i don't think this is realistic for the complete process instances. think of the legal case taking 3 years to complete and new legislation requiring updates to the process in the meantime. we need some form of process instance migration for that. but a clean shutdown could make sure that all asynchronous messages get processed before the shutdown is completed. that only leaves the timers to be taken into consideration. "thomas.diesler(a)jboss.com" wrote : IFrom that perspective, it is unnecessary and not even desired to provide backwards compatibility for database layout. i agree. backwards compatibility of DB layout is not feasible and not necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161705#4161705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161705

16 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining a public API for jBPM

by thomas.diesler＠jboss.com

Please discuss here Need for database compatibility between jBPM versions http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161691#4161691 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161692#4161692 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161692

16 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev July 2008