This maven plugin is used to generate the required version of the camel model json. It is published to maven central but the source is only available from the hawtio/hawtio 1.x branch. It was then removed(?). Where is it now located if at all and if it was never moved elsewhere, should it be??

• Issue #1 - Tidy up Tasks
• Issue #2 - Migrate project to hawtio organisation

Camel plugin should provide the view for managing Camel endpoints from the web console, which includes:

• Add a new endpoint
• Browse messages in an endpoint
• Send a test message to an endpoint

The full Basic auth implementation requires a Java runtime with JAAS but Hawtio.next needs to implement its supporting mechanism.

JMX plugin provides the general JMX MBean tree from workspace. A plugin that works on top of the MBean tree like Camel plugin needs to implement a way to postprocess and decorate them into a specialised view of the tree.

• Extract only Camel-related MBeans from the entire JMX tree
• Assign custom icons according to the types of Camel MBeans

The Camel tree view from the original Hawtio looks like this:

Right now the project is private and cannot publish to NPM registry as-is. Making it a publich package is necessary for the downstream projects such as hawtio and hawtio-online to consume it.

Hawtio.next is being integrated into the main Hawtio at https://github.com/hawtio/hawtio/tree/3.x, but there are minor issues to fix at Hawtio.next side.

• #75

Let's port https://github.com/hawtio/hawtio-integration/tree/main/plugins/jmx/ts/charts

Export connections is already available, but Import connections is not yet implemented.

This feature should basically just import the JSON file exported using Export connections and then persist the config into local storage.

Camel plugin should provide the view for managing Camel contexts that enables users to start, stop, resume, and delete them from the web console.

The Camel model schema is imported into the old UI for icon lookup and model validation.

Maybe instead of importing it into a vendor directory, we should publish it as a separate npm package that is then brought in as a yarn dependency?

Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of FindRefWrapper which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node

This should be fixed by upgrading to the latest PatternFly 4 and apply removeFindDomNode to ClipboardCopy component:
patternfly/patternfly-react#8368

The About modal should collect and display the right versions of components. Refer to how the legacy Hawtio substitutes the PACKAGE_VERSION_PLACEHOLDER string during build & publish.

• https://github.com/hawtio/hawtio-core/tree/main/src/app/about

Let's port https://github.com/hawtio/hawtio-integration/tree/main/plugins/camel

This task can be broken down into the following sub tasks:

• #17
• #18
• #19
• #20
• #21
• #22
• #23
• #41

Additional Views:

• #181
• #182
• #183
• #184
• #185
• 'Properties' - '/camel/propertiesDataFormat' -> won't fix in the same reason as the other properties views
• #186
• #280
• #281
• #282

Camel plugin should provide the features of tracing and debugging Camel routes from the web console. Tracing and debugging are backed by the following Camel features:

• Tracer - https://camel.apache.org/manual/tracer.html
• Debugger - https://camel.apache.org/manual/debugger.html

Trace

Debug

The plugin interface and mechanism have already been implemented for the Connect and JMX plugins, but we need to further polish and stabilise them with new built-in plugins such as Camel, etc. and then expose the interface for external plugin developers, including Artemis plugin.

What we need to complete on the design and implementation of Hawtio.next plugin are:

• How to provide the JMX MBean tree to other plugins
• How to allow other plugins to post-process the JMX tree
• How to load external plugins dynamically at runtime

This also includes the following sub tasks:

• #33
• #34

Camel plugin should provide the view for managing Camel routes from the web console.

It should provides the following features:

