Patience.
It's not Lomboz that's determining how webapps run, it's sysdeo. Sysdeo uses an external copy of Tomcat. I think you'll find the translated index.jsp in TOMCAT_HOME/Catalina/localhost/webappname, where TOMCAT_HOME is the path to the copy of Tomcat you installed and bound to the sysdeo plug-in, and 'webappname' is probably going to be the name of the WAR that you distributed your webapp in.
Normally you shouldn't have to look at the
java translation of the JSP. They tend to be quite ugly, and the only human value they have is if you're having trouble making the JSP work and you want to verift that the generated code is what you think it should be. Also, keep in mind that once the JSP is translated, it's then compiled into a class, and the actual code that the webapp executes will be that class - changing the java code may not cause the class to recompile, although (depending on settings) changing the original JSP may.
For some versions of Tomcat, I've had problems with stale code. To remedy that, when I deploy, I'll generally delete the exploded WAR from TOMCAT_HOME/webapps and delete the work files from TOMCAT_HOME/Catalina/localhost.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.