allowedAttributes not being stored

[Robert Lewis]

Hi Scott,

First background, when I used StubPersonAttributeDao per the user's
manual, I did see the backingMap attributes in the multi-valued dropdown
when I add the service. As a test, I selected a couple of the attributes
as allowed attributes. Then, I could use discovery to look in the mysql
db and see the service and all fields looked normal, except the allowed
attributes field had binary stuff in it. Finally, I used a log message
to list the allowed attributes retrieved by getAlowedAttributes(), and
it showed no allowed attributes being retrieved.

Then I changed the attributeRepository bean class to
MultiRowJdbcPersonAttributeDao as previously described, which has the
attribute map in property named nameValueColumnMappings.

Using this class for the attributeRepository bean, the behavior I am
observing when I add a service is the multi-valued dropdown has nothing
in it.

I guess hibernate is not picking up the attribute map. I need some help
on configuring this, any help would be appreciated.

Thanks,

Robert Lewis


> Robert,
> This may seem like a completely dumb question but when you view the
> service
> in the Services Management tool, before you save it, are you selecting
> the
> attributes in the multi-valued dropdown and then pressing save?

> AttributeRepository is used to display the list of potential
> attributes a
> service could access, while the Services Management tool allows you to
> select which ones it actually can access.

> -Scott