WLS 9.2: JSP error when attribute enclosed in double vs single quote

Question

Hi all,
          We are trying to deploy a WAR file on WLS 9.2 on a Unix box. This app uses Struts, and does not use any app-server specific extensions/tags etc. We run into JSP compilations errors when we try to deploy as well as when we run weblogic.appc on the WAR. The errors are generally the same type..."This attribute is not recognized" for multiple Tags that are used...not just Struts tags, but even plain vanilla <jsp:include tags...liks so:
          LookupPO.jsp:102:72: This attribute is not recognized.
          <jsp:include flush="true" page="
          <%=(String)request.getAttribute("selectTile")%>"/>
          ^--------^
          However, if we just change the same tag to use single quotes for attribute values, like so:
          <jsp:include flush="true" page='
          <%=(String)request.getAttribute("selectTile")%>'/>
          then it works fine.
          What throws me off is that these tags in the same double-quoted format work well on other servers such as Sun Java System.
          Changing the double to single quotes for every single tag in our applications 600-odd JSPs will be a huge burden...is there any other way?
          Any help is sincerely appreciated.
          Thanks,
          Vik.
          Edited by vshevde at 03/26/2008 9:09 AM

Answer 1

quote:
Originally posted by:
joeG
Ok I see what you mean, actually the insert in that fashion
with MySQL still puts the data in normalized, its just in one
statement. From the docs:
INSERT statements that use VALUES syntax can insert multiple
rows. To do this, include multiple lists of column values, each
enclosed within parentheses and separated by commas. Example:
INSERT INTO tbl_name (a,b,c) VALUES(1,2,3),(4,5,6),(7,8,9);
thanks for the response.
Oh, that's what you meant. See what happens when you get old,
you go blind.
I have two suggestions. First, keep trying with cfqueryparam.
I don't use it that often myself because the db I work with doesn't
support it, but, I think it has a list attribute.
Second, what you are attempting, a loop within a query, is
intuitively more efficient than putting your query inside a loop.
This is something I have tested and what I found is that the most
efficient approach depends on the db. I did not test MySQL, but I
suggest you do. The gettickcount() function is handy for these
sorts of tests.