On Thu, Dec 10, 2015 at 3:55 PM, Michael Perelman < mikhail_perel...@hotmail.com> wrote:
> hi. i am running 2.0.0M17 in regular (i.e. not embedded) mode, and i would > like to introduce my own custom interceptor. i am trying to model it after > the OOTB AuthenticationInterceptor, so mine will contain a password policy > bearing several attributes that will be configurable via Apache Studio. > after digging around through the source, i came across PasswordPolicyBean > class that is apparently populated with the values from such attributes. > the problem is that i am unable to determine as to how the attributes' > values get propagated to this class. i noticed that each such attribute is > represented with a respective variable tagged with > @ConfigurationElement(attributeType = "attribute-name", isOptional = true, > defaultValue = "some-val"). if i were to introduce my own > MyPasswordPolicyBean class, would it be enough to just create variables > with the same @ConfigurationElement tags, or do i need to perform > additional steps in order for those variables to be populated with their > respective attribute values? > for this annotation to work you need to add a new config element in config schema, then server will automatically populate the values in the new bean > > thanks! > -- Kiran Ayyagari http://keydap.com
