[
https://issues.apache.org/jira/browse/WICKET-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985713#action_12985713
]
Martin Grigorov commented on WICKET-3354:
-----------------------------------------
Sorry. I didn't mean that you cannot use log4j in our tests.
With my first comment I said that it would be good to have
BaseWicketTester.assertLogMessage() method which can be used by Wicket's users
but unfortunately we cannot depend on log4j in BaseWicketTester (because it is
in wicket-core).
You can depend on log4j in wicket-core/src/test/**. Sorry again for the
confusion.
> Improve SerializableChecker message
> -----------------------------------
>
> Key: WICKET-3354
> URL: https://issues.apache.org/jira/browse/WICKET-3354
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.4.15, 1.5-M3
> Reporter: Pedro Santos
> Priority: Minor
> Attachments: WICKET-3354-2.patch, WICKET-3354-3.patch,
> WICKET-3354.patch
>
>
> Currently if the object has an problematic implementation of equals method,
> the serializable checker will stop its work with an runtime exception. The
> best would be just log an warn explaining the the problem on console and
> continue the checks until the non serializable source of the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
