I want to use client STATE_SAVING_METHOD in my jsf portlet. When I test portlet like separate jsf application it works ok.
But when I make a portlet from this jsf application and inject it into jboss
I receive in the log :
11:00:25,346 ERROR [CommandFilter] Exception in command invocation
org.apache.jasper.JasperException: serialFactory at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
when I set
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
the portlet started to work but the logic of my app requires STATE_SAVING_METHOD = client
Can anybody help me with this problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984444#3984444
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984444
Is there any way to stop specific exception messages that are thrown during page execution from hitting the logs?
My JSPs commonly throw a SecurityException when the user visits a deep link and is not yet logged in. This is handled nicely by a custom error page that recognizes the specific error. However, it still results in an exception in the logs. Unfortunately this case is common enough that it floods my logs with garbage and makes the real problems hard to find.
Is there a way to say that some (or even all) exceptions thrown while executing JSPs should not log stacktraces? Disabling all log output from org.apache.catalina.core.ContainerBase seems far too heavy-handed.
Thanks,
Jeff
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984439#3984439
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984439