[JBoss JIRA] Created: (RF-5113) scrollableDataTable: sorting feature doesn't work at all.
by Mikhail Vitenkov (JIRA)
scrollableDataTable: sorting feature doesn't work at all.
---------------------------------------------------------
Key: RF-5113
URL: https://jira.jboss.org/jira/browse/RF-5113
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: IE 6,7, FF 3.0.3, Opera 9.62, Safari 3.1(3.3.0 last snapshot)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Priority: Critical
#1. Add scrollableDataTable(SDT) rich component(use "sortMode" attribute for SDT and "sortBy", "sortable" attributes for rich:column):
<rich:scrollableDataTable
binding="#{scrollableDT.htmlScrollableDataTable}" id="sdt" var="sdt"
sortMode="#{scrollableDT.sortMode}" eventsQueue="myEventsQueue"
...
>
<f:facet name="header">
<h:outputText value="facet header"></h:outputText>
</f:facet>
<rich:column sortBy="#{sdt.int0}" sortable="true" id="colID">
<f:facet name="header">
<h:outputText value="#" />
</f:facet>
<h:outputText value="#{sdt.int0}"></h:outputText>
<f:facet name="footer">
<h:outputText value="#" />
</f:facet>
</rich:column>
...
</rich:scrollableDataTable>
#2. Navigate to page.
#3. Click on sortable column header two times.
Actual behavior:
Nothing happens.
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-5196) Editor does not rerender after converter error.
by Alexander Dubovsky (JIRA)
Editor does not rerender after converter error.
-----------------------------------------------
Key: RF-5196
URL: https://jira.jboss.org/jira/browse/RF-5196
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: 3.3.0.BETA2
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
Priority: Critical
# Input incorrect html in source mode (e.g. some tag is not closed and useSeamText=true):
<ol>
<li>first item</li>
<li>second item<li>
<li>and even the <i>third</i> item</li>
</ol>
# Rerender editor => converter error is triggered
# Correct html:
<ol>
<li>first item</li>
<li>second item</li>
<li>and even the <i>third</i> item</li>
</ol>
# Rerender editor
Result: error is disappeared. Seems like all is Ok, but...
# Submit page
Result: editor was disappeared from page
The same occurs in case custom converter was triggered.
If rerender editor after converter error in visual mode in JSP following exception was sent:
SEVERE: An exception occurred
javax.faces.FacesException: Exception while calling encodeEnd on component : {Component-Path : [Class: org.ajax4jsf.component.AjaxViewRoot,ViewId: /pages/Rich/Rich.jsp][Class: javax.faces.component.html.HtmlForm,Id: formID][Class: javax.faces.component.html.HtmlPanelGrid,Id: richGridID][Class: javax.faces.component.html.HtmlPanelGroup,Id: j_id_jsp_1726272691_12][Class: javax.faces.component.UINamingContainer,Id: editorSubviewID][Class: javax.faces.component.html.HtmlPanelGrid,Id: EditorPanelID][Class: org.richfaces.component.html.HtmlEditor,Id: editorID]}
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:627)
at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:286)
...................
Caused by: javax.faces.convert.ConverterException: Converter error
at editor.Editor$1.getAsString(Editor.java:95)
at org.ajax4jsf.util.InputUtils.getConvertedStringValue(InputUtils.java:114)
at org.richfaces.renderkit.EditorRendererBase.getConvertedStringValue(EditorRendererBase.java:87)
at org.richfaces.renderkit.EditorRendererBase.getFormattedComponentStringValue(EditorRendererBase.java:117)
at org.richfaces.renderkit.html.EditorRenderer.doEncodeEnd(EditorRenderer.java:234)
at org.richfaces.renderkit.html.EditorRenderer.doEncodeEnd(EditorRenderer.java:305)
at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:135)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:624)
... 49 more
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-5212) CLONE -Richfaces 3.2.2SR1 breaks SJSAS 9.2_01 Admin web-app, when the libs are put into domain1/lib folder
by John Leed (JIRA)
CLONE -Richfaces 3.2.2SR1 breaks SJSAS 9.2_01 Admin web-app, when the libs are put into domain1/lib folder
----------------------------------------------------------------------------------------------------------
Key: RF-5212
URL: https://jira.jboss.org/jira/browse/RF-5212
Project: RichFaces
Issue Type: Bug
Environment: Sun Java System Application Server 9.1 (build b58g-fcs)
Richfaces 3.1.2
Reporter: John Leed
Assignee: Tsikhon Kuprevich
Fix For: 3.2.1
When the Richfaces 3.1.2 libs are put into a domains lib folder under SJSAS 9.1, the Admin web application breaks.
I filed a bug report on glassfish https://glassfish.dev.java.net/issues/show_bug.cgi?id=3626 , here's what they had to say about this:
"In order to understand what is happening you have to know a little bit about how
JSF configures itself. It looks for faces-config.xml files in the classpath to
see if should add new jsf extensions (such as a new ViewHandler) to help it
process jsf pages. JSF does NOT do anything to ensure that a new component
(i.e. ViewHanler) doesn't break other custom jsf extensions. It is unfortunate
that these extensions can't be restricted to a subset of URLs, or be guarenteed
to behave well.
In this case, Ajax4JSF does not behave well. It both of your stack traces it
appears Ajax4JSF is not doing the right thing. In the first, it is not handling
the rendering of the page and has either changed the viewId or done something
else to cause the default viewHandler to also not handle it (it appears it is
redispatching recursively b/c of this). In the 2nd example, it is attempting to
handle a JSFTemplating page instead of delegating to JSFTemplating -- it is
unable to do so and fails.
Ajax4JSF could fix both of these problems -- I cannot. Based on these stack
traces, I would strongly suggest that you not include Ajax4JSF in a shared lib
area as it will effect ALL JSF applications, not just the ones you want it to
effect. Instead place the Ajax4JSF jar files in the WEB-INF/lib of your
application(s)."
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-5245) SuggestionBox: NumberConvertException on livedemo
by Nick Belaevski (JIRA)
SuggestionBox: NumberConvertException on livedemo
-------------------------------------------------
Key: RF-5245
URL: https://jira.jboss.org/jira/browse/RF-5245
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Priority: Critical
Fix For: 3.3.0
1. Open SB live demo
2. Type 'a', select 'austin' using mouse
3. Type 't' in input
Exception occurs in FF3, script error happens in IE7:
javax.faces.FacesException: java.lang.NumberFormatException: For input string: "undefined"
at javax.faces.component.UIData.invokeOnComponent(UIData.java:807)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:720)
at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:242)
at org.ajax4jsf.component.AjaxViewRoot.processDecodes(AjaxViewRoot.java:409)
at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:307)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:407)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:534)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.lang.NumberFormatException: For input string: "undefined"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at org.richfaces.component.UISuggestionBox.processDecodes(UISuggestionBox.java:477)
at org.ajax4jsf.component.AjaxViewRoot$1.invokeContextCallback(AjaxViewRoot.java:392)
at org.ajax4jsf.component.ContextCallbackWrapper.invokeContextCallback(ContextCallbackWrapper.java:44)
at javax.faces.component.UIData.invokeOnComponent(UIData.java:803)
... 41 more
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-4987) ajax response faise Javascript XML parser without jTidy
by Gal Rubinstein (JIRA)
ajax response faise Javascript XML parser without jTidy
-------------------------------------------------------
Key: RF-4987
URL: https://jira.jboss.org/jira/browse/RF-4987
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: win XP/Linux, jboss 4.2.2 GA + JDK 1.5u11
Reporter: Gal Rubinstein
in web.xml we added the contex-param/init -param to remove jTidy Filer:
--fragment---
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<context-param>
<param-name>org.richfaces.LoadScriptStrategy</param-name>
<param-value>ALL</param-value>
</context-param>
<context-param>
<param-name>org.richfaces.LoadStyleStrategy</param-name>
<param-value>ALL</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.COMPRESS_SCRIPT</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.SERIALIZE_SERVER_STATE</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.xmlparser.ORDER</param-name>
<param-value>NONE</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.xmlparser.NONE</param-name>
<param-value>.*</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.xmlfilter.forcenotrf</param-name>
<param-value>false</param-value>
</context-param>
<filter>
<display-name>RichFaces Filter</display-name>
<filter-name>richfaces</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
<init-param>
<param-name>enable-cache</param-name>
<param-value>true</param-value>
<init-param>
<param-name>forceparser</param-name>
<param-value>false</param-value>
</init-param>
</init-param>
</filter>
..........
--end fragment---
the JSP fragment causing this problem is apparently this (judging from from the id inside response):
--fragment---
<rich:simpleTogglePanel switchType="ajax"
bodyClass="toggle_panel_body" styleClass="toggle_panel"
headerClass="toggle_panel_header" id="panel_of_my_projects_list"
opened="true">
<%@ include file="simpleToggleMarkers.jsp"%>
<f:facet name="header">
<h:panelGrid
columnClasses="text_aligned_left,text_aligned_right"
styleClass="toggle_panel_header_controls" columns="2"
cellpadding="0" cellspacing="0" border="0">
<h:outputLabel styleClass="toggle_panel_header_caption"
value="#{msg.title_my_projects}"></h:outputLabel>
<h:commandLink onclick="event.cancelBubble=true;"
id="create_new_project_link"
actionListener="#{ProjectListBean.doCreateNewProject}"
value="#{msg.button_create_new_project}"
styleClass="non_toggling_panel_header_link_last_on_right_second_level"
action="projectDetailsBackground">
</h:commandLink>
</h:panelGrid>
</f:facet>
.....
-- end fragment---
a4j:log outputs:
--fragment---
error[15:58:07,101]: Error parsing XML
error[15:58:07,101]: Parse Error: XML Parsing Error: Whitespace is not allowed at this location.
Location: Line Number 56, Column 123:
<script type="text/javascript" language="Javascript">function dpf(f) {var adp = f.adp;if (adp != null) {for (var i = 0;i < adp.length;i++) {f.removeChild(adp[i]);}}};function apf(f, pvp) {var adp = new Array();f.adp = adp;var ps = pvp.split(',');for (var i = 0,ii = 0;i < ps.length;i++,ii++) {var p = document.createElement("input");p.type = "hidden";p.name = ps[i];p.value = ps[i + 1];f.appendChild(p);adp[ii] = p;i += 1;}};function jsfcljs(f, pvp, t) {apf(f, pvp);var ft = f.target;if (t) {f.target = t;}f.submit();f.target = ft;dpf(f);};</script>
---------------------------------------------------------------------------------------------------------------------------^
--end fragment---
finding this fragment inside the log console we can see this:
....
--fragment---
pvp.split(',');for (var i = 0,ii = 0;i < ps.length;i++,ii++) {var p = document.createElement("input");p.type = "hidden";p.name = ps[i];p.value = ps[i + 1];f.appendChild(p);adp[ii] = p;i += 1;}};function jsfcljs(f, pvp, t) {apf(f, pvp);var ft = f.target;if (t) {f.target = t;}f.submit();f.target = ft;dpf(f);};</script>
<a id="j_id_jsp_1399388119_3:create_new_project_link" href="#" onclick="var a=function(){event.cancelBubble=true;};var b=function(){if(typeof jsfcljs == 'function'){jsfcljs(document.forms['j_id_jsp_1399388119_3'],'j_id_jsp_1399388119_3:create_new_project_link,j_id_jsp_1399388119_3:create_new_project_link','');}return false};return (a()==false) ? false : b();" class="non_toggling_panel_header_link_last_on_right_second_level">Create a New Project</a></td>
</tr></tbody></table>
</div><div class="dr-stglpnl-b rich-stglpanel-body toggle_panel_body" id="j_id_jsp_1399388119_3:panel_of_my_projects_list_body" style="display : ; height: ;"><table border="0" cellpadding="0" cellspacing="0" width="100%">
<tbody><tr class="item_inside_panel"><td><
...... (notice th '<a href...>' id "matches" the one in jsp fragment
--end fragment---
between '</script>' and '<a id=...' there is a whitespace
--
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
14 years, 9 months