OAE Release and Email
Carl Hall
carl at hallwaytech.com
Mon Aug 15 13:39:10 PDT 2011
For those following along at home,
https://confluence.sakaiproject.org/display/KERNDOC/KERN-739+Dynamic+user+profiles
On Mon, Aug 15, 2011 at 3:35 PM, Ian Boston <ianboston at gmail.com> wrote:
> Doc is in kerndoc. Oszkar wrote it.
>
> Sent from my iPhone
>
> On 15 Aug 2011, at 20:22, Carl Hall <carl at hallwaytech.com> wrote:
>
> Well, never mind that. ProviderSettingsImpl binds to javax.jcr.Node. I can
> only assume this is so configuration can be added as initial content but
> there isn't any documentation stating this. I'll work on getting a JCR
> session in the smtp router.
>
>
>
> On Mon, Aug 15, 2011 at 3:18 PM, Carl Hall < <carl at hallwaytech.com>
> carl at hallwaytech.com> wrote:
>
>> In looking at using the ProfileService to get back the profile
>> information, I'm blocked by ProfileService's continued use of
>> javax.jcr.Session. From LiteSmtpRouter, I don't have a JCR session.
>> Also, ProviderSettingsFactory still uses a JCR session. If no one is against
>> it, I'll change ProviderSettingsFactory to use a sparse session which should
>> allow me to free up most of the other uses of a JCR session in
>> ProfileService and start binding to a sparse session. I'll keep the changes
>> to a minimum in hopes of cleaning up the JCR remnants in post-v1.
>>
>>
>> On Mon, Aug 15, 2011 at 1:32 PM, Carl Hall < <carl at hallwaytech.com>
>> carl at hallwaytech.com> wrote:
>>
>>> The ProfileService does seem like the right place to get the email but I
>>> still wonder about finding the email in some place outside of "basic". The
>>> quick fix is to look over the whole profile until an "email" field is found
>>> but that might not be the _right_ email field and could lead to a lot of
>>> digging. Should the search be depth or breadth first? Could find a different
>>> field depending on which we use. The bigger the profile the longer the
>>> search, too.
>>>
>>> If folks are fine with a profile scan to find an email outside of
>>> "basic", I can have a patch posted pretty soon. Otherwise, could there be
>>> defined a field that tells where to find a user's email address?
>>>
>>>
>>> On Mon, Aug 15, 2011 at 1:19 PM, Ray Davis < <ray at media.berkeley.edu>
>>> ray at media.berkeley.edu> wrote:
>>>
>>>> All very much MHO, but to me, the Profile Service seems like the right
>>>> place to abstract this. (It's pretty much the same requirement as met by
>>>> the Sakai CLE Kernel's User getEmail() API.) That would let the OAE put
>>>> a simple but not-as-efficient-as-possible implementation in for V1.0 and
>>>> then improve it.
>>>>
>>>> I wouldn't want to sink a lot of time into one particular optimization,
>>>> since AFAICT the whole area of email delivery needs more UX design
>>>> attention to meet requirements like preference-driven delivery
>>>> mechanisms and multiple email address for different contexts.
>>>>
>>>> Best,
>>>> Ray
>>>>
>>>> On 8/15/11 9:55 AM, Carl Hall wrote:
>>>> > That patch was a blind change to use the existing function which now
>>>> > shows that it hasn't been updated in ages. It will need updating based
>>>> > on this conversation and others.
>>>> >
>>>> > If the email address lives on the user (ie. basic info), then that's a
>>>> > quick lookup. If the email address lives somewhere else, we need some
>>>> > way to know where that is as scanning the whole profile doesn't seem
>>>> > feasible.
>>>> > Should there be a field somewhere that says, "here is where the system
>>>> > can find a user's email address"?
>>>> >
>>>> >
>>>> > On Mon, Aug 15, 2011 at 12:43 PM, Ian Boston < <ieb at tfd.co.uk>
>>>> ieb at tfd.co.uk
>>>> > <mailto: <ieb at tfd.co.uk>ieb at tfd.co.uk>> wrote:
>>>> >
>>>> > Looks like the patch [1] isnt looking at the user at all, its
>>>> looking
>>>> > at the profile and hoping that its being synced with the User.
>>>> >
>>>> > I suspect that this is due to the fact that no one really knows
>>>> where
>>>> > this information should be stored by default so we keep flip
>>>> flopping
>>>> > from one location to another depending on who made the last
>>>> commit,
>>>> > and if the moon was in a particular phase. (ie random). Is there
>>>> any
>>>> > documentation on what the standard is.... anywhere ?
>>>> >
>>>> > IMHO the patch should look at the user first, and if the
>>>> information
>>>> > is not there it should look at the profile, but we should not rely
>>>> on
>>>> > it being in the profile. This information is BasicUserInfo by
>>>> default.
>>>> >
>>>> > On 15 August 2011 16:31, N. Matthijs
>>>> > < <nicolaas.matthijs at caret.cam.ac.uk>
>>>> nicolaas.matthijs at caret.cam.ac.uk
>>>> > <mailto: <nicolaas.matthijs at caret.cam.ac.uk>
>>>> nicolaas.matthijs at caret.cam.ac.uk>> wrote:
>>>> > > Given that most institutions will move email out of the basic
>>>> > > info section, we should make sure that the patch is able
>>>> > > to find the email address in other profile sections as well.
>>>> > >
>>>> > > Nicolaas
>>>> > >
>>>> > >> <https://jira.sakaiproject.org/browse/KERN-2165>
>>>> https://jira.sakaiproject.org/browse/KERN-2165
>>>> > >>
>>>> > >>
>>>> > >> On Mon, Aug 15, 2011 at 7:50 AM, Carl Hall <<carl at hallwaytech.com>
>>>> carl at hallwaytech.com
>>>> > <mailto: <carl at hallwaytech.com>carl at hallwaytech.com>> wrote:
>>>> > >>
>>>> > >>> Is there a JIRA for this? I have a fix ready to be reviewed.
>>>> > >>>
>>>> > >>>
>>>> > >>> On Mon, Aug 15, 2011 at 5:49 AM, Ian Boston <<ieb at tfd.co.uk>
>>>> ieb at tfd.co.uk
>>>> > <mailto: <ieb at tfd.co.uk>ieb at tfd.co.uk>> wrote:
>>>> > >>>
>>>> > >>>> On 15 August 2011 06:26, David Roma <<david.roma.csu at gmail.com>
>>>> david.roma.csu at gmail.com
>>>> > <mailto: <david.roma.csu at gmail.com>david.roma.csu at gmail.com>>
>>>> wrote:
>>>> > >>>> > LOG.debug("Message is an SMTP Message,
>>>> getting
>>>> > email
>>>> > >>>> address
>>>> > >>>> > for the user {}", user.getId());
>>>> > >>>> > // TODO PersonalUtils not yet implemented
>>>> for
>>>> > Sparse
>>>> > >>>> > // String rcptEmailAddress =
>>>> > >>>> > PersonalUtils.getPrimaryEmailAddress(profileNode);
>>>> > >>>> > String rcptEmailAddress = "<someguy at example.com>
>>>> someguy at example.com
>>>> > <mailto: <someguy at example.com>someguy at example.com>";
>>>> > >>>>
>>>> > >>>>
>>>> > >>>> If this is in the current code base.... it must be a blocker
>>>> for a
>>>> > >>>> release
>>>> > >>>> ?
>>>> > >>>>
>>>> > >>>> Why didnt it get spotted earlier ?
>>>> > >>>> I did some testing a few weeks ago, and IIRC, once the user
>>>> > had set
>>>> > >>>> and email... it worked, but I could have been dreaming.
>>>> > >>>> Ian
>>>> > >>>> _______________________________________________
>>>> > >>>> sakai-ui-dev mailing list
>>>> > >>>> <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <mailto: <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org>
>>>> > >>>>
>>>> <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> > >>>>
>>>> > >>>
>>>> > >>>
>>>> > >>> _______________________________________________
>>>> > >>> sakai-ui-dev mailing list
>>>> > >>> <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <mailto: <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org>
>>>> > >>>
>>>> <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> > >>>
>>>> > >>>
>>>> > >>
>>>> > >>
>>>> > >> --
>>>> > >>
>>>> > >> Alan Marks
>>>> > >> Sakai OAE Project Director
>>>> > >> skype: skramnala
>>>> > >> _______________________________________________
>>>> > >> sakai-ui-dev mailing list
>>>> > >> <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <mailto: <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org>
>>>> > >>
>>>> <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> > >>
>>>> > >
>>>> > >
>>>> > > _______________________________________________
>>>> > > sakai-ui-dev mailing list
>>>> > > <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <mailto: <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org>
>>>> > > <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> > >
>>>> > _______________________________________________
>>>> > sakai-ui-dev mailing list
>>>> > <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <mailto: <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org>
>>>> > <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > sakai-ui-dev mailing list
>>>> > <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> > <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>>
>>>> _______________________________________________
>>>> sakai-ui-dev mailing list
>>>> <sakai-ui-dev at collab.sakaiproject.org>
>>>> sakai-ui-dev at collab.sakaiproject.org
>>>> <http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>>
>>>
>>>
>>
> _______________________________________________
> sakai-ui-dev mailing list
> sakai-ui-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>
>
> _______________________________________________
> sakai-ui-dev mailing list
> sakai-ui-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-ui-dev/attachments/20110815/934b9f64/attachment-0001.html
More information about the sakai-ui-dev
mailing list