This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Tomcat JSP problems  RSS feed

 
Bob Randall
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have deployed jsps as part of our ear on JBOSS 4.0 (using tomcat for presentation tier). We are getting this warnings related to compilation
of our jsps.

293871458 http-0.0.0.0-60606-Processor18 ERROR STDERR Note: /opt/jboss/server/default/work/jboss.web/localhost/
account/org/apache/jsp/WEB_002dINF/jsp/acctDeleteHoldConfrm_jsp.java uses unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

How do I remove this message. I guess this has to do with 1.5 generics and we are having tag lib declarions and generated java code has

_jspx_dependants.add("/WEB-INF/lib/struts-bean.tld");
_jspx_dependants.add("/WEB-INF/lib/struts-html.tld");
_jspx_dependants.add("/WEB-INF/lib/struts-logic.tld");
 
Paul Clapham
Sheriff
Posts: 22502
43
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, it's a warning message. And yes, it does have to do with Java 5 generics. But why do you want to "remove" it? Does the JSP not run correctly?
 
Bob Randall
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No the JSP runs fine, But the operation team here does not want unnecessary messages in the production log file.
 
Paul Clapham
Sheriff
Posts: 22502
43
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You're only going to get it once, when the JSP is compiled. If it's being caused by scriptlets in your JSP, and the management decision that your time to learn Java 5 generics and implement them in those scriptlets is worth spending so that the message doesn't occur, then go ahead and do that. If the message is being caused by code generated by (say) JSTL tags, then I suggest you'll just have to declare the messages as "necessary". Generics were an attempt to ensure type-safety in Java, and JSTL pretty much explicitly disavows type safety; that conflict isn't up to you to resolve.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!