[
https://issues.apache.org/jira/browse/JSPWIKI-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662031#action_12662031
]
Janne Jalkanen commented on JSPWIKI-467:
----------------------------------------
TemplateManager.listLanguages() assumes that the file is called "JSPWiki.jar".
There's the unfortunate side effect that you can't put i18n resources in
anywhere else than JSPWiki.jar.
This should be fixed for 3.0 - this is rather hackish right now.
Suggestion: use the ini/jspwiki_modules.xml system to list the available
languages, so you can deploy your own localization without having to put it in
JSPWiki.jar...
> Enable name of JSPWiki.jar to be changed without breaking webapp
> ----------------------------------------------------------------
>
> Key: JSPWIKI-467
> URL: https://issues.apache.org/jira/browse/JSPWIKI-467
> Project: JSPWiki
> Issue Type: Wish
> Components: Servlet Container/Java compatibility
> Affects Versions: 2.8.1, 2.8.2
> Environment: Fedora 9 x86, Tomcat 6.0.18
> Reporter: Scott Douglass
> Priority: Minor
> Fix For: 3.0
>
>
> I prefer that .jar files I deploy have a version number in the name, i.e.
> instead of JSPWiki.jar, jspwiki-2.8.2svn4.jar.
> If I build JSPWiki and give my choice of name to the JSPWiki.jar file in the
> webapp's WEB-INF/lib I can't use the UserPreferences.jsp anymore.
> The error displayed in the browser is:
> JSPWiki has detected an error
> Error Message
> in is null
> Exception
> java.lang.NullPointerException
> Place where detected
> java.util.zip.ZipInputStream.(), line 56
> Renaming the .jar file back to JSPWiki.jar eliminates the problem.
> No stack trace or any other related output appears in the jspwiki log file or
> the tomcat log files.
> I'd love to know why this happens. I've grep'd the JSPWiki source code for
> uses of ZipInputStream and found none. Very odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
