[JBoss JIRA] (RF-13541) Photoalbum - JPA tests
by Michal Petrov (JIRA)
Michal Petrov created RF-13541:
----------------------------------
Summary: Photoalbum - JPA tests
Key: RF-13541
URL: https://issues.jboss.org/browse/RF-13541
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.5.0.Alpha1
Reporter: Michal Petrov
In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD)
It's not currently runnable (outdated dependencies and/or settings).
Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run.
--
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
10 years, 4 months
[JBoss JIRA] (RF-12801) Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB
by Erdem YILMAZ (JIRA)
[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ]
Erdem YILMAZ closed RF-12801.
-----------------------------
Resolution: Partially Completed
it seems an OWB bug
> Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB
> ------------------------------------------------------------------------------------
>
> Key: RF-12801
> URL: https://issues.jboss.org/browse/RF-12801
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.3.0.Final
> Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final
> Reporter: Erdem YILMAZ
> Labels: ELResolver, optimization, owb, resource, websphere
> Fix For: 5-Tracking
>
>
> when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere.
> resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour.
> we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13251:
----------------------------
Labels: (was: waiting_on_user)
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
> Key: RF-13251
> URL: https://issues.jboss.org/browse/RF-13251
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.4
> Reporter: Immo Benjes
> Assignee: Lukáš Fryč
> Priority: Minor
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13531) selects: cannot select option on IE11
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13531:
-------------------------------
Labels: IE11 (was: IE11 needs-qe)
> selects: cannot select option on IE11
> -------------------------------------
>
> Key: RF-13531
> URL: https://issues.jboss.org/browse/RF-13531
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3
> Environment: IE 11
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Labels: IE11
> Fix For: 4.3.6
>
>
> Components: autocomplete, select, inplaceSelect.
> Works on IE 10.
> ----
> Issues:
> * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class.
> ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}.
> ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller.
> * User cannot select option with keyboard.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times
by Sebastian Cramer (JIRA)
Sebastian Cramer created RF-13540:
-------------------------------------
Summary: Websphere incarnation of MyFaces renderes optimized resources multiple times
Key: RF-13540
URL: https://issues.jboss.org/browse/RF-13540
Project: RichFaces
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 5.0.0.Alpha3, 4.3.5
Environment: Myfaces/Websphere on all platforms
Reporter: Sebastian Cramer
When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl.
--
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
10 years, 4 months
[JBoss JIRA] (RF-12801) Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB
by Sebastian Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ]
Sebastian Cramer commented on RF-12801:
---------------------------------------
The workaround by [~mayerle] works (just triggers a different bug - refer to the forum thread for info). Since this issue seems to be a OWB bug I would suggest closing it (for now).
> Use of Resource Optimization prevents the WebBeansELResolver from registering in OWB
> ------------------------------------------------------------------------------------
>
> Key: RF-12801
> URL: https://issues.jboss.org/browse/RF-12801
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.3.0.Final
> Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final
> Reporter: Erdem YILMAZ
> Labels: ELResolver, optimization, owb, resource, websphere
> Fix For: 5-Tracking
>
>
> when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere.
> resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour.
> we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete
by Immo Benjes (JIRA)
[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ]
Immo Benjes commented on RF-13251:
----------------------------------
Hi Lukáš,
sorry I am quite busy at the moment but it is really easy to reproduce. Just have a rich:autocomplete and an ajax button. The ajax button submits and rerenders the form. The action method on the a:commandButton tries to set the focus on the rich:autocomplete with the FocusManager - done. You probably have a 'test' autocomplete component flying around anyway.
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
> Key: RF-13251
> URL: https://issues.jboss.org/browse/RF-13251
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.4
> Reporter: Immo Benjes
> Assignee: Lukáš Fryč
> Priority: Minor
> Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13378) extendedDataTable not shown inside Bootstrap tab panel
by Steve Oh (JIRA)
[ https://issues.jboss.org/browse/RF-13378?page=com.atlassian.jira.plugin.s... ]
Steve Oh edited comment on RF-13378 at 2/11/14 6:16 AM:
--------------------------------------------------------
REMOVED
was (Author: cc2000):
same problem with me (using rich:tabPanel), I am digging into suspected javascript - see this snippet from extendedDataTable.js:
{code:javascript}
initialize: function() {
this.deActivateResizeListener();
if (! $(this.element).is(":visible")) {
this.showOffscreen(this.element);
}
{code}
> extendedDataTable not shown inside Bootstrap tab panel
> ------------------------------------------------------
>
> Key: RF-13378
> URL: https://issues.jboss.org/browse/RF-13378
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4
> Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2
> Reporter: Salvo Isaja
> Labels: extendedDataTable
> Fix For: 5-Tracking
>
> Attachments: ExtendedDataTableTest.7z
>
>
> As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3.
> Attached a minimal project which demonstrates the issue.
> Thanks.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13378) extendedDataTable not shown inside Bootstrap tab panel
by Steve Oh (JIRA)
[ https://issues.jboss.org/browse/RF-13378?page=com.atlassian.jira.plugin.s... ]
Steve Oh edited comment on RF-13378 at 2/11/14 6:16 AM:
--------------------------------------------------------
REMOVED
was (Author: cc2000):
Hello,
I put together a list of JS statements, that seams to fix the layout. But I don't think, this is a stable workaround.
{code}
var edt = RichFaces.$("#{rich:clientId('theTable')}");
var bodyy = document.getElementById("#{rich:clientId('theTable')}:b");
$(bodyy).height(300);
$(edt).triggerHandler('rich:onajaxcomplete', {reinitializeHeader: true});
edt.updateLayout();
{code}
> extendedDataTable not shown inside Bootstrap tab panel
> ------------------------------------------------------
>
> Key: RF-13378
> URL: https://issues.jboss.org/browse/RF-13378
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4
> Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2
> Reporter: Salvo Isaja
> Labels: extendedDataTable
> Fix For: 5-Tracking
>
> Attachments: ExtendedDataTableTest.7z
>
>
> As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3.
> Attached a minimal project which demonstrates the issue.
> Thanks.
--
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
10 years, 4 months