Community
Participate
Working Groups
Removing the configuration file for a JAXB RM from my workspace causes bad things to happen. Ideally this should remove the RM as well, but as a minimum the RM should deal with a missing config file better.
I've cleaned up the handling of this error in starting the RM and also in the Launch Tab. I'm not sure how one would automatically eliminate the RM from the list without breaking encapsulation in several places, so at this point the user is just warned to do it.
See also Bug 345108.