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)
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
