[Ivar Vasara]

<email:emailUser userType="<%= ""+EmailUserTag.FROM_USER %>" display="<%= ""+EmailUserTag.FULLNAME %>"/>

MyEclipse barfs on this line with the error “expected %>”..

[Ivar Vasara]

59:<div class="footer-list"><div class="show-more">
<content:search text="browse recent episodes" header="ZeD Episodes" query="recent episodes"/></div></div>
60: </div>
61:
62:</div> <%-- closes wrap --%>

I get an error on line 61, “no setter found: (classname)”. I open up the associated .java file, and lo and behold there’s a valid “setHeader” method.
(so it’s the wrong line # as well as being a bogus error)

win2k, 3m6, 3.7rc2, yada yada

[Scott Anderson]

Ivar,

The problem with your first line is that you have not properly used both single and double quotes to disambiguate the line as is required by the spec. Try this instead:

<email:emailUser userType='<%= ""+EmailUserTag.FROM_USER %>' display='<%= ""+EmailUserTag.FULLNAME %>'/>

By the way, is there some reason you’re taking your strings and using a null concatenation in front of them? if EmailUserTag.FROM_USER isn’t a String, you can make it one by using one of the conversion methods on the String class directly (ie String#valueOf).

There’s not enough context around the second thing you report for me to content on its validity or invalidity. However, if you have quoting issues further up the file, the parser may not be able correctly identify problems past them.

[mrzeld]

@ivar wrote:

59:<div class="footer-list"><div class="show-more">
<content:search text="browse recent episodes" header="ZeD Episodes" query="recent episodes"/></div></div>
60: </div>
61:
62:</div> <%-- closes wrap --%>

I get an error on line 61, “no setter found: (classname)”. I open up the associated .java file, and lo and behold there’s a valid “setHeader” method.
(so it’s the wrong line # as well as being a bogus error)

win2k, 3m6, 3.7rc2, yada yada

the code snipet you show is out of the original jsp file. the error message gives line numbers from the generated .java file. you will need to go into the tomcat (assuming that is what you are using) work directory and go find the correct .java file in order for the error message to make complete sense.

[Riyad Kalla]

Yes ivar, mrzeld makes a very good point, when you get exceptions in JSP pages and so forth, they are exceptions pertaining to the translated source file, NOT the original JSP. A JSP’s life looks like this:

index.jsp (HTML-like file that you code in the editor) -> JspCC compiles index.jsp -> index_jsp.java (Translated JSP, this is now a giant servlet with TONS of “out.println”‘s in it and method calls -> javac compiles index_jsp.java -> index_jsp.class (This is loaded by the container as your “JSP Page”. When you get errors about lines and so forth, its actually talking about your “index_jsp.java” page, which can be found in (on Tomcat):

<tomcat install dir>\work\Standalone\localhost\<webapp dir>\<somewhere under here, in a subdirectory maybe>

[Ivar Vasara]

arg.. i had a serious configuration error, so these bug reports are bogus (though scott’s comment was still helpful once I figured out what the problem was ) sorry for the confusion.

[Riyad Kalla]

no problem, we are glad you are up and running now.

[Author]

Posts