Thanks for the feedback
Looking at the WCF Facility I can see how the logging facility was
initialized using the
container.Kernel.ConfigurationStore.AddFacilityConfiguration( )
method.
And I can see your pain for implementing the same for the
NHibernateIntegration facililty.
For now I'll use the normal config file and just configure the rest in
code.
I guess something like the following could work to fluently configure
the facilities so that they function similar to the WCF facility.
container
.AddFacility<LoggingFacility>(f => {
f.LoggingApi =
LoggerImplementation.Log4net;
f.ConfigFile =
"log4net.config";
})
.AddFacility<NHibernateFacility>(f => {
f.IsWeb =
false;
f.ConfigFile
= "nhibernate.config";
})
On Jun 24, 1:29 pm, Tuna Toksoz <[email protected]> wrote:
> Currently there is no easy way, it is on my to do list tho.
>
> You can use container.Kernel.ConfigurationStore.AddFacilityConfiguration( )
> method to do it. This will be what the fluent interface is going to do.
>
> Tuna Toksöz
> Eternal sunshine of the open source mind.
>
> http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/tehlike
>
>
>
>
>
> On Wed, Jun 24, 2009 at 2:10 PM, Paladin_za <[email protected]> wrote:
> > NHibernateFacility
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