• Start, stop, resume, and delete Camel routes
• View and update the source of the routes on the fly (Updating routes on the fly is no longer supported in Camel 3 hawtio/hawtio#2779)
• #144
• #145

Routes

Source

Exchanges

Type converters

This should be done at the main Hawtio project but is filed here for records.

James has already done some implementation but someone needs to take over the work here:

• hawtio/hawtio-integration#100

Connect plugin should provide Discovery tab that allows users to discover locally running Jolokia agents automatically.

The code from hawtio-integration (v2):

• https://github.com/hawtio/hawtio-integration/blob/main/plugins/jvm/ts/discover.ts

Hawtio.next should catch info and error messages from internal processes such as Jolokia invocations and use toast to notify the user.

Port the core logging feature and preferences:
https://github.com/hawtio/hawtio-core/blob/main/src/app/core/logging-init.ts
https://github.com/hawtio/hawtio-core/tree/main/src/app/preferences/logging-preferences

Hawtio.next should provide the ability to read the external configuration named hawtconfig.json from the server and customise the application settings based on the JSON file.

Among others, hawtconfig.json should be able to configure:

• branding info
• login page detail info
• about modal
• explicit disabling of specific routes

hawtconfig.json

{
  "branding": {
    "appName": "Hawtio Management Console",
    "appLogoUrl": "img/hawtio-logo.svg",
    "companyLogoUrl": "img/hawtio-logo.svg",
    "css": "",
    "favicon": ""
  },
  "login": {
    "description": "",
    "links": []
  },
  "about": {
    "title": "Hawtio Management Console",
    "productInfo": [],
    "additionalInfo": "",
    "copyright": "",
    "imgSrc": "img/hawtio-logo.svg"
  },
  "disabledRoutes": []
}

We've implemented the loading state for components with the loaded state hook, but the newer way to implement it from React v18 is using Suspense.
https://beta.reactjs.org/reference/react/Suspense

In the long term, consider migrating to Suspense in our React components.

The Home preferences is not fully implemented yet.

What should be implemented:

• Switch to show/hide the vertical navigation by default
• Reset button to clear all Hawtio settings in the local storage

Help

Preferences

They are mostly the same as what JMX plugin provides, but they are embedded in the Camel plugin. We need to find a way to reuse the parts of JMX plugin from a different plugin.

Attributes

Operations

Port the Keycloak integration formerly implemented by hawtio-oauth. This feature should be a plugin named keycloak under plugins/ directory.

Automatic dependency upgrade #50 is failing because React Router v6 is not backward-compatible with v5.
https://reactrouter.com/en/main/upgrading/v5

We need to follow this guide to upgrade it to v6.

jolokia.js depends on jQuery only for ajax communications, which is not preferrable as it will solicit a ton of vulnerabilities on jQuery to the project. We can rewrite only a subset of Jolokia functionalities that Hawtio really relies on with a lighter HTTP client library such as axios and switch to it.

Due to the introduction of a new package (camel-model), the @hawtio ident prioritizes the new purpose of being an organisation. In order to avoid confusion and failure, the ident referencing src paths is modified to @Hawtiosrc (see #93).

Is this the correct alias?
Should this alias even be retained or is there something better?

One of the key things that were missing in the original Hawtio project was an E2E test suite; without E2E testing, we were unable to perform automated quality assurance on each new version release. We should ensure that this does not happen in Hawtio.next. Hawtio.next development should take E2E testing into account well into the early stages of the project.

The E2E testing strategy I'm considering at this time is as follows:

• E2E tests with runtimes to be run at hawtio and hawtio-online projects
  • hawtio - E2E tests for Spring Boot and Quarkus standalone
  • hawtio-online - E2E tests on Kubernetes and OpenShift (with microshift-action or a self-hosted runner)
• Component-level UI testing can be done at hawtio-next project
  • Leverage React Testing Library

Relating issue:

• hawtio/hawtio#2782

Especially after upgrade to React Router v6 #84, where / doesn't redirect to /hawtio.

When selecting an item from the JMX tree that item is not highlighted as selected so you end up not seeing what you selected in the tree. The Camel Plugin tree has a solution to this already.

Camel plugin should provide the view for visualising Camel routes.

Since the functionality of visualising Camel routes is a recurring common feature required by various Camel development tools, including Karavan, Camel Designer, VS Code extension, and Kaoto, it is not desirable to implement it independently in Hawtio. Rather, we should consider reusing code from the aforementioned tools or developing the feature as a reusable JS library together with the developers of those tools so that they can reuse it later.

The old Attributes Component includes the ability to display the children of a group category, eg. Contexts, as a table with the bean attributes as the columns and mbeans as the rows:

Old Attributes component for camel contexts ^

structuredClone() is a built-in browser function. Rather than retaining the JSON parse method, which is considered quite slow and weighty, migrate to the newer browser-native function.

This will require node 17+ as described here.

Connect prefenreces is not yet fully implemented. See // TODO comments in ConnectPreferences.tsx.

What should be implemented:

• Apply the parameters to Jolokia instance
• Reset the connections settings persisted in local storage

This feature is not yet implemented.

So that it can be consumed to e.g. https://dependencytrack.org/ and further analyse CVEs in advance. Consider introducing tools like https://github.com/CycloneDX/cyclonedx-node-module for generating SBOM.

Hawtio.next needs to provide RBAC on UI based on the canInvoke info from Jolokia. Port the feature from hawtio-integration.

This includes the following subtasks:

• #133
• #134

Document the new plugin API defined and implemented at #32.

Relates #8