[JFR Writer] Make constant pool optional when registering a new type

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P3
    • 8.0.0
    • Affects Version/s: None
    • Component/s: Mission Control Core
    • None

      JFR allows complex types not to use constant pool.
      However, currently the writer will always make the custom types go to the corresponding constant pool and this might not be always desirable.

      Hence, a control point allowing to mark a custom type as not eligible for constant pool should be added.

            Assignee:
            Jaroslav BachorĂ­k
            Reporter:
            Jaroslav BachorĂ­k
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: