> *I don't see how the registration would ever be persisted to the database > via the ConferenceRepository*. I don't have 2008 so I can't run this, I'm > just looking at all these files in Notepad. I've walked it several times > and can't figure out how the database would ever be hit with the attendee > (person) information.
On Tue, May 6, 2008 at 7:04 PM, Ben Scheirman <subdigi...@gmail.com> wrote: > this discussion is probably better had over at the codecampserver list, > which I have copied in this email.
> On Tue, May 6, 2008 at 11:18 AM, Tim Barcz <timba...@gmail.com> wrote:
> > I'm looking at something in code camp server and need your help.
> > I can't see how an attendee ever get's registered for a conference.
> > If you look at the code in *ConferenceService *you'll see
> > *I don't see how the registration would ever be persisted to the > > database via the ConferenceRepository*. I don't have 2008 so I can't > > run this, I'm just looking at all these files in Notepad. I've walked it > > several times and can't figure out how the database would ever be hit with > > the attendee (person) information.
I thought it was, but I just have to look into it.
I should mention that I've been looking to eliminate ConferenceService altogether, because it seemed to just mimic what the repository was doing. It still has some unique functionality that I don't see a better home for, so it stays for now.
Feel free to submit a patch. :)
On Tue, May 6, 2008 at 12:22 PM, Simone Chiaretta <
simone.chiare...@gmail.com> wrote: > I had the same problem a few days ago... I don't think the db persistence > is already implemented for this feature > Simo
> On Tue, May 6, 2008 at 7:04 PM, Ben Scheirman <subdigi...@gmail.com> > wrote:
> > this discussion is probably better had over at the codecampserver list, > > which I have copied in this email.
> > On Tue, May 6, 2008 at 11:18 AM, Tim Barcz <timba...@gmail.com> wrote:
> > > I'm looking at something in code camp server and need your help.
> > > I can't see how an attendee ever get's registered for a conference.
> > > If you look at the code in *ConferenceService *you'll see
> > > *I don't see how the registration would ever be persisted to the > > > database via the ConferenceRepository*. I don't have 2008 so I can't > > > run this, I'm just looking at all these files in Notepad. I've walked it > > > several times and can't figure out how the database would ever be hit with > > > the attendee (person) information.
after looking at it again, there is a way that this is persisted, but I'm not 100% positive that it's being done yet.
Basically we've made a change to a persistent object's collection (conference.Attendees). The session that lives for our entire request gets flushed when the request is served, so the attendee might get saved.
Again I have to confirm this, but it's a possibility.
On Tue, May 6, 2008 at 12:35 PM, Ben Scheirman <subdigi...@gmail.com> wrote: > I thought it was, but I just have to look into it.
> I should mention that I've been looking to eliminate ConferenceService > altogether, because it seemed to just mimic what the repository was doing. > It still has some unique functionality that I don't see a better home for, > so it stays for now.
> Feel free to submit a patch. :)
> On Tue, May 6, 2008 at 12:22 PM, Simone Chiaretta < > simone.chiare...@gmail.com> wrote:
> > I had the same problem a few days ago... I don't think the db > > persistence is already implemented for this feature > > Simo
> > On Tue, May 6, 2008 at 7:04 PM, Ben Scheirman <subdigi...@gmail.com> > > wrote:
> > > this discussion is probably better had over at the codecampserver > > > list, which I have copied in this email.
> > > On Tue, May 6, 2008 at 11:18 AM, Tim Barcz <timba...@gmail.com> wrote:
> > > > I'm looking at something in code camp server and need your help.
> > > > I can't see how an attendee ever get's registered for a conference.
> > > > If you look at the code in *ConferenceService *you'll see
> > > > *I don't see how the registration would ever be persisted to the > > > > database via the ConferenceRepository*. I don't have 2008 so I > > > > can't run this, I'm just looking at all these files in Notepad. I've walked > > > > it several times and can't figure out how the database would ever be hit > > > > with the attendee (person) information.
On Tue, May 6, 2008 at 12:37 PM, Ben Scheirman <subdigi...@gmail.com> wrote: > after looking at it again, there is a way that this is persisted, but I'm > not 100% positive that it's being done yet.
> Basically we've made a change to a persistent object's collection > (conference.Attendees). The session that lives for our entire request gets > flushed when the request is served, so the attendee might get saved.
> Again I have to confirm this, but it's a possibility.
> On Tue, May 6, 2008 at 12:35 PM, Ben Scheirman <subdigi...@gmail.com> > wrote:
>> I thought it was, but I just have to look into it.
>> I should mention that I've been looking to eliminate ConferenceService >> altogether, because it seemed to just mimic what the repository was doing. >> It still has some unique functionality that I don't see a better home for, >> so it stays for now.
>> Feel free to submit a patch. :)
>> On Tue, May 6, 2008 at 12:22 PM, Simone Chiaretta < >> simone.chiare...@gmail.com> wrote:
>>> I had the same problem a few days ago... I don't think the db persistence >>> is already implemented for this feature >>> Simo
>>> On Tue, May 6, 2008 at 7:04 PM, Ben Scheirman <subdigi...@gmail.com> >>> wrote:
>>>> this discussion is probably better had over at the codecampserver list, >>>> which I have copied in this email.
>>>> On Tue, May 6, 2008 at 11:18 AM, Tim Barcz <timba...@gmail.com> wrote:
>>>>> I'm looking at something in code camp server and need your help.
>>>>> I can't see how an attendee ever get's registered for a conference.
>>>>> If you look at the code in *ConferenceService *you'll see
>>>>> public Person RegisterAttendee(string firstName, string >>>>>> lastName, string emailAddress, string website, string comment, Conference >>>>>> conference, string cleartextPassword) >>>>>> { >>>>>> var passwordSalt = _cryptoUtil.CreateSalt(); >>>>>> var encryptedPassword = >>>>>> _cryptoUtil.HashPassword(cleartextPassword, passwordSalt);
>>>>>> var person = new Person(firstName, lastName, emailAddress) >>>>>> { >>>>>> Website = website, >>>>>> Comment = comment, >>>>>> PasswordSalt = passwordSalt, >>>>>> Password = encryptedPassword >>>>>> };
>>>>>> conference.AddAttendee(person);
>>>>>> return person; >>>>>> }
>>>>> This is called from the *ConferenceController
>>>>> *
>>>>>> public ActionResult Register(string conferenceKey, string >>>>>> firstName, string lastName, string email, string website, >>>>>> string comment, string password) >>>>>> { >>>>>> try >>>>>> { >>>>>> //register the attendee >>>>>> var conference = >>>>>> _conferenceService.GetConference(conferenceKey); >>>>>> var person = >>>>>> _conferenceService.RegisterAttendee(firstName, lastName, email, website, >>>>>> comment,
>>>>>> conference, password);
>>>>>> //sign them in >>>>>> ViewData.Add(person).Add(new Schedule(conference, >>>>>> _clock, null, null)); >>>>>> return RenderView("registerconfirm"); >>>>>> } >>>>>> catch (Exception exc) >>>>>> { >>>>>> TempData[TempDataKeys.Error] = "An error occurred >>>>>> while registering your account."; >>>>>> Log.Error(this, "An error occcurred while registering >>>>>> a user", exc); >>>>>> return RenderView("pleaseregister"); >>>>>> } >>>>>> }
>>>>> *I don't see how the registration would ever be persisted to the >>>>> database via the ConferenceRepository*. I don't have 2008 so I can't >>>>> run this, I'm just looking at all these files in Notepad. I've walked it >>>>> several times and can't figure out how the database would ever be hit with >>>>> the attendee (person) information.
>>> -- >>> Simone Chiaretta >>> codeclimber.net.nz >>> Any sufficiently advanced technology is indistinguishable from magic >>> "Life is short, play hard"
