Petals ESB CLI

Exceptions thrown on the container side and not known by the classpath of the CLI results in useless output

Details

  • Type: Bug Bug
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 2.2.0
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Currently, if an exception thrown (during a command executed by the CLI) at the container side is not known in the CLI classpath (petals-admin-jmx more precisely), then we get an error from RMI saying it can't unmarshal the exception instead of the exception itself.

    For now we added some of the potential dependencies that hold such exceptions (fractal-api, petals-microkernel-api), but it's not the right solution because we will end-up bringing the whole container with us.

    Show
    Currently, if an exception thrown (during a command executed by the CLI) at the container side is not known in the CLI classpath (petals-admin-jmx more precisely), then we get an error from RMI saying it can't unmarshal the exception instead of the exception itself. For now we added some of the potential dependencies that hold such exceptions (fractal-api, petals-microkernel-api), but it's not the right solution because we will end-up bringing the whole container with us.
  • Environment:
    -

Activity

There aren't workflow transitions executed yet.

People

Dates

  • Created:
    Fri, 27 Nov 2015 - 12:14:29 +0100
    Updated:
    Fri, 27 Nov 2015 - 14:28:22 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.