All work
- Burrow throws a null reference exception when added as a module in IIS7 and static content is servedNHB-22Resolved issue: NHB-22Kailuo Wang
- Naming incorrect persistantUnits should be persistenceUnitsNHB-11Resolved issue: NHB-11Kailuo Wang
- Assembly info should be excluded from proj and svnNHB-10Resolved issue: NHB-10Kailuo Wang
- Get the NHibernate.Cfg.Configuration for each PersistentUnitNHB-8Resolved issue: NHB-8Kailuo Wang
- BurrowEnvironment.Shutdown should reset all SessionFactoriesNHB-4Resolved issue: NHB-4Kailuo Wang
- DeletableEntityBase doesn't deleteNHB-3Resolved issue: NHB-3Kailuo Wang
6 of 6
Burrow throws a null reference exception when added as a module in IIS7 and static content is served
Fixed
Description
Environment
None
Attachments
1
Details
Details
Assignee
Kailuo Wang
Kailuo WangReporter
Nathan Rains Stott
Nathan Rains StottComponents
Fix versions
Priority
BlockerWho's Looking?
Open Who's Looking?
Created January 23, 2009 at 6:16 AM
Updated January 24, 2009 at 1:37 PM
Resolved January 24, 2009 at 1:37 PM
Activity
Show:
I added NHibernate.Burrow as a module to my asp.net MVC site in IIS7. When serving static content, it throws a null reference exception in WorkSpaceSnifferByAttribute.Sniff. The handler passed is null and the call to GetType() on the first line of the method throws the exception.
I have attached a trivial fix that simply checks to see if the handler is null and if so returns string.empty. This seems like appropriate behavior since this is the same behavior that happens when WorkSpaceInfo is null and if there is no handler there can be no WorkSpaceInfo.
This problem never occurred in Casinni, only in IIS7. I believe that a more thorough solution may be available preventing this method call all together by changing the HandlerIsIrrelavant method in WebUtilHTTPModule, but I was not sure what to do there.