[
https://issues.apache.org/jira/browse/WICKET-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-2174.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC3
Assignee: Juergen Donnerstag
Introduced Form#onFileUploadException(final FileUploadException e,
final Map<String, Object> model) which you may subclass to
modify or extend the Model which turn can be used for the messages.
> Form#getMaxSize() -> no custom format
> -------------------------------------
>
> Key: WICKET-2174
> URL: https://issues.apache.org/jira/browse/WICKET-2174
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-RC2
> Reporter: Jan Loose
> Assignee: Juergen Donnerstag
> Fix For: 1.4-RC3
>
>
> Hi,
> I found problem with format of 'maxSize' property in component Form:
> final Map<String, Object> model = new HashMap<String, Object>();
> model.put("exception", e);
> model.put("maxSize", getMaxSize());
> ... the main problem is if you want modify 'look and feel' of the Bytes
> format in error messages.
> Can you add e.g. new method String formatMaxSize() or something similar? The
> other solution is modification of toString of bean Bytes to get results look
> like 300kB (now there is 300K ... this is not good for common users). Or is
> there other simple way how to do this?
> Regards,
> H.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
