[JBoss JIRA] (RF-12666) Showcase - Drag and Drop with indicator - the styles do not apply for indicator when dragging over various targets
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12666?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12666:
----------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> Showcase - Drag and Drop with indicator - the styles do not apply for indicator when dragging over various targets
> ------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12666
> URL: https://issues.jboss.org/browse/RF-12666
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop, showcase
> Affects Versions: 4.3.0.M3
> Environment: Firefox 17, Chrome 23
> JBoss AS 7.1.1.Final
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Fix For: 4.3.0.CR1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When dragging a source over targets styles which should change the indicator color do not apply.
> It means that the indicator is still green, even when it is moved over target which is not proper drop place for it.
> Note that this works with metamer and that there are no new commits in that showcase sample.
> The DaD functionality works correctly and there are no JS errors or other exceptions. It is the same for the SNAPSHOT.
--
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
13 years, 4 months
[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12670:
------------------------------------
[~gonzalad] Are you able to bundle a JSF implementation with your deployment to Websphere? Are you able to ask IBM to update their JSF implementation? (2.1 has been available since [March 2011|http://javaserverfaces.java.net/nonav/2.1/releasenotes.html]
> JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> ---------------------------------------------------------------------------------------------------
>
> Key: RF-12670
> URL: https://issues.jboss.org/browse/RF-12670
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.M3
> Reporter: Dupont Dupont
> Fix For: 4.3.0.CR1
>
>
> When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a
> {code}
> java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION
> at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387)
> at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:793)
> at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007)
> at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90)
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142)
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at
> {code}
> RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor.
> See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288...
--
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
13 years, 4 months
[JBoss JIRA] (RF-12608) pickList without collectionType results in failure to lazily load
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12608?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12608:
-------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.M3)
> pickList without collectionType results in failure to lazily load
> -----------------------------------------------------------------
>
> Key: RF-12608
> URL: https://issues.jboss.org/browse/RF-12608
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.3.Final, 4.3.0.M2
> Reporter: Ken H
> Labels: regression
> Fix For: 4.3.0.CR1
>
>
> Changes to the selectManyHelper class in 4.2.3+ causes a lazy loading exception in hibernate when the backing collection is persistent and is not eagerly loaded.
> The problem seems to be that fetching the collection in SelectManyHelper.getConvertedValue bypasses the PersistentSet getter that would normally issue the lazy load request.
> Defining the collectionType (e.g. java.util.ArrayList) bypasses this issue.
> Ideally this method would detect Hibernate proxy collections and handle them appropriately. However, I realize that may cause a dependency so perhaps it would be enough to document this option and situation in the component reference.
> The stack trace for the exception is below:
> {code}
> [org.richfaces.log.Context] (http-localhost-127.0.0.1-8080-1) failed to lazily initialize a collection, no session or session was closed: org.hibernate.LazyInitializationException: failed to lazily initialize a collection, no session or session was closed
> at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:393) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:385) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:378) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.collection.internal.AbstractPersistentCollection.write(AbstractPersistentCollection.java:208) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
> at org.hibernate.collection.internal.PersistentBag.add(PersistentBag.java:291) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
> at org.richfaces.renderkit.SelectManyHelper.getConvertedValue(SelectManyHelper.java:350) [richfaces-components-ui-4.2.3.Final.jar:4.2.3.Final]
> at org.richfaces.renderkit.SelectManyRendererBase.getConvertedValue(SelectManyRendererBase.java:108) [richfaces-components-ui-4.2.3.Final.jar:4.2.3.Final]
> at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.2.3.Final.jar:4.2.3.Final]
> at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.2.3.Final.jar:4.2.3.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.2.3.Final.jar:4.2.3.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.2.3.Final.jar:4.2.3.Final]
> at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.2.3.Final.jar:4.2.3.Final]
> at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.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
13 years, 4 months
[JBoss JIRA] (RF-12313) Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12313?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12313:
-------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.M3)
> Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous
> -------------------------------------------------------------------------------------------
>
> Key: RF-12313
> URL: https://issues.jboss.org/browse/RF-12313
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.2.Final
> Reporter: Mark Bloomfield
> Priority: Minor
> Fix For: 4.3.0.CR1
>
>
> In the component referacne guide Example 9.7 the example states the value @previous as the keyword to use to switch to a previous panel. I believe it should be @prev as per the online example.
> The bug is in the text prior to the example and in the example itself.
> Please note I am new to RichFaces so perhaps it's wrong in the component? However I have tested with @prev and it works.
--
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
13 years, 4 months
[JBoss JIRA] (RF-12647) rich:dataTable rowclick with nested f:param
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12647:
-------------------------------
Labels: (was: waiting_on_user)
> rich:dataTable rowclick with nested f:param
> -------------------------------------------
>
> Key: RF-12647
> URL: https://issues.jboss.org/browse/RF-12647
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.0.M2
> Environment: Win7, JDK7, Glassfish3, Mojarra 2.1.14, SeamFaces, RF 4.x.x
> Reporter: Fab Mars
>
> During my migration from RF 3.3 I found this:
> Before (with RF 3.3.3):
> {code:xml|title="RF 3 Sample"}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:support event="onRowClick" reRender="shippingEditForm">
> <a4j:actionparam name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/>
> </a4j:support>
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> There was nothing really impacting on the migration guide
> https://community.jboss.org/wiki/RichFacesMigrationGuide33x-4xMigration-C...
> So I logically did that with RF4.x.x:
> {code:xml|title="RF 4 Sample 1"}
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping">
> <a4j:ajax event="rowclick" render="shippingEditForm">
> <a4j:param name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/>
> </a4j:ajax>
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> But the a4j:ajax isn't triggered (not at all, it's NOT a param assignment issue). To start having something that responds, one needs to remove the a4j:param and do it EL-newlook style.
> {code:xml|title="RF 4 Sample 2"}
> <a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/>
> {code}
> Anyhow we're close to RF-11446 and whenever that one gets fixed, one should check whether this case here is also solved.
> But wait, even that doesn't work: when one clicks on a row with that code, the listener is called but an ArrayIndexOutOfBoundsException is thrown because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself, NOT this of the row/cell. Hence, String rowId = clientId.substring(baseId.length() + 1) ends up tragically.
> So...to make it really work, you have to do what's described here: https://community.jboss.org/thread/174063 and not fall into the trap of RF-11446.
> Working code (RF 4.2.3+)
> {code:xml:xml|title="RF 4 Sample 3"}
> <a4j:jsFunction name="shippingListRowClick" render="shippingEditForm">
> <a4j:param name="shippingId" assignTo="#{shippingEdit.id}"/>
> </a4j:jsFunction>
> <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping" onrowclick="shippingListRowClick(#{shipping.id});">
> <rich:column>
> <f:facet name="header">
> <h:outputText value="Destination"/>
> </f:facet>
> <h:outputText value="#{shipping.destinationCountry.name}" />
> </rich:column>
> <!-- other columns here -->
> </rich:dataTable>
> {code}
> All that...for that.
> Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say we have a couple of regressions. Or at least that needs an extra clarification in the documentation and migration guide. Thank you.
--
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
13 years, 4 months
[JBoss JIRA] (RF-12645) rich:autoComplete's valueChangeListener property doesn't fire
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12645?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-12645 at 12/17/12 12:12 PM:
---------------------------------------------------------------
Thanks for reply. I appreciate your comments and the component start to work, but, I still have some problems with it I didn't have when I used to use it on Richfaces 3.3.x. Follow my questions:
- Is there a way the 'selectitem' event to be fired by the TAB key?
- How could I send some parameters to the backing bean when I select the item? I've been trying to use the jsFunction, but it doens't work, not even a4j:param.
This is my code snippet:
{code}
<h:form>
<a4j:jsFunction action="#{autoCompleteController.ajaxMethod}"
name="ajaxSend">
<a4j:param name="param1" assignTo="#{autoCompleteController.code}" />
</a4j:jsFunction>
<h:panelGrid columns="2">
<h:outputText value="Name:" />
<rich:autocomplete id="auto" mode="ajax"
autocompleteMethod="#{autoCompleteController.autoComplete()}"
var="person" fetchValue="#{person.name}"
layout="table" onselectitem="ajaxSend(#{person.code})"
value="#{autoCompleteController.name}">
<rich:column>
<h:outputText value="#{person.name}" />
</rich:column>
<rich:column>
<h:outputText value="#{person.code}" />
</rich:column>
</rich:autocomplete>
</h:panelGrid>
</h:form>
{code}
I want to send the value 'person.code' to the managed bean when I select the item.
Thank for your attention and time
Junior
was (Author: junior.mendes):
Thanks for reply. I appreciate your comments and the component start to work, but, I still have some problems with it I didn't have when I used to use it on Richfaces 3.3.x. Follow my questions:
- Is there a way the 'selectitem' event to be fired by the TAB key?
- How could I send some parameters to the backing bean when I select the item? I've been trying to use the jsFunction, but it doens't work, not even a4j:param.
This is my code snippet:
<h:form>
<a4j:jsFunction action="#{autoCompleteController.ajaxMethod}"
name="ajaxSend">
<a4j:param name="param1" assignTo="#{autoCompleteController.code}" />
</a4j:jsFunction>
<h:panelGrid columns="2">
<h:outputText value="Name:" />
<rich:autocomplete id="auto" mode="ajax"
autocompleteMethod="#{autoCompleteController.autoComplete()}"
var="person" fetchValue="#{person.name}"
layout="table" onselectitem="ajaxSend(#{person.code})"
value="#{autoCompleteController.name}">
<rich:column>
<h:outputText value="#{person.name}" />
</rich:column>
<rich:column>
<h:outputText value="#{person.code}" />
</rich:column>
</rich:autocomplete>
</h:panelGrid>
</h:form>
I want to send the value 'person.code' to the managed bean when I select the item.
Thank for your attention and time
Junior
> rich:autoComplete's valueChangeListener property doesn't fire
> -------------------------------------------------------------
>
> Key: RF-12645
> URL: https://issues.jboss.org/browse/RF-12645
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.2.2.Final
> Environment: Google Chrome Version 21.0.1180.89;
> Debian wheezy/sid
> Richfaces 4.2.2
> Reporter: Valdir Mendes Junior
> Labels: valueChangeListener, waiting_on_user
>
> After made the search, I select the option and expected the valueChangeListener method to be called, but it' doesn't.
--
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
13 years, 4 months
[JBoss JIRA] (RF-12460) RF-11138 Tree does not invoke selectionChangeListener in popupPanel with 4.2.0 final also
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12460?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12460:
------------------------------------
[~ppitonak] thanks for reproducing the issue and providing a work around
> RF-11138 Tree does not invoke selectionChangeListener in popupPanel with 4.2.0 final also
> -----------------------------------------------------------------------------------------
>
> Key: RF-12460
> URL: https://issues.jboss.org/browse/RF-12460
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.0.Final, 4.3.0.M2
> Reporter: venkat kavali
> Assignee: Brian Leathem
>
> Rich Tree working fine below source code. But same code applied in Popup panel, unable to get selected Item. Popup div also within same form.
> Working Fine below code
> {code}
> <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul"
> selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax">
> <rich:treeNode>
> <h:outputText value="#{node}" />
> </rich:treeNode>
> </rich:tree>
> {code}
> Please provide solution ASAP. This is showstopper for me.
> Problem Here
> {code}
> <rich:popupPanel id="popup" modal="true" autosized="true" resizeable="false" overlapEmbedObjects="true">
> <f:facet name="header">
> <h:outputText value="Tree View" />
> </f:facet>
> <f:facet name="controls">
> <h:outputLink value="#" onclick="#{rich:component('popup')}.hide(); return false;">X</h:outputLink>
> </f:facet>
> <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul"
> selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax">
> <rich:treeNode>
> <h:outputText value="#{node}" />
> </rich:treeNode>
> </rich:tree>
> </rich:popupPanel
> {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
13 years, 4 months