Thank you Thiago H de Paula Figueiredo! I found the solution in http://tapestry.apache.org/loading-the-project-into-eclipse.html, it says: > Tapestry runs best with a couple of additional options; click the "Arguments" tab and enter the following VM Arguments: -XX:MaxPermSize=256M -Xmx600m -Dtapestry.execution-mode=development I just followed this step, and it became normal again! Thank you anyway!
2013/10/2 Thiago H de Paula Figueiredo <thiag...@gmail.com> > Hi! > > I guess you're missing setting the tapestry.execution-mode symbol. In your > web.xml, that would be: > > <context-param> > <param-name>tapestry.**execution-mode</param-name> > <param-value>development</**param-value> > </context-param> > > > In addition, I ran it in tomcat 7.0.27. I found a temporary solution for >> this, I added a @SubModule annotation on AppModule, and it seemed that >> tapestry could start in development mode..It's weird. Still need your >> help! >> > > Actually, with @Submodule, it seems that the application started in > production mode, which is the default, but the DevelopmentModule was only > loaded because you did it explicitly through @Submodule > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
