@craig: correct. and my services are Transient as well.

On Sep 30, 1:38 pm, Craig Neuwirt <[email protected]> wrote:
> And you use the WebSessionContext from nhib for GetCurrentSession()?
>
> On Wed, Sep 30, 2009 at 12:32 PM, Jason Meckley <[email protected]>wrote:
>
>
>
> > followup with my sessionadapter class (in case someone else tries to
> > use it). it appears that this is actually causing problems with my app
> > as a singleton. I didn't come across this until recently. the 2 "red
> > flags" where
> > 1. objectdisposedexception which occurred when the container was
> > disposed. the session adapter was disposed and tried to dispose the
> > session, which wasn't there.
> > 2. Future queries caused exceptions to throw about sqlstring
> > interceptors and List<> queries returned no results at all.
>
> > I did away with the adapter all together in favor of
> > container
> >        .AddFacility<FactorySupportFacility>()
> >        .Register(Component
> >                          .For<ISession>()
> >                          .Lifestyle.Is(LifestyleType.Transient)
> >                          .UsingFactoryMethod
> > (k=>k.Resolve<ISessionFactory>().GetCurrentSession()));
>
> > and transactions are managed with TransactionScope in web apps at the
> > beginning/ending of the request. this all feels much cleaner than
> > castle ATM and NH facility.
>
> > On Sep 28, 7:00 pm, petemounce <[email protected]> wrote:
> > > I set up my WindsorContainer by sub-classing, and performing
> > > registrations via FI-code within the constructor.  The constructor
> > > takes an XmlInterpreter as a parameter and passes this down to the
> > > base-class, which means I can do the bulk of my registrations in code,
> > > and override settings by using the config file (as long as I remember
> > > to name all my components - which I do :-)  ).
>
> > > That said, I've never had to actually _use_ that in production - but
> > > it's nice to have!
>
> > > Regards
> > > Pete
>
> > > On Sep 10, 7:06 pm, Nathan Stott <[email protected]> wrote:
>
> > > > I disagree.  Binsor, on several occasions, has saved me a lot of
> > headache by
> > > > allowing me to reconfigure my apps in production without having to
> > recompile
> > > > them.  Windsor Fl does not allow for this.
>
> > > > On Thu, Sep 10, 2009 at 2:02 PM, Ayende Rahien <[email protected]>
> > wrote:
> > > > > To be absolutely honest, with the Windsor FI, I am not sure there is
> > a lot
> > > > > of place for Binsor.
>
> > > > > On Thu, Sep 10, 2009 at 8:59 PM, rg <[email protected]>
> > wrote:
>
> > > > >> Please save the Binsor!
> > > > >> R
--~--~---------~--~----~------------~-------~--~----~
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