9:12 a.m.
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in message
body. Now when the ObjectMapper is used the default is used only when the exception is
thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=all ]
Jiri Pechanec updated JBESB-1431:
---------------------------------
Component/s: Process flow
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:16 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=all ]
Jiri Pechanec reassigned JBESB-1431:
------------------------------------
Assignee: Kurt Stam
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=comments#action_12393725 ]
Kurt Stam commented on JBESB-1431:
----------------------------------
Can you explain a little more what you mean with 'default values'?
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=comments#action_12393726 ]
Kurt Stam commented on JBESB-1431:
----------------------------------
Ah I get it now. I changed the name to tag to 'default'. It should still work. Can
you verify? Sorry I'm still working on the documentation, so I know you are
completely in the dark here.
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=comments#action_12393730 ]
Jiri Pechanec commented on JBESB-1431:
--------------------------------------
Thanks for notice about renaming but it still does not work
See code
try {
value = objectMapper.getObjectFromMessage(message, mapping.getEsb());
} catch (ObjectMappingException ome) {
log.info(mapping.getEsb() + " not found");
value =mapping.getDefaultValue();
}
This is only plae when default value is used. But the exception is not throw whene there
is no such key in ESB message (returns null)
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=all ]
Kevin Conner reassigned JBESB-1431:
-----------------------------------
Assignee: Kevin Conner (was: Kurt Stam)
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1431) Default values are ignored in jBPM to ESB mapper (ESB side)
[ http://jira.jboss.com/jira/browse/JBESB-1431?page=all ]
Kevin Conner closed JBESB-1431.
-------------------------------
Resolution: Done
Fixed in revision 17761.
Default values are ignored in jBPM to ESB mapper (ESB side)
-----------------------------------------------------------
Key: JBESB-1431
URL: http://jira.jboss.com/jira/browse/JBESB-1431
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Priority: Critical
Fix For: 4.2.1 CP1
The old behaviour was that the defaut value was used when there was no such key in
message body. Now when the ObjectMapper is used the default is used only when the
exception is thrown. This is significant change that breaks backward compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6686
days inactive
6695
days old
7 comments
3 participants
participants (3)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)
-
Kurt Stam (JIRA)