My Tech Blog

If the Component is not rendered on screen then the f:ajax cant do any refreshing as the Id itself is not present on the client DOM.The <f:ajax render> client ID should refer a component which is always rendered on the client side. It will then be exactly the HTML representation of that component which will be updated by JavaScript. If the HTML representation of that component is not there on the client side DOM because the rendered of the component is false , then JavaScript has nothing to find and update and in effect "nothing" will happen. Set it to for example @form which indicates the entire form: which is a very bad practice. Try to wrap the entire component with some thing like a panelGrid or worst case a Form tag and rerender it so that all within the scope is rerendred.

Stack Trace looks some what like this java.lang.NoSuchMethodError: javax/servlet/http/HttpServletResponse.getStatus() this happens mostly when there is a cookie clash. if Different applications have same cookie configured then the request from browser is unable to reach server and eventually throws a 500 error .. :)..

The Content Assist for Eclipse Helios JEE Version seems to be very slow and i did some basic googling and found this quick cure which actually work for me so documenting it here. Turn off JAX-WS Proposals in Content Assist Window > Preferences --> Java > Editor > Content Assist > Advanced " Not Only this other than the following and what format you are working disable everyhting else. The basic things required for JSF perspective are 1.Basic Proposals 2.java Proposals 3. SWT Template 4. Template Proposals Remove all unused items from both the windows and restart eclipse .. Definitely a visible change in content Assist :).. Also one other thing is changing the file assosiation in the Window -- >preferences --> general --> Editors -->File Assosiation and select the Xhtml and use the editor as HTML Editor and click on default.