Petals SE RMI

Include whole stacktrace in exchange errors and other exceptions thrown by remote objects

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.7.1
  • Fix Version/s: 1.7.2
  • Component/s: Component
  • Security Level: Public
  • Description:
    Hide

    Because of PETALSSERMI-22 (and previous old code actually), the cause of the exceptions thrown by the remote objects of the RMI SE were lost in the conversion.

    The rational was to allow for proper serialisation of exceptions not present in the classpath of the RMI client, but it was more restricting than useful.

    Since the RMI Client is only meant for tests, it is ok to assume that we can modify the tests when needed to include desired elements in the classpath when testing for some specific errors.

    Show
    Because of PETALSSERMI-22 (and previous old code actually), the cause of the exceptions thrown by the remote objects of the RMI SE were lost in the conversion. The rational was to allow for proper serialisation of exceptions not present in the classpath of the RMI client, but it was more restricting than useful. Since the RMI Client is only meant for tests, it is ok to assume that we can modify the tests when needed to include desired elements in the classpath when testing for some specific errors.
  • Environment:
    -

Activity

Hide
Victor NOËL added a comment - Mon, 22 May 2017 - 15:53:25 +0200

Fixed by r41271

Show
Victor NOËL added a comment - Mon, 22 May 2017 - 15:53:25 +0200 Fixed by r41271

People

Dates

  • Created:
    Mon, 22 May 2017 - 15:52:55 +0200
    Updated:
    Mon, 22 May 2017 - 15:53:25 +0200
    Resolved:
    Mon, 22 May 2017 - 15:53:25 +0200