December 2009 - jbpm-dev - Jboss List Archives

by Bernd Rücker (camunda)

Hi Joram, Hi Sebastian. Just a remark for the editor: I still have some ideas in my mind, how to extend Signavio to even include developer stuff (like class browsing). I still didn't had the time to put my concrete ideas on this and what we talked about in Berlin to slides :-( Hopefully next weekend! If we get a good eclipse designer, fine, but actually I wouldn't put it on the high priority list (since the jPDL Designer needs still a lot of work as well and is more important in my opinion). Cheers and greetings from Lausanne Bernd ----- Original Message ----- From: "Joram Barrez" <joram.barrez(a)gmail.com> To: "Sebastian Schneider" <Sebastian.Schneider(a)alumni.fh-aachen.de> Cc: "jBPM Dev List" <jbpm-dev(a)lists.jboss.org> Sent: Tuesday, December 15, 2009 9:05:17 AM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [jbpm-dev] BPMN 2.0 implementation Hi Sebastian, See inline On Sun, Dec 13, 2009 at 7:30 PM, Sebastian Schneider < schneider(a)dvz.fh-aachen.de > wrote: Good evening folks! A few days ago I read Joram's great blog post about BPMN 2.0 and jBPM: http://www.jorambarrez.be/blog/2009/12/04/jbpm-goes-bpmn/ First of all my congratulations for your work and thanks to everybody who is putting effort into this. It is really astonishing to see how the PVM can be leveraged to implement BPMN 2.0. Regarding the implementation I have some questions: You seem to have implemented a basic parsing of BPMN 2.0 process definitions already. Does this mean that the OMG has agreed on a serialization format? From what I could see in Joram's post it is not XPDL. No it's definitely not XPDL, but a BPMN2 specific format. The serialization format is not yet 100% completed, but stable enough to already build an implementation for it. In his post Joram wrote that task-forms can already be used with BPMN process definitions. Is the storage of the necessary information about which form to use a jBPM-specific thing, a BPMN standard or a kind of extension which is supported by BPMN? The BPMN spec has a 'rendering' element, but the actual content of that element is not in the spec. This means that these things will be vendor-specific. Are you planning to extend the GPD to support modelling in BPMN 2.0? Or will it be possible in the future to use the Signavio Editor to design process models which are executable? AFAIK right now they use their own file format to store BPDs and jPDL in case you are using the jBPM stencil set which is quite limited. We are currently very close collaborating with Signavio to be able to create executable processes through their editor. If all goes well, we should have some announcement regarding that topic before the 4.3 release. AFAIK there is the Eclipse BPMN modeler. Assuming they are going to support BPMN 2.0 it would be possible to use this editor, right? So implementating an own BPMN-2.0 Eclipse editor would not make sense? What's your opinion on this? The more editors, the better ;-) Definitely if they are open source ;-) Koen did already take a look at the BPMN modeler by Eclipse, but they have nothing very concrete yet. For me personally, a BPMN2 editor would make sense, since some things (code completion, class searching, etc) make the life of the developer easy. Regards Joram Lots of questions. I'd love to hear your statements and your opinions on these. Sebastian -- Sebastian Schneider _______________________________________________ jbpm-dev mailing list jbpm-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbpm-dev _______________________________________________ jbpm-dev mailing list jbpm-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbpm-dev

14 years, 4 months

1
0
0 / 0

BPMN 2.0 implementation

by Sebastian Schneider

Good evening folks! A few days ago I read Joram's great blog post about BPMN 2.0 and jBPM: http://www.jorambarrez.be/blog/2009/12/04/jbpm-goes-bpmn/ First of all my congratulations for your work and thanks to everybody who is putting effort into this. It is really astonishing to see how the PVM can be leveraged to implement BPMN 2.0. Regarding the implementation I have some questions: You seem to have implemented a basic parsing of BPMN 2.0 process definitions already. Does this mean that the OMG has agreed on a serialization format? From what I could see in Joram's post it is not XPDL. In his post Joram wrote that task-forms can already be used with BPMN process definitions. Is the storage of the necessary information about which form to use a jBPM-specific thing, a BPMN standard or a kind of extension which is supported by BPMN? Are you planning to extend the GPD to support modelling in BPMN 2.0? Or will it be possible in the future to use the Signavio Editor to design process models which are executable? AFAIK right now they use their own file format to store BPDs and jPDL in case you are using the jBPM stencil set which is quite limited. AFAIK there is the Eclipse BPMN modeler. Assuming they are going to support BPMN 2.0 it would be possible to use this editor, right? So implementating an own BPMN-2.0 Eclipse editor would not make sense? What's your opinion on this? Lots of questions. I'd love to hear your statements and your opinions on these. Sebastian -- Sebastian Schneider

