J2SE From Tomcat

I discovered two other issues when upgrading to the J2SE 1.5 compiler for JSP's on Tomcat:

1) You'll probably want to set

<init-param>
<param-name>errorOnUseBeanInvalidClassAttribute</param-name>
<param-value>false</param-value>
</init-param>

in the jsp declaration in TOMCAT_HOME/conf/server.xml if you want to use jsp:useBean with generics. For example:

<jsp:useBean id="users" class="java.util.ArrayList<UserVO>" scope="request"/>

2) The ant compiler seems to be a lot more picky than Jasper. For example, I had a bunch of import statements on classes that didn't exist in my classpath. Jasper has no issue with the issue and the pages ran fine w/ this import, but Ant reported these as errors whenever the page compiled. For this reason, I strongly recommend testing every page before deploying this to production environments.

I will continue posting new issues that I find on this Blog. If you have any that you've found, publish a comment here.

No comments:

Post a Comment

Comments on this blog are moderated and we do not accept comments that have links to other websites.

Share

About Isaac Sacolick

Isaac Sacolick is President of StarCIO, a technology leadership company that guides organizations on building digital transformation core competencies. He is the author of Digital Trailblazer and the Amazon bestseller Driving Digital and speaks about agile planning, devops, data science, product management, and other digital transformation best practices. Sacolick is a recognized top social CIO, a digital transformation influencer, and has over 900 articles published at InfoWorld, CIO.com, his blog Social, Agile, and Transformation, and other sites. You can find him sharing new insights @NYIke on Twitter, his Driving Digital Standup YouTube channel, or during the Coffee with Digital Trailblazers.