Uploaded image for project: 'Tupelo'
  1. Tupelo
  2. TUP-461

Bean session should handle TYPE vs. class confusion better

XMLWordPrintableJSON

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 2.5
    • None
    • Beans
    • None

      Java's reflection API does not play well with classes vs. types. Some autoboxing can cause runtime errors on this account.

      The bean session should anticipate that users might use a wrong type (e.g. Long.class where Long.TYPE corresponding to a long's java type is meant) and catch runtime exceptions, then throw an OperatorException with a useful diagnostic message.

              jgaynor Jeffrey Gaynor
              jgaynor Jeffrey Gaynor
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: