-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop using jolokia.js and create a homebrew minimal Jolokia library #8
Comments
Or maybe better to just use the built-in |
Can I assign myself to this? I might be able to tackle it after finishikg the JMX Chart feature |
@joshiraez Don't do this now. It's a future task, the lowest priority. There are higher ones within 0.3 or 0.x milestones. |
Alright
El mar., 11 abr. 2023 1:32, Tadayoshi Sato ***@***.***>
escribió:
… @joshiraez <https://github.com/joshiraez> Don't do this now. It's a
*future* task, the lowest priority. There are higher ones within 0.3 or
0.x milestones.
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEEIPLEW5TYHXBL4FGLIFQDXASJ7RANCNFSM6AAAAAAQ7HIGLY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Let me just clear assignment to this issue for now, as we won't work on it soon. |
Once the jolokia project implements this jolokia/jolokia#580 we can use it. Let's close this in favour of the Jolokia issue. |
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.
The text was updated successfully, but these errors were encountered: