December 2009 - jbpm-dev - Jboss List Archives

[jBPM Development] - jpdl syntax for jms activity

by tom.baeyens＠jboss.com

14 years, 11 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for ejb method invoke activity

by tom.baeyens＠jboss.com

"Koen" wrote : Do we only target ejb3 or also ejb2 ? I think ejb 3 to get started with in incubation. Then if we get enough requests for ejb 2 we can consider it. If we tackle it later, do you think it could impact the current attributes ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269939#4269939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269939

14 years, 11 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for ejb method invoke activity

by tom.baeyens＠jboss.com

I think the invoking an ejb should be called just 'java' As the java activity actually means invoke a java method. At least, that is the reasoning behind it. Some more questions we need to think about: 1) there is a <jndi jndi-name="..." /> element in the wiring section of jpdl. What is then the most consistent way of naming the jndi element ? In that case the full element specifies only jndi so i don't really know what is the most consistent here. 2) do we need to distinct between session and entity beans ? or can we use reflection to find out ? or maybe that doesn't matter any more in ejb 3 ? i don't know. but if we need to make a distinction in the language between session and entities, we might have to consider attributes like session-ejb-jndi-name and entity-ejb-jndi-name. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269938#4269938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269938

14 years, 11 months

1
0
0 / 0

[jBPM Development] - jpdl syntax for ejb method invoke activity

by tom.baeyens＠jboss.com

"Koen" wrote : | | | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269937#4269937 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269937

14 years, 11 months

1
0
0 / 0

#JBPM-2506

by Sebastian Schneider

Good morning, regarding issue #JBPM-2506 I have a question and some remarks: https://jira.jboss.org/jira/browse/JBPM-2506 Does this issue just refer to process variables or also to task-variables? In case of task-variables I am proposing the following: - add an attribute stating if a task-variable is needed for a task to be completed properly or if the variable is optional - extend the API so that one can query the list of a task's variables - distinguish between optional and obligatory task-variables In combination with issue #JBPM-2609 this could simplify development of user interfaces which aim to be generic. https://jira.jboss.org/jira/browse/JBPM-2609 Am I misleaded or does this make sense to you? Regards Sebastian -- Sebastian Schneider

14 years, 11 months

2
2
0 / 0

[jBPM Development] - Re: Extracting information from a jpdl file

by ajaygautam

Sorry. Wrong forum. Discussion continued at the user forums: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269440#4269440 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269441#4269441 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269441

14 years, 11 months

1
0
0 / 0

[jBPM Development] - Extracting information from a jpdl file

by ajaygautam

I have a state diagram in a jpdl file. I need to extract possible transition strings from the current state, so that the UI can figure out which string to send back to the jbpm process. Can't seem to find an easy way to do this. What am I missing? Its seems to be a basic thing to do. Any help / pointers will be greatly appreciated. Thanks Ajay (Using jbpm 4.2) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269436#4269436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269436

14 years, 11 months

1
0
0 / 0

[jBPM Development] - Re: Wondering about where the best place for forms really is

by kukeltje

This is not a strange thing to think, not at all. I implemented something like this on jbpm 3 once. I added custom tags to the transitions and used the forms on the task to present the INCOMING data. The user then got the choice of transitions and when picked did not take the transition but displayed a form that I configured on the transition. Only after submitting the form, the transition was taken. I did this without creating custom jBPM classes, but just by reading the process xml from the database. Personally I would think this could be a very nice enhancement to at least the core of jBPM and in a second step maybe the console (but I do not use that either for end-users) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269108#4269108 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269108

14 years, 11 months

1
0
0 / 0

[jBPM Development] - Wondering about where the best place for forms really is

by rmoskal

I've been developing a fairly substantial app and as I work I've been going back and forth on task forms. I keep wanting to be able to assign them to transitions instead of task nodes as is supported by the jpdl. This way way use cases like a a review task, where a manager can "reject", "approve", or "ask for "rework from a another department" can be handled elegantly: I simply show a different form for each transition. I actually started down this path a fair way then become worried that I would freak out my client making such an non-idiomatic use of jbpm. So I started reworking my forms to be task node based. When I moved my forms to the task nodes, they suddenly need to become a lot smarter. I have to show different you elements based on which transition I want to take anyway. The UI is a bit different when one approves something than when one rejects (one might want to reassign the work for example). And different again if I want to send the task to another department for rework. I have many scenarios like the above, and they were handled elegantly when I associated tasks with transitions. I thought about making the reassignment or the rework step to be separate task nodes, but this complexifies the work flows and it seems that from the users and the systems perspective this should be thought of as one task and not many. Has anyone had thoughts down these lines? Am I being perverse? My app has a completely custom admin console (written in extjs) so I'm not losing anything by not having the jbpm console. Color me curious, Robert Moskal Brooklyn, USA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268923#4268923 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268923

14 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev December 2009