ljnb01 wrote:
JSPs can be precompiled and commercial products do it.
They don't deliver the JSPs - only the precompiled files. How would Click
work in this case?
I need to work this out since we have an old code base/scripts that automate
pre-compiling jsps and now my click jsp's would not pass nightly build. Any
directions?
Interesting. To answer its probably worth explaining what is happening under the
hood.
At application startup Click recursively scans through the web folder looking
for any JSP and htm templates. For every JSP and template found, Click attempts
to find its matching Page class. It derives the Page class from the template
name. This feature is called page-automapping[1].
Problem with compiled JSPs is that there is no JSP template Click can use to
lookup the corresponding Page class.
My only suggestions at this point is to try and manually map the JSPs to Page
classes.
For example:
<pages package="com.myapp.page">
<!-- map index.jsp to com.myapp.page.Home -->
<page path="index.jsp" classname="Home"/>
<page path="customer/edit-customer.jsp" classname="customer.EditCustomer"/>
<page path="customer/view-customers.jsp" classname="customer.ViewCustomers"/>
</pages>
kind regards
bob
[1]:
http://incubator.apache.org/click/docs/user-guide/html/ch04s02.html#application-automapping
