Hi Mark, thank you for the testcase.
I fixed that now in svn. I have to think about the solution if this is the final one, but it at least works. The reason for the last crash was, that the scope takes the ownership of all objects put into the scope. And this scope mechanism is also used for named parameters. In your case the parameter-scope takes ownership of your ServerSessionState and after the subcomponent this ServerSessionState is deleted, which is not expected. The objects in the scope are held within smart pointers. Luckily the smart pointer has a destroy policy and by setting this to a null-policy, the object is actually not deleted. Tommi ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
