That is sad situation. So, you have some crazy locked configuration that never assume that JS content can be generated by code? What about images? Other resources (css)?
We perhaps can implement something for static resources, but we have tons of dynamically generated resources in Richfaces.
That is general problem now, many frameworks make an assumptions, and sometimes it is bad assemptions.
Yes basically we have a list of "accepted" url's and anything outside of that is automatically redirected to the login page. So, in order to make A4J work without hacks I'd have to submit the additional urls to be added to this list by somebody in a different department...doable but annoying.
I know this is probably more my problem than a problem with A4J, but it would just be nice to have the option.
May be you can just add resource location to the accepted URL list?
I think your request is reasonable, but it hard to determine overall impact. And again, we have tons of dynamically generated resources.
Question - how your system determine that something like http://myserver.foo.bar/myapp/pages/just-stuff-not-fluff.jsf
is valid, but
Yes adding the resource location to the list of accepted URL's would probably work but just less convenient--I'd have to enlist the assistance of people outside of my immediate team since we don't have control over much of our deployment environment (which sucks!).
Additionally, each piece of additional environmental setup required is just another opportunity for screw-ups to happen when they finally promote our code to the production environment.
But I think you answered my question. I can see the advantages of having dynamically generated resources in a typical environment and, from the lack of other people making similar complaints, it looks like our environment is anything but typical.