Bauke Scholtz
Bauke Scholtz
I created a PR. You might want to run it through the integration tests. > maybe we can dynamically decide to render it static or call PrimeFaces.current().executeScript(...), based on that...
Noted should be that this also changed the behavior of PrimeFaces#executeScript(). - it's now invoked during oncomplete instead of during DOM update - it's now got access to the same...
> > Noted should be that this also changed the behavior of PrimeFaces#executeScript(). > > where is exactly this change? we would have to check multiple issues in the past...
> Can we assume that if the request is ajax and beanStorage ==null then we can safely throw a ViewExpiredException? Nope, the condition is the same when navigating to another...
Fixed, thank you very much for reporting this peculiar corner case and improving OmniFaces!
Point taken, I'll take a second look later. Managing it via ViewScopeStorageInSession wasn't working as expected.
Fixed now.
Allowing real URL pattern would require more work for implementors and induce yet more ambiguity/confusion for endusers. E.g. when using minimal config, FacesServlet by default already listens on /faces/*, *.faces,...
The alternative would be to adjust the spec on this but this ends up ugly as it would still potentially confuse developers who don't carefully read the spec.
Bump, @tandraschko wdyt? It's not an uncommon demand and already implemented in PrimeFaces and OmniFaces. Seems it's about time to standardize it in h:message(s) as well.