You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It is now quite hard to detect if a droplet is targeted wrong, i.e. target class and/or method doesn't exist anymore or there is a mistake in droplet itself.
Describe the solution you'd like
It would be nice to make jMint somehow inform the user about such mismatch after the startup of the application. The feature should be switchable, i.e. the user should have a way to turn it off in order to support postponed class loading (e.g. in servlet containers)
Describe alternatives you've considered
There is currently no alternatives except of manual checking the behavior.
Additional context
Probably the feature should be implemented with the help of additional droplet that would inform jMint about the end of the startup routines.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It is now quite hard to detect if a droplet is targeted wrong, i.e. target class and/or method doesn't exist anymore or there is a mistake in droplet itself.
Describe the solution you'd like
It would be nice to make jMint somehow inform the user about such mismatch after the startup of the application. The feature should be switchable, i.e. the user should have a way to turn it off in order to support postponed class loading (e.g. in servlet containers)
Describe alternatives you've considered
There is currently no alternatives except of manual checking the behavior.
Additional context
Probably the feature should be implemented with the help of additional droplet that would inform jMint about the end of the startup routines.
The text was updated successfully, but these errors were encountered: