[ 
https://issues.apache.org/jira/browse/JSPWIKI-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794674#action_12794674
 ] 

Janne Jalkanen commented on JSPWIKI-620:
----------------------------------------

I'm all for dropping the precompiled jsp's (option 3).  Considering that with 
3.0, the JSPs become quite a lot lighter as code is moved into ActionBeans, I'm 
not even sure whether they really benefit anyone.

(the way we could implement 1 is that the precompilation process could create a 
simple text file of compiled JSPs, which we could then read in and check in 
TemplateManager.findResource(). But I'm not sure it's a good solution, 
especially if we can't find people who can speak up for this feature. But as 
it's a feature drop, we should vote on it on the mailing list.)

> templates not copied
> --------------------
>
>                 Key: JSPWIKI-620
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-620
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Servlet Container/Java compatibility
>    Affects Versions: 2.8.3
>         Environment: Debian linux, ant 1.7.1, tomcat 6.0.20
>            Reporter: Rolf Schumacher
>
> What I did:
> checked out branch 2.8.3 or downloaded source distribution from jspwiki.org, 
> built with "ant war" or "ant war-tomcat", unjared to webapps location, 
> configuration page is handled properly, restart tomcat, entered 
> http://localhost:8080/JSPWiki.
> What I expected:
> to see the Main.txt page
> What I got:
> a blank window
> Workaround:
> manually copied all jsp pages from webdocs/templates/default of the source 
> distribution to tomcat/webapps/JSPWiki/templates/default inclunding 
> subdirectories.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to