In fact, it's the above commit (c2d7115109021) and the changes made to this file:
src/Castle.Windsor/Core/DependencyModelCollection.cs On Jun 27, 5:47 pm, Henrik <[email protected]> wrote: > This is the commit that broke interceptors: > > https://github.com/castleproject/Castle.Windsor/commit/c2d7115109021 > > On Jun 27, 5:27 pm, Henrik <[email protected]> wrote: > > > > > > > > > ...besides that, the tag 2.5.1 doesn't contain the namespace: > > Castle.Facilities.TypedFactory > > > so I couldn't just checkout the correct tag, but have to manually test > > my way forward... > > > We should set up a proper tagging system, imo, so that source can be > > correlated with packages. > > > On Jun 27, 5:25 pm, Henrik <[email protected]> wrote: > > > > I have started the debugging ritual... > > > > I can state that commit > > > 31be4bb4305dd54813f7 > > > contains the problem. > > > > Moving on... > > > > On Jun 23, 11:57 am, Henrik <[email protected]> wrote: > > > > > You will have to downgrade it till we have solved this problem, or you > > > > will have to solve it yourself. We accept pull requests. > > > > > On top of things, the NHibernate Facility that you are using is in > > > > beta at the moment, but has no known bugs. I am working as much as I > > > > can with respect to other committments, to make both Tx, AutoTx and > > > > NHFac GA-releases. > > > > > Cheers, > > > > Henrik > > > > > On Jun 20, 10:45 am, Berke Sokhan <[email protected]> wrote: > > > > > > I also tried to gather all Castle projects to one solution to see > > > > > what is > > > > > failing but w/o success. > > > > > > Got all sources from git/castleproject source and > > > > > git/haf/castle.facilities.nhibernate built them. But NH facility uses > > > > > Windsor 2.5.1, and I dont want to downgrade to it. I already spent > > > > > too much > > > > > time try to integrate the new nh facility. I also noticed old > > > > > NHIntegration > > > > > facility uses an old version of Castle. > > > > > > So may I ask you guys, to achive* session-per-call/tx-per-call > > > > > nhibernate > > > > > WCF application server (that is not using IIS or httpbinding), > > > > > excluding > > > > > nhfacilities and including wcf facility*... > > > > > > Can you guide me to a best practice? > > > > > > 2011/6/18 Henrik Feldt <[email protected]> > > > > > > > Hmm, I don’t know how to fix this properly... **** > > > > > > > ** ** > > > > > > > The only work-around so far for me is to downgrade Windsor to > > > > > > 2.5.1. That > > > > > > works. I suggested that some of the improvements from v3 might be > > > > > > back-ported to change some of the bits in Windsor and make it go > > > > > > away.**** > > > > > > > ** ** > > > > > > > Henrik**** > > > > > > > ** ** > > > > > > > *From:* [email protected] [mailto: > > > > > > [email protected]] *On Behalf Of *Berke Sokhan > > > > > > *Sent:* den 16 juni 2011 14:11 > > > > > > *To:* [email protected] > > > > > > > *Subject:* Re: Problem with Windsor null reference exception**** > > > > > > > ** ** > > > > > > > My stack looks same with Henrik: > > > > > > > at System.Collections.ObjectModel.Collection`1.Add(T item) > > > > > > at > > > > > > Castle.Facilities.AutoTx.TransactionalComponentInspector.AddInterceptor(ComponentModel > > > > > > model) in > > > > > > d:\Builds\Castle.Transactions-beta\src\Castle.Facilities.AutoTx\TransactionalComponentInspector.cs:line > > > > > > 78 > > > > > > at > > > > > > Castle.Facilities.AutoTx.TransactionalComponentInspector.ProcessModel(IKernel > > > > > > kernel, ComponentModel model) in > > > > > > d:\Builds\Castle.Transactions-beta\src\Castle.Facilities.AutoTx\TransactionalComponentInspector.cs:line > > > > > > 46 > > > > > > at > > > > > > Castle.MicroKernel.ModelBuilder.DefaultComponentModelBuilder.BuildModel(String > > > > > > key, Type service, Type classType, IDictionary extendedProperties) > > > > > > in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\ModelBuilder\DefaultComponentModelBuilder.cs:line > > > > > > 67 > > > > > > at > > > > > > Castle.MicroKernel.Registration.ComponentRegistration`1.Castle.MicroKernel.Registration.IRegistration.Register(IKernel > > > > > > kernel) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\Registration\ComponentRegistration.cs:line > > > > > > 904 > > > > > > at Castle.MicroKernel.DefaultKernel.Register(IRegistration[] > > > > > > registrations) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\DefaultKernel.cs:line > > > > > > 595 > > > > > > at > > > > > > Castle.MicroKernel.Registration.BasedOnDescriptor.TryRegister(Type > > > > > > type, IKernel kernel) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\Registration\BasedOnDescriptor.cs:line > > > > > > 208 > > > > > > at > > > > > > Castle.MicroKernel.Registration.FromDescriptor.Castle.MicroKernel.Registration.IRegistration.Register(IKernel > > > > > > kernel) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\Registration\FromDescriptor.cs:line > > > > > > 96 > > > > > > at > > > > > > Castle.MicroKernel.Registration.BasedOnDescriptor.Castle.MicroKernel.Registration.IRegistration.Register(IKernel > > > > > > kernel) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\Registration\BasedOnDescriptor.cs:line > > > > > > 325 > > > > > > at Castle.MicroKernel.DefaultKernel.Register(IRegistration[] > > > > > > registrations) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\MicroKernel\DefaultKernel.cs:line > > > > > > 595 > > > > > > at Castle.Windsor.WindsorContainer.Register(IRegistration[] > > > > > > registrations) in > > > > > > e:\OSS.Code\Castle.Windsor\src\Castle.Windsor\Windsor\WindsorContainer.cs:line > > > > > > 689 > > > > > > at PayFlex.Vpos.Server.Container.Bootstrapper.Initialize() in > > > > > > D:\SVN > > > > > > Repositories\iPayVPOS\trunk\PayFlex.Vpos\PayFlex.Vpos.Server.Container\Bootstrapper.cs:line > > > > > > 32 > > > > > > at PayFlex.Vpos.Server.Application.Program.Main() in D:\SVN > > > > > > Repositories\iPayVPOS\trunk\PayFlex.Vpos\PayFlex.Vpos.Server.Application\Program.cs:line > > > > > > 19 > > > > > > at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, > > > > > > String[] > > > > > > args) > > > > > > at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence > > > > > > assemblySecurity, String[] args) > > > > > > at > > > > > > Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() > > > > > > at System.Threading.ThreadHelper.ThreadStart_Context(Object > > > > > > state) > > > > > > at System.Threading.ExecutionContext.Run(ExecutionContext > > > > > > executionContext, ContextCallback callback, Object state, Boolean > > > > > > ignoreSyncCtx) > > > > > > at System.Threading.ExecutionContext.Run(ExecutionContext > > > > > > executionContext, ContextCallback callback, Object state) > > > > > > at System.Threading.ThreadHelper.ThreadStart() > > > > > > > I am using Henrik's version of Transactions/AutoTx lib coming with > > > > > > new NH > > > > > > Facility. > > > > > > > And I get this exception when registering some POCO service class > > > > > > which > > > > > > have "Transactional" attribute on it (removing attr. prevents > > > > > > exception, but > > > > > > nh facility need it to open injected session). > > > > > > > My early impression was AutoTx has some bug in inspecting > > > > > > attributes, maybe > > > > > > a null check before adding to interceptors collection obviously ... > > > > > > > Will look at source and try to point exact location. > > > > > > > **** > > > > > > > 2011/6/16 Krzysztof Koźmic <[email protected]>**** > > > > > > > If you can reproduce it in a way that points to some reasonable bug > > > > > > in > > > > > > Windsor or elsewhere... > > > > > > > I looked at it when Henrik originally reported it but other than > > > > > > "that's > > > > > > bizarre it can't be happening" I didn't find any good explanation > > > > > > for that. > > > > > > > Krzysztof**** > > > > > > > On 16/06/2011 8:47 AM, Berke Sokhan wrote: **** > > > > > > > Any news on this one? I am getting it too. > > > > > > > Without a resolution to this, whole new Castle.Facilities.AutoTx / > > > > > > Castle.Services.Transactions / Castle.Facilities.NHibernate trilogy > > > > > > become > > > > > > useless :(**** > > > > > > > 2011/5/6 Henrik <[email protected]>**** > > > > > > > I was wondering if I could get some help debugging this exception? > > > > > > > TearDown : System.NullReferenceException : Object reference not set > > > > > > to > > > > > > an instance of an object. > > > > > > at System.Collections.ObjectModel.Collection`1.Add(T item) > > > > > > > at > > > > > > Castle.Facilities.AutoTx.TxComponentInspector.AddInterceptor(ComponentModel > > > > > > model) > > > > > > at > > > > > > Castle.Facilities.AutoTx.TxComponentInspector.ProcessModel(IKernel > > > > > > kernel, ComponentModel model) > > > > > > > at > > > > > > > Castle.MicroKernel.ModelBuilder.DefaultComponentModelBuilder.BuildModel(String > > > > > > key, Type service, Type classType, IDictionary extendedProperties) > > > > > > at > > > > > > > Castle.MicroKernel.Registration.ComponentRegistration`1.Castle.MicroKernel.Registration.IRegistration.Register(IKernel > > > > > > kernel) > > > > > > > at Castle.MicroKernel.DefaultKernel.Register(IRegistration[] > > > > > > registrations) > > > > > > at Castle.Windsor.WindsorContainer.Register(IRegistration[] > > > > > > registrations) > > > > > > NHibernateFacility_ValidationError_OnSave.cs(75,0): at > > > > > > Castle.Facilities.NHibernate.Tests.Container..ctor() > > > > > > NHibernateFacility_ValidationError_OnSave.cs(48,0): at > > > > > > > Castle.Facilities.NHibernate.Tests.NHibernateFacility_ValidationError_OnSave.SetUp() > > > > > > --TearDown > > > > > > NHibernateFacility_ValidationError_OnSave.cs(54,0): at > > > > > > > Castle.Facilities.NHibernate.Tests.NHibernateFacility_ValidationError_OnSave.TearDown() > > > > > > > A repro is here: > > > > > > >https://github.com/haf/Castle.Facilities.NHibernate/commit/bc2257cd4e... > > > > > > > Windsor 2.5.2, 2.5.3 are affected. Not 2.5.1.xxxx > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > > Groups... > > read more » -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
