sonus21
Rqueue decoupling and dependency lightweight management
Is your feature request related to a problem? Please describe. At present, rqueue as a component is a bit dependent.
Describe the solution you'd like Split the module management of the runtime and management side; remove the three-party tool class dependency package and outdated and unpopular class packages. The current dependencies are too bloated. In addition, the template engine recommends replacing with JSTL and EL.
Describe alternatives you've considered See the structure diagram below for details.
Additional context
Rqueue controller requires various rqueue system status, though it makes sense to separate them for the cases where they don;t need the dashboard. As per my observations people needs Dashboard most of the time for debugging.
For other dependencies, I understand we can build and use them, is it causing any issue or something for you?
Rqueue controller requires various rqueue system status, though it makes sense to separate them for the cases where they don;t need the dashboard. As per my observations people needs Dashboard most of the time for debugging.
For other dependencies, I understand we can build and use them, is it causing any issue or something for you?
For other users, we need to address the compatibility issues of tools such as Commons. In the future, if users' applications really need to use the new version of tools but the methods are removed, it will indirectly affect the stability and compatibility of rqueue.
Minimizing dependencies makes it easier to maintain and improve compatibility in the future.