How to debug resolver issues in Spring4D?
How to debug resolver issues in Spring4D?
When in constructor occur unregistered type parameter (or registered, but uncompletly - without register his constructor parameters types), Spring creates the object with a bad constructor (without parameters, come from base class), but does not warn about it!
And an unfinished object is created, with nil in the key fields.
How to avoid this, how to detect it?
When in constructor occur unregistered type parameter (or registered, but uncompletly - without register his constructor parameters types), Spring creates the object with a bad constructor (without parameters, come from base class), but does not warn about it!
And an unfinished object is created, with nil in the key fields.
How to avoid this, how to detect it?
There is the unit Spring.Container.ActivatorExtension which has a container extension that prevents the container to fall back on the parameterless ctor.
ReplyDeleteStefan Glienke You mean TActivatorInspector? How to use it?
ReplyDeleteAdd the extension to the container.
ReplyDelete