I have a project where we need to precompile JSPs. I have followed the instructions here: http://mojo.codehaus.org/jspc-maven-plugin/usage.html
We are servlet spec 2.4, JDK 1.5. Works great. Deploys and runs under my local Tomcat without problems. Under WebSphere however is where we encounter an issue. SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. SRVE0187E: Check your classpath to ensure that all classes required by the servlet are present.SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath SRVE0234I: Application classpath=[...]... Unfortunately, it doesn't tell me what file it is missing. Right now, I'm going down the route that the generated source is different than what would have been generated by WebSphere. I'm trying to get a generated JSP from our dev server from a prior deployment now to compare Generated from Maven2 project... public final class error_jsp extends org.apache.jasper.runtime.HttpJspBase implements org.apache.jasper.runtime.JspSourceDependent I'm suspecting I need to include a Jasper jar or somehow change what is generated during the build process. While I'm in limbo, just thought I would reach out and see if anyone else encountered this situation before. Thanks. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
