You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Valentin Valchev (JIRA)" <ji...@apache.org> on 2010/09/23 15:05:32 UTC
[jira] Resolved: (FELIX-2610) WebConsole doesn't work with JDK
1.3.1_06 because of problem in MessageFormat
[ https://issues.apache.org/jira/browse/FELIX-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Valchev resolved FELIX-2610.
-------------------------------------
Assignee: Valentin Valchev
Fix Version/s: webconsole-3.1.4
Resolution: Fixed
Fixed in rev.1000446
> WebConsole doesn't work with JDK 1.3.1_06 because of problem in MessageFormat
> ------------------------------------------------------------------------------
>
> Key: FELIX-2610
> URL: https://issues.apache.org/jira/browse/FELIX-2610
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-3.1.2
> Environment: Sun JDK 1.3.1_06, Windows
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
> Fix For: webconsole-3.1.4
>
> Attachments: varresolver-insteadof-messageformat.patch
>
>
> When running webconsole with JDK 1.3.1 it generates internal server error when opened from browser and it is completely unusable. In the logs the following exception is added:
> {code}
> Exception: java.lang.IllegalArgumentException: argument number too large at
> at java.text.MessageFormat.makeFormat(MessageFormat.java:795)
> at java.text.MessageFormat.applyPattern(MessageFormat.java:318)
> at java.text.MessageFormat.<init>(MessageFormat.java:248)
> at java.text.MessageFormat.format(MessageFormat.java:475)
> at org.apache.felix.webconsole.AbstractWebConsolePlugin.startResponse(AbstractWebConsolePlugin.java:548)
> at org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:141)
> at org.apache.felix.webconsole.internal.core.BundlesServlet.doGet(BundlesServlet.java:275)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:702)
> {code}
> Obviously, older JDK has some problems with MessageFormat. A simple workaround is to use our variable resolver instead of MessageFormat. IMHO using the variable resolver is even better because now we do 2 kinds of pre-processing of the HTML - first via the message formatter and second - with the variable resolver.
> So WDYT?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.