Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1145

[DMN Designer] Java Date field is not converted to DMN date type

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.7.0.GA
    • 7.6.0.GA
    • DMN
    • 2
    • Release Notes
    • CR1
    • Generation of DMN data type from Java data objects doesn't work as expected for 'java.util.Date' fields.
    • Hide
      1. Opena project in business central
      2. Add a java data object, that will have one java.util.Date field
      3. Save and close the java class
      4. Open a dmn file
      5. Select Data Types tab
      6. Click Import Data Object
      7. Pick the java class from this Steps to Reproduce
      8. Click import
      9. Check if the given java java.util.Date field was converted to DMN date nor date and time
      Show
      Opena project in business central Add a java data object, that will have one java.util.Date field Save and close the java class Open a dmn file Select Data Types tab Click Import Data Object Pick the java class from this Steps to Reproduce Click import Check if the given java java.util.Date field was converted to DMN date nor date and time
    • 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10)

    Description

      DROOLS-4694 introduces possibility to generate DMN data type from a Java class. There is an issue that if Java class has a java.util.Date field, such is not converted into a DMN date nor date and time field.

      Note, regarding java built in types, there is one more not expected conversion, java Character is converted into DMN string. However I am not sure as Character is single character, if it shouldn't be converted into DMN number.

      Acceptance criteria

      java.util.Date is converted to DMN date and time

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1144 [DMN Designer] List Java field is not converted to DMN collection

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DROOLS-4983 Support java.util.Date and Character in engine

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dadossan Daniel José dos Santos (Inactive)
              rh-ee-jomarko Jozef Marko
              Jozef Marko Jozef Marko
              Jozef Marko Jozef Marko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: