November 2008 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: jpdl 3.3.GA / Why isn't the jar provided?

by heiko.braun＠jboss.com

The installer unpacks all artifcats to ~/jbpm-3.3.1-SNAPSHOT/: | xyz:trunk hbraun$ ll ~/jbpm-3.3.1-SNAPSHOT/ | total 136 | -rw-r--r-- 1 hbraun staff 8102 Nov 20 10:32 JBossORG-EULA.txt | drwxr-xr-x 3 hbraun staff 102 Nov 20 10:32 Uninstaller | drwxr-xr-x 24 hbraun staff 816 Nov 20 10:32 config | drwxr-xr-x 18 hbraun staff 612 Nov 20 10:32 database | drwxr-xr-x 3 hbraun staff 102 Nov 20 10:32 designer | drwxr-xr-x 3 hbraun staff 102 Nov 20 10:32 docs | drwxr-xr-x 4 hbraun staff 136 Nov 20 10:32 examples | drwxr-xr-x 17 hbraun staff 578 Nov 20 10:32 lib | -rw-r--r-- 1 hbraun staff 59558 Nov 20 10:32 release.notes.html | drwxr-xr-x 7 hbraun staff 238 Nov 20 10:32 src | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191763#4191763 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191763

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jpdl 3.3.GA / Why isn't the jar provided?

by camunda

Hmm, and it seems there is no single war provided any more? Just an ear? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191746#4191746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191746

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - jpdl 3.3.GA / Why isn't the jar provided?

by camunda

Hi! Just a quick question: Why is ONLY the installer available for the new release? I got the question already a couple of times and for myself the same is true: If I want to update to the latest jbpm I only need the jbpm-jpdl.jar. But I cannot download it standalone any more? And with the installer I am forced to install jbpm into a JBoss AS? I think the jar should be provided standalone too! Or was I too blind to find it somewhere? Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191742#4191742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191742

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM 3.3 GA feedback in the user forum

by kukeltje

Ok.. I'll do it tonight... weekend was kind of busy ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191696#4191696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191696

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: comments on initial xsd jpdl 4

by kukeltje

anonymous wrote : | i wouldn't consider this a 180 degrees turn :-) If you take jBPM 3 'as is' it isn't :-) anonymous wrote : | The only other info that we consider inside the scope of what we target might This is where we might see things differently, or to be more precise, I do not see anything at all :-) The other info I was talking about was location, size etc... where does that 'designer' info go to? Regarding the extension mechanism, you propbably misunderstood me. I do not think 'g' should be left out in the xsd. Au contraire... it should be more specific (you know, namespaces ;-)) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191693#4191693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191693

15 years, 7 months

1
0
0 / 0

GPD integration

by Thomas Diesler

Hi Koen, in Antwerp we talked about the GPD not having a direct dependency on the jBPM4 code base but rather on the API that exposes the concepts that jBPM4 should implement. By providing support for the jBPM3 threading model the basic concepts that we talked about are applicable to the jBPM3 code base as well. If the API is the integration point for the GPD (btw this argument holds true for the GWT Console as well) it should be possible to implement a single GPD code base that works across jBPM versions. The API would become the common base were all integration concerns would come together. In this light the term SPI is probably even more applicable. Thoughts? cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler BPM Product Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

15 years, 7 months

2
2
0 / 0

[Design of JBoss jBPM] - Re: jBPM 3.3 GA feedback in the user forum

by thomas.diesler＠jboss.com

anonymous wrote : | I'll make Jira issues of these in the weekend, but thought I'd initially share them here. | Thanks, we need jira's for everything that is supposed to get done. Please initially schedule for 3.3.2 (1-Mar-2009) since we are already passed Jira Freeze for 1-Jan-2009 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191642#4191642 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191642

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: comments on initial xsd jpdl 4

by tom.baeyens＠jboss.com

"kukeltje" wrote : "thomas.diesler(a)jboss.com" wrote : Yes, a general extension mechanism should be put in place that allows the GPD and other consumers of the jPDL to extend the definition in an appropriate way. | | | | GPD concerns should not leak into the jPDL XSD | | Funny, this latter remark is a 180 degree turn from what was initially the idea. Making one jpdl file with process and graphical info in it instead of having to keep two files in sync. The 'general extension machanism' is using good extensionpoints in the xsd. i wouldn't consider this a 180 degrees turn :-) but if i understand you correct, you do have a point: we could as well leave the 'g' attributes out of the specified schema and leave it up the the designer to add this as one of the anyAttributes. that is something we did not consider yet. and at first thought it makes sense to me as then the g attribute won't be offered in code completions to developers writing xml by hand. what do you think of that, Koen ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191641#4191641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191641

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: comments on initial xsd jpdl 4

by tom.baeyens＠jboss.com

"kukeltje" wrote : "tom.baeyens(a)jboss.com" wrote : we discussed exactly the topic element vs attribute a full hour yesterday. and we swinged back and forth between element and attribute. | | | | we looked into various bpmn modellers to see what kind of information they had apart from the | | * diagram size | | * activity box bounds coordinates, width and height | | * transition/flow anchor points and bendpoints | | | Where is this info going then? | | "tom.baeyens(a)jboss.com" wrote : does this reasoning make sense to you as well ? | | No, since it does not say where the other info is going.... The only other info that we consider inside the scope of what we target might be color (although definitely not in the first releases). And we concluded that can always be encoded within the text field as only the designer has to manage it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191638#4191638 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191638

15 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM 3.3 GA feedback in the user forum

by kukeltje

Just to let you guys know the urgency of this: I'm not going to answer those..... and it will make jBPM look bad if it is not solved in 3.3.1 (7 weeks still????) I think something should be updated before that... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191512#4191512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191512

15 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev November 2008