[
https://issues.apache.org/jira/browse/WICKET-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892555#action_12892555
]
Hudson commented on WICKET-2966:
--------------------------------
Integrated in Apache Wicket 1.5.x #175 (See
[http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/175/])
> "markupStream" field in MarkupException breaks Exception's Serializable
> contract.
> ---------------------------------------------------------------------------------
>
> Key: WICKET-2966
> URL: https://issues.apache.org/jira/browse/WICKET-2966
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Maarten Billemont
> Assignee: Juergen Donnerstag
> Fix For: 1.4.10, 1.5-M1
>
>
> {code}
> private org.apache.wicket.markup.MarkupStream
> org.apache.wicket.markup.MarkupException.markupStream
> [class=org.apache.wicket.markup.MarkupStream] <----- field that is not
> serializable
> {code}
> Exceptions have the contract of being serializable. That means, all their
> fields have to be serializable; otherwise you break that contract. I think
> for Wicket especially, it is important to respect and honor that contract.
> Therefore, MarkupException (or any other Wicket exceptions) should not
> contain any non-serializable objects in their fields. Either the
> markupException field should become transient or it should be replaced with a
> serializable view of it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
