June 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - GroupId or (groupName & GroupType)

by jeff.yuchang

Just found out that we've used the groupId in the jPDL file, for example, in the TaskCandidateTest.class, we've had following jpdl file. | <?xml version="1.0" encoding="UTF-8"?> | | <process name="TaskCandidates"> | | <start g="20,20,48,48"> | <transition to="review" /> | </start> | | <task name="review" | candidate-groups="jbpid_group_id_._._unit_._._sales-dept" | g="96,16,127,52"> | | <transition to="wait" /> | </task> | | <state name="wait" g="255,16,88,52"/> | | </process> | For the candiate-groups, we need to specify the groupId, because the groupId is identity component specific, which means it might differ in different identity implementation. So I don't think it is good to use the id in this case. Because in the process of doing jboss identity integration, I've found if I want to make the test suite passed, I need to update the jpdl file. And if I want to switch to use the jbpm-built-in identity, then need to update the jpdl file again due to the change of groupId difference. My suggestion is: for groups, we used: | candidate-groups = "groupName/groupType" | if the groupType == null or a default jBPM groupType (unit), it can be just specified as only groupName, like: | candidate-groups="groupName" | While, for the users, we've used username as the value. | user="username" | Got any thoughts?? thanks Jeff View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237698#4237698 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237698

17 years

1
0
0 / 0

[Design of JBoss ESB] - Http Gateway - requirements please...

by tfennelly

The HttpGateway added in v4.5 was based on an embedded tomcat, which has proven to be troublesome due to the sheer complexity of embedding tomcat. Because of this, we have decided to go to a model similar to that of EBWS, where we generate an actual war and deploy it as a sub deployment of the containing esb deployment. >From a usability point of view, what would people like to see in a new HttpGateway? What I mean is ... what would they like to be able to configure, and how? What do we want to inherit from the existing HttpGateway config? >From an implementation point of view, what would people like to see? Exactly the same as EBWS again, or should we try and create a new mechanism that abstracts this type of thing (creating sub deployments) away from the deployer and then use this as an opportunity to start evolving the EBWS specific code out of the deployer (where I would think it doesn't belong)? Do we want to merge deployments of the same type as in this case, where the EBWS and the new HttpGateway both require war deployments? What would that gain and would the added complexity be worth it? Apart from potential implementation similarities, what else should the new HttpGateway have in common with the EBWS functionality? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237696#4237696 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237696

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Problems with transmitting content from ESB to jBPM via

by Kevin.Conner＠jboss.com

Apologies for coming into this late. The EsbActionHandler should be initialising all information necessary, from the jBPM process definition, so that BpmCallback has access to the information necessary to signal the job. At present this information includes - esbToBpmVars - whether these are set in global scope or not - token id - node id - process instance id - node version counter All that should be necessary is to reply using this EPR (done automatically if you have a RequestResponse service) with data which matches the expectations of the process definition. What I do not understand is why you need to create the EPR, at least if I am following this correctly. Can you please elaborate on this? Thanks, Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237694#4237694 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237694

17 years

1
0
0 / 0

[Design of JBoss Build System] - Re: maven.opts for building thirdparty module

by pgier

"jaikiran" wrote : | So is the build.sh in the build folder no longer being used in the build process? | | Right, the build.sh in the build dir is not used anymore. I will switch that one to call the maven build like how the modules are set up. The project should be built from the root directory now, and the build directory only packages the distribution instead of doing the full build. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237682#4237682 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237682

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: native-src in kit

by gaohoward

for the build problem, it is because that I have libtool and libaio-dev missing. Once I installed them, the compile goes fine. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237678#4237678 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237678

17 years

1
0
0 / 0

[Design of JBoss Build System] - Re: maven.opts for building thirdparty module

by jaikiran

I had tried passing the properties directly but from the build folder. "pgier" wrote : From the root directory (not the build dir) | That was the only thing that i hadn't tried :) Let me see how it goes. Thanks. So is the build.sh in the build folder no longer being used in the build process? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237677#4237677 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237677

17 years

1
0
0 / 0

[Design of JBoss Build System] - Re: maven.opts for building thirdparty module

by pgier

Trunk is using Maven directly instead of through Ant, so you can just pass the properties directly. From the root directory (not the build dir) | ./build.sh -Dskip-download-sources -D... | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237675#4237675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237675

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: native-src in kit

by clebert.suconic＠jboss.com

Say you have a Linux for some very unique platform. (Say... an IBM Mainframe with Linux installed). As we wrote on the doc, we only distribute Intel 32 and 64 bits and Itanium. http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/... On that case all the user has to do is recompile the library for his platform, as we have native-src on the distribution for that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237672#4237672 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237672

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Problems with transmitting content from ESB to jBPM via

by andreskusa

Hi Bernd, yes, of course, obviously this was still somehow not clear to me. I just tested it and it works as well. So, you "only" need to set the esbToBpmVars-Mapping in the processdefiniton.xml and afterwards take care about that this mapping is also copied from replyTo() to To() in the Call object of the message header. Thanks again! Andre View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237671#4237671 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237671

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: native-src in kit

by gaohoward

Hi Clebert, just want you to note that the native-src are built into the distro. is it intended? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237668#4237668 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237668

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2009