[JBoss JIRA] (RF-12694) <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12694:
----------------------------------
Assignee: Brian Leathem
> <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
> ----------------------------------------------------------------------------------------
>
> Key: RF-12694
> URL: https://issues.jboss.org/browse/RF-12694
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.2.3.Final
> Environment: Tested in Galssfish3.1 and WAS8
> Reporter: Srinivas Reddy Malipeddi
> Assignee: Brian Leathem
> Priority: Minor
> Labels: richfaces, waiting_on_user
>
> When rich component like <rich:dropDownMenu is used, throwing warning"
> {quote}
> com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed.
> {quote}
> Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars
> My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming.
> {code:title=index.xhtml}
> <?xml version="1.0" encoding="UTF-8" ?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
>
> </h:head>
> <h:body>
> <rich:dropDownMenu label="IT Asset">
> <rich:menuItem label="Search" />
> <rich:menuItem label="Create" />
> </rich:dropDownMenu>
> </h:body>
> </ui:composition>
> {code}
> {code:title=Web.xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="3.0"
> xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
> <display-name>TestWeb</display-name>
> <context-param>
> <description>
> The location where state information is saved.
> Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
> saved as a hidden field in the form.
> Default is server.</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
> <context-param>
> <description>
> Comma-delimited list of context-relative resource paths under which the JSF implementation
> will look for application configuration resources, before loading a configuration resource
> named /WEB-INF/faces-config.xml (if such a resource exists).</description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value></param-value>
> </context-param>
> <context-param>
> <description>
> The default suffix for extension-mapped resources that contain JSF components.
> Default is '.jsp'.</description>
> <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
> <param-value>.xhtml</param-value>
> </context-param>
> <context-param>
> <description>
> A human readable string describing where this particular JSF application is
> in the software development lifecycle.
> Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'.
> Default is 'Production'.
> This parameter is not available in JSF 1.x.</description>
> <param-name>javax.faces.PROJECT_STAGE</param-name>
> <param-value>Development</param-value>
> </context-param>
> <context-param>
> <description>
> Monitors Faces JSP files for modifications and synchronizes a running server with
> the changes without restarting the server. If this parameter is set to false or
> removed from the deployment descriptor, any changes made to Faces JSP files may
> not be seen by the server until it is restarted. This parameter is usually set
> to true while the Faces JSP files are being developed and debugged in order to
> improve the performance of the development environment.</description>
> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
> <param-value>true</param-value>
> </context-param>
> <context-param>
> <description>
> Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
> JSF runtime will be loaded and initialized when the first JSF request is processed.
> This may disable custom JSF extensions, such as factories defined in the project.</description>
> <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
> <param-value>true</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>-1</load-on-startup>
> <enabled>true</enabled>
> <async-supported>false</async-supported>
> </servlet>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.xhtml</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> *.faces</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> /faces/*</url-pattern>
> </servlet-mapping>
> <welcome-file-list>
> <welcome-file>index.xhtml</welcome-file>
> </welcome-file-list>
> </web-app>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-12694) <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12694:
----------------------------------
Assignee: (was: Brian Leathem)
> <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."
> ----------------------------------------------------------------------------------------
>
> Key: RF-12694
> URL: https://issues.jboss.org/browse/RF-12694
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.2.3.Final
> Environment: Tested in Galssfish3.1 and WAS8
> Reporter: Srinivas Reddy Malipeddi
> Priority: Minor
> Labels: richfaces, waiting_on_user
>
> When rich component like <rich:dropDownMenu is used, throwing warning"
> {quote}
> com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed.
> {quote}
> Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars
> My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming.
> {code:title=index.xhtml}
> <?xml version="1.0" encoding="UTF-8" ?>
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
>
> </h:head>
> <h:body>
> <rich:dropDownMenu label="IT Asset">
> <rich:menuItem label="Search" />
> <rich:menuItem label="Create" />
> </rich:dropDownMenu>
> </h:body>
> </ui:composition>
> {code}
> {code:title=Web.xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="3.0"
> xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
> <display-name>TestWeb</display-name>
> <context-param>
> <description>
> The location where state information is saved.
> Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
> saved as a hidden field in the form.
> Default is server.</description>
> <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
> <param-value>server</param-value>
> </context-param>
> <context-param>
> <description>
> Comma-delimited list of context-relative resource paths under which the JSF implementation
> will look for application configuration resources, before loading a configuration resource
> named /WEB-INF/faces-config.xml (if such a resource exists).</description>
> <param-name>javax.faces.CONFIG_FILES</param-name>
> <param-value></param-value>
> </context-param>
> <context-param>
> <description>
> The default suffix for extension-mapped resources that contain JSF components.
> Default is '.jsp'.</description>
> <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
> <param-value>.xhtml</param-value>
> </context-param>
> <context-param>
> <description>
> A human readable string describing where this particular JSF application is
> in the software development lifecycle.
> Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'.
> Default is 'Production'.
> This parameter is not available in JSF 1.x.</description>
> <param-name>javax.faces.PROJECT_STAGE</param-name>
> <param-value>Development</param-value>
> </context-param>
> <context-param>
> <description>
> Monitors Faces JSP files for modifications and synchronizes a running server with
> the changes without restarting the server. If this parameter is set to false or
> removed from the deployment descriptor, any changes made to Faces JSP files may
> not be seen by the server until it is restarted. This parameter is usually set
> to true while the Faces JSP files are being developed and debugged in order to
> improve the performance of the development environment.</description>
> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
> <param-value>true</param-value>
> </context-param>
> <context-param>
> <description>
> Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
> JSF runtime will be loaded and initialized when the first JSF request is processed.
> This may disable custom JSF extensions, such as factories defined in the project.</description>
> <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
> <param-value>true</param-value>
> </context-param>
>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>-1</load-on-startup>
> <enabled>true</enabled>
> <async-supported>false</async-supported>
> </servlet>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.xhtml</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> *.faces</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>
> /faces/*</url-pattern>
> </servlet-mapping>
> <welcome-file-list>
> <welcome-file>index.xhtml</welcome-file>
> </welcome-file-list>
> </web-app>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13279) Extend Logger interface with method log(Level level, CharSequence message, Object... args);
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13279?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13279:
------------------------------------
The RichFaces logger is an abstraction over various logging implementations. We have to take care when we extend the interfaces to ensure that the new feature is supported by all anticipated logging implementations.
As a workaround, you can use String#format in the CharSequence.
> Extend Logger interface with method log(Level level, CharSequence message, Object... args);
> -------------------------------------------------------------------------------------------
>
> Key: RF-13279
> URL: https://issues.jboss.org/browse/RF-13279
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Minor
>
> Currently there are following methods:
> {code}
> void log(Level level, CharSequence content);
> void log(Level level, Throwable error, Enum<?> messageKey, Object... args);
> {code}
> But if someone wants to log String message and interpolate it with list of arguments, there is no equivalent available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13279) Extend Logger interface with method log(Level level, CharSequence message, Object... args);
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13279?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13279:
-------------------------------
Fix Version/s: 5-Tracking
> Extend Logger interface with method log(Level level, CharSequence message, Object... args);
> -------------------------------------------------------------------------------------------
>
> Key: RF-13279
> URL: https://issues.jboss.org/browse/RF-13279
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Minor
> Fix For: 5-Tracking
>
>
> Currently there are following methods:
> {code}
> void log(Level level, CharSequence content);
> void log(Level level, Throwable error, Enum<?> messageKey, Object... args);
> {code}
> But if someone wants to log String message and interpolate it with list of arguments, there is no equivalent available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months