I'm targetting three different scenarios:

1) Operations department add event listeners at runtime, i.e. e-mail
notifications of updates and deletes. This requires Windsor
integration.
2) Event listeners are part of the model itself.
2a) The listeners are explicitly created for that model and are part
of the model's functionality. The listeners should be created with the
EventListenerAttribute and are automatically part of the model (given
that the assembly is used in initialization instead of single types).
2b) The listeners are part of a reusable library (auditing library
etc.). But the definition of the listeners should be part of the
model, not part of the application. The latter is because a model can
be used by different applications (CLI, GUI, Web (Service)) and should
behave consistently without making assumptions on the initialization
of AR on the application's code. This is what the assembly attributes
are for.

-Markus

2009/1/20 hammett <[email protected]>:
>
> Looks fantastic. I just wonder to whom decision of an event
> registration is important? The app or the model should make the call?
> If it's the app, I would specify them through ARStarter.Initialize,
> instead of looking for assembly level attributes. If it's the model,
> then assembly lvl attributes seems better.
>
>
>
> On Mon, Jan 19, 2009 at 11:04 AM, Markus Zywitza
> <[email protected]> wrote:
>>
>> Hi all
>>
>> I'm planning to support NH 2.x event system in ActiveRecord and have
>> created a specification document for this:
>> http://using.castleproject.org/display/AR/NHEventListenerSpecs
>>
>> Please tell me what you think and if you have any other needs
>> regarding the NH event architecture.
>>
>> -Markus
>>
>> >
>>
>
>
>
> --
> Cheers,
> hammett
> http://hammett.castleproject.org/
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to