… your issue is going to be Tomcat if deploying this page to your upgraded install no longer works. The reason I say that is that MyEclipse is just a bunch of editors and editing facilities, we don’t manhandle the code or do any injection to it… so if this code *used* to work on your old TOmcat install and now doesn’t anymore after updating it, then my money is on Tomcat.
Have you tried searching the JSF Forums for similar errors? I’m wondering if Tomcat updated a library or now ships a library that conflicts with one in JS… does the exception really say [my class] or did you just remove that? Have you tried checking your log files for output pertaining to exactly the line causing the problem? Try and redeploy this to your old Tomcat install, does it still work? DO you have another test machine to try it on? Have you ever tried dipping your french fries in a chocolate shake before?
Answering these questions might help us unconver what happened… just like CSI, only boring-er.