Re: [MO-java-dev] DynaMock proxy toString issue

[<st...@m3...>]

> How about NOT using the call factory to create the decorator chains for
> toString in the constructor.  Instead, create them explicitly with the new
> operator.
>=20
> The CallFactory was created so that we could test how the Mock constructed
> objects in response to other calls.  If we have Tim's unit tests for
> toString then we don't need to use the CallFactory to test the mocking of
> toString in the constructor.
>=20
> Does that make sense?

But then we would have two mechanisms for creating calls. One with the fact=
ory and one without. That doesn't sound right to me.