[Design of JBoss jBPM] - Re: Status / Documentation of gwt-console & report-server
by heiko.braun@jboss.com
That's right, the docs are still missing. Some of the functionality is only available in particular situations, i.e:
- depending on the process itself (i.e task forms)
- the type & contents of process deployments (i.e. process image)
- plugin functionality (forms)
Before you go ahead a d discuss UI elements, it would make more sense to think about meaningful constraints, that can be applied to process deployments. Currently the console has to cope with a lot of unknowns, which derive from the "everything possible, but nothing mandatory" style of coding that jbpm4 reflects.
Up to now I tried to include functionality in the console that is applicable to most of the use cases, but of course there is much more do add. However if it only applies to a small percentage of use cases and furthermore isn't even constrained to a certain degree we cannot simply add it.
I'll give you an example:
Process variable inspection is one of those cases. There is currently no constraint on variables whatsoever. The "hashmap" style of design allows for everything and nothing at the same time. Of course it would be useful have that feature in the console, but without any type descriptions associated with the process it will only work in particular situations and break in others.
I can list plenty of other features that have been hold back, because the core codebase doesn't allow for reliable hook into runtime inspection.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238129#4238129
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238129
15 years, 5 months
[Design of JBoss jBPM] - Extending jBPM, Plugging in custom IdentityService implement
by shekharv
I was trying to identify how one could extend the current jbpm identity implementation or plugin one's own IdentityServiceImpl. I dug around in the code a bit and noticed that there are a couple of bindings.xml files that really are responsible for configuring what Implementation classes are responsible for each of the high level Service interfaces that we have in jBPM. TaskService, ExecutionService, etc.
jbpm.wire.bindings.xml
jbpm.user.bindings.xml
Had a few points to note about the approach mentioned above,
1.) Is this the intent of the designers of the system and the api developers to provide extension points into the engine in this manner?
2.) There is also the jbpm.user.bindings.xml. From the looks of how the bindings are being stored(as a list) it does not seem that any bindings that we add to this file would override the bindings in the jbpm.wire.bindings.xml. So it seems to be more of an additive nature than overriding. So you could add new bindings, but you cannot replace/override the ones that the engine sets up by itself(default wire.bindings.xml)
3.)Taking the above point into consideration, should the jbpm.wire.bindings.xml be user configurable option? If needed? So that there is a more straightforward way to 'register' one's custom implementations for Identity and other Services(If needed). Or should the jbpm.user.bindings.xml be loaded in such a manner that it can override the existing ones. So store the bindings in a Map rather than a List?
All this is based on my understanding of the way things are being setup within the engine, we have really been working with jbpm4 for a little over a week now. So I could be really miles away from the truth and the bigger picture. Excuse me if that is the case.
Plugging in a custom IdentityServiceImpl would be a big gain if we are able to hook it up seamlessly to work with our own auth mechanism.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238088#4238088
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238088
15 years, 5 months