[Design of JBoss jBPM] - Re: New console snapshot published, Task Forms included
by SNy
OK, while the dynamic approach ain't working, I'll workaround by hardcoding the template options (it's a mockup, anyway, so the main aim is to get it working ASAP).
As far as suggesting a solution, I guess it depends on wether or not the outcome (as in: result of the action) is actually useful in subsequent process steps. If not, it probably should not be introduced into the process at all. I don't have sufficient insight into the ways of jBPM yet and therefore don't know about side-effects.
Another idea would be to have the default context stuff that you put into the form as an independent element/namespace 'ctx' or somesuch, containing everything that would go there (it would be nice, BTW, to have a list of the items one can use, I looked in vain for the activity name). 'ctx' should then be regarded as reserved in some way and not be taken from the process.
Or, maybe it would be even better to encapsulate the process variables in an element/namespace of their own, maybe named 'process'?
Just my 2 cent,
regards,
Marko
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245829#4245829
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245829
16 years, 7 months
Party pooper? Back to work...
by Ronald van Kuijk
Guys,
I hate to be the one to bring everybody back to reality after the
release, but I would hate it to see improvements that were made over the
last year slip again. Now I'm not talking about improvements in the
engine which were for the outside mostly invisible. No, I'm talking
about the much improved use of directly visible things like using the
jira, wiki etc. Thomas did a great job in that regard. Deutsche
Gründlichkeit is what we miss
Now, I'd love to take that upon me, but my free time is becomming
limited again and I think it should belong to someone directly in the
project. Why do I bring this up now?
http://www.jboss.org/community/docs/DOC-13217 contains several things.
The most important being
September 1st: jBPM-4.1
*Milestone*
*Date*
Jira Freeze July 22th
Code freeze August 18th
*Release* *September 1st*
July 22th being yesterday. So this means the issue list for 4.1 is
frozen now since I assume everybody had these dates in mind. If that is
not the case, I'd like you all to go over your issues and see if they
can be fixed before august 18th. If not, assign them to the next
release, so expectations on the outside are realistic!!!
In addition, I'd like this 'roadmap' page to be either kept up to date
or for the most part just contain links to the jira. The way the details
of features are mentioned there do not add anything to the fact that you
can have these kinds of reports from Jira. e.g. by using labels if we do
not want to have to many components. Going over issues that were
reported lately against 4.0 is not wrong either, there might be some
that can be fixed quickly and give a positive impression of the project.
So come on and do your housecleaning duties by obeying this order or
next time you guys all drink Heineken a full evening here in Utrecht.
Ronald
16 years, 7 months