Menu

#51 Startup error if model is renamed or deleted

open
nobody
5
2004-02-19
2004-02-19
No

If a model or any other service is renamed (e.g. it's id
changed), the "old" config/metadata is not cleared on the next
build. It is necessary to do an "ant clean", then a new
assemble-deploy to clear the problem.

The error is seen during startup as a "No class found matching
configuration name", followed by an error message whose
length rivals a small novel :-)

We need to either fix or at the least document this, as it is
entirely mysterious to the novice.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB