toString overriding

Vaadin 6 / 7 / 8
1

I am sure you guys had the best intent by overriding the toString method to warn users they were doing something they shouldn’t but in a test suite this is really painful.

assertion methods takes the component to provide a dedicated message if the assertion fails. And some assert methods are generic so they don’t even know the component behind.

Because the exception message is resolved no matter what, we have zillions of warnings in our logs now and we’re not doing anything wrong in the code.

Is there a chance you would revert that?

S.

2

Problem will be fixed in 7.1.0beta1.

See this
ticket

3

Thanks but that does not help. I am in a unit test and the init param won’t help me much. Setting a system property is also painful.

Why don’t you make this disabled by default? After all this thing is an assertion, no?

4

Sadly I can’t answer that because I am not one of the Vaadin Dev’s. I’m just a “User” like you. I just stumbled over this ticket and thought it would help you. Maybe a Dev can help you better.

5

I see. Thanks for the link anyway !