David Sean Taylor <david <at> bluesunrise.com> writes: > > We *can* change the API.... > It seems like the UserInfoManger API is a bit empty anyway. > IMO, I'd prefer something more like the Portlet API's preferences: get a > map, and edit the map, and then have a store() method. Seems wasteful to > have atomic updates everytime you put a property. The more I see the > Java Prefs api, the less I like it. > > I'd like to see a User Info impl that persists to LDAP > Willing to work with you on this, change the API to suit your needs, its > up to you.... >
David, I don't think I will have any time to work on a generalized solution until sometime in the new year. I have a pretty tight deadline to get version one of our portal out the door. I think some discussion would have to take place as to what kind of schema would be needed to support this anyway. In the mean time, I suggest you guys only change the API if you think feel that it needs it. If you prefer to leave it as is for now so that you can focus on getting j2 final out the door, then by all means. I will work with whatever. cheers, aaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
