Now that I wrote this, it becomes clear how bad this idea is - still it
would be nice, if you could reply to my questions above...

On Fri, May 21, 2010 at 3:50 PM, Jan Limpens <[email protected]> wrote:

> Whew, that's a bit complicated...
> All my (saga) messages implement ISagaMessage, so I should not have to to
> implement ISagaFinder. Isn't this already baked in, supposing there is an
> NHibernateSagaPersister<T> : ISagaPersister<T>?
>
> As I found out, every ISaga state needs to implement IAccessibleSaga, so
> this rules out my Order entity as I want to keep my domains poco.
>
> So my current idea is to create another nhibernate entity, pointing to the
> very same orders table, pointing to the state column (shared between the 2
> entities) and adding two cols for the required IAccessibleSaga properties.
> Quite hackish, I suppose, but it would help me to keep the order's state
> property read only and allow changes only via the saga.
>
>
>
> On Fri, May 21, 2010 at 1:46 PM, Ayende Rahien <[email protected]> wrote:
>
>> IIRC, check ISagaFinder
>>
>> On Fri, May 21, 2010 at 7:36 PM, Jan Limpens <[email protected]>wrote:
>>
>>> Ok, so my ISaga<Order> handles the Order's states. Order is an entity.
>>> The state is initializes, the saga received a CorrelationId.
>>>
>>> Some days later somebody, interactively wants to change some order's
>>> state.
>>> How would he send the message?
>>>
>>> Should I give the order entity a CorrelationId property, pass it in at
>>> saga initialization?
>>> Then later, I would get my order from the repo and send ISagaMessage with
>>> its CorrelationId?
>>>
>>> Just rechecking to make no basic mistakes, early on...
>>>
>>> Thanks!
>>> --
>>> Jan
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Rhino Tools Dev" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected]<rhino-tools-dev%[email protected]>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/rhino-tools-dev?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Rhino Tools Dev" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<rhino-tools-dev%[email protected]>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/rhino-tools-dev?hl=en.
>>
>
>
>
> --
> Jan
>



-- 
Jan

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" 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/rhino-tools-dev?hl=en.

Reply via email to