[JBoss JIRA] Created: (RF-4312) Toolbar: HTML events are dublicated in children elements
by Tsikhon Kuprevich (JIRA)
Toolbar: HTML events are dublicated in children elements
--------------------------------------------------------
Key: RF-4312
URL: https://jira.jboss.org/jira/browse/RF-4312
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: 3.2.2.BETA5
Reporter: Tsikhon Kuprevich
Assignee: Nick Belaevski
Here is a page code:
<rich:toolBar ondblclick="alert('ondblclick');" onkeydown="alert('onkeydown');"
onkeypress="alert('onkeypress');" onkeyup="alert('onkeyup');"
onmousedown="alert('onmousedown');" onmousemove="alert('onmousemove');"
onmouseout="alert('onmouseout');" onmouseover="alert('onmouseover');"
onmouseup="alert('onmouseup');" >
<h:outputLink value="#" onclick="enlarge('#{rich:clientId('pic')}');">
Enlarge
</h:outputLink>
<h:outputLink value="#"
onclick="decrease('#{rich:clientId('pic')}');">Decrease</h:outputLink>
</rich:toolBar>
<rich:panel>
<h:graphicImage value="#{slidesBean.currentPicture}" id="pic" />
</rich:panel>
<rich:toolBar>
<a4j:commandLink value="<< Previous"
action="#{slidesBean.previous}" reRender="slide"
disabled="#{not (slidesBean.currentIndex > 1)}" />
<a4j:commandLink value="Next >>" action="#{slidesBean.next}"
reRender="slide" disabled="#{(slidesBean.currentIndex == 8)}" />
</rich:toolBar>
Here is HTML generated:
<form id="j_id_jsp_1491964007_1" name="j_id_jsp_1491964007_1" method="post" action="/jsp/CustomizePage/CustomizePage.jsf" enctype="application/x-www-form-urlencoded"><table border="0" cellpadding="0" cellspacing="0" class="dr-toolbar-ext rich-toolbar " id="j_id_jsp_1491964007_1:j_id_jsp_1491964007_2" ondblclick="alert('ondblclick');" onkeydown="alert('onkeydown');" onkeypress="alert('onkeypress');" onkeyup="alert('onkeyup');" onmousedown="alert('onmousedown');" onmousemove="alert('onmousemove');" onmouseout="alert('onmouseout');" onmouseover="alert('onmouseover');" onmouseup="alert('onmouseup');" width="100%"><tr valign="middle"><td class="dr-toolbar-int rich-toolbar-item " onkeydown=";alert('onkeydown');" onkeypress=";alert('onkeypress');" onkeyup=";alert('onkeyup');" ondblclick=";alert('ondblclick');" onmousedown=";alert('onmousedown');" onmousemove=";alert('onmousemove');" onmouseover=";alert('onmouseover');" onmouseout=";alert('onmouseout');" onmouseup=";alert('onmouseup');"><a href="#" onclick="enlarge('j_id_jsp_1491964007_1:pic');">
Enlarge
</a></td><td class="dr-toolbar-int rich-toolbar-item " onkeydown=";alert('onkeydown');" onkeypress=";alert('onkeypress');" onkeyup=";alert('onkeyup');" ondblclick=";alert('ondblclick');" onmousedown=";alert('onmousedown');" onmousemove=";alert('onmousemove');" onmouseover=";alert('onmouseover');" onmouseout=";alert('onmouseout');" onmouseup=";alert('onmouseup');"><a href="#" onclick="decrease('j_id_jsp_1491964007_1:pic');">Decrease</a></td><td width="100%"></td></tr></table><div class="dr-pnl rich-panel " id="j_id_jsp_1491964007_1:j_id_jsp_1491964007_5"><div class="dr-pnl-b rich-panel-body " id="j_id_jsp_1491964007_1:j_id_jsp_1491964007_5_body"><img id="j_id_jsp_1491964007_1:pic" /></div></div><table border="0" cellpadding="0" cellspacing="0" class="dr-toolbar-ext rich-toolbar " id="j_id_jsp_1491964007_1:j_id_jsp_1491964007_7" width="100%"><tr valign="middle"><td class="dr-toolbar-int rich-toolbar-item "><a href="#" id="j_id_jsp_1491964007_1:j_id_jsp_1491964007_8" name="j_id_jsp_1491964007_1:j_id_jsp_1491964007_8" onclick="return false;">&lt;&lt; Previous</a></td><td class="dr-toolbar-int rich-toolbar-item ">
--
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, 9 months
[JBoss JIRA] Created: (RF-3758) add a4j:supportAll to mirror Seam's s:validateAll
by Dan Allen (JIRA)
add a4j:supportAll to mirror Seam's s:validateAll
-------------------------------------------------
Key: RF-3758
URL: http://jira.jboss.com/jira/browse/RF-3758
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.1
Reporter: Dan Allen
Priority: Minor
Fix For: 3.2.2
To save the developer from having to add the <s:validate> tag to every input component, Seam introduced the <s:validateAll> tag which walks its descendents and applies the Seam model validator to the input components. The same technique could be added to Ajax4jsf to avoid the need of having to add the <a4j:support> tag to every input.
Often times you see the following markup:
<h:panelGroup id="fieldNameGroup">
<h:inputText id="fieldName" value="#{model.fieldName">
<a4j:support event="onblur" ajaxSingle="true" bypassUpdates="true" reRender="fieldNameGroup"/>
</h:inputText>
<h:message for="fieldName"/>
</h:panelGroup>
It sure would be nice to be able to simplify this to the following:
<h:panelGroup id="fieldNameGroup">
<a4j:supportAll event="onblur" ajaxSingle="true" bypassUpdates="true" reRender="fieldNameGroup">
<h:inputText id="fieldName" value="#{model.fieldName}"/>
</a4j:supportAll>
<h:message for="fieldName"/>
</h:panelGroup>
At first, you may think to yourself what the difference is. Well, a Facelet template can accomodate the second example to eliminate the need to specify the <a4j:support> tag. The first example cannot since there is no way to add a child element to a component passed into a template. So you could reduce this to:
<s:decorate id="fieldNameDecorate" template="layout/edit.xhtml">
<ui:param name="reRender" value="fieldNameDecorate"/>
<h:inputText id="fieldName" value="#{model.fieldName}"/>
</s:decorate>
We could even modify Seam to make the id of the decorate component available to the template so that the reRender parameter is not necessary. The template would look like the second example above, except that the input component would be replaced with <ui:insert/> and the value of reRender would be set to #{reRender}. The other benefit, of course, is that it is easy to turn on and off Ajax4jsf.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (RF-4082) beanValidator: "id", "binding" & "rendered" attributes using lead to the exception listed below.
by Mikhail Vitenkov (JIRA)
beanValidator: "id", "binding" & "rendered" attributes using lead to the exception listed below.
------------------------------------------------------------------------------------------------
Key: RF-4082
URL: https://jira.jboss.org/jira/browse/RF-4082
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: IE6, IE7, FF 3.1, Opera 9.27, Safari 3.1(3.2.2.BETA3)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Stack trace:
An exception occurred
javax.faces.FacesException: /Validator/ValidatorStraightforward.jsp(74,1) Attribute binding invalid for tag beanValidator according to TLD
at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:344)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.buildView(JspViewHandlerImpl.java:480)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:334)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:193)
at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:150)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:379)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:506)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Similar exception take place for others two attributes.
--
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, 9 months
[JBoss JIRA] Created: (RF-3946) contextMenu: if parent component doesn't have manually defined id contextMenu won't appear
by Tatyana Romanovich (JIRA)
contextMenu: if parent component doesn't have manually defined id contextMenu won't appear
------------------------------------------------------------------------------------------
Key: RF-3946
URL: https://jira.jboss.org/jira/browse/RF-3946
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: jsp
test application
Tomcat 6
all browsers
3.2.2.BETA1
Reporter: Tatyana Romanovich
Assignee: Nick Belaevski
1. Go to the jsp test application
2. Select contextMenu component
3. Set event="onclick"
4. Try to call context menu for firs tested panel (panel with contextMenu(DEFAULT) testing events)
Result: contextMenu doesn't appear
Another Scenario:
1. create tested application with two examples for context menu: firs example: parent component has id, second: parent component doesn't have id:
<h:outputText id="text2" value="Some text with context menu2">
<rich:contextMenu>
<rich:menuItem value="a">
<f:param name="cmdParam" value="a" />
</rich:menuItem>
</rich:contextMenu>
</h:outputText>
<h:outputText value="Some text with context menu3">
<rich:contextMenu>
<rich:menuItem value="b">
<f:param name="cmdParam" value="b" />
</rich:menuItem>
</rich:contextMenu>
</h:outputText>
2. Run application on the server
3. Try to call context menu for each example
result: context menu doesn't appear for second example (where parent component doesn't have id)
--
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, 9 months
[JBoss JIRA] Created: (RF-3847) Error using custom components inside scrollableDataTable
by Ilya Musihin (JIRA)
Error using custom components inside scrollableDataTable
--------------------------------------------------------
Key: RF-3847
URL: http://jira.jboss.com/jira/browse/RF-3847
Project: RichFaces
Issue Type: Feature Request
Reporter: Ilya Musihin
We are developing custom JSF components and have found the following problem when placing our components inside of <rich:scrollableDataTable> component. Everything worked fine before we added the "col" tag as part of our component. Now if we use our component inside of <rich:scrollableDataTable> , we get the JavaScript error "columns[j] has no properties" appear. Our investigation has shown that this error is caused by the specifics of implementation of RichFaces' scrollable-date-table.js.jsf JavaScript file that uses function getElementsByTagName("col") in line 149:
cols=this.templNormal.getElement().getElementsByTagName("col");for(i=0;i<cols.length;i++){columns[j].bodyCol=$(cols[i]);j++;}
This piece of code works correctly unless a component inside of ScrollableDataTable component renders its own "col" tags. So the problem of interoperability of such components with ScrollableDataTable would be solved if the mentioned code would just retrieve ScrollableDataTable's own "col" tags without searching the inner parts of sub-components.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months