7:28 a.m.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a string
needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Daniel Bevenius reassigned JBESB-2317:
--------------------------------------
Assignee: Daniel Bevenius
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Work on JBESB-2317 started by Daniel Bevenius.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2317:
----------------------------------------
The EPR contains information such as variable mappings, information
that can be retrieved from the action rather than passed via the EPRs.
This
information is also currently used by the CALLBACK_EXECUTOR:
String esbToBpmXml = toEpr.getAddr().getExtensionValue(Constants.ESB_TO_BPM_VARS_TAG);
The JBpmCallback does not have a action config containing the mapping as this is a general
action jbpm.esb/META-INF/jboss-esb.xml:
<action action="action"
class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback"/>
This info is used to map variables from the Message to jbpm variables. With out this
variable will not be set.
We could store the mapping information in the body using the same key as we are using
today.
Anyone have a better idea?
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:28 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2317:
-------------------------------------
It should be possible to take these from the process definition, through the action
delegate previously mentioned.
We only have two choices for this information
- embed it in the EPR (as at present)
- discover it from the process definition
If we cannot do the second then we have to do the first. The message body is not an
option as it will not be returned to the callback service.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2317:
----------------------------------------
It should be possible to take these from the process definition,
through the action delegate previously mentioned.
Yeah, that is possible and this
can be done.
The issue I am seeing is not the information about which variables are mapped, but the
actual setting of the variables and their values before reaching jBPM.
When JBpmCallBack execute method is currently using the information in the epr to find out
which variables should be extracted from the Message object and be included in the
variables map passed to jBPM.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2317:
-------------------------------------
The CallbackCommand.execute method is where the lookup should occur, not where it is
currently being retrieved.
One of the other tasks we should have, if there is time, would be to simplify all this
integration code. Perhaps some time next week :)
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2317:
----------------------------------------
Ah, I think I see what you mean now :)
Yeah, it would be nice if we could simplify this a little, so that would be worth doing I
think.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2317) Reduce verbosity of jBPM callback EPRs
[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Daniel Bevenius closed JBESB-2317.
----------------------------------
Resolution: Done
Committed to main trunk with revision 25054.
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL: https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5778
days inactive
5783
days old
8 comments
2 participants
participants (2)
-
Daniel Bevenius (JIRA) -
Kevin Conner (JIRA)