This is not the uNhAddIns group.
btw it is because:
              /// <summary>
                /// Fixed Conversation's Id for the target class.
                /// </summary>
                /// <remarks>
                /// Optional.
                /// <para>
                /// Only use it when multiple instances of the target class
must work in the same conversation.
                /// </para>
                /// </remarks>
                public string ConversationId { get; set; }

                /// <summary>
                /// Conversation's Id prefix.
                /// </summary>
                /// <remarks>
                /// Optional.
                /// <para>
                /// The result conversation's Id will be composed by
IdPrefix + UniqueId
                /// </para>
                /// </remarks>
                public string IdPrefix { get; set; } that with
//<summary>
                /// Define the class where conversation's events handlers
are implemented.
                ///</summary>
                /// <remarks>
                /// The class must implements
IConversationCreationInterceptor.
                /// </remarks>
                public Type ConversationCreationInterceptor { get; set; } or
with
            /// <summary>
                /// Use the IoC container to discover the implementor of
IConversationCreationInterceptorConvention{T}
                /// where T is the class indicated by <seealso
cref="PersistenceConversationalAttribute"/>.
                /// </summary>
                public bool UseConversationCreationInterceptorConvention {get
; set; }
and the properly adapter, will give you the ability to implements a custom
CreationInterceptor and intercept all actions/event (as for example the
OnException to manage StaleObjectStateException).
Basically the reason of the string is to give you the ability to recognize a
conversation for a specific Service or group of services.
On Tue, Sep 21, 2010 at 2:53 AM, pvginkel <[email protected]> wrote:

> I've looked at the uNhAddins conversation convention example and I
> can't figure out why the conversation referenced is passed as a
> string. This looks like a weak reference construct, and we have a
> WeakReference class for that.
>
> Could somebody explain the reason conversation ID's are passed as
> strings and not as a reference or a WeakReference?
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>


-- 
Fabio Maulo

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" 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/nhusers?hl=en.

Reply via email to