hi zack,
i'am very sorry to hear that it was'nt possible to find a solution and that you
are going to switch the framework. we've had problems too but luckily we were
able to solve them all so far.
since we are using tapestry we are way more productive than with other
frameworks or technologies before - i wish you could tell the same.
here are some more tipps:
- somtimes the page or page class rewriting fails - mostly if you access
services, session state object or symbols in event methods in nested method
calls. in these cases i divide and remove parts from the code until it starts to
work again and then i split up the method calls in several lines like:
before:
boolean result = myService1.serviceCall1(myOhterService2.serviceCall2());
after:
Bean b = myOtherService2.serviceCall2();
boolean result = myService1.serviceCall1(b);
- make absolutely sure, that you have the right dependencies in your path (maven
dependency tree).
- use the latest jdk version
- since you posted a stack trace with filesystem related problems before: check
the lower/UPPER case names of files (classes/tml/gfx). we have people over here
working with windows and since the windows filesystems don't make a differeence
between uppper and lower case problems occur first on unix machines.
I am sure that you already knew my points, but maybe you missed one.
I hope that you will finally find a solution.
Felix
zack1403 schrieb:
Ummm alright well I guess this is just a bug? We are switching the site
slowly back over to a more mature framework without all the bugs. I am
having to rewrite this isolated page in php to get it working in the mean
time. I guess I bet on the wrong horse with tapestry.
Zack
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
