October 2009 - jbpm-dev - Jboss List Archives

[jBPM Development] - Re: parser for each jpdl release

by sebastian.s

Thank you very much for the update, Tom. From what I can say with my limited knowledge to me this sounds like a reasonable way to account for backwards comptability while allowing enhancements for jPDL which are necessary. By the way: Did anybody manage to look in to this issue here? https://jira.jboss.org/jira/browse/JBPM-2537 I'd love to here your opinion on this. To me it is a priority issue for the next release because the bug prevents you from using a lot of the features and the power jBPM offers. Thanks for your efforts and keep up the good work! :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258281#4258281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258281

15 years, 1 month

1
0
0 / 0

[jBPM Development] - parser for each jpdl release

by tom.baeyens＠jboss.com

Just wanted to give you guys an early update. I encountered a significant unexpected issue. It was related to updating the classloading. Due to updates in classloading, I came to change the jPDL parsing. the occasion here is minor: i want to refactor the expr attribute to object-expr in user code declarations. but the implications seem to be hard. Then I realized that the old (v4.0 and v4.1) process files are in the DB. For users that want to upgrade, this parser change potentially breaks existing installations in a non-recoverable manner as the new parser might not parse the existing deployed process definitions in the same way. (the XML is stored in the DB) The solution I'm currently targetting for is pretty involved: * Each release will have its own namespace URI. (i forgot this in 4.1. so release 4.1 still contains the 4.0 namespace) * Each version of jPDL will add it's own parser. All old parsers will be kept in the codebase as well. So that jBPM can still deploy older process versions that are deployed and stored in the DB. * Each time when a process is deployed, the optional namespace declaration is checked. If not present, the jPDL version deployer will add the namespace and re-serialize the process xml in the deployment that will be stored in the DB. That way the deployed process in the DB will contain the version explicitly of the process XML. And later, each time when jBPM parses that process file after a reboot, then the correct parser associated with that jPDL version can be used. * So users should still be able to deploy e.g. a jPDL process in version 4.3 XML in jBPM version 4.7 * Migration tool will apply the namespace check and add the 4.0 namespace. * For testing, I think it is sufficient to use a single test suite. When we embark on a new version, the full test suite will be using the new version's parser. The old version's parser will not be changed any more. So that is why I think it is ok if it is not tested any more. from a first glance, this seens to be the only way in which we can support decent backwards compatibility and still allow us to evolve the language. thoughts ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258277#4258277 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258277

15 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by kukeltje

afaik the forms engine does not pas the actor to the bpm engine/core yet. There is a jira issue for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258231#4258231 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258231

15 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by alexf83

It does make sense and that was what I was afraid of. Is there at least a way to know which user started a process? (so that we could use a java node after the start, to check who started the process and in case cancel it) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258186#4258186 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258186

15 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by heiko.braun＠jboss.com

In that case you'd need to discuss such an authentication schema first the jBPM core team first, because if the engine doesn't have it build in, the console cannot make that up. It needs to be metadata associated with the process definition in the first place. Does that make sense? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258175#4258175 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258175

15 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by alexf83

First of all thank you for your kind answer. We would like each user to log in (in the console) and be able to view and start only certain processes (the business processes he should have the right to start). A per group/per user authorization mechanism would be really great for our needs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258170#4258170 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258170

15 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by heiko.braun＠jboss.com

it's currently not possible. we don't have any kind of authorization scheme in the console yet. but if you outline your use case further we can put it on the roadmap. Do you want restrict it to certain process definitions only, or in general? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258168#4258168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258168

15 years, 1 month

1
0
0 / 0

[jBPM Development] - (JBPM 4.1) Console process definition list

by alexf83

Hi, we are currently trying to understand if it's possible to limit the visibility of some process definitions (and consequently inhibit the ability to start the related process instances) only to certain users (in the JBoss web console process definition list). Any help you could offer would be greatly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258139#4258139 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258139

15 years, 1 month

1
0
0 / 0

ProcessEngine not waiting on JbpmDS in 4.2.3

by Ronald van Kuijk

Does anybody have an idea? http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257977#4257977 Especially read the 3 page Is it possible at all? Maybe some JBoss (AS) dev can have a quick look. Would be nice if this would be supported. Ronald

15 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev October 2009