Stan, I'm not using StartupServletContextListener in the portlet configuration. Without Ajax4JSF, all is working fine.
However, without Ajax4JSF, the exception above is still thrown, even though everything works. So, clearly, something still isn't quite right, even though everything "works". My point is that, possibly, if the reason why the exception is thrown on a working config can be identified and sorted out, Ajax4JSF might work. I'm not familiar enough with the codebase at the moment to figure it out. Andy. Andy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981624#3981624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981624 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
