Petals ESB Container

Move ContainerConfiguration from client-server-api to microkernel-api

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.1
  • Fix Version/s: 5.0.2
  • Component/s: JMX
  • Security Level: Public
  • Description:
    Hide

    ContainerConfiguration store local configuration information, but not anything that is meant to be accessed remotely through client server api!

    Modifying this class impacts almost half of our code base when we want to add some server configuration while it shouldn't.

    So it should be moved to microkernel were it is meant to be so that future modification of it won't impact all of our artifacts (such as JMX or CLI).

    The main impact it has in practice is that the API for Topology attachment is changed and thus Petals CLI must be modified (see PETALSESBCLI-154).

    Show
    ContainerConfiguration store local configuration information, but not anything that is meant to be accessed remotely through client server api! Modifying this class impacts almost half of our code base when we want to add some server configuration while it shouldn't. So it should be moved to microkernel were it is meant to be so that future modification of it won't impact all of our artifacts (such as JMX or CLI). The main impact it has in practice is that the API for Topology attachment is changed and thus Petals CLI must be modified (see PETALSESBCLI-154).
  • Environment:
    -

Issue Links

Activity

People

Dates

  • Created:
    Wed, 25 May 2016 - 14:06:36 +0200
    Updated:
    Wed, 25 May 2016 - 14:59:04 +0200
    Resolved:
    Wed, 25 May 2016 - 14:07:00 +0200