Bug 779572 (SOA-1948) - jBPM variable mapping does not map correctly an empty String.
Summary: jBPM variable mapping does not map correctly an empty String.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1948
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA
Version: 4.3 CP04 ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-12 17:41 UTC by Marek Baluch
Modified: 2011-04-08 20:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 779573 (view as bug list)
Environment:
Last Closed: 2011-04-08 20:27:17 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1948 0 None None None Never

Description Marek Baluch 2010-02-12 17:41:07 UTC
Date of First Response: 2010-03-18 18:45:22
project_key: SOA

See linked issue.

Comment 1 Marek Baluch 2010-02-12 17:41:40 UTC
Link: Added: This issue depends JBPM-2791


Comment 2 David Le Sage 2010-03-18 22:45:22 UTC
Documented as Known Issue in Release Notes:



https://jira.jboss.org/jira/browse/JBPM-2791

    If there is a variable mapping between the Enterprise Service Bus and the Business Process
    Manager and the mapped value happens to be an empty string, then the result will be null. Also,
    if an object is persisted in an Oracle database with a field set to be an empty sting, the field value
    will also be null.

    Currently, there is no work-around for this problem.


Comment 3 Anne-Louise Tangring 2010-09-21 19:48:45 UTC
This was triaged for SOA 5.1.0. Not in SOA 5.1.0

Comment 4 Alejandro Guizar 2010-12-09 00:22:57 UTC
Oracle treats a zero length string as NULL. That is a well known "feature" of Oracle; jBPM is innocent.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5984520277372


Note You need to log in before you can comment on or make changes to this bug.