I ran into the same issue.

After digging around I found this:
http://stackoverflow.com/questions/1038914/using-castle-windsor-and-the-nhibernate-facility-on-shared-hosting

Basically you have to change the ActivityManager. Just register a one
in the config.
<component id="activityManager"
service="Castle.Services.Transaction.IActivityManager,
Castle.Services.Transaction"
type="Castle.Services.Transaction.TLSActivityManager,
Castle.Services.Transaction" />

I should say as well, that adding the above in the config solved that
particular problem, but now I am getting permission issues
SessionWebModule tries to access the SessionStore.

Joe


On Jun 25, 2:45 am, Keith Bloom <[email protected]> wrote:
> I'm attempting to use Windsor andNHibernatein amediumtrust
> environment and I'm running up against some problems with
> permissions.
>
> I have compiled the binaries to allow partialtrustcallers and this
> got me a long way. What has stopped me, is a dependency on the
> Castle.Service.Transations assembly when the container starts up. This
> tries to creates an instance of:
>
> Castle.Services.Transaction.CallContextActivityManager()
>
> When this happens a security exception is raised as
> CallContextActivityManager() tires to call
> System.Runtime.Remoting.Messaging.CallContext.SetData() which is only
> allowed if you have infrastructure permission. I'm guessing 
> thatmediumtrustapps don't.
>
> I haven't reference Castle.Service.Transaction anywhere but I assume
> theNHibernatefacilityuses it.  Does anyone know a way around
> this?
>
> Should I dump the HNibernatefacilityand wire it up manually?
>
> Thanks, Keith.

--~--~---------~--~----~------------~-------~--~----~
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