RE: Custom Configuration always go to Third Party Secton

thumbnail
Jamie Sammons, modified 3 Years ago. New Member Posts: 7 Join Date: 3/19/15 Recent Posts

I am on DXP 7.2

I am using custom configurations mostly on System scope in our project.  But no matter what category I give in @ExtendedObjectClassDefinition annotation. My configuration always ends up under Platform -> Third Party. 

I have tried with existing categories such as "blogs" and will my custom ConfigurationCategory as well. Can someone help me with what am I doing wrong?

package com.abc.configuration;

import com.liferay.portal.configuration.metatype.annotations.ExtendedObjectClassDefinition;

import aQute.bnd.annotation.metatype.Meta;

@ExtendedObjectClassDefinition(scope = ExtendedObjectClassDefinition.Scope.PORTLET_INSTANCE, category="blogs")
@Meta.OCD(id = "com.abc.portlet.instance.configuration", name = "ABC Portlet Configuration")
public interface ABCPortletInstanceConfiguration {

    @Meta.AD(optionLabels = { "A", "B", "C" }, optionValues = { "a", "b",
            "c" }, required = false, deflt = "a")
    public String feature();
}

 

thumbnail
Jamie Sammons, modified 3 Years ago. New Member Posts: 7 Join Date: 3/19/15 Recent Posts

My bad, I did not keep the configuration id as the fully qualified class name of configuration class, due to which ExtendedObjectClassDefinition which as the name suggests reads confiugration definition from the class was not working.