JMX & Studio

Open
#481 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
devtools, frontend

Research direction

Start by evaluating how Studio could access the JMX bean and how its parameter list can be loaded dynamically. No file or test entry point is named; done means Studio continues working when parameter names change or parameters are added or removed between releases.

Written by the indexing model from the issue text.

Description

enhancement

Evaluate adding access to our jmx bean to Studio, as this will make life much easier to many

Note that those parameters are subject to change between releases even minor once --> find a way to dinamically load the list, so that even if the variable names change (or are added / removed) things will keep working anyway from Studio

Thanks,

Dominant language
HTML
Stars
128
Forks
51
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from orientechnologies/orientdb-studio

All issues in orientechnologies/orientdb-studio

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.