VelocityViewServlet works fine with JDK1.5 > -----Original Message----- > From: Will Glass-Husain [mailto:[EMAIL PROTECTED] > Sent: Saturday, February 11, 2006 12:33 PM > To: Velocity Users List > Subject: Re: JDK1.5 Issues > > That's kind of a strange exception... > > Try the latest version of Velocity Tools and the > VelocityViewServlet. It's better maintained than > VelocityServlet (we're deprecating it in the next release). > We recommend using this instead of VelocityServlet in almost > all situations. > > WILL > > ----- Original Message ----- > From: "Sujay Jayaram" <[EMAIL PROTECTED]> > To: <velocity-user@jakarta.apache.org> > Sent: Saturday, February 11, 2006 6:24 AM > Subject: Re: JDK1.5 Issues > > > > Hi Will, > > > > > > > > Thanks for the quick response! > > > > > > > > I'm thinking that there's a servlet problem (I'm extending the > > VelocityServlet) as TomCat can't instantiate the servlet. the error > > message > > I get is: > > > > > > > > INFO: Marking servlet WeddingPathServlet as unavailable > > > > Feb 11, 2006 12:22:59 PM > org.apache.catalina.core.StandardWrapperValve > > invoke > > > > SEVERE: Allocate exception for servlet WeddingPathServlet > > > > java.lang.ClassCastException: com.weddingpath.web. > WeddingPathServlet > > > > at > > > org.apache.catalina.core.StandardWrapper.loadServlet(StandardW > rapper.java:10 > > 55) > > > > at > > > org.apache.catalina.core.StandardWrapper.allocate(StandardWrap > per.java:757) > > > > > > > > > > > > It all works fine on a jdk1.4.2 setup so the > ClassCastException made me > > think that perhaps the init() method of the VelocityServlet is doing > > something that the 1.5 jvm doesn't like? > > > > > > > > We haven't had to do much with velocity in the past (it's > soooo easy to > > use > > :-) ) so looking at the code now, I notice that > VelocityServlet has been > > deprecated.perhaps there's an issue here??? > > > > > > > > Has anyone else had this ClassCastException problem? I > could be going down > > the wrong road here and it could be a TomCat issue - be > good to know > > though. > > > > > > > > Thanks again > > > > Sujay > > > > > > > > > > > > --- Will Glass-Husain <[EMAIL PROTECTED]> wrote: > > > > > > > >> Hi Sujay, > > > >> > > > >> You should be able to un Velocity 1.4 with JDK 1.5, > > > >> just not compile it. > > > >> Otherwise, you can use HEAD which is pretty stable. > > > >> > > > >> WILL > > > >> > > > >> ----- Original Message ----- > > > >> From: "Sujay Jayaram" <[EMAIL PROTECTED]> > > > >> To: <velocity-user@jakarta.apache.org> > > > >> Sent: Saturday, February 11, 2006 5:38 AM > > > >> Subject: JDK1.5 Issues > > > >> > > > >> > > > >> > Morning all! > > > >> > > > > >> > > > > >> > > > > >> > We are using the wonderful Velocity at > > > >> weddingpath.com and the site is > > > >> > getting a lot busier so we're looking at moving > > > >> over to the latest Tomcat > > > >> > (which requires on JDK1.5). > > > >> > > > > >> > > > > >> > > > > >> > My questions is: how do I get a JDK1.5 compatible > > > >> Velocity release please? > > > >> > I > > > >> > know that I could build from the HEAD but I have > > > >> no idea how stable it > > > >> > is.is > > > >> > there a good checkpoint version before that and > > > >> are there any plans for a > > > >> > formal JDK1.5 compatible release? > > > >> > > > > >> > > > > >> > > > > >> > My hunting around in the archives didn't get these > > > >> answers so I hope it's > > > >> > ok > > > >> > to ask! > > > >> > > > > >> > > > > >> > > > > >> > Cheers > > > >> > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
