Nitro 1.1 JSP compilation bug

Question

empty

Answer 1

I am starting to see a pattern here of problems. One issue might be that we
are using Resin as a container. Im not sure if that is contibuting to some
compile issues but it might. For example, nitro complains about this
scriptlet
<%
this.getServletContext().log("Bad Hashcode for RegulatoryApplication");
%>
Changing the "this" to "seesion" fixes it. Since this works in resin, I
assume resin, I assume it is an container issue.
Nitro's jsp complier seems to really not like stuff like this:
<% if (noUser.booleanValue()) { %>
href="javascript:window.alert('You must be a member of DrillingInfo to
access the download functions.')">Download this data</a>
<% } else { %>
href="/download.do?type=prod&format=<%=com.drillinginfo.struts.actions.downl
oad.ProductionDownloadController.DOWNLOAD_FORMAT_DRI %>"
target="_blank">Download this data</a>
<% } %>
Giving an error "syntax error on else: finally expected"
Is there some way to turn off jsp complile entirely or on a file by file
bases?
"Alan Berezin" <[email protected]> wrote in message
news:[email protected]...
Installed Nitro1.1 along with it's eclipse3.0.I am seeing an error reported in a scriptlet. Here is a clip of the JSP:
table bgcolor="eeeeee" width="650"
% int[] npvp =
(int[])calcAnalysisDO.getNetPresentValuePercentsIntegers();
logic:iterate name="calcAnalysisDO" property="netPresentValues"
id="value"
indexId="index"
tr
td><font face="Arial, Helvetica, sans-serif"
size="2"><b><%=npvp[index.intValue()]%>%</b
$<bean:write name="value" format="###,###"/></font></td
/tr
/logic:iterate
/table
It is reporting an error on this line: <% int[] npvp ...
The error is "Type Mismatch: cannot convert from null to int"
Interestly, when I move that statement to the top of the file, into a
scriptlet with some other code, the error disappears. That will work fine
at runtime.
This jsp scriptlet causes the same error: <%=
leaseData.getWells().toString() %
I change it to this but still get the same error (getWells() returns a
String): <% out.print(leaseData.getWells()); %
Note that Nitro knows this object, leaseData, because it properly does
statement completion on it.