I am using the the 1.1.6 sandbox but I don't have your problem ... have you tried a simple page with just one command link on it and see if that works ... do you use any components from the sandbox on all those pages ? are command buttons also affected or just command links ? if not, have you tried replacing a command link with a command button ? ...
On 5/16/07, Shane Petroff <[EMAIL PROTECTED]> wrote:
Sorin Silaghi wrote: Can you please send us some details on this ... ? like how do the pages and action methods look like ?? have you tried to change a commandLink with a commandButton and see if you get the same errors ?(the unaffected button might work because of other reasons) There is nothing wrong with either the code or the navigation rules, the breakage appears in areas unmodified for several weeks. The mere presence of the tomahawk-sandbox-1.1.6-SNAPSHOT.jar in the application's classpath (web-inf\lib) causes the problem. If I stop tomcat, rename this jar to some other extension (and comment out the code which needs it), everything works again. If I rename it back and restart tomcat again, all the links are broken. I've tried 2 versions of the 1.1.6 sandbox and had the same problem with both. Which sucks given that I want to use some of the sandbox components... Shane thank you.. On 5/15/07, Shane Petroff <[EMAIL PROTECTED]> wrote: > > Hello all, > > I have somehow broken my application and can't figure out what I've done > to cause it. Every h:commandLink in my app is currently broken and not > only do I not know why, but I've spent several days working in an area > of the application which is accessible by navigating via a > h:commandButton, so I don't even know when I broke things. CommandLinks > now generate javascript errors either trying to reference a non-existent > component or a non-existent function. Some of the now broken pages have > been unchanged for weeks, others completely reworked. Since navigation > via button works, I can confirm that managed beans are being created and > > called, but I can't figure out why the javascript used for commandLinks > gets hosed. Anyone else seen something like this? > > -- > Shane > > -- Shane
