...
[11:09:11 CDT(-0500)] <EricDalquist> then it is order dependent
[11:09:18 CDT(-0500)] <b-cause> maybe we need to change it to MultivaluedAttributeMerger?
[11:09:24 CDT(-0500)] <EricDalquist> later DAOs in the personAttributeDaos list
[11:09:31 CDT(-0500)] <EricDalquist> replace attributes from earlier
[11:09:51 CDT(-0500)] <b-cause> ok I see that the requestAttributesDao is not in that list, should I add it?
[11:10:08 CDT(-0500)] <b-cause> right now theldapAttributeSource is last in the list.
[11:10:21 CDT(-0500)] <b-cause> with AccountUserSource and JdbcUserSource before it
[11:10:32 CDT(-0500)] <EricDalquist> so requestAttributesDao is never included anywhere?
[11:11:14 CDT(-0500)] <b-cause> it is included in the requestAttributeMergingDao
[11:11:28 CDT(-0500)] <EricDalquist> ok so you probably need to restructure things a bit
[11:11:44 CDT(-0500)] <EricDalquist> so that it is referenced in the same merging dao that contains the other attributes
[11:11:52 CDT(-0500)] <b-cause> I see that is part of the personAttributeDao which I guess is used in person attrs swapper.
[11:12:18 CDT(-0500)] <EricDalquist> gotta run to a meeting ... back in ~30
[11:12:25 CDT(-0500)] <b-cause> ok. thanks Eric
[12:31:38 CDT(-0500)] <b-cause> Hi EricDalquist. I"m not sure if you have a second to look at this http://pastebin.com/rjfHWCuh but its our personDirectoryConfirguration.xml . when I log in, I can see attributes that were only available to me through the RequestAttributeSourceFilter, but all of the other attributes are being reffed from the ldap source.
[14:00:36 CDT(-0500)] <b-cause> ok EricDalquist. I think those configuration tips for the personDirectoryContext.xml are working now. Thanks for your help.