Read-only errors trying to use MDS in JDeveloper 11.1.1.4.0

Question

JDeveloper 11.1.1.4.0
I'm trying to set up MDS in our application using the usual docs, cue cards and blog posts.
We use our own LDAP-based authentication, which we'll set up later. In the meantime, I have a custom UserCC class which just returns one user name.
In the adf-config.xml setup, in "View", I set to track column.
In the code I have println statements for each method, my UserCC constructor is called.
When I rearrange the order of columns, I get the following error messages in my console:
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.No other messages or indicators that other forum posts mention, nothing with any more details.
Here is my UserCC code, built as part of my Models project, put in ...\jdeveloper\jdev\lib\patches
package oracle.documaker.idocumaker.model;
import oracle.mds.core.MetadataObject;
import oracle.mds.core.RestrictedSession;
import oracle.mds.cust.CacheHint;
import oracle.mds.cust.CustomizationClass;
public class UserCC extends CustomizationClass {
    private static final String DEFAULT_LAYER_NAME = "user";
    private String mLayerName = "user";
    public UserCC() {
        System.out.println("XXX In the UserCC Constructor");
    public CacheHint getCacheHint() {
        System.out.println("XXX In the UserCC getCacheHint");
        return CacheHint.USER;
    public String getName() {
        System.out.println("XXX In the UserCC getName");
        return mLayerName;
    public String[] getValue(RestrictedSession sess, MetadataObject mo) {
        System.out.println("XXX I was asked about the user name");
        return (new String[] { "alanabrams" });
}

Answer 1

We've always had security on, the only thing that changed was my understanding of how we were doing security.
Before, I had written a custom UserCC that always returned the same name, after I used the standard UserCC. I had the same results both time.
The cause of my error message is "MDS repository may be configured incorrectly", which I kind of figured, but there's nothing to point me to diagnose how it is incorrectly configured or how to fix it.