Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Custom Configuration always go to Third Party Secton
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();
}
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.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™