Thx!
On Feb 11, 7:07 pm, Craig Neuwirt cneuw...@gmail.com wrote:
It needs to be an IContractBehavior to ensure that it is propertly applied
to the operations at the right time during channel or service host
initialization
On Wed, Feb 11, 2009 at 4:28 AM, Tavo gustavo.rin...@gmail.com wrote:
Craig talking about this, i have seen that you set the UnitOfWork
Behavior as an IEndpointBehavior.
I have seen others doing it as an IContractBehavior or
IServiceBehavior.
Can you tell what was your consideration to decide going for this
instead of the others?
Thanks.
Gustavo.
On Feb 10, 3:57 pm, Craig Neuwirt cneuw...@gmail.com wrote:
They are independent. You should be able to configure them
independently.
I suspect what you are looking for is how to manage session/transaction
scope per request. If you look at the WcfFacility tests you will find a
UnitOfWorkBehavior which shows you how to create the plumbing you need.
For
AR, you will just need to create a new SessionScope/TransactionScope in
the
BeforeInvoke and Dispose it in the AfterInvoke.
On Tue, Feb 10, 2009 at 4:41 AM, crios...@gmail.com crios...@gmail.com
wrote:
Hey guys,
Can anyone provide working snippet for integration AR and WCF services
using windsor container (facility perhaps?) for PerCall (per request)
model?..
Thank you in advance! :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Castle Project Users group.
To post to this group, send email to castle-project-users@googlegroups.com
To unsubscribe from this group, send email to
castle-project-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~--~~~~--~~--~--~---