What is exactly the status of this issue?...I thought it's fixed in the latter snapshots but I just tested it with ajax4jsf-1.1.1-20070420.000856-41.jar and stil have the same problem.

What I do: I submit a login form: <h:form....> that contains a <a4j:commandLink....>It goes wrong when the login page want to navigate, according to the faces rules to the same page when the login wasn't successfully or another secured page in case the login was successfully.Javascript error:

BTW: It works when I disable in the advanced IE optons: "enable native XMLHTTP support". I only get another javascript error then (Line 34, char 1, A4J is undefined), but the rest seems to work ok.

We use IE7 for testing very hard, but did not meet the problem like that. Just in case, the new jira issue (http://jira.jboss.com/jira/browse/AJSF-49 ) has been created for further investigations. If you can provide more specific information to help to reproduce the problem, do it please

Here some more information:I am using myfaces 1.1.5 and tomcat 5.0.19 and tomahawk 1.1.3 and facelets 1.0.14.

Below you find the login xhtml which is the form that I use to login. When I login and a validation occurs it goes fine, but when the validation is succesfull it will navigate through another page through faces config and then the described error is shown.I fyou need more information, just let me know.

Hmmm.. Sorry id didn't showed the "redirect" tag in my quick topic response.So again the text:At least I found a workaround:use the faces "redirect" tag in your faces config navigation and you won't get the permission denied error.

I'd like to add some explanations what is going on in case of using < redirect / > in navigation case and why not not using it might cause problems.

Usually, Ajax4jsf works in "Ajax Request generates Ajax Response" mode. I.e. Ajax Request is sent, the Ajax Response is received and the required part(s) of page is(are) replaced. To work in this mode, the action method (if presents) must return null.

However, Assume you want to implement the following use case: "User presses the submit button. If form validation is OK proceed to the next page, otherwise show the current page with error messages on it". For this use case you need "Ajax Request generates Non-Ajax Response" mode for success thread.

Ajax4jsf supports this mode. The action method should return an outcome string that matches one of the navigation rule in the faces configuration file.

As soon as the decision is made on the server (the validation performs on the server), it is always a "Ajax Request" at the beginning. I.e. the request is invoked on the XMLHttpRequest Object, but not on the browser itself.

So If no < redirect />:

when the validation is OK, action returns existing outcome and the view is changed, Ajax4jsf returns the whole view instead of parts pointed with ReRender attribute. When the new view comes to the client, Ajax4jsf script replaces the whole page with the new one in the DOM tree.Visually, it looks like you are on the new page. However, as soon as it was not a browser request, browser still keeps the environment (javascript variables and functions) from the previous page mixing and matching it with the ones from the new page.This might causes unexpected glitches (or might be not).

If < redirect /> is defined:

when the validation is OK, action returns existing outcome and the view is changed, the redirect request is sent to the client instead of the view itself. When the request comes, browser (but not XMLHttpRequest Object) requests for the new page. Then, what is called in JSF Specification "Non-JSF Request generates JSF Response" performed.

So, use < redirect /> in most cases. < redirect / > cause only one famous problem - request scope is reset.

In our project we find that we we have aredirect to another page with a4j:commandLink or commandButton, sourrended by h:form, nothing happens with only IE7. We found that this behaviour is correlated with a security fix relause by Microsoft 10th July for italy.

I solved converting all commandLink and button, where possible, in h:commandLink or h:commandButton, and only where isn't possible, for the opening of modal Panel, with a4j: commandLink or Button.

But I sorrended all with a4j:form and not with h:form. Tomorrow I will add the code of microsoft patch. We have tested on different PC, and unistall that patch always insn't the solution. On one pc we reinstall IE7 and then the patch. We don't know how about that patch.