[JBoss JIRA] (RF-12943) ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12943:
-------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
> ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly
> ---------------------------------------------------------------------------------------
>
> Key: RF-12943
> URL: https://issues.jboss.org/browse/RF-12943
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.1
> Environment: Tomcat 7, Mojarra 2.1.21
> Reporter: dako ak
> Labels: testcase_provided
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: JSF2-RichFaces-Test.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> According to my appended test project:
> I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too.
> The second problem with the input filter is that I can't clear this filter input text components by a a4j:commandButton. The table is correct filtered but the filter input text fields are not cleared.
--
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-12891) Datatable with ExtendedDataModel ajax call
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12891?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12891:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> Datatable with ExtendedDataModel ajax call
> ------------------------------------------
>
> Key: RF-12891
> URL: https://issues.jboss.org/browse/RF-12891
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.1
> Environment: apache-tomcat-7.0.34, servlet-weld 1.1.11.
> Reporter: tehackio teha
> Priority: Critical
> Labels: ExtendedDataModel, UIDataAdaptor, a4j:commandLink, datatable
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> If one ajax call inside column of datatable(org.ajax4jsf.model.ExtendedDataModel) to render outside, method walk is called many times;
> On org.richfaces.component.UIDataAdaptor.requiresRowIteration(VisitContext context), context.getFacesContext().getAttributes().get("javax.faces.visit.SKIP_ITERATION") returns "null", therefore "false".
--
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-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12675:
-------------------------------
Original Estimate: 2 hours (was: 2 minutes)
Remaining Estimate: 2 hours (was: 2 minutes)
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: Drag, drop, myfaces
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12675:
-------------------------------
Original Estimate: 2 minutes
Remaining Estimate: 2 minutes
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: Drag, drop, myfaces
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
> Original Estimate: 2 minutes
> Remaining Estimate: 2 minutes
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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-11469) autocomplete method does not resolve bean if ui:included
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11469:
-------------------------------
Priority: Minor (was: Major)
> autocomplete method does not resolve bean if ui:included
> --------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Priority: Minor
> Fix For: 4.3.4, 5-Tracking
>
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {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-9653) popupPanel: trimOverlayedElements not working
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-9653?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem updated RF-9653:
------------------------------
Description:
{code}
<rich:popupPanel show="true" trimOverlayedElements="false">
<rich:panel id="panel">
test1
<rich:tooltip>
test2
</rich:tooltip>
</rich:panel>
...
{code}
tooltip should not be cut by table borders in that case but it is being cut actually.
was:
<rich:popupPanel show="true" trimOverlayedElements="false">
<rich:panel id="panel">
test1
<rich:tooltip>
test2
</rich:tooltip>
</rich:panel>
...
tooltip should not be cut by table borders in that case but it is being cut actually.
> popupPanel: trimOverlayedElements not working
> ---------------------------------------------
>
> Key: RF-9653
> URL: https://issues.jboss.org/browse/RF-9653
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.0.0.Milestone4, 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_06-b24 @ Linux
> Firefox 21.0 @ Linux x86_64
> Reporter: Ilya Shaikovsky
> Fix For: 4.0.0.Milestone6, 5-Tracking
>
>
> {code}
> <rich:popupPanel show="true" trimOverlayedElements="false">
> <rich:panel id="panel">
>
> test1
> <rich:tooltip>
> test2
> </rich:tooltip>
> </rich:panel>
> ...
> {code}
> tooltip should not be cut by table borders in that case but it is being cut actually.
--
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-11469) autocomplete method does not resolve bean if ui:included
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11469:
-------------------------------
Original Estimate: 45 minutes
Remaining Estimate: 45 minutes
> autocomplete method does not resolve bean if ui:included
> --------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Priority: Minor
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {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-13098) Regression: mediaOutput broken for CDI MediaData beans
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13098.
--------------------------------
Labels: (was: regression)
Resolution: Cannot Reproduce Bug
Thanks [~manovotn], it's good to know the _SerializableResource_ interface works as expected.
Closing as unreproducible.
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {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-13128) Automatic rendering of transitive dependencies
by Juraj Húska (JIRA)
Juraj Húska created RF-13128:
--------------------------------
Summary: Automatic rendering of transitive dependencies
Key: RF-13128
URL: https://issues.jboss.org/browse/RF-13128
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: architectural, base functionality, core
Affects Versions: 5.0.0.Alpha1
Reporter: Juraj Húska
Priority: Minor
Consider please following pseudo code for using {{r:dataScroller}}:
{code:xml}
<r:dataScroller id="topScroller" for="table" />
<r:dataTable>
<r:column>Blah</r:column>
<f:facet name="footer">
<r:dataScroller render="topScroller"/>
</f:facet>
</r:dataTable>
{code}
When the bottom scroller is changed, then the top scroller is as well, because the bottom one has {{render}} attribute set correctly.
It would be IMHO nice addition, if this had been done automatically. The {{r:dataTable}} may know which scroller is bound to it, and update it automatically.
[~lfryc] idea for general implementation:
??Support for it does not exist in JSF/RF right now. But it can be added. If you have {{render="A"}}, then also X would be rendered, where X are all transitive dependencies, which make the component. A component can have an interface, to which you can register those explicit targets. Datascroller would use such interface.??
--
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