This content has been marked as final.
Show 3 replies
-
1. Re: jbpm 3.1 Monitoring
mennen Feb 16, 2006 3:34 AM (in response to mennen)Forgot to add that any user can delete any process instance according to the actual setting.. isn't that a little dangerous?
Thanks in advance, -
2. Re: jbpm 3.1 Monitoring
hoogenbj Feb 16, 2006 4:02 AM (in response to mennen)Hi there
I think it should not be jBPM's responsibility to decide who should and should do whatever. jBPM is the engine, or the library. Your application should take care of all that stuff.
In my case, jBPM is my workflow and pageflow engine, and I have an extensive implementation of J2EE roles and permission sets guarding all kinds of access.
That is how it should be, I think.
Regards
Johan H -
3. Re: jbpm 3.1 Monitoring
koen.aers Feb 16, 2006 4:50 AM (in response to mennen)Totally right Johan!
Regards,
Koen