Really sorry to spam the list but has anyone got any ideas at all here? A new session definately gets created with the call to OpenSession(), and then gets disposed when the current transaction is commited which results in "failed to lazily initialize a collection" in my view.
If I remove Automatic Transaction Management but leave in the web module, OpenSession() still creates a second session, but it doesn't get disposed so I don't get the lazy initialization error. I should add that I'm using asp.net mvc (don't know if this makes any difference). Would any other info help? I'm on the verge of giving up on this approach, which seems a shame because it should be so simple to set up. I suppose my last resort is compiling a debug version of castle and then stepping through the code to see what is happening. regards, Jordan. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
