[Design of JBoss Web Services] - Re: JBossWS Deployers Integration
by richard.opalka＠jboss.com
"alessio.soldano(a)jboss.com" wrote :
| So, what's actually the reason for doing this, instead of having an actual separate deployer for each of the current deployment aspect, instead of doing the wrap process into WSDeploymentAspectDeployer? Wouldn't it be clearer?
|
The main reason is to enable other AS deployers to hook into WS deployers pipeline, see this.
"alessio.soldano(a)jboss.com" wrote :
| So my question is, why is relativeOrder required for all the deployment aspects turning into WSDeploymentAspectDeployer instances?
Comment in jboss-beans config files is self descriptive ;)
<!-- [JBDEPLOY-201] workaround -->
In short about JBDEPLOY-201.
There's a bug in domino ordering (deployers ordeing AS implementation) we have to workaround until fix is available in AS. This bug appears if there are multiple inputs/outputs specified on deployers (this affects all WS deployers, except WSDescriptorDeployer).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248338#4248338
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248338
17 years, 1 month
[Design of JBoss jBPM] - Re: [BPMN2] Resource assignment
by koen.aers＠jboss.com
<resource id="regionalManager" name="Regional Manager">
| <resourceParameter id="buyerName" isRequired="true" name="Buyer Name"
| type="xsd:string"/>
| <resourceParameter id="region" isRequired="false" name="Region"
| type="xsd:string"/>
| <resourceParameter id="type" isRequired="false" name="jBPM type"
| type="xsd:string"/>
| </resource>
Bernd wrote :
| I had something like this in mind first, but wonder if that is correct (since the regionalManager is maybe always a user)?
|
I nevertheless think that this is the way the spec wants us to do it. A resource only specifies a number of parameters that are used at runtime to resolve the actual potential owner. There is probably room to define shortcuts that make it less clumsy to work with the jBPM task management implementation, but I would not concentrate on that for now.
Regards,
Koen
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248308#4248308
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248308
17 years, 1 month
[Design of JBoss jBPM] - [BPMN2] advanced pvm/parsing question
by camunda
Ronald wrote :
| > ActivityResources have a resourceRef to resources, just like
| > sequenceflows have to activities, at least in bpmn. There are two
| > differences. Sequenceflows need to be added to activities which can be
| > retrieved with findActivirty and that the level they are on the xml
| > file is different. I've been looking in detail at the jPDL parser,
| > but maybe because of tiredness, I do not seem to get a grip on how to to do this.
| > push, pop, unresolvedTransitions like, I've seen it al but cannot find out.
| >
| > If you have a tip, I can continue with this tomorrow and probably do
| > the same for dataObjects.
|
Tom wrote :
| BpmnParser should first parse the resources and build up an internal datastructure for it. So that resourceRefs can look em up there.
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248301#4248301
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248301
17 years, 1 month
[Design of JBoss jBPM] - [BPMN2] Resource assignment
by camunda
Moving from Mail to forum:
Ronald:
| >>> This works:
| >>>
| >>> <bpmn:userTask id="UserTask" name="user task"
| >>> implementation="other">
| >>> <!-- use jbpm internal task management -->
| >>> <bpmn:performer id="myPerformer"
| >>> resourceRef="sampleResource">
| >>> <bpmn:resourceAssignmentExpression
| >>> id="rae">
| >>> <bpmn:formalExpression
| >>> language="juel">${assignedUser}</bpmn:formalExpression>
| >>> </bpmn:resourceAssignmentExpression>
| >>> </bpmn:performer>
| >>> <bpmn:rendering id="myRendering">
| >>> <jbpm:form>MyForm.ftl</jbpm:form>
| >>> </bpmn:rendering>
| >>> </bpmn:userTask>
| >>>
| >>> Assigning a task to a user while parsing a processvariable. Not sure
| >>> how I have to use the resource though, that's still a blurry subject
| >>> for me in this regard.
| >>>
| >>> What also works is setting the form on the taskDefinition based on
| >>> the jbpm:form inside the rendering element (yes Tom, OTHER namespace
| >>> required :-P), so it might just be that it is possible to hook this
| >>> up to the console already.
| >>>
| >>> What I'm currently looking into is how to differentiate between
| >>> users and groups. There is a potentialOwner element of which you can
| >>> have multiple, but it might be that
|
Ronald:
| >> I could initially do something like:
| >>
| >> <bpmn:potentialOwner id="myPerformer"
| >> resourceRef="sampleResource" jbpm:type="group">
| >>
| >> for groups
| >>
| >> and
| >>
| >> <bpmn:potentialOwner id="myPerformer"
| >> resourceRef="sampleResource" jbpm:type="user">
| >>
| >> for users.
|
Tom wrote :
| > isn't the simplest way if we couple resourceRef directly to our groups ?
| >
| > <bpmn:potentialOwner id="myPerformer" resourceRef="accounting">
| >
| > in jBPM we could then associate the group as a candidate for that
| > task. i think that covers the most common form of task assignment.
| >
| > wdyt?
|
Bernd:
| > This is not the BPMN 2 way of thinking I guess. So I would go for what
| > Ronald proposed, that looks like valid BPMN 2.
| >
| > For the groups I didn't find anything in the spec. I check Bruce's
| > book. Maybe there...
| >
| > Intuitivley I would put it in the resource (example from spec, p. 183):
| >
| > <resource id="regionalManager" name="Regional Manager">
| > <resourceParameter id="buyerName" isRequired="true" name="Buyer Name"
| > type="xsd:string"/>
| > <resourceParameter id="region" isRequired="false" name="Region"
| > type="xsd:string"/>
| > <jbpm:type>user</jbpm:type>
| > </resource>
|
Tom:
| can't we start with resourceAssignmentExpression instead of the resourceRef as the most basic way of assigning a task?
|
| <potentialOwner id="myPerformer">
| <resourceAssignmentExpression>
| <formalExpression body="tom" language="jbpm-user" />
|
| or
|
| <potentialOwner id="myPerformer">
| <resourceAssignmentExpression>
| <formalExpression body="sales-dept" language="jbpm-group" />
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248300#4248300
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248300
17 years, 1 month