14 years, 4 months

2
1
0 / 0

[jBPM Development] - Re: jpdl syntax for jms activity

by kukeltje

Me to, but a 'destination' with a 'type="queue/topic" attribute would have been ok to. But do whatever is easiest. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270071#4270071 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270071

14 years, 5 months

1
0
0 / 0

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

by kukeltje

Since Joram referred to a remark I made earlier, let me add something else I mentioned. What is the added value of using a jndi attribute if there is an 'expression' attribute? The (jndi) name of an ejb can be put in there in the form of an EL expression. That is just like what seam does when injecting stuff. It does not matter if it is an ejb, springbean, seam (weld/cdi) component or whatever. We just need to have the correct resolvers in place... Oh.. and yes, just EJB3 please. Oh, and state that it (initially?) only is local ejb's otherwise a (remote) initialcontext is needed as well View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270070#4270070 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270070

14 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for jms activity

by koen.aers＠jboss.com

OK about the connection-factory, I should have thought about it in the first place. I am certainly not married to the destination attribute. It actually would make things easier to implement as well if it was split in queue and topic. I also agree on your refactoring of the message element into meaningful tags. So pretty much agreed about everything ;-) Cheers, Koen View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269984#4269984 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269984

14 years, 5 months

1
0
0 / 0

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

by koen.aers＠jboss.com

Ok, these opinions are pretty clear and a lot like I anticipated. Cheers, Koen View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269981#4269981 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269981

14 years, 5 months

1
0
0 / 0

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

by jbarrez

"tom.baeyens(a)jboss.com" wrote : I think the invoking an ejb should be called just 'java' I agree. As Ronald also stated before, this makes a lot of sense in for example a Seam environment. "tom.baeyens(a)jboss.com" wrote : | 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. Where is that jndi element used today? I think an attribute makes sense. "tom.baeyens(a)jboss.com" wrote : | 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. EJB 3 'entity beans', or JPA, don't have a JNDI name. So this use case doesn't make much sense. "tom.baeyens(a)jboss.com" wrote : | I think ejb 3 to get started with in incubation. Then if we get enough requests for ejb 2 we can consider it. I agree. EJB3 is the way to go. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269952#4269952 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269952

14 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for jms activity

by tom.baeyens＠jboss.com

we should also consider the properties. e.g. <jms name="send message" | connectionFactory="ConnectionFactory" | queue="queue/MyQueue"> | <text> | This is the body | </text> | <property name="aString"><string value="txt" /></property> | <property name="aBoolean"><false /></property> | <property name="aShort"><short value="8" /></property> | <property name="aByte"><byte value="8" /></property> | <property name="anInt"><int value="4" /></property> | <property name="aLong"><long value="8888888888" /></property> | ... and so on for all basic types... | | <property name="someExpression" expr="#{person.address.number}" /> | <transition to="wait" /> | </jms> | for the expression, (and probably for the other basic types too) you can use the setObjectProperty method. it only accepts the basic types that are supported. but we can leave it to that jms message to throw an exception if a non-supported type is supplied via the expression. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269946#4269946 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269946

14 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for jms activity

by tom.baeyens＠jboss.com

i would prefer to use tag names to indicate the message type. e.g. use element text for text messages and element map for map messages <jms name="send message" | connectionFactory="ConnectionFactory" | queue="queue/MyQueue"> | <text> | This is the body | </text> | <transition to="wait" /> | </jms> | <jms name="send message" | connectionFactory="ConnectionFactory" | queue="queue/MyQueue"> | <map> | <entry> | <key><string value="one" /></key> | <value><int value="3" /></value> | </entry> | </map> | <transition to="wait" /> | </jms> | Note that with this map, I used the syntax that is already in jpdl for maps. So you can leverage the map parsing and it will be more consistent. <jms name="send message" | connectionFactory="ConnectionFactory" | queue="queue/MyQueue"> | <object expr="#{someObjectExpression}" /> | <transition to="wait" /> | </jms> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269945#4269945 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269945

14 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: jpdl syntax for jms activity

by tom.baeyens＠jboss.com

i think connectionFactory should be connection-factory. we always use dashes instead of camelcase in jpdl. for attribute 'destination', are you sure that you can code for queue's and topics in the same way? if not, you might need different attributes for that. for example replace attribute destination="MyDestination" with queue="myQueue" or topic="MyTopic". to me using attributes queue and topic reads more naturally. what do you think ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269942#4269942 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269942

14 years, 5 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