Disallow signaling on tokens that are terminated or have active children
by Ronald van Kuijk
Heiko,
I saw that you did a check-in in the new console regarding the subject of
this mail. Good addition, since a fair amount of people had conceptual
problems with this. But wouldn't it be better to (also) add this to the
core? I know it is not in 3.3 so it is needed in the console as well.
Besides that, I thought Tom mentioned once that jBPM 4 will have this afaik,
but maybe 3.3.1 should as well.
Any thoughts?
Ronald
17 years, 11 months
jbpm-3.3.1.GA & jbpm-4.0.0.Alpha1 release cycle
by Thomas Diesler
Hi Folks,
here is the first cut of the set of issues that should get fixed in the
next release cycle (see attached or the link below)
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?mode=hide&requestI...
https://jira.jboss.org/jira/secure/ConfigureReport.jspa?filterid=12311991...
Given that not much will happen after 22-Dec and that we are already 13
days into the release cycle, we will have to compensate for the missing
time by shortening the periods before Jira Freeze and for QA if we want
to have the full length of 20 days of development.
Jira Freeze should be early next week (i.e 20-Nov-2008)
Code Freeze would then be mid December (i.e. 18-Dec-2008)
Attention can be divided among these three areas: jbpm3, jbpm4, gpd/gwt.
I propose that:
* Heiko mainly works on gwt but also assists Alejandro to deal with the
more complicated sybase issues that require direct access to the QA box
* Koen works on the GPD with the goal to support the agreed API constructs
* Alejandro works on the jbpm3 backlog with help from the rest of the team
* Tom mainly works on jbpm4 to provide an implementation of the API and
also helps with the jbpm3 backlog
* Thomas works on porting the code base to the SOA branch, helps with
the API and also gets involved in the jbpm3 backlog
There are currently 66 issues to deal with. Please have a look and
create, update, resolve, assign appropriately.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
BPM Product Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 11 months
bpm think tank
by Tom Baeyens
Hi,
Here's my short report on the BPM Think Thank last tuesday and wednesday.
Great networking opportunities. Small, but relevant crowd. Lots of time to hang
around with Jan Baan (ex Baan, now Cordys), Phil Gilbert (Lombardi), Derek Miers
(loudmouth with way too much influence compared to his knowledge:), John Pyke (ex
Staffware, now Cordys) and some tibco guys.
It's another kind of world then where we typically live in. It was all business
level talks. Normally I shy away from this world, but it was a really good
experience to be soaked in it for 2 full days. I now know a lot better what world
people like Burr live in. And I much better understand their needs. Whether we can
satisfy those with the resources we have in the short term is of course another topic :-)
Especially Phil Gilbert made a very big impression on me. He gave what could have
been a historic visionary speach. "This technology is going to change the whole
industry"-type of talk. But then doing this in front of only 35 people is kind a
painful. I already saw some indications before that this conference was declining,
but this talk made the confrontation could not have been bigger.
The roundtables still had the flavour of the original idea around the think tank:
inspiring people, broad topics always lead to new insights. This was great. I even
got some very concrete new ideas that we'll apply during the development of jBPM 4.
One downside was that the conference didn't have the ambition any more to come out
with new positions on what is to be relevant in the industry. All the relevant
discussion is currently going on in BPMN 2.0 and ideally that discussion would have
been held in public. The crowd was certainly small and knowledgeable enough to
discuss these topics.
IBM and SAP weren't present. I assume that this is a consequence of the previous
paragraph, but it might also be the other way round.
Second downside was that a lot of preaching to the choir happened.
Overall it was still time spend worth while. The networking, roundtables and getting
soaked in business requirements made it great.
--
regards, tom.
17 years, 11 months
