[JBoss JIRA] Created: (RF-7396) The level attribute on <richfaces:messages /> does not work properly
by Sondre Eikanger Kvalø (JIRA)
The level attribute on <richfaces:messages /> does not work properly
--------------------------------------------------------------------
Key: RF-7396
URL: https://jira.jboss.org/jira/browse/RF-7396
Project: RichFaces
Issue Type: Bug
Components: component, component-output
Affects Versions: 3.3.1
Environment: Windows XPSP3, Tomcat 6, Myfaces 1.2.7
Reporter: Sondre Eikanger Kvalø
We're trying to limit the messages rendered using the level attribute on the <rich:messages /> tag.
However, no matter what values we specify for the level attribute it renders no messages. Leaving out the attribute renders all messages.
Looking through the source we observed that the attribute value was "uppercased" before it was compared with the severity property on the message in the isApplicableMessages method in the UIRichMessages class. After comparing the value of the severity property on the message with an object from the list of severities the method returns with the statement severenities.contains(key) and this will never return true as the "key" parameter is camel case (eg: Error) while the severenities list (retrieved from the tag attribute) use upper case string values (eg: INFO, ERROR).
See comments below! :-)
protected boolean isApplicableMessage(List<String> severenities,
FacesMessage message) {
if (severenities.size() == 0 || severenities.contains("ALL")) {
return true;
}
Severity severity = message.getSeverity();
for (Object key : FacesMessage.VALUES_MAP.keySet()) {
Severity sev = (Severity) FacesMessage.VALUES_MAP.get(key);
if (0 == sev.compareTo(severity)) {
// Make the value of the "key" uppercase before invoking "contains"
return severenities.contains(key.toString().toUpperCase());
// original source
return severenities.contains(key);
}
}
return false;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RF-7698) java.lang.IllegalStateException when using rich:editor under Resin 4.0.1
by Mikhail Vitenkov (JIRA)
java.lang.IllegalStateException when using rich:editor under Resin 4.0.1
------------------------------------------------------------------------
Key: RF-7698
URL: https://jira.jboss.org/jira/browse/RF-7698
Project: RichFaces
Issue Type: Bug
Components: component-input
Affects Versions: 3.3.2.CR1
Environment: Resin 4.0.1(http://www.caucho.com/download/); all supported browsers; Vista SP2
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Priority: Critical
#1. Build richfaces-demo.
#2. Before deploying move jsf-api & jsf-impl-1.2_12 jars from project web-inf/lib to resin 'lib' folder. Copy tools.jar from JAVA_HOME/lib directory to resin 'lib' folder.
#3. Copy builded richfaces-demo into server 'webapps' folder and run server.
#4. Navigate to http://localhost:8080/richfaces-demo
#5. Go to rich:editor page in Rich Input section.
#6. Select Advanced "Select Editor Theme" option.
Actual results:
Editor have broken layout. Exception below take place:
[09-08-13 17:11:52.549] {http--8080-9} WebApp[http://default/richfaces-demo] jav
a.lang.IllegalStateException: http://localhost:8080/richfaces-demo/a4j/g/3_3_2-S
NAPSHOTscripts/tiny_mce/themes/advanced/skins/richfaces/ui.xcss/DATB/eAFb-IhhU-j
yGdIAE0wD5Q__.jsf: tried to write 19002 bytes with content-length 18739 (At 'a',
char=97). Check that the Content-Length header correctly matches the expected
bytes, and ensure that any filter which modifies the content also suppresses the
content-length (to use chunked encoding).
[09-08-13 17:11:52.549] {http--8080-9} java.lang.IllegalStateException: http://l
ocalhost:8080/richfaces-demo/a4j/g/3_3_2-SNAPSHOTscripts/tiny_mce/themes/advance
d/skins/richfaces/ui.xcss/DATB/eAFb-IhhU-jyGdIAE0wD5Q__.jsf: tried to write 1900
2 bytes with content-length 18739 (At 'a', char=97). Check that the Content-Len
gth header correctly matches the expected bytes, and ensure that any filter whic
h modifies the content also suppresses the content-length (to use chunked encodi
ng).
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.Response
Stream.lengthException(ResponseStream.java:661)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.Response
Stream.setBufferOffset(ResponseStream.java:464)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.vfs.i18n.ISO8859_1Writer.w
rite(ISO8859_1Writer.java:134)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.ToByteRe
sponseStream.flushCharBuffer(ToByteResponseStream.java:488)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.ToByteRe
sponseStream.flushBuffer(ToByteResponseStream.java:441)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.Response
Stream.flush(ResponseStream.java:691)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.Response
Stream.flushChar(ResponseStream.java:739)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.connection.Response
Writer.flush(ResponseWriter.java:174)
[09-08-13 17:11:52.549] {http--8080-9} at org.ajax4jsf.webapp.CacheContent.flus
h(CacheContent.java:319)
[09-08-13 17:11:52.549] {http--8080-9} at org.ajax4jsf.resource.InternetResourc
eService.serviceResource(InternetResourceService.java:217)
[09-08-13 17:11:52.549] {http--8080-9} at org.ajax4jsf.resource.InternetResourc
eService.serviceResource(InternetResourceService.java:141)
[09-08-13 17:11:52.549] {http--8080-9} at org.ajax4jsf.webapp.BaseFilter.doFilt
er(BaseFilter.java:508)
[09-08-13 17:11:52.549] {http--8080-9} at org.jboss.seam.web.Ajax4jsfFilter.doF
ilter(Ajax4jsfFilter.java:56)
[09-08-13 17:11:52.549] {http--8080-9} at org.jboss.seam.servlet.SeamFilter$Fil
terChainImpl.doFilter(SeamFilter.java:69)
[09-08-13 17:11:52.549] {http--8080-9} at org.jboss.seam.servlet.SeamFilter.doF
ilter(SeamFilter.java:158)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.dispatch.FilterFilt
erChain.doFilter(FilterFilterChain.java:87)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.webapp.WebAppFilter
Chain.doFilter(WebAppFilterChain.java:184)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.dispatch.ServletInv
ocation.service(ServletInvocation.java:264)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.http.HttpRequest.ha
ndleRequest(HttpRequest.java:280)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.port.TcpConnection.
handleRequests(TcpConnection.java:579)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.port.TcpConnection$
AcceptTask.doAccept(TcpConnection.java:1357)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.server.port.TcpConnection$
AcceptTask.run(TcpConnection.java:1298)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.util.ThreadPool$PoolThread
.runTasks(ThreadPool.java:874)
[09-08-13 17:11:52.549] {http--8080-9} at com.caucho.util.ThreadPool$PoolThread
.run(ThreadPool.java:787)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (RF-7704) simpleTogglePanel: doesn't became collapsed in ajax and server mode.
by Mikhail Vitenkov (JIRA)
simpleTogglePanel: doesn't became collapsed in ajax and server mode.
--------------------------------------------------------------------
Key: RF-7704
URL: https://jira.jboss.org/jira/browse/RF-7704
Project: RichFaces
Issue Type: Bug
Components: component-panels-layout-themes
Affects Versions: 3.3.2.CR1
Environment: all supported browsers; jsf1.2_12; rf 3.3.2.CR1
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Priority: Critical
#1. Use code listed below:
<h:form>
<rich:simpleTogglePanel switchType="ajax" label="Ajax Switch Type" height="90px">
This type allows to perform the partial view update instead of the
whole page reloading. You also can reRender other components
while the panel content is toggled.
</rich:simpleTogglePanel>
</h:form>
#2. Navigate to the page and click on STP header.
Actual behavior:
Text content is disappeared, but panel isn't collapsed. The same issue for switchType="server". For 'client' mode it works fine.
It works fine for all modes in 3.3.1.GA richfaces libs(regression issue).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months