From jira-events at lists.jboss.org Sun Dec 1 03:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 1 Dec 2013 03:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id set to tbody differs from component id and break rendering. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-10756: ------------------------------- Fix Version/s: 5-Tracking > collapsibleSubtable: id set to tbody differs from component id and break rendering. > ----------------------------------------------------------------------------------- > > Key: RF-10756 > URL: https://issues.jboss.org/browse/RF-10756 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Fix For: 5-Tracking > > > added to richfaces-showcase code: > {code} > > > > > > > expandMode="client"> > > > > {code} > and > {code} > public void incDaysLive(){ > for (InventoryVendorList vendor : inventoryVendorLists) { > for (InventoryVendorItem item : vendor.getVendorItems()) { > item.setDaysLive(item.getDaysLive()+1); > } > > } > } > {code} > do not see values updated before refreshing the browser. > According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated. -- 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 From jira-events at lists.jboss.org Sun Dec 1 03:10:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 1 Dec 2013 03:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id set to tbody differs from component id and break rendering. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927693#comment-12927693 ] Brian Leathem commented on RF-10756: ------------------------------------ We will address this when we look at decoupling the data table's client-side implementation from the JSF server-side in RichFaces 5.0 > collapsibleSubtable: id set to tbody differs from component id and break rendering. > ----------------------------------------------------------------------------------- > > Key: RF-10756 > URL: https://issues.jboss.org/browse/RF-10756 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Fix For: 5-Tracking > > > added to richfaces-showcase code: > {code} > > > > > > > expandMode="client"> > > > > {code} > and > {code} > public void incDaysLive(){ > for (InventoryVendorList vendor : inventoryVendorLists) { > for (InventoryVendorItem item : vendor.getVendorItems()) { > item.setDaysLive(item.getDaysLive()+1); > } > > } > } > {code} > do not see values updated before refreshing the browser. > According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated. -- 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 From jira-events at lists.jboss.org Sun Dec 1 03:12:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 1 Dec 2013 03:12:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) DataTable: row height strechted to 100% of the table height In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13356: ------------------------------- Fix Version/s: 5-Tracking > DataTable: row height strechted to 100% of the table height > ----------------------------------------------------------- > > Key: RF-13356 > URL: https://issues.jboss.org/browse/RF-13356 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Anton Bogoslavskyi > Assignee: Pavol Pitonak > Fix For: 5-Tracking > > Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png > > > The same as in the parent issue: > Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing). -- 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 From jira-events at lists.jboss.org Sun Dec 1 04:04:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 1 Dec 2013 04:04:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927696#comment-12927696 ] Brian Leathem commented on RF-13394: ------------------------------------ [~ppitonak] this works for me with a fresh build of RichFaces. Can you confirm whether this is indeed still an issue? > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Sun Dec 1 04:04:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Sun, 1 Dec 2013 04:04:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13394: ------------------------------- Assignee: Pavol Pitonak > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 02:36:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 2 Dec 2013 02:36:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple file selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RF-12224: ------------------------------ [~lfryc], could you, please, look into Metamer and see what is wrong? The sample was working before this feature was introduced. > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Luk?? Fry? > Labels: needs-qe > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 04:53:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 04:53:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript API doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13398. ------------------------------ Verified. > Autocomplete: JavaScript API doesn't work > ----------------------------------------- > > Key: RF-13398 > URL: https://issues.jboss.org/browse/RF-13398 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > # open browser console > # run in console RichFaces.component("form:autocomplete").disable() > result: > * the method fails with this error: > {code} > TypeError: Cannot call method 'attr' of undefined > {code} > * the method enable() doesn't work as well -- 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 From jira-events at lists.jboss.org Mon Dec 2 05:07:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 05:07:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x, input number slider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13395. ------------------------------ Verified > Showcase 4.5.x, input number slider > ----------------------------------- > > Key: RF-13395 > URL: https://issues.jboss.org/browse/RF-13395 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha1 > Environment: JBoss AS 7.1 > Firefox 25 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186]. > It is about a RF 4.5.x Showcase. > The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186. > {code} > > javax.faces.PROJECT_STAGE > Production > > {code} > Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code). > {code} > Uncaught TypeError: Object [object Object] has no method 'setPosition' inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145 > {code} > The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub. > Otherwise I found no problems/errors/warnings. -- 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 From jira-events at lists.jboss.org Mon Dec 2 07:08:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 07:08:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple file selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927815#comment-12927815 ] Luk?? Fry? commented on RF-12224: --------------------------------- Hey Jiri, the problem with Metamer was caused because Metamer sets @acceptedTypes attribute to empty string, which was interpreted that you require only files with no extension. I have handled this special case and interpret empty string as "no special requirements for accepted file type". > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Luk?? Fry? > Labels: needs-qe > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 07:48:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 07:48:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927827#comment-12927827 ] Pavol Pitonak commented on RF-13394: ------------------------------------ Still broken for me > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 07:56:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 07:56:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13394: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:02:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid of commons-lang dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927834#comment-12927834 ] Luk?? Fry? commented on RF-13335: --------------------------------- RF 4: {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 > Page fragments: get rid of commons-lang dependency > -------------------------------------------------- > > Key: RF-13335 > URL: https://issues.jboss.org/browse/RF-13335 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. > I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java]. -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:02:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid of commons-lang dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927834#comment-12927834 ] Luk?? Fry? edited comment on RF-13335 at 12/2/13 8:00 AM: ---------------------------------------------------------- RF 4: (BaseComponent) {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: (Widget Factory) {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 was (Author: lfryc): RF 4: {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 > Page fragments: get rid of commons-lang dependency > -------------------------------------------------- > > Key: RF-13335 > URL: https://issues.jboss.org/browse/RF-13335 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. > I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java]. -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:04:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple file selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-12224. ----------------------------- Resolution: Done > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Luk?? Fry? > Labels: needs-qe > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:04:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13394: ------------------------------- Assignee: Luk?? Fry? (was: Brian Leathem) > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:14:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:14:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927836#comment-12927836 ] Juraj H?ska commented on RF-13343: ---------------------------------- According to [this|https://issues.jboss.org/browse/RF-13335?focusedCommentId=12927834&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12927834] Lukas's comment, in most cases it will be the same for RF4 and RF5. Therefore, where possible I will use: {{RichFaces.component("j_idt108").options}} > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:20:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:20:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927839#comment-12927839 ] Luk?? Fry? commented on RF-13394: --------------------------------- Pavol, I have tried and it works for me as well. > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:20:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:20:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13394: ------------------------------- Assignee: Pavol Pitonak (was: Luk?? Fry?) > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:42:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:42:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12981) Expose the ResourceOptimizer for usage from command line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927852#comment-12927852 ] Luk?? Fry? commented on RF-12981: --------------------------------- I don't think this is Alpha-stage concern. We should do that in Beta releases once it is clear what is strategy for resource packaging in 5.0. > Expose the ResourceOptimizer for usage from command line > -------------------------------------------------------- > > Key: RF-12981 > URL: https://issues.jboss.org/browse/RF-12981 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is mainly issue for simplification of the usage of GenerateResourcesMain in order to allow users optimize resources from command line (or ant-based builds). > The usage of Resource Optimizer should be documented. -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:44:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:44:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13379. ----------------------------- Assignee: Luk?? Fry? Resolution: Duplicate Issue Duplicated by RF-13399 > Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization) > --------------------------------------------------------------------------------------------------------------- > > Key: RF-13379 > URL: https://issues.jboss.org/browse/RF-13379 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > https://travis-ci.org/richfaces/richfaces/builds/14381706 > {code} > [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<< > [INFO] > [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces --- > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute > SEVERE: null > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:188) > at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437) > at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39) > at sun.reflect.NativethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) > at java.net.URLClassLoader.access$100(URLClassLoader.java:71) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) > {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 From jira-events at lists.jboss.org Mon Dec 2 08:58:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927856#comment-12927856 ] Luk?? Fry? commented on RF-13394: --------------------------------- Ah, I missed a fact this is 4.5 issue, I can really reproduce Pavol's issue. > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 08:58:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 08:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13394: ------------------------------- Assignee: Luk?? Fry? (was: Pavol Pitonak) > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 09:34:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Dec 2013 09:34:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: Juraj H?ska created RF-13400: -------------------------------- Summary: PickList from Metamer is not responsive on real mobile device Key: RF-13400 URL: https://issues.jboss.org/browse/RF-13400 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska Priority: Critical PickList in the _Metamer_ demo is not responsive at all on real mobile device. When changing the size of the desktop browser screen it works correctly. Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Mon Dec 2 09:36:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 09:36:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: Pavol Pitonak created RF-13401: ---------------------------------- Summary: Mobile Showcase: picklist and ordering list don't work Key: RF-13401 URL: https://issues.jboss.org/browse/RF-13401 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects, showcase Affects Versions: 5.0.0.Alpha2 Environment: Showcase 5.0.0-SNAPSHOT iPad, Motorola Xoom, Android phones Reporter: Pavol Pitonak Attachments: picklist.png # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet # open pick list demo result: * pick list is rendered wrong (see attached screenshot from Samsung S III mini) * ordering list looks similar -- 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 From jira-events at lists.jboss.org Mon Dec 2 09:36:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 09:36:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13401: ------------------------------- Attachment: picklist.png > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Mon Dec 2 09:40:09 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 09:40:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927874#comment-12927874 ] Luk?? Fry? commented on RF-13394: --------------------------------- The issue here is that the ToggleControl on "universal toggle button" renders wrong scripts: initially: panel 1, item 1 click on "item 3" -> RichFaces.component('panel1').switchToItem('item1'); click on "item 2" -> RichFaces.component('panel1').switchToItem('item3'); click on "panel 2" -> RichFaces.component('panel1').switchToItem('item2'); ...and so on. Notice how all the changes are one request back. --- During debugging I have discrovered that a following difference between * 4.5 (where the component doesn't work): ** In 4.5, JSF calls {{ToggleControl#setTargetItem(item)}} with *the state of variable in previous request* ** e.g. since you have chosen item3, the setTargetItem(item1) is called instead and * 5.0 (where the component works). ** the method {{ToggleControl#setTargetItem(item)}} is not called at all. > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 10:00:07 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Dec 2013 10:00:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple file selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-12224. ------------------------------ Verified > fileUpload: Multiple file selection > ----------------------------------- > > Key: RF-12224 > URL: https://issues.jboss.org/browse/RF-12224 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.1.Final > Reporter: Anthony O. > Assignee: Luk?? Fry? > Labels: needs-qe > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 12:15:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 12:15:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12981) Expose the ResourceOptimizer for usage from command line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12981: ------------------------------- Fix Version/s: 5-Tracking (was: 5.0.0.Alpha3) > Expose the ResourceOptimizer for usage from command line > -------------------------------------------------------- > > Key: RF-12981 > URL: https://issues.jboss.org/browse/RF-12981 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Fix For: 5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is mainly issue for simplification of the usage of GenerateResourcesMain in order to allow users optimize resources from command line (or ant-based builds). > The usage of Resource Optimizer should be documented. -- 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 From jira-events at lists.jboss.org Mon Dec 2 12:15:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 12:15:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12981) Expose the ResourceOptimizer for usage from command line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927947#comment-12927947 ] Brian Leathem commented on RF-12981: ------------------------------------ +1 > Expose the ResourceOptimizer for usage from command line > -------------------------------------------------------- > > Key: RF-12981 > URL: https://issues.jboss.org/browse/RF-12981 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Fix For: 5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is mainly issue for simplification of the usage of GenerateResourcesMain in order to allow users optimize resources from command line (or ant-based builds). > The usage of Resource Optimizer should be documented. -- 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 From jira-events at lists.jboss.org Mon Dec 2 13:10:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 13:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13394. ----------------------------- Resolution: Done > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 13:10:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 13:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927964#comment-12927964 ] Luk?? Fry? commented on RF-13394: --------------------------------- Fixed. The problem was based in having two ClientBehavior classes - one in 5.0 and second one in 4.5 UI. The final responbility is put on core, so I have removed ClientBehavior from 4.5. > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 13:45:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 13:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13401. -------------------------------- Assignee: Brian Leathem Fix Version/s: 5.0.0.Alpha2 Resolution: Done Added a css reference to the bootstrap css file on the mobile template. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Mon Dec 2 14:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 14:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13402) JavaScript error thrown for the orderingList in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927980#comment-12927980 ] Brian Leathem commented on RF-13402: ------------------------------------ This is because the ordering list bridge is not invoked on the root element of the ordering list. I will change the ordering list bridge logic to execute on the root element of the ordering list, and then look for the child list element on which to execute the widget plugin. > JavaScript error thrown for the orderingList in the showcase > ------------------------------------------------------------ > > Key: RF-13402 > URL: https://issues.jboss.org/browse/RF-13402 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Viewing the orderingLIst in the showcase yields the JavaScript error: > {code} > Uncaught TypeError: Object [object Object] has no method 'detach' > {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 From jira-events at lists.jboss.org Mon Dec 2 14:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 14:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13402) JavaScript error thrown for the orderingList in the showcase In-Reply-To: References: Message-ID: Brian Leathem created RF-13402: ---------------------------------- Summary: JavaScript error thrown for the orderingList in the showcase Key: RF-13402 URL: https://issues.jboss.org/browse/RF-13402 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 5.0.0.Alpha2 Viewing the orderingLIst in the showcase yields the JavaScript error: {code} Uncaught TypeError: Object [object Object] has no method 'detach' {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 From jira-events at lists.jboss.org Mon Dec 2 14:31:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 14:31:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13400. -------------------------------- Resolution: Duplicate Issue > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Mon Dec 2 14:33:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 14:33:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13401: ------------------------------- Labels: needs-qe (was: ) > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Mon Dec 2 15:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 15:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13403) Create a styling guide for the RichFaces 5 components In-Reply-To: References: Message-ID: Brian Leathem created RF-13403: ---------------------------------- Summary: Create a styling guide for the RichFaces 5 components Key: RF-13403 URL: https://issues.jboss.org/browse/RF-13403 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: skinning Reporter: Brian Leathem Fix For: 5-Tracking The RichFaces 4 style guide is out-of-date with the new RichFaces 5 components. We need to replace the RichFaces 4 style guide with a bootstrap centric one for RichFaces 5. We should look to leverage any OSS community efforts done in the Bootstrap skinning space. -- 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 From jira-events at lists.jboss.org Mon Dec 2 15:28:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 15:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13402) JavaScript error thrown for the orderingList in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13402. -------------------------------- Resolution: Done > JavaScript error thrown for the orderingList in the showcase > ------------------------------------------------------------ > > Key: RF-13402 > URL: https://issues.jboss.org/browse/RF-13402 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Viewing the orderingLIst in the showcase yields the JavaScript error: > {code} > Uncaught TypeError: Object [object Object] has no method 'detach' > {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 From jira-events at lists.jboss.org Mon Dec 2 15:33:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 15:33:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928006#comment-12928006 ] Luk?? Fry? commented on RF-13343: --------------------------------- Reporting my comment: RF 4: (BaseComponent) {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: (Widget Factory) {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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 From jira-events at lists.jboss.org Mon Dec 2 15:33:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 2 Dec 2013 15:33:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928006#comment-12928006 ] Luk?? Fry? edited comment on RF-13343 at 12/2/13 3:31 PM: ---------------------------------------------------------- Re-posting my comment: RF 4: (BaseComponent) {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: (Widget Factory) {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 was (Author: lfryc): Reporting my comment: RF 4: (BaseComponent) {code} RichFaces.component(..).options {code} https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L92 RF 5: (Widget Factory) {code} RichFaces.component(..).options {code} https://github.com/jquery/jquery-ui/blob/47db52b9c98a5c593eb86e5b75309568d11b3bef/ui/jquery.ui.widget.js#L240 > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12439) Re-structure the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12439: ------------------------------- Epic Status: Done > Re-structure the build > ---------------------- > > Key: RF-12439 > URL: https://issues.jboss.org/browse/RF-12439 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Labels: rf5-build > Fix For: 5.0.0.Alpha1 > > > Restructure the build as per the requirements gathered at: > https://community.jboss.org/wiki/RichFaces43BuildRedesign > https://github.com/richfaces/richfaces -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12439) Re-structure the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-12439: -------------------------------- > Re-structure the build > ---------------------- > > Key: RF-12439 > URL: https://issues.jboss.org/browse/RF-12439 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Labels: rf5-build > Fix For: 5.0.0.Alpha1 > > > Restructure the build as per the requirements gathered at: > https://community.jboss.org/wiki/RichFaces43BuildRedesign > https://github.com/richfaces/richfaces -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:06:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:06:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12439) Re-structure the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem closed RF-12439. ------------------------------ Resolution: Done > Re-structure the build > ---------------------- > > Key: RF-12439 > URL: https://issues.jboss.org/browse/RF-12439 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Labels: rf5-build > Fix For: 5.0.0.Alpha1 > > > Restructure the build as per the requirements gathered at: > https://community.jboss.org/wiki/RichFaces43BuildRedesign > https://github.com/richfaces/richfaces -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:17:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:17:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13211) Rewrite Push 4.5 component so that it will re-use RichFaces 5 renderer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13211. -------------------------------- Fix Version/s: (was: 4.5-Tracking) Resolution: Rejected This issues isn't worth tracking, as we won't schedule it for the sake of doing it. Rather if an issue comes up, and consolidating the Push components/renderers is the best solution, we can proceed with doing so. > Rewrite Push 4.5 component so that it will re-use RichFaces 5 renderer > ---------------------------------------------------------------------- > > Key: RF-13211 > URL: https://issues.jboss.org/browse/RF-13211 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.5.0.Alpha1 > Reporter: Luk?? Fry? > > a4j:push and r:push will should reuse same logic since they share client-side Push service that implements topic registration, etc. > That's why they shouldn't be two non-conflicting (name-spaced) components, but just one which shares logic (even renderers). -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:17:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:17:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13079) Port RichFaces 4.x UI components to work with core present in RichFaces 5 framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13079. -------------------------------- Assignee: Michal Petrov Resolution: Done > Port RichFaces 4.x UI components to work with core present in RichFaces 5 framework > ----------------------------------------------------------------------------------- > > Key: RF-13079 > URL: https://issues.jboss.org/browse/RF-13079 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 5-Tracking > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 16:19:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 16:19:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13079) Port RichFaces 4.x UI components to work with core present in RichFaces 5 framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13079: ------------------------------- Epic Status: Done (was: To Do) > Port RichFaces 4.x UI components to work with core present in RichFaces 5 framework > ----------------------------------------------------------------------------------- > > Key: RF-13079 > URL: https://issues.jboss.org/browse/RF-13079 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 5-Tracking > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13307: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Support java.util.Set in iteration components > --------------------------------------------- > > Key: RF-13307 > URL: https://issues.jboss.org/browse/RF-13307 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Environment: Wildfly-8.0.0.Beta1 > Reporter: Matti Bickel > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > JSF-2.2 now supports iteration over sets as in > {code:xml} > > #{elem.name} > > {code} > Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values. > Would be nice if RF catches up with JSF here. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13093: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > extendedDataTable column resizing and reordering not working on transient (stateless) views > ------------------------------------------------------------------------------------------- > > Key: RF-13093 > URL: https://issues.jboss.org/browse/RF-13093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23 > Reporter: Salvo Isaja > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only: > {code:xml} > > > {code} > This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead. > Other features seem to work pretty well in stateless mode, by the way. > 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13199: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.skin/ITBlueSkySkin/org_richfaces_skin_ITBlueSkySkin/] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.ui.extendedDataTable/ITDisablingBuiltinSortingAndFiltering/org_richfaces_ui_extendedDataTable_ITDisablingBuiltinSortingAndFiltering/] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render after ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13390: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Region fails to render after ajax request > ----------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > When > {code} > > > > > > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13197: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13168: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:26:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:26:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13041) Metamer: demos throw NullPointerException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13041: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Metamer: demos throw NullPointerException > ----------------------------------------- > > Key: RF-13041 > URL: https://issues.jboss.org/browse/RF-13041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > WildFly: Weld Integration 8.0.0.Alpha1 > JBoss AS 8.0.0.Alpha1 > Java(TM) SE Runtime Environment 1.7.0_17-b02 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64 > Reporter: Jan Papousek > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13248: ------------------------------- Labels: jsf22 (was: ) > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13062: ------------------------------- Labels: jsf22 (was: jsf2) > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13040: ------------------------------- Labels: jsf22 (was: ) > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13080) Support for JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13080: ------------------------------- Labels: jsf22 (was: ) > Support for JSF 2.2 > ------------------- > > Key: RF-13080 > URL: https://issues.jboss.org/browse/RF-13080 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Labels: jsf22 > Fix For: 5-Tracking > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13248: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13062: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:28:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:28:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13040: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13062: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13248: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13040: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13041) Metamer: demos throw NullPointerException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13041: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Metamer: demos throw NullPointerException > ----------------------------------------- > > Key: RF-13041 > URL: https://issues.jboss.org/browse/RF-13041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > WildFly: Weld Integration 8.0.0.Alpha1 > JBoss AS 8.0.0.Alpha1 > Java(TM) SE Runtime Environment 1.7.0_17-b02 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64 > Reporter: Jan Papousek > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13199: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.skin/ITBlueSkySkin/org_richfaces_skin_ITBlueSkySkin/] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.ui.extendedDataTable/ITDisablingBuiltinSortingAndFiltering/org_richfaces_ui_extendedDataTable_ITDisablingBuiltinSortingAndFiltering/] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13197: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13307: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Support java.util.Set in iteration components > --------------------------------------------- > > Key: RF-13307 > URL: https://issues.jboss.org/browse/RF-13307 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Environment: Wildfly-8.0.0.Beta1 > Reporter: Matti Bickel > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > JSF-2.2 now supports iteration over sets as in > {code:xml} > > #{elem.name} > > {code} > Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values. > Would be nice if RF catches up with JSF here. -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:30:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:30:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render after ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13390: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Region fails to render after ajax request > ----------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > > > > > > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:56:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:56:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3 In-Reply-To: References: Message-ID: Brian Leathem created RF-13404: ---------------------------------- Summary: Port the RichFaces 5 improvements back to RichFaces 4.3 Key: RF-13404 URL: https://issues.jboss.org/browse/RF-13404 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples Reporter: Brian Leathem Fix For: 4.3.5 -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:56:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:56:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: Brian Leathem created RF-13405: ---------------------------------- Summary: Merge the photoalbum fixes from QE Key: RF-13405 URL: https://issues.jboss.org/browse/RF-13405 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples Reporter: Brian Leathem Fix For: 4.3.5 -- 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 From jira-events at lists.jboss.org Mon Dec 2 17:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 17:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12949) Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12949: ------------------------------- Fix Version/s: 4.3.5 (was: 5.0.0.Alpha3) > Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works > ---------------------------------------------------------------------------------------------------- > > Key: RF-12949 > URL: https://issues.jboss.org/browse/RF-12949 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Ji?? ?tefek > Fix For: 4.3.5 > > > The Photoalbum example should have a test which will make sure it starts correctly and basic functionality works as expected. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:00:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:00:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12949) Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12949: ------------------------------- Affects Version/s: (was: 5.0.0.Alpha1) > Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works > ---------------------------------------------------------------------------------------------------- > > Key: RF-12949 > URL: https://issues.jboss.org/browse/RF-12949 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Ji?? ?tefek > Fix For: 4.3.5 > > > The Photoalbum example should have a test which will make sure it starts correctly and basic functionality works as expected. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:02:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13227) Prepare the RichFaces 4.3.x photoalbum for release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13227: ------------------------------- Description: Review the photoalbum example application addressing any usability issues. (was: * Backport the Social Media improvements from the RichFaces 5.x photoalbum * Run through the application looking for usability issues * Handoff the example for QE review) > Prepare the RichFaces 4.3.x photoalbum for release > -------------------------------------------------- > > Key: RF-13227 > URL: https://issues.jboss.org/browse/RF-13227 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Fix For: 4.3.5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Review the photoalbum example application addressing any usability issues. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:02:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12901) Showcase improvements for RF5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928039#comment-12928039 ] Brian Leathem commented on RF-12901: ------------------------------------ Many of these issues will be addressed with the planned showcase rewrite. > Showcase improvements for RF5 > ----------------------------- > > Key: RF-12901 > URL: https://issues.jboss.org/browse/RF-12901 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Fix For: 5-Tracking > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13405. -------------------------------- Fix Version/s: (was: 4.3.5) Resolution: Duplicate Issue Duplicates RF-13257 > Merge the photoalbum fixes from QE > ---------------------------------- > > Key: RF-13405 > URL: https://issues.jboss.org/browse/RF-13405 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:06:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:06:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13405: -------------------------------- > Merge the photoalbum fixes from QE > ---------------------------------- > > Key: RF-13405 > URL: https://issues.jboss.org/browse/RF-13405 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:06:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:06:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13405: ------------------------------- Comment: was deleted (was: Duplicates RF-13257) > Merge the photoalbum fixes from QE > ---------------------------------- > > Key: RF-13405 > URL: https://issues.jboss.org/browse/RF-13405 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:22:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13404: ---------------------------------- Assignee: Michal Petrov > Port the RichFaces 5 improvements back to RichFaces 4.3 > ------------------------------------------------------- > > Key: RF-13404 > URL: https://issues.jboss.org/browse/RF-13404 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:22:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13405: ---------------------------------- Assignee: Michal Petrov > Merge the photoalbum fixes from QE > ---------------------------------- > > Key: RF-13405 > URL: https://issues.jboss.org/browse/RF-13405 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:22:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13257) PhotoAlbum bugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13257: ---------------------------------- Assignee: Michal Petrov > PhotoAlbum bugs > --------------- > > Key: RF-13257 > URL: https://issues.jboss.org/browse/RF-13257 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Fix For: 4.3.5 > > > PhotoAlbum 4.3.x known bugs: > * uploading file to album (image isn't saved to DB) > * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog) -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:24:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13047) Implement improvements to the photoalbum application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13047: ------------------------------- Fix Version/s: 4.3.5 (was: 5-Tracking) > Implement improvements to the photoalbum application > ---------------------------------------------------- > > Key: RF-13047 > URL: https://issues.jboss.org/browse/RF-13047 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: examples > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:30:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:30:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13406) Create a new showcase for RichFaces 5 In-Reply-To: References: Message-ID: Brian Leathem created RF-13406: ---------------------------------- Summary: Create a new showcase for RichFaces 5 Key: RF-13406 URL: https://issues.jboss.org/browse/RF-13406 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Fix For: 5.0.0.Alpha3 The new showcase should: # Include the examples from the existing RichFaces4 showcase #* Simplications should be made as appropriate to reduce complexity (eg. no JMS, no JPA - these can be addressed in standalone examples) # Be based on the RichFaces Sandbox Bootstrap demo #* The layout will have to be changed to use generic bootstrap CSS as required # Drop (as much as possible) the container specific configuration found in the RichFaces4 showcase #* consider any sample simplifications required to achieve this goal -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:32:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12243) Showcase: remove parent from pom In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12243: ------------------------------- Assignee: (was: Luk?? Fry?) > Showcase: remove parent from pom > -------------------------------- > > Key: RF-12243 > URL: https://issues.jboss.org/browse/RF-12243 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution, showcase > Affects Versions: 4.2.1.Final > Reporter: Pavol Pitonak > Fix For: 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Showcase POM (https://github.com/richfaces/showcase/blob/develop/pom.xml) contains parent section. > {code} > > org.richfaces > richfaces-root-parent > 4.3.0-SNAPSHOT > ../build/parent/pom.xml > > {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 From jira-events at lists.jboss.org Mon Dec 2 18:32:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13039) Showcase RF5 - notify demos - set escape attribute to false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928044#comment-12928044 ] Brian Leathem commented on RF-13039: ------------------------------------ [~lfryc] can you please comment on why you re-opened this issue? > Showcase RF5 - notify demos - set escape attribute to false > ----------------------------------------------------------- > > Key: RF-13039 > URL: https://issues.jboss.org/browse/RF-13039 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Fix For: 5-Tracking > > > The {{escape}} attribute for {{r:notify}} was ported to RF 5. - RF-13013 > Demos in Showcase need to be updated as well. The {{r:notify}} 's {{escape}} attribute needs to be set to {{false}} in order to show {{HTML}} code correctly. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:48:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:48:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13168: ------------------------------- Comment: was deleted (was: This issue was previously scheduled to be worked on in more than one sprint: * 'RichFaces 4.3.5 Sprint 1' (on board 'RichFaces 4.3') * '5.0.0.Alpha2 - Sprint 2' (on board 'RichFaces 5') Starting from JIRA Agile 6.3, an issue can only belong to a single future sprint. Read more about this change: http://docs.atlassian.com/agile/docs-0630/Sprint+Marker+Migration This issue is now scheduled for future sprint '5.0.0.Alpha2 - Sprint 2' (on board 'RichFaces 5'). If this is incorrect, please update the issue accordingly. This comment was automatically generated by JIRA. If it is no longer relevant, please feel free to delete it.) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:50:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:50:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13168: ---------------------------------- Assignee: (was: Brian Leathem) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:52:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13093: ------------------------------- Fix Version/s: (was: 4.3.5) > extendedDataTable column resizing and reordering not working on transient (stateless) views > ------------------------------------------------------------------------------------------- > > Key: RF-13093 > URL: https://issues.jboss.org/browse/RF-13093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23 > Reporter: Salvo Isaja > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only: > {code:xml} > > > {code} > This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead. > Other features seem to work pretty well in stateless mode, by the way. > 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 From jira-events at lists.jboss.org Mon Dec 2 18:52:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13168: ------------------------------- Fix Version/s: (was: 4.3.5) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:52:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render after ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13390: ------------------------------- Fix Version/s: (was: 4.3.5) > Region fails to render after ajax request > ----------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > > > > > > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:54:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12813) rich:panelMenuItem executes action even if disabled attribute evaluates to true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12813: ------------------------------- Sprint: (was: RichFaces 4.3.5 Sprint 1) > rich:panelMenuItem executes action even if disabled attribute evaluates to true > ------------------------------------------------------------------------------- > > Key: RF-12813 > URL: https://issues.jboss.org/browse/RF-12813 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Reporter: Andrey Zhemoytuk > Assignee: Pavel Slegr > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > org.richfaces.renderkit.html.PanelMenuItemRenderer#doDecode does not check 'disabled' attribute (how usually do other components before executing action) which may cause security issues. > Initially reported on: > http://stackoverflow.com/questions/15130807/richfaces-panelmenuitem-reevaluating-disabled-not-working -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:54:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:54:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13247: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Priority: Minor > Fix For: 4.3.5 > > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:54:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:54:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and down arrow keys not working in Opera In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13292: ------------------------------- Summary: Autocomplete: up and down arrow keys not working in Opera (was: Autocomplete: up and down arrow keys not working in Opera!) > Autocomplete: up and down arrow keys not working in Opera > --------------------------------------------------------- > > Key: RF-13292 > URL: https://issues.jboss.org/browse/RF-13292 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha2 > Reporter: alexey plotnikov > Fix For: 4.3.5 > > > Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera. -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:56:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:56:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Fix For: 4.3.5 > > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:56:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:56:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13369: ------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 4.3.5) > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > autocomplete: the pop-up list always appears empty -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:56:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:56:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13173) Address issues preventing 4.3.x framework/component use with JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13173. -------------------------------- Fix Version/s: (was: 4.3.5) Resolution: Duplicate Issue This is a duplicate of RF-13080 > Address issues preventing 4.3.x framework/component use with JSF 2.2 > -------------------------------------------------------------------- > > Key: RF-13173 > URL: https://issues.jboss.org/browse/RF-13173 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13173) Address issues preventing 4.3.x framework/component use with JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13173: ------------------------------- Epic Status: Done (was: To Do) > Address issues preventing 4.3.x framework/component use with JSF 2.2 > -------------------------------------------------------------------- > > Key: RF-13173 > URL: https://issues.jboss.org/browse/RF-13173 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:58:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:58:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13405) Merge the photoalbum fixes from QE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13405: ------------------------------- Fix Version/s: 4.3.5 > Merge the photoalbum fixes from QE > ---------------------------------- > > Key: RF-13405 > URL: https://issues.jboss.org/browse/RF-13405 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Mon Dec 2 18:58:08 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 18:58:08 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13369: ------------------------------- Fix Version/s: 4.5.0.Alpha2 (was: 5.0.0.Alpha3) > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Labels: jsf22 > Fix For: 4.5.0.Alpha2 > > > autocomplete: the pop-up list always appears empty -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13317: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and Warp in 4.3 branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13310: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Upgrade Graphene and Warp in 4.3 branch > --------------------------------------- > > Key: RF-13310 > URL: https://issues.jboss.org/browse/RF-13310 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.5 > Reporter: Luk?? Fry? > Fix For: 4.3.5 > > > The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue. > Why we want to upgrade: > * Graphene = Final version API changes changes > * Warp = ease of debugging > I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik. -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13397: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > a4j:push not working with Internet Explorer >= 10 > ------------------------------------------------- > > Key: RF-13397 > URL: https://issues.jboss.org/browse/RF-13397 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.4 > Environment: Any where Internet Explorer 10 or above is available > Reporter: Tobias Seppenhauser > Labels: richfaces > Fix For: 4.3.5 > > > The mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. > Unfortunately I can't see any error in the Javascript console. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13358) rich:panelMenuGroup allowing actions executions even if originally disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13358: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > rich:panelMenuGroup allowing actions executions even if originally disabled > --------------------------------------------------------------------------- > > Key: RF-13358 > URL: https://issues.jboss.org/browse/RF-13358 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.4 > Environment: Linux, AS 7.1.1 Brontes, FF 25 with FireBug addOn > Reporter: Pavel Slegr > Assignee: Pavel Slegr > Priority: Critical > Fix For: 4.3.5 > > > related to https://issues.jboss.org/browse/RF-12813 > This can be possibly a security hole, as the second component piece is discovered to allow tampering actions through JS. > I suggest to try out on other components as well !!! > with following example > {code} > { > > > > > > > > } > {code} > the group43 element is intended to be disabled and thus not allowing any actions execution on it > Once tampered with > {code} > { > new RichFaces.ui.PanelMenuGroup("f:group43",{"collapseEvent":"click","unselectable":false,"selectable":false,"name":"group43","ajax":{"incId":"1"} ,"stylePrefix":"rf\u002Dpm\u002Dgr","expanded":false,"expandEvent":"click","disabled":false,"mode":"client"} ) > } > {code} > It is possible to expand the group and execute further actions on its children elements -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:02:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize value from DOM (was: ignored API call .setValue('')) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928048#comment-12928048 ] Brian Leathem commented on RF-13306: ------------------------------------ [~alixey] any luck with that pull request? We are ramping up our development efforts for a 4.3.5 release. It would be great to see this fix included if you can take the time to create the PR. > Autocomplete: initialize value from DOM (was: ignored API call .setValue('')) > ----------------------------------------------------------------------------- > > Key: RF-13306 > URL: https://issues.jboss.org/browse/RF-13306 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Fix For: 4.3.5 > > > All described here https://community.jboss.org/thread/233973 > I have this autocomplete component: > {code} > > > > > >
> minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion" > autofill="false" > onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.providerName}" > > > > > > > > > > > > alt=""/> > onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);" > alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/> > >
> {code} > as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window. > I use JavaScript function "autocompleteChangeProvider" for extract selected id. > I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API. > > And a problem: > if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!! > > I think i found a solution > AutocompleteBase.js has this code: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = ""; > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens. > i replace this code by this: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = $(rf.getDomElement(fieldId)).val(); > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > 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 From jira-events at lists.jboss.org Mon Dec 2 19:02:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13298) Richfaces BOM manages a non Maven Central dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13298: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Richfaces BOM manages a non Maven Central dependency > ---------------------------------------------------- > > Key: RF-13298 > URL: https://issues.jboss.org/browse/RF-13298 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.2, 4.3.3, 4.3.4 > Reporter: Rafael Benevides > Fix For: 4.3.5 > > > Richfaces BOMs http://repo1.maven.org/maven2/org/richfaces/richfaces-bom/4.3.4.Final/richfaces-bom-4.3.4.Final.pom manages the following GAV: > org.richfaces.ui.common:richfaces-ui-common-api:${version.richfaces} which is not present on Maven Central ( http://search.maven.org/#search%7Cga%7C1%7Crichfaces-ui-common-api ) > BOM should have this scope changed or declare a https://repository.jboss.org/nexus repository -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:02:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:02:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13266: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:02:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:02:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13252) a4j:ajax includes jsf.js script twice In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13252: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > a4j:ajax includes jsf.js script twice > ------------------------------------- > > Key: RF-13252 > URL: https://issues.jboss.org/browse/RF-13252 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Reporter: Jon?? Trantina > Fix For: 4.3.5 > > Attachments: reproducer.zip > > > When a4j:script is used in the page like so: > {noformat} > > > > {noformat} > Then two script tags pointing to jsf.js are added to the page, once in the head by the inclusion of @ResourceDependency [1], and once again by Overriding the ClientBehaviorRenderer#getScript method [2,3]. > Note, that according to Brian, resolving this without introducing any functional regressions may require the resolution of RF-12270 [4]. > [1] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L53 > [2] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L123 > [3] https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/java/javax/faces/render/ClientBehaviorRenderer.java#L95 > [4] https://issues.jboss.org/browse/RF-12270 -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928050#comment-12928050 ] Brian Leathem commented on RF-13230: ------------------------------------ [~ppitonak] any update on the regression status of this issue? Knowing this is an important part of the 4.3.5 release planning effort. > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:04:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:04:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13220) Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13220: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts > --------------------------------------------------------------------- > > Key: RF-13220 > URL: https://issues.jboss.org/browse/RF-13220 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Assignee: Vineet Reynolds > Fix For: 4.3.5 > > > The readme files provide instruction on how to run quickstarts on both AS 7.1 and EAP 6. Quickstarts now target EAP 6.1, so we need to remove references to AS 7.1. -- 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 From jira-events at lists.jboss.org Mon Dec 2 19:04:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 2 Dec 2013 19:04:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12813) rich:panelMenuItem executes action even if disabled attribute evaluates to true In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12813: ------------------------------- Sprint: RichFaces 4.3.5 Sprint 1 > rich:panelMenuItem executes action even if disabled attribute evaluates to true > ------------------------------------------------------------------------------- > > Key: RF-12813 > URL: https://issues.jboss.org/browse/RF-12813 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Reporter: Andrey Zhemoytuk > Assignee: Pavel Slegr > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > org.richfaces.renderkit.html.PanelMenuItemRenderer#doDecode does not check 'disabled' attribute (how usually do other components before executing action) which may cause security issues. > Initially reported on: > http://stackoverflow.com/questions/15130807/richfaces-panelmenuitem-reevaluating-disabled-not-working -- 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 From jira-events at lists.jboss.org Tue Dec 3 02:45:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 02:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13039) Showcase RF5 - notify demos - set escape attribute to false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928079#comment-12928079 ] Luk?? Fry? commented on RF-13039: --------------------------------- I can't remember, but the issue seems to be covered: http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=notify&sample=stackingMessages&skin=blueSky > Showcase RF5 - notify demos - set escape attribute to false > ----------------------------------------------------------- > > Key: RF-13039 > URL: https://issues.jboss.org/browse/RF-13039 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Fix For: 5-Tracking > > > The {{escape}} attribute for {{r:notify}} was ported to RF 5. - RF-13013 > Demos in Showcase need to be updated as well. The {{r:notify}} 's {{escape}} attribute needs to be set to {{false}} in order to show {{HTML}} code correctly. -- 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 From jira-events at lists.jboss.org Tue Dec 3 02:45:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 02:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13039) Showcase RF5 - notify demos - set escape attribute to false In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13039. ----------------------------- Assignee: Luk?? Fry? (was: Juraj H?ska) Fix Version/s: (was: 5-Tracking) Resolution: Out of Date > Showcase RF5 - notify demos - set escape attribute to false > ----------------------------------------------------------- > > Key: RF-13039 > URL: https://issues.jboss.org/browse/RF-13039 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Priority: Trivial > > The {{escape}} attribute for {{r:notify}} was ported to RF 5. - RF-13013 > Demos in Showcase need to be updated as well. The {{r:notify}} 's {{escape}} attribute needs to be set to {{false}} in order to show {{HTML}} code correctly. -- 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 From jira-events at lists.jboss.org Tue Dec 3 03:51:07 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Dec 2013 03:51:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control: attributes targetItem and targetPanel don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13394. ------------------------------ Verified > Toggle control: attributes targetItem and targetPanel don't work > ---------------------------------------------------------------- > > Key: RF-13394 > URL: https://issues.jboss.org/browse/RF-13394 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.5.0.Alpha1 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > EAP 6.1.1 > Mojarra 2.1.19 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Labels: regression > Fix For: 4.5.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml > # set targetPanel=panel2 > # set targetItem=item3 > # click on "universal toggle control" button > result: > * nothing happens > * third item on second panel should be active > * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3 -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:09:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Dec 2013 04:09:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reopened RF-13401: -------------------------------- Components are rendered correctly now, pick list works fine. However, only the first ordering list work on iPad and Motorola Xoom. In the second one, I'm not able to select any item. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:11:07 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Dec 2013 04:11:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928095#comment-12928095 ] Pavol Pitonak commented on RF-13400: ------------------------------------ [~bleathem], could you please write more information why is this issue a duplicate of RF-13401? > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:24:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 04:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928104#comment-12928104 ] Brian Leathem commented on RF-13401: ------------------------------------ [~ppitonak] it works fine for me with the latest Chrome browser on my Samsung Galaxy S II. Can you do some investigations to determine if this is only broken on some specific browsers? No hurry, we can address this in 5.0.0.Alpha3. We should file a new issue to track it though. This issue was resolved with the introduction of the Bootstrap CSS file. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:24:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 04:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13401. -------------------------------- Resolution: Done > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:24:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 04:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928105#comment-12928105 ] Brian Leathem commented on RF-13401: ------------------------------------ [~ppitonak] one thing: be sure to refresh the page to get the latests CDD files. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:24:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 04:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928105#comment-12928105 ] Brian Leathem edited comment on RF-13401 at 12/3/13 4:23 AM: ------------------------------------------------------------- [~ppitonak] one thing: be sure to refresh the page to get the latest CSS files. was (Author: bleathem): [~ppitonak] one thing: be sure to refresh the page to get the latests CDD files. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:44:05 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Dec 2013 04:44:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928115#comment-12928115 ] Pavol Pitonak commented on RF-13401: ------------------------------------ You are right...after refreshing the page several times it works on iPad and Motorola Xoom. > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 04:44:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Dec 2013 04:44:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13401) Mobile Showcase: picklist and ordering list don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13401. ------------------------------ > Mobile Showcase: picklist and ordering list don't work > ------------------------------------------------------ > > Key: RF-13401 > URL: https://issues.jboss.org/browse/RF-13401 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects, showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Showcase 5.0.0-SNAPSHOT > iPad, Motorola Xoom, Android phones > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Attachments: picklist.png > > > # open http://showcaselatest-richfaces.rhcloud.com on a mobile phone or tablet > # open pick list demo > result: > * pick list is rendered wrong (see attached screenshot from Samsung S III mini) > * ordering list looks similar -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:24:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:24:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13343: ---------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928160#comment-12928160 ] Luk?? Fry? commented on RF-13343: --------------------------------- Moved to Alpha3 as we hadn't chance to finish it before tagging. We agreed to shift with with Pavol and Juraj. > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13407: ------------------------------- Summary: Clean-up RichFaces Grunt build Key: RF-13407 URL: https://issues.jboss.org/browse/RF-13407 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Luk?? Fry? The build contains unnecessary dependencies. The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13407: ---------------------------- Fix Version/s: 5.0.0.Alpha3 > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13407: ---------------------------- Issue Type: Bug (was: Feature Request) > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13407: ---------------------------- Fix Version/s: (was: 5.0.0.Alpha3) > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 07:32:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 3 Dec 2013 07:32:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13407: ---------------------------- Component/s: build/distribution > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 11:11:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 11:11:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12681) Curious settings for rf-cal-hov in calendar.ecss In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12681: ------------------------------- Fix Version/s: 4.5-Tracking (was: 4.2.3.CR1) > Curious settings for rf-cal-hov in calendar.ecss > ------------------------------------------------ > > Key: RF-12681 > URL: https://issues.jboss.org/browse/RF-12681 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final > Reporter: Lutz Ulrich > Priority: Trivial > Fix For: 4.5-Tracking > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > CSS specification is redundant / inconsistent: > {code} > .rf-cal-hov { > background-color: '#{richSkin.calendarSpecBackgroundColor}'; > background-color: '#{richSkin.calendarSpecTextColor}'; > } > {code} > Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . -- 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 From jira-events at lists.jboss.org Tue Dec 3 11:37:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 11:37:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13138) a4j:log - should print partial-response value in a level=debug, but prints [Object] instead In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928259#comment-12928259 ] Brian Leathem commented on RF-13138: ------------------------------------ Running the metamer sample: http://localhost:8080/metamer/faces/components/a4jLog/simple.xhtml I get the result below, where the partial-response is clearly visible: {code} debug[08:23:15.706]: New request added to queue. Queue requestGroupingId changed to form:submitButton debug[08:23:15.709]: Queue will wait 0ms before submit debug[08:23:15.710]: richfaces.queue: will submit request NOW info [08:23:15.718]: Received 'begin' event from info [08:23:15.811]: Received 'beforedomupdate' event from debug[08:23:15.812]: Server returned responseText: ]]>16:23:15.782
  • RESTORE_VIEW 1
  • APPLY_REQUEST_VALUES 2
  • PROCESS_VALIDATIONS 3
  • UPDATE_MODEL_VALUES 4
  • INVOKE_APPLICATION 5
  • RENDER_RESPONSE 6
]]>Hello John!]]>
help for attribute level help for attribute mode
help for attribute rendered
help for attribute style
help for attribute styleClass
]]>form:out info [08:23:15.832]: Listing content of response changes element: Element update for id=a4jStatusPanel ]]> Element update for id=phasesPanel 16:23:15.782
  • RESTORE_VIEW 1
  • APPLY_REQUEST_VALUES 2
  • PROCESS_VALIDATIONS 3
  • UPDATE_MODEL_VALUES 4
  • INVOKE_APPLICATION 5
  • RENDER_RESPONSE 6
]]> Element update for id=form:out Hello John!]]> Element update for id=afterForm:attributes:panel
help for attribute level help for attribute mode
help for attribute rendered
help for attribute style
help for attribute styleClass
]]> Element update for id=javax.faces.ViewState Element extension for id=org.richfaces.extension form:out debug[08:23:15.863]: richfaces.queue: ajax submit successfull debug[08:23:15.864]: richfaces.queue: Nothing to submit debug[08:23:15.866]: RESTORE_VIEW 1 debug[08:23:15.866]: APPLY_REQUEST_VALUES 2 debug[08:23:15.866]: PROCESS_VALIDATIONS 3 debug[08:23:15.866]: UPDATE_MODEL_VALUES 4 debug[08:23:15.867]: INVOKE_APPLICATION 5 debug[08:23:15.867]: RENDER_RESPONSE 6 info [08:23:15.867]: Received 'success' event from info [08:23:15.868]: Received 'complete' event from {code} However, when the _mode_ is changed to _console_, _\[object Object]_ is printed instead. > a4j:log - should print partial-response value in a level=debug, but prints [Object] instead > ------------------------------------------------------------------------------------------- > > Key: RF-13138 > URL: https://issues.jboss.org/browse/RF-13138 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha1 > > > {code} > RichFaces: New request added to queue. Queue requestGroupingId changed to form:j_idt9 log.js.jsf?ln=org.richfaces:160 > RichFaces: Queue will wait 0ms before submit log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: will submit request NOW log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'begin' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'beforedomupdate' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: [object Object] log.js.jsf?ln=org.richfaces:160 > RichFaces: [object Object] log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: ajax submit error: During update: form:surnameMsg not found log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: Nothing to submit log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'error at malformedXML' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: [status=200] During update: form:surnameMsg not found log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'complete' event from > {code} > The issue is caused by the fact that richfaces.log suppose to accept text messages but this [formatPartialResponse|https://github.com/richfaces/richfaces/blob/5.0.0.Alpha1/framework/src/main/resources/META-INF/resources/richfaces-jsf-log.js#L98] generated jQuery object, which is in turn printed as {{[Object]}}. -- 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 From jira-events at lists.jboss.org Tue Dec 3 11:37:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 11:37:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13138) a4j:log - should print partial-response value in a level=debug, but prints [Object] instead In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13138: ------------------------------- Fix Version/s: 5-Tracking (was: 5.0.0.Alpha1) > a4j:log - should print partial-response value in a level=debug, but prints [Object] instead > ------------------------------------------------------------------------------------------- > > Key: RF-13138 > URL: https://issues.jboss.org/browse/RF-13138 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3 > Reporter: Luk?? Fry? > Fix For: 5-Tracking > > > {code} > RichFaces: New request added to queue. Queue requestGroupingId changed to form:j_idt9 log.js.jsf?ln=org.richfaces:160 > RichFaces: Queue will wait 0ms before submit log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: will submit request NOW log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'begin' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'beforedomupdate' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: [object Object] log.js.jsf?ln=org.richfaces:160 > RichFaces: [object Object] log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: ajax submit error: During update: form:surnameMsg not found log.js.jsf?ln=org.richfaces:160 > RichFaces: richfaces.queue: Nothing to submit log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'error at malformedXML' event from log.js.jsf?ln=org.richfaces:160 > RichFaces: [status=200] During update: form:surnameMsg not found log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'complete' event from > {code} > The issue is caused by the fact that richfaces.log suppose to accept text messages but this [formatPartialResponse|https://github.com/richfaces/richfaces/blob/5.0.0.Alpha1/framework/src/main/resources/META-INF/resources/richfaces-jsf-log.js#L98] generated jQuery object, which is in turn printed as {{[Object]}}. -- 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 From jira-events at lists.jboss.org Tue Dec 3 11:39:06 2013 From: jira-events at lists.jboss.org (alexey plotnikov (JIRA)) Date: Tue, 3 Dec 2013 11:39:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize value from DOM (was: ignored API call .setValue('')) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928261#comment-12928261 ] alexey plotnikov commented on RF-13306: --------------------------------------- [~bleathem] i created pull request :) > Autocomplete: initialize value from DOM (was: ignored API call .setValue('')) > ----------------------------------------------------------------------------- > > Key: RF-13306 > URL: https://issues.jboss.org/browse/RF-13306 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Fix For: 4.3.5 > > > All described here https://community.jboss.org/thread/233973 > I have this autocomplete component: > {code} > > > > > >
> minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion" > autofill="false" > onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.providerName}" > > > > > > > > > > > > alt=""/> > onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);" > alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/> > >
> {code} > as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window. > I use JavaScript function "autocompleteChangeProvider" for extract selected id. > I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API. > > And a problem: > if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!! > > I think i found a solution > AutocompleteBase.js has this code: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = ""; > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens. > i replace this code by this: > {code} > rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) { > // call constructor of parent class > $super.constructor.call(this, componentId); > this.selectId = selectId; > this.fieldId = fieldId; > this.options = $.extend({}, defaultOptions, options); > this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId); > this.currentValue = $(rf.getDomElement(fieldId)).val(); > this.tempValue = this.getValue(); > this.isChanged = this.tempValue.length != 0; > bindEventHandlers.call(this); > }; > {code} > 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 From jira-events at lists.jboss.org Tue Dec 3 14:50:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 14:50:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13047) Implement improvements to the photoalbum application In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928332#comment-12928332 ] Brian Leathem commented on RF-13047: ------------------------------------ This issue is being tracked in the WFK product via the issue: WFK2-124. > Implement improvements to the photoalbum application > ---------------------------------------------------- > > Key: RF-13047 > URL: https://issues.jboss.org/browse/RF-13047 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: examples > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Tue Dec 3 15:08:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 15:08:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13407: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 15:08:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 15:08:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13407) Clean-up RichFaces Grunt build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13407: ------------------------------- Priority: Minor (was: Major) > Clean-up RichFaces Grunt build > ------------------------------ > > Key: RF-13407 > URL: https://issues.jboss.org/browse/RF-13407 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha3 > > > The build contains unnecessary dependencies. > The package.json depends on approximate versions ("~"). -- 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 From jira-events at lists.jboss.org Tue Dec 3 15:10:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 15:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928345#comment-12928345 ] Brian Leathem commented on RF-13400: ------------------------------------ Sorry [~ppitonak]. On re-reading the issue I see this addresses metamer, and not the showcase. It is possibly not a duplicate issue. However it is also likely not a RichFaces picklist issue, but rather a metamer issue. Do you have other elements in your metamer page preventing the viewport from shrinking with the window size? > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Tue Dec 3 17:41:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 17:41:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-7353) TabPanel: value evaluated at phase1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12479545#comment-12479545 ] Brian Leathem edited comment on RF-7353 at 12/3/13 5:39 PM: ------------------------------------------------------------ Reproduced at jsp+tomcat6 Java bean request scope: {code} public class Custom { private String selectedTab; private String firstName; private String lastName; public Custom() { this.selectedTab = "firstname"; this.firstName = "tisha"; this.lastName = "kuprevich"; } ... } {code} JSP: {code} {code} was (Author: tkuprevich): Reproduced at jsp+tomcat6 Java bean request scope: public class Custom { private String selectedTab; private String firstName; private String lastName; public Custom() { this.selectedTab = "firstname"; this.firstName = "tisha"; this.lastName = "kuprevich"; } ... } JSP: > TabPanel: value evaluated at phase1 > ----------------------------------- > > Key: RF-7353 > URL: https://issues.jboss.org/browse/RF-7353 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.2.CR1 > Reporter: Nick Belaevski > Assignee: Alexander Smirnov > Fix For: 3.3.2.GA > > -- 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 From jira-events at lists.jboss.org Tue Dec 3 17:41:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Dec 2013 17:41:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12062) a4j:outputMedia does not reRender in Firefox 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12062: ------------------------------- Description: a4j:outputMedia does not reRender in Firefox 11. The following error appears: {quote} ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] at java.lang.Thread.run(Unknown Source) [:1.6.0_31] Caused by: java.util.zip.DataFormatException: invalid bit length repeat at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] ... 30 more {quote} The picture is not visible. But if you refresh the site with f5, there is no error and all works great. was: a4j:outputMedia does not reRender in Firefox 11. The following error appears: ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] at java.lang.Thread.run(Unknown Source) [:1.6.0_31] Caused by: java.util.zip.DataFormatException: invalid bit length repeat at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] ... 30 more The picture is not visible. But if you refresh the site with f5, there is no error and all works great. > a4j:outputMedia does not reRender in Firefox 11 > ------------------------------------------------ > > Key: RF-12062 > URL: https://issues.jboss.org/browse/RF-12062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 3.3.3.Final > Environment: JBoss AS 6 > Reporter: Toni Neubert > Labels: a4j, outputmedia, richfaces > Fix For: 3.Future > > Attachments: richfaces-impl-3.3.3.Final.jar, WebXml.patch > > > a4j:outputMedia does not reRender in Firefox 11. The following error appears: > {quote} > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BPM-Process].[default]] Servlet.service() for servlet default threw exception: javax.faces.FacesException: Error decode resource data > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:627) [:3.3.3.Final] > at org.ajax4jsf.resource.ResourceBuilderImpl.getResourceDataForKey(ResourceBuilderImpl.java:371) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:156) [:3.3.3.Final] > at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) [:3.3.3.Final] > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) [:3.3.3.Final] > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) [:2.2.2.Final] > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.2.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.1.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.1.0.Final] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.1.0.Final] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.1.0.Final] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:6.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] > at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.1.0.Final] > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.1.0.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:159) [:6.1.0.Final] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.1.0.Final] > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.1.0.Final] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.1.0.Final] > at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.1.0.Final] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.1.0.Final] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.1.0.Final] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.1.0.Final] > at java.lang.Thread.run(Unknown Source) [:1.6.0_31] > Caused by: java.util.zip.DataFormatException: invalid bit length repeat > at java.util.zip.Inflater.inflateBytes(Native Method) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at java.util.zip.Inflater.inflate(Unknown Source) [:1.6.0_31] > at org.ajax4jsf.resource.ResourceBuilderImpl.decrypt(ResourceBuilderImpl.java:621) [:3.3.3.Final] > ... 30 more > {quote} > The picture is not visible. But if you refresh the site with f5, there is no error and all works great. -- 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 From jira-events at lists.jboss.org Tue Dec 3 18:46:08 2013 From: jira-events at lists.jboss.org (Val Blant (JIRA)) Date: Tue, 3 Dec 2013 18:46:08 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort order of source list after add/remove operations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924210#comment-12924210 ] Val Blant edited comment on RF-4308 at 12/3/13 6:44 PM: -------------------------------------------------------- I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving. {code:javascript|title=orderedPickListFix.js|borderStyle=solid} /** * This is an extension to the RichFaces PickList that preserves the original order of items in the source list * * @author Val Blant */ if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) { window.PickListExtension = {}; if ( typeof window.RichFaces.ui.PickList != 'undefined' ) { /** * Overriding original constructor found in "org.richfaces/pickList.js" resource */ window.RichFaces.ui.PickList = function(oldPickListConstructor) { return function(id, options) { // Instantiate the original PickList // var pickList = new oldPickListConstructor(id, options); // Assign item indecies to each item in the source list to preserve original order // pickList.sourceList.items.each(function( index ) { this.itemIndex = index; }); return pickList; }; }(window.RichFaces.ui.PickList); } /** * Original code taken from "org.richfaces/list.js" resource */ (function($, rf, list) { /** * Insert items into a pick list according to their original order stored in 'itemIndex' attribute */ list.prototype.addItems = function(items) { var parentContainer = this.scrollContainer; items.each(function() { if ( parentContainer.children().length <= this.itemIndex ) { parentContainer.append(this); } else { itemAtOurIndex = parentContainer.children()[this.itemIndex]; jQuery(this).insertBefore( itemAtOurIndex ); } }); this.__updateItemsList(); rf.Event.fire(this, "additems", items); }; }(jQuery, window.RichFaces, window.RichFaces.ui.List)); } {code} was (Author: vace117): I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving. {code:javascript|title=orderedPickListFix.js|borderStyle=solid} /** * This is an extension to the RichFaces PickList that preserves the original order of items in the source list * * @author Val Blant */ if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) { window.PickListExtension = {}; if ( typeof window.RichFaces.ui.PickList != 'undefined' ) { /** * Overriding original constructor found in "org.richfaces/pickList.js" resource */ window.RichFaces.ui.PickList = function(oldPickListConstructor) { return function(id, options) { // Instantiate the original PickList // var pickList = new oldPickListConstructor(id, options); // Assign item indecies to each item in the source list to preserve original order // pickList.sourceList.items.each(function( index ) { this.itemIndex = index; }); return pickList; }; }(window.RichFaces.ui.PickList); } /** * Original code taken from "org.richfaces/list.js" resource */ (function($, rf, list) { /** * Insert items into a pick list according to their original order stored in 'itemIndex' attribute */ list.prototype.addItems = function(items) { var parentContainer = this.scrollContainer; items.each(function() { if ( parentContainer.children().length < this.itemIndex ) { parentContainer.append(this); } else { itemAtOurIndex = parentContainer.children()[this.itemIndex]; jQuery(this).insertBefore( itemAtOurIndex ); } }); this.__updateItemsList(); rf.Event.fire(this, "additems", items); }; }(jQuery, window.RichFaces, window.RichFaces.ui.List)); } {code} > rich:pickList: keep sort order of source list after add/remove operations > ------------------------------------------------------------------------- > > Key: RF-4308 > URL: https://issues.jboss.org/browse/RF-4308 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1 > Reporter: Martin H?ller > Labels: low_hanging_fruit, order, picklist, sort > Fix For: 5-Tracking > > > When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. > My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- 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 From jira-events at lists.jboss.org Wed Dec 4 03:24:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 03:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928447#comment-12928447 ] Juraj H?ska commented on RF-13400: ---------------------------------- There is only {{r:pickList}} on the page. IMHO it is not caused by any other component, because as it is said in description the shrinking works on desktop browser when it changes its size. Is my assumption right ? > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:14:06 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 04:14:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: Holger Walter created RF-13408: ---------------------------------- Summary: ExtendedDataTable, ajax loading delay of 1000ms Key: RF-13408 URL: https://issues.jboss.org/browse/RF-13408 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Holger Walter -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:25:05 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 04:25:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Holger Walter updated RF-13408: ------------------------------- Description: When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:25:05 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 04:25:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Holger Walter updated RF-13408: ------------------------------- Affects Version/s: 4.3.4 > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:25:06 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 04:25:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Holger Walter updated RF-13408: ------------------------------- Description: When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , was: When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:29:05 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 04:29:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Holger Walter updated RF-13408: ------------------------------- Description: When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) Is it possible to reduce this timeout, or make it configurable via properties was: When using ajax loading in the extendeddatatable, an data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:54:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 04:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: Juraj H?ska created RF-13409: -------------------------------- Summary: PlotClickEvent - toString method return value needs better formatting and is not platform independent Key: RF-13409 URL: https://issues.jboss.org/browse/RF-13409 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-output Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska {{PlotClickEvent}} {{toString}} method needs some improvements: * there is missing space in returned value * it is not platform independent - uses {{\n}} as line separator. -- 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 From jira-events at lists.jboss.org Wed Dec 4 04:54:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 04:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13409: ----------------------------- Assignee: Juraj H?ska > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:00:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:00:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13409: ----------------------------- Description: {{PlotClickEvent}} {{toString}} method needs some improvements: * there is missing space in returned value * it is not platform independent - uses {{\n}} as line separator. Steps to reproduce: 1. load latest showcase chard demo for event handling: This can be seen in showcase: http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky 2. click on some point 3. See the missing space in the msg. was: {{PlotClickEvent}} {{toString}} method needs some improvements: * there is missing space in returned value * it is not platform independent - uses {{\n}} as line separator. > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:02:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13410: -------------------------------- Summary: Inplace input: when triggering 'click' event on control buttons a wrong request is made Key: RF-13410 URL: https://issues.jboss.org/browse/RF-13410 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Milestone4 Environment: RichFaces 4.0.0-SNAPSHOT r.20201 Metamer 4.0.0-SNAPSHOT r.20203 Mojarra 2.0.2-FCS GlassFish Server Open Source Edition 3.0.1 OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 7.0.517.44 @ Linux x86_64 Reporter: Ji?? ?tefek Fix For: 4.0.0.Milestone5 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml 2. set showControls=true 3. click on inplace input, change value and click cancel button result: an ajax request is sent (status and time in header change) -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:02:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Fix Version/s: (was: 4.0.0.Milestone5) > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Milestone4 > Environment: RichFaces 4.0.0-SNAPSHOT r.20201 > Metamer 4.0.0-SNAPSHOT r.20203 > Mojarra 2.0.2-FCS > GlassFish Server Open Source Edition 3.0.1 > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 7.0.517.44 @ Linux x86_64 > Reporter: Ji?? ?tefek > > 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > 2. set showControls=true > 3. click on inplace input, change value and click cancel button > result: > an ajax request is sent (status and time in header change) -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:02:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Affects Version/s: 5.0.0.Alpha1 4.3.4 (was: 4.0.0.Milestone4) > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Environment: RichFaces 4.0.0-SNAPSHOT r.20201 > Metamer 4.0.0-SNAPSHOT r.20203 > Mojarra 2.0.2-FCS > GlassFish Server Open Source Edition 3.0.1 > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 7.0.517.44 @ Linux x86_64 > Reporter: Ji?? ?tefek > > 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > 2. set showControls=true > 3. click on inplace input, change value and click cancel button > result: > an ajax request is sent (status and time in header change) -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:04:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Environment: (was: RichFaces 4.0.0-SNAPSHOT r.20201 Metamer 4.0.0-SNAPSHOT r.20203 Mojarra 2.0.2-FCS GlassFish Server Open Source Edition 3.0.1 OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 7.0.517.44 @ Linux x86_64) > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > > 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > 2. set showControls=true > 3. click on inplace input, change value and click cancel button > result: > an ajax request is sent (status and time in header change) -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:04:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Description: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml # set @showControls=true # open console and run this command: {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} * have: an ajax request is sent * expected: no request is sent With this command it works as expected: {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{code} was: 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml 2. set showControls=true 3. click on inplace input, change value and click cancel button result: an ajax request is sent (status and time in header change) > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an ajax request is sent > * expected: no request is sent > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 05:06:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:06:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Description: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml # set @showControls=true # open console and run this command: {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} * have: an HTTP request is sent * expected: ajax request is sent With this command it works as expected: {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{code} was: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml # set @showControls=true # open console and run this command: {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} * have: an ajax request is sent * expected: no request is sent With this command it works as expected: {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{code} > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: ajax request is sent > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 05:06:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:06:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Description: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml # set @showControls=true # open console and run this command: {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} * have: an HTTP request is sent * expected: no request is sent (canceling the value, when confirming an ajax request should be made) With this command it works as expected: {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{code} was: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml # set @showControls=true # open console and run this command: {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} * have: an HTTP request is sent * expected: ajax request is sent With this command it works as expected: {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{code} > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 05:08:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:08:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13410: ----------------------------- Summary: Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made (was: Inplace input: when triggering 'click' event on control buttons a wrong request is made) > Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 05:10:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-9872) Inplace input: when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-9872. --------------------------- Resolution: Done recreated in https://issues.jboss.org/browse/RF-13410 > Inplace input: when triggering 'click' event on control buttons a wrong request is made > --------------------------------------------------------------------------------------- > > Key: RF-9872 > URL: https://issues.jboss.org/browse/RF-9872 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Milestone4 > Environment: RichFaces 4.0.0-SNAPSHOT r.20201 > Metamer 4.0.0-SNAPSHOT r.20203 > Mojarra 2.0.2-FCS > GlassFish Server Open Source Edition 3.0.1 > OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux > Chrome 7.0.517.44 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 4.0.0.Milestone5 > > > 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > 2. set showControls=true > 3. click on inplace input, change value and click cancel button > result: > an ajax request is sent (status and time in header change) -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:12:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:12:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13411) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13411: -------------------------------- Summary: popupPanel: trimOverlayedElements not working Key: RF-13411 URL: https://issues.jboss.org/browse/RF-13411 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: Ji?? ?tefek Fix For: 4.0.0.Milestone6, 5-Tracking {code} test1 test2 ... {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 From jira-events at lists.jboss.org Wed Dec 4 05:12:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:12:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-9653) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-9653: ---------------------------- Affects Version/s: (was: 5.0.0.Alpha1) > 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 > 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} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:12:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:12:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13411) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13411: ----------------------------- Affects Version/s: (was: 4.0.0.Milestone4) > popupPanel: trimOverlayedElements not working > --------------------------------------------- > > Key: RF-13411 > URL: https://issues.jboss.org/browse/RF-13411 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 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: Ji?? ?tefek > Fix For: 4.0.0.Milestone6, 5-Tracking > > > {code} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:12:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:12:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13411) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13411: ----------------------------- Fix Version/s: (was: 4.0.0.Milestone6) > popupPanel: trimOverlayedElements not working > --------------------------------------------- > > Key: RF-13411 > URL: https://issues.jboss.org/browse/RF-13411 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 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: Ji?? ?tefek > Fix For: 5-Tracking > > > {code} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:12:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:12:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-9653) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-9653: ---------------------------- Fix Version/s: (was: 5-Tracking) > 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 > 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 > > > {code} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:14:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:14:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13411) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13411: ----------------------------- Environment: (was: 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 ) > popupPanel: trimOverlayedElements not working > --------------------------------------------- > > Key: RF-13411 > URL: https://issues.jboss.org/browse/RF-13411 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > Fix For: 5-Tracking > > > {code} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:14:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:14:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-9653) popupPanel: trimOverlayedElements not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-9653. --------------------------- Resolution: Done recreated in https://issues.jboss.org/browse/RF-13411 > 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 > 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 > > > {code} > > > > test1 > > test2 > > > ... > {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 From jira-events at lists.jboss.org Wed Dec 4 05:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13409: ----------------------------- Assignee: (was: Juraj H?ska) > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928483#comment-12928483 ] Juraj H?ska commented on RF-13409: ---------------------------------- Linkin pull request. > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:24:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928483#comment-12928483 ] Juraj H?ska edited comment on RF-13409 at 12/4/13 5:22 AM: ----------------------------------------------------------- Linking pull request. was (Author: jhuska): Linkin pull request. > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:32:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:32:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13412) autocomplete: after item selection the input is re-focused on IE In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13412: -------------------------------- Summary: autocomplete: after item selection the input is re-focused on IE Key: RF-13412 URL: https://issues.jboss.org/browse/RF-13412 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha2 Environment: IE 9, IE 10 Reporter: Ji?? ?tefek -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:36:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:36:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13413: -------------------------------- Summary: orderingList, pickList: the buttons have different size on IE Key: RF-13413 URL: https://issues.jboss.org/browse/RF-13413 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Environment: IE 9, IE 10 Reporter: Ji?? ?tefek Attachments: 1.png, 2.png -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:36:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:36:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13413: ----------------------------- Attachment: 1.png 2.png > orderingList, pickList: the buttons have different size on IE > ------------------------------------------------------------- > > Key: RF-13413 > URL: https://issues.jboss.org/browse/RF-13413 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Attachments: 1.png, 2.png > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 05:38:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Dec 2013 05:38:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13413: ----------------------------- Description: In both layouts > orderingList, pickList: the buttons have different size on IE > ------------------------------------------------------------- > > Key: RF-13413 > URL: https://issues.jboss.org/browse/RF-13413 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Attachments: 1.png, 2.png > > > In both layouts -- 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 From jira-events at lists.jboss.org Wed Dec 4 08:17:08 2013 From: jira-events at lists.jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Dec 2013 08:17:08 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928526#comment-12928526 ] Michal Petrov commented on RF-13404: ------------------------------------ Ported into [dev-examples/photoalbum-improvements|https://github.com/richfaces4/dev-examples/tree/photoalbum-improvements] along with RF-13405. I have to verify everything works but so far it looks good. > Port the RichFaces 5 improvements back to RichFaces 4.3 > ------------------------------------------------------- > > Key: RF-13404 > URL: https://issues.jboss.org/browse/RF-13404 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 08:19:07 2013 From: jira-events at lists.jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Dec 2013 08:19:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13404. -------------------------------- Resolution: Done > Port the RichFaces 5 improvements back to RichFaces 4.3 > ------------------------------------------------------- > > Key: RF-13404 > URL: https://issues.jboss.org/browse/RF-13404 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13168: ------------------------------- Assignee: Luk?? Fry? > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Luk?? Fry? > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13248: ------------------------------- Assignee: Luk?? Fry? > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: Juraj H?ska created RF-13414: -------------------------------- Summary: showcase - chart demo - event handling - when chart clicked it renders redundant info Key: RF-13414 URL: https://issues.jboss.org/browse/RF-13414 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-output, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: {code:none} Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] Series index: 3 DataIndex: 3 [1995,10.5] {code} The information is duplicated because it is retrieved in two ways: one from _server side_ ({{}}) and _client side script_. I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? Steps to reproduce: # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13414: ----------------------------- Priority: Trivial (was: Major) > showcase - chart demo - event handling - when chart clicked it renders redundant info > ------------------------------------------------------------------------------------- > > Key: RF-13414 > URL: https://issues.jboss.org/browse/RF-13414 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > > When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: > {code:none} > Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] > Series index: 3 DataIndex: 3 [1995,10.5] > {code} > The information is duplicated because it is retrieved in two ways: one from _server side_ ({{}}) and _client side script_. > I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? > Steps to reproduce: > # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13062: ------------------------------- Assignee: Luk?? Fry? > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13040: ------------------------------- Assignee: Luk?? Fry? > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13414: ----------------------------- Description: When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: {code:none} Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] Series index: 3 DataIndex: 3 [1995,10.5] {code} The information is duplicated because it is retrieved in two ways: one from _server side_ (__) and _client side script_. I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? Steps to reproduce: # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky # click on any chart line point and see the output was: When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: {code:none} Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] Series index: 3 DataIndex: 3 [1995,10.5] {code} The information is duplicated because it is retrieved in two ways: one from _server side_ ({{}}) and _client side script_. I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? Steps to reproduce: # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky # click on any chart line point and see the output > showcase - chart demo - event handling - when chart clicked it renders redundant info > ------------------------------------------------------------------------------------- > > Key: RF-13414 > URL: https://issues.jboss.org/browse/RF-13414 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > > When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: > {code:none} > Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] > Series index: 3 DataIndex: 3 [1995,10.5] > {code} > The information is duplicated because it is retrieved in two ways: one from _server side_ (__) and _client side script_. > I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? > Steps to reproduce: > # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:26:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:26:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13197: ------------------------------- Assignee: Luk?? Fry? > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:28:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928567#comment-12928567 ] Juraj H?ska commented on RF-13414: ---------------------------------- Note that I have already sent one pull request for further improving the output. See RF-13409. > showcase - chart demo - event handling - when chart clicked it renders redundant info > ------------------------------------------------------------------------------------- > > Key: RF-13414 > URL: https://issues.jboss.org/browse/RF-13414 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > > When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: > {code:none} > Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] > Series index: 3 DataIndex: 3 [1995,10.5] > {code} > The information is duplicated because it is retrieved in two ways: one from _server side_ (__) and _client side script_. > I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? > Steps to reproduce: > # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:28:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:28:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13414: ----------------------------- Description: When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: {code:none} Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] Series index: 3 DataIndex: 3 [1995,10.5] {code} The information is duplicated because it is retrieved in two ways: one from _server side_ - {code:xml} {code} and _client side script_. I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? Steps to reproduce: # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky # click on any chart line point and see the output was: When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: {code:none} Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] Series index: 3 DataIndex: 3 [1995,10.5] {code} The information is duplicated because it is retrieved in two ways: one from _server side_ (__) and _client side script_. I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? Steps to reproduce: # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky # click on any chart line point and see the output > showcase - chart demo - event handling - when chart clicked it renders redundant info > ------------------------------------------------------------------------------------- > > Key: RF-13414 > URL: https://issues.jboss.org/browse/RF-13414 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > > When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: > {code:none} > Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] > Series index: 3 DataIndex: 3 [1995,10.5] > {code} > The information is duplicated because it is retrieved in two ways: one from _server side_ - > {code:xml} > > {code} > and _client side script_. > I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? > Steps to reproduce: > # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 09:30:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 09:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13199: ------------------------------- Assignee: Luk?? Fry? > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.skin/ITBlueSkySkin/org_richfaces_skin_ITBlueSkySkin/] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.ui.extendedDataTable/ITDisablingBuiltinSortingAndFiltering/org_richfaces_ui_extendedDataTable_ITDisablingBuiltinSortingAndFiltering/] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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 From jira-events at lists.jboss.org Wed Dec 4 10:52:09 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 10:52:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13415) r:autocomplete - autofill attribute is not working In-Reply-To: References: Message-ID: Juraj H?ska created RF-13415: -------------------------------- Summary: r:autocomplete - autofill attribute is not working Key: RF-13415 URL: https://issues.jboss.org/browse/RF-13415 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska {{autofill}} attribute of {{r:autocomplete}} does not work. Setting of {{autofill}} to {{false}} does not prevent from autofilling the option. IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. -- 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 From jira-events at lists.jboss.org Wed Dec 4 10:52:09 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 10:52:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13415) r:autocomplete - autofill attribute is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13415: ----------------------------- Description: {{autofill}} attribute of {{r:autocomplete}} does not work. Setting of {{autofill}} to {{false}} does not prevent from autofilling the suggestion. IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. was: {{autofill}} attribute of {{r:autocomplete}} does not work. Setting of {{autofill}} to {{false}} does not prevent from autofilling the option. IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. > r:autocomplete - autofill attribute is not working > -------------------------------------------------- > > Key: RF-13415 > URL: https://issues.jboss.org/browse/RF-13415 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{autofill}} attribute of {{r:autocomplete}} does not work. > Setting of {{autofill}} to {{false}} does not prevent from autofilling the suggestion. > IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. > Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. -- 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 From jira-events at lists.jboss.org Wed Dec 4 10:54:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 10:54:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13415) r:autocomplete - autofill attribute is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13415: ----------------------------- Description: {{autofill}} attribute of {{r:autocomplete}} does not work. Setting of {{autofill}} to {{false}} does not prevent from autofilling a suggestion. IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. was: {{autofill}} attribute of {{r:autocomplete}} does not work. Setting of {{autofill}} to {{false}} does not prevent from autofilling the suggestion. IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. > r:autocomplete - autofill attribute is not working > -------------------------------------------------- > > Key: RF-13415 > URL: https://issues.jboss.org/browse/RF-13415 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{autofill}} attribute of {{r:autocomplete}} does not work. > Setting of {{autofill}} to {{false}} does not prevent from autofilling a suggestion. > IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. > Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. -- 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 From jira-events at lists.jboss.org Wed Dec 4 10:54:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 10:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13415) r:autocomplete - autofill attribute is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928631#comment-12928631 ] Juraj H?ska commented on RF-13415: ---------------------------------- The question is whether we do not want to rename the attribute to {{autoFill}} as it is in RW. IMHO it makes more sense. Note that in RF 4.x it was {{autofill}}. > r:autocomplete - autofill attribute is not working > -------------------------------------------------- > > Key: RF-13415 > URL: https://issues.jboss.org/browse/RF-13415 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > {{autofill}} attribute of {{r:autocomplete}} does not work. > Setting of {{autofill}} to {{false}} does not prevent from autofilling a suggestion. > IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. > Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. -- 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 From jira-events at lists.jboss.org Wed Dec 4 11:00:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 11:00:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13416) showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used In-Reply-To: References: Message-ID: Juraj H?ska created RF-13416: -------------------------------- Summary: showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used Key: RF-13416 URL: https://issues.jboss.org/browse/RF-13416 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska See the source code for autocomplete modes demo: * at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L43] line * and at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L53] line There are used both {{autofill}} and {{autoFill}}. We should decide which one is correct in RF-13415 and alter the showcase accordingly. -- 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 From jira-events at lists.jboss.org Wed Dec 4 11:00:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 4 Dec 2013 11:00:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13416) showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13416: ----------------------------- Priority: Trivial (was: Major) > showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used > ------------------------------------------------------------------------------------------- > > Key: RF-13416 > URL: https://issues.jboss.org/browse/RF-13416 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > > See the source code for autocomplete modes demo: > * at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L43] line > * and at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L53] line > There are used both {{autofill}} and {{autoFill}}. > We should decide which one is correct in RF-13415 and alter the showcase accordingly. -- 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 From jira-events at lists.jboss.org Wed Dec 4 11:06:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 4 Dec 2013 11:06:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render after ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13390: ------------------------------- Assignee: Luk?? Fry? > Region fails to render after ajax request > ----------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > > > > > > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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 From jira-events at lists.jboss.org Wed Dec 4 12:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 12:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13198) ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13198: ------------------------------- Labels: jsf22 (was: ) > ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 > --------------------------------------------------------------------------------------------- > > Key: RF-13198 > URL: https://issues.jboss.org/browse/RF-13198 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly8.0.0.alpha4 > JSF 2.2 > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > When loading the page which is generated by {{ITAutoRegisteredPushServlet}}, deployed on Wildfly 8.0.0 an {{IllegalArqumentEception}} is thrown by WildFly Undertow web server: > {code} > 11:02:19,931 ERROR [io.undertow.request] (default task-13) Servlet request failed HttpServerExchange{ GET /push/__richfaces_push}: java.lang.IllegalStateException: UT010026: Async is not supported for this request, as not all filters or Servlets were marked as supporting async > at io.undertow.servlet.spec.HttpServletRequestImpl.startAsync(HttpServletRequestImpl.java:876) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.atmosphere.cpr.AtmosphereRequest.startAsync(AtmosphereRequest.java:565) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.suspend(Servlet30CometSupport.java:137) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:103) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) [arquillian-warp.jar:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:207) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:628) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Note that it is probably not connected with JSF 2.2, as the same page works correctly with *GlassFish 4*. It works with *JBoss AS 7.1.Final* as well. -- 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 From jira-events at lists.jboss.org Wed Dec 4 12:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 12:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13198) ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13198: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 > --------------------------------------------------------------------------------------------- > > Key: RF-13198 > URL: https://issues.jboss.org/browse/RF-13198 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly8.0.0.alpha4 > JSF 2.2 > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When loading the page which is generated by {{ITAutoRegisteredPushServlet}}, deployed on Wildfly 8.0.0 an {{IllegalArqumentEception}} is thrown by WildFly Undertow web server: > {code} > 11:02:19,931 ERROR [io.undertow.request] (default task-13) Servlet request failed HttpServerExchange{ GET /push/__richfaces_push}: java.lang.IllegalStateException: UT010026: Async is not supported for this request, as not all filters or Servlets were marked as supporting async > at io.undertow.servlet.spec.HttpServletRequestImpl.startAsync(HttpServletRequestImpl.java:876) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.atmosphere.cpr.AtmosphereRequest.startAsync(AtmosphereRequest.java:565) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.suspend(Servlet30CometSupport.java:137) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:103) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) [arquillian-warp.jar:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:207) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:628) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Note that it is probably not connected with JSF 2.2, as the same page works correctly with *GlassFish 4*. It works with *JBoss AS 7.1.Final* as well. -- 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 From jira-events at lists.jboss.org Wed Dec 4 12:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 12:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13369: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Labels: jsf22 > Fix For: 4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > autocomplete: the pop-up list always appears empty -- 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 From jira-events at lists.jboss.org Wed Dec 4 12:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 12:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13369: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Labels: jsf22 > Fix For: 4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > autocomplete: the pop-up list always appears empty -- 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 From jira-events at lists.jboss.org Wed Dec 4 12:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 12:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13198) ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13198: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > ITAutoRegisteredPushServlet fails with - Async is not supported for this request on WildFly80 > --------------------------------------------------------------------------------------------- > > Key: RF-13198 > URL: https://issues.jboss.org/browse/RF-13198 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly8.0.0.alpha4 > JSF 2.2 > Reporter: Juraj H?ska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When loading the page which is generated by {{ITAutoRegisteredPushServlet}}, deployed on Wildfly 8.0.0 an {{IllegalArqumentEception}} is thrown by WildFly Undertow web server: > {code} > 11:02:19,931 ERROR [io.undertow.request] (default task-13) Servlet request failed HttpServerExchange{ GET /push/__richfaces_push}: java.lang.IllegalStateException: UT010026: Async is not supported for this request, as not all filters or Servlets were marked as supporting async > at io.undertow.servlet.spec.HttpServletRequestImpl.startAsync(HttpServletRequestImpl.java:876) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.atmosphere.cpr.AtmosphereRequest.startAsync(AtmosphereRequest.java:565) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.suspend(Servlet30CometSupport.java:137) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:103) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) [arquillian-warp.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) [arquillian-core.jar:] > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) [arquillian-core.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) [arquillian-warp.jar:] > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) [arquillian-warp.jar:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:207) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:628) [undertow-core-1.0.0.Beta7.jar:1.0.0.Beta7] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Note that it is probably not connected with JSF 2.2, as the same page works correctly with *GlassFish 4*. It works with *JBoss AS 7.1.Final* as well. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928668#comment-12928668 ] Brian Leathem commented on RF-13400: ------------------------------------ I'll have to take a look. Can you provide steps to reproduce? > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:00:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:00:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13400: -------------------------------- re-opening for further investigation > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:02:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928670#comment-12928670 ] Brian Leathem commented on RF-13404: ------------------------------------ Nice work, thanks [~mpetrov]! > Port the RichFaces 5 improvements back to RichFaces 4.3 > ------------------------------------------------------- > > Key: RF-13404 > URL: https://issues.jboss.org/browse/RF-13404 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.5 > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:12:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:12:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13408: ------------------------------- Issue Type: Feature Request (was: Enhancement) > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:12:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:12:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13408: ------------------------------- Fix Version/s: 5-Tracking > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:14:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:14:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928674#comment-12928674 ] Brian Leathem commented on RF-13408: ------------------------------------ Nice idea. We'll file this feature request away for future consideration. If you would like to accelerate it's implementation, feel free to file a Pull Request. > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:16:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:16:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13410: ------------------------------- Fix Version/s: 4.5-Tracking > Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > Fix For: 4.5-Tracking > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 13:16:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:16:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13410) Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13410: ------------------------------- Fix Version/s: 5-Tracking (was: 4.5-Tracking) > Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > Fix For: 5-Tracking > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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 From jira-events at lists.jboss.org Wed Dec 4 13:18:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13412) autocomplete: after item selection the input is re-focused on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13412: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > autocomplete: after item selection the input is re-focused on IE > ---------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Fix For: 5.0.0.Alpha3 > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:18:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13412) autocomplete: after item selection the input is re-focused on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928676#comment-12928676 ] Brian Leathem commented on RF-13412: ------------------------------------ [~jstefek] is this reproducible in a RichWidgets sample? > autocomplete: after item selection the input is re-focused on IE > ---------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Fix For: 5.0.0.Alpha3 > > -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:24:07 2013 From: jira-events at lists.jboss.org (Holger Walter (JIRA)) Date: Wed, 4 Dec 2013 13:24:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928678#comment-12928678 ] Holger Walter commented on RF-13408: ------------------------------------ Hi Brian, thanks for your feedback. Just one question - what is a 'Pull Request'? Regards wlh > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:24:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:24:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928679#comment-12928679 ] Brian Leathem commented on RF-13413: ------------------------------------ In [richwidgets/issues/53|https://github.com/richwidgets/richwidgets/issues/53] this was fixed for FireFox by using the CSS 3 flexbox technique. According to this [w3c schools page|http://www.w3schools.com/cssref/css3_pr_box-flex.asp] css3 flexbox is only supported in ie >= 10, but we have to sue the {{-ms-flex}} property. I've filed a new richwidget issue to track this: https://github.com/richwidgets/richwidgets/issues/159 > orderingList, pickList: the buttons have different size on IE > ------------------------------------------------------------- > > Key: RF-13413 > URL: https://issues.jboss.org/browse/RF-13413 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Attachments: 1.png, 2.png > > > In both layouts -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:26:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:26:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13413: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > orderingList, pickList: the buttons have different size on IE > ------------------------------------------------------------- > > Key: RF-13413 > URL: https://issues.jboss.org/browse/RF-13413 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Fix For: 5.0.0.Alpha3 > > Attachments: 1.png, 2.png > > > In both layouts -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:26:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:26:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13414) showcase - chart demo - event handling - when chart clicked it renders redundant info In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13414: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > showcase - chart demo - event handling - when chart clicked it renders redundant info > ------------------------------------------------------------------------------------- > > Key: RF-13414 > URL: https://issues.jboss.org/browse/RF-13414 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > Fix For: 5.0.0.Alpha3 > > > When clicking on the chart in the showcase demo for event handling, e.g. following output is rendered: > {code:none} > Point with index 3within series 3 was clicked. Point coordinates [1995,10.5] > Series index: 3 DataIndex: 3 [1995,10.5] > {code} > The information is duplicated because it is retrieved in two ways: one from _server side_ - > {code:xml} > > {code} > and _client side script_. > I see that it is nice showcase of both ways, but IMHO the script for *hover* event is doing this well. The output would be more cleaner. WDYT ? > Steps to reproduce: > # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > # click on any chart line point and see the output -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:36:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:36:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13409: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:38:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:38:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13415) r:autocomplete - autofill attribute is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13415: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > r:autocomplete - autofill attribute is not working > -------------------------------------------------- > > Key: RF-13415 > URL: https://issues.jboss.org/browse/RF-13415 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > > {{autofill}} attribute of {{r:autocomplete}} does not work. > Setting of {{autofill}} to {{false}} does not prevent from autofilling a suggestion. > IMHO it is caused by missing the attribute passing in the render template, [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml]. > Note that the attribute needs to be renamed, as RW one uses: {{autoFill}} and RichFaces {{autofill}}. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:38:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:38:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13416) showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13416: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > showcase - autocomplete - modes demo - there are both autoFill and autofill attributes used > ------------------------------------------------------------------------------------------- > > Key: RF-13416 > URL: https://issues.jboss.org/browse/RF-13416 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Trivial > Fix For: 5.0.0.Alpha3 > > > See the source code for autocomplete modes demo: > * at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L43] line > * and at [this|https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/webapp/richfaces/autocomplete/samples/modes-sample.xhtml#L53] line > There are used both {{autofill}} and {{autoFill}}. > We should decide which one is correct in RF-13415 and alter the showcase accordingly. -- 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 From jira-events at lists.jboss.org Wed Dec 4 13:40:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Dec 2013 13:40:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928682#comment-12928682 ] Brian Leathem commented on RF-13408: ------------------------------------ Ah sorry, I've been living and breathing git for so long that I forget not everyone does. A _Pull Request_ is basically a patch submitted through the git workflow mechanism, a task made easier with the web ui's of github. See this wiki page for more details: https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Thu Dec 5 01:49:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 01:49:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13412) autocomplete: when @autofill=true after item is selected the input is re-focused on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13412: ----------------------------- Summary: autocomplete: when @autofill=true after item is selected the input is re-focused on IE (was: autocomplete: after item selection the input is re-focused on IE) > autocomplete: when @autofill=true after item is selected the input is re-focused on IE > -------------------------------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Fix For: 5.0.0.Alpha3 > > -- 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 From jira-events at lists.jboss.org Thu Dec 5 02:02:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 02:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13412) autocomplete: when @autofill=true after item is selected the input is re-focused on IE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928782#comment-12928782 ] Ji?? ?tefek commented on RF-13412: ---------------------------------- Created and linked widget issue to track this. > autocomplete: when @autofill=true after item is selected the input is re-focused on IE > -------------------------------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Ji?? ?tefek > Fix For: 5.0.0.Alpha3 > > -- 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 From jira-events at lists.jboss.org Thu Dec 5 03:23:06 2013 From: jira-events at lists.jboss.org (Mike K (JIRA)) Date: Thu, 5 Dec 2013 03:23:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928797#comment-12928797 ] Mike K commented on RF-13408: ----------------------------- Ohh and could you please cache the list data in the client - so that when you scroll (back) you don't have to reload the data again? > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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 From jira-events at lists.jboss.org Thu Dec 5 03:45:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:45:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13417: ------------------------------- Summary: Some warp-based framework tests fail on WildFly with exception 'Could not inject members' Key: RF-13417 URL: https://issues.jboss.org/browse/RF-13417 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 5.0.0.Alpha2 Reporter: Luk?? Fry? Exception and cause: {code} java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue {code} {code} Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) at java.lang.reflect.Field.set(Field.java:741) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) {code} Failed tests: {code} org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis org.richfaces.ui.region.ITExecuteRichAjax.testDefaults org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis org.richfaces.ui.region.ITRegionJSFAjax.testDefaults org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis org.richfaces.ui.region.ITRegionRichAjax.testDefaults org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis org.richfaces.ui.menu.ITDropDownMenuItem.testServer {code} Full stack trace: {code} java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) at java.lang.reflect.Field.set(Field.java:741) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) ... 115 more {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 From jira-events at lists.jboss.org Thu Dec 5 03:47:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:47:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13417: ---------------------------- Workaround Description: Workaround is using regular classes as inspections instead of static inner classes > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 03:47:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:47:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13417: ---------------------------- Fix Version/s: 5.0.0.Alpha3 > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 03:47:06 2013 From: jira-events at lists.jboss.org (Mike K (JIRA)) Date: Thu, 5 Dec 2013 03:47:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13418) After sorting on extendedDataTable the contextMenu is broken In-Reply-To: References: Message-ID: Mike K created RF-13418: --------------------------- Summary: After sorting on extendedDataTable the contextMenu is broken Key: RF-13418 URL: https://issues.jboss.org/browse/RF-13418 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu, component-selects Affects Versions: 4.3.4 Environment: Win7 IE9 / FF 25.0.1 Reporter: Mike K After sorting on extendedDataTable the contextMenu is not shown anymore Detailled description and code here: https://community.jboss.org/message/803276#803276 Maybe related to https://issues.jboss.org/browse/RF-11973 -- 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 From jira-events at lists.jboss.org Thu Dec 5 03:49:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:49:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928802#comment-12928802 ] Luk?? Fry? commented on RF-13417: --------------------------------- I will use the workaround and create Warp issue. > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 03:49:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:49:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13417: ---------------------------- Labels: warp (was: ) > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Labels: warp > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 03:55:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 03:55:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13417: ---------------------------- Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Labels: warp > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 04:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13090) named functions not working as documented In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13090: ----------------------------- Labels: (was: needs-qe) > named functions not working as documented > ------------------------------------------------------- > > Key: RF-13090 > URL: https://issues.jboss.org/browse/RF-13090 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.2 > Reporter: Vincent W?lcknitz > Assignee: Vincent W?lcknitz > Priority: Minor > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I have found some strange behaviour with the component when you implement named functions like described in the component reference: > http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/html/chap-Component_Reference-Layout_and_appearance.html#sect-Component_Reference-richjQuery-Named_queries > If I implement the given code from the reference: > {code} > > > ... > > > {code} > only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout. > I found out that if I do some small changes to the onmouseout call it works fine: > {code} > > > ... > > > {code} > It only works when adding a second parameter to the call even if its empty. -- 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 From jira-events at lists.jboss.org Thu Dec 5 04:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13090) named functions not working as documented In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13090. ---------------------------- Verified in both 4.5.0.Alpha1 and 5.0.0.Alpha2. > named functions not working as documented > ------------------------------------------------------- > > Key: RF-13090 > URL: https://issues.jboss.org/browse/RF-13090 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.2 > Reporter: Vincent W?lcknitz > Assignee: Vincent W?lcknitz > Priority: Minor > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I have found some strange behaviour with the component when you implement named functions like described in the component reference: > http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/html/chap-Component_Reference-Layout_and_appearance.html#sect-Component_Reference-richjQuery-Named_queries > If I implement the given code from the reference: > {code} > > > ... > > > {code} > only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout. > I found out that if I do some small changes to the onmouseout call it works fine: > {code} > > > ... > > > {code} > It only works when adding a second parameter to the call even if its empty. -- 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 From jira-events at lists.jboss.org Thu Dec 5 04:40:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:40:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13400: ----------------------------- Steps to Reproduce: # load pickList Metamer page in real Android device: http://localhost:8080/metamer/faces/components/richPickList/simple.xhtml # see that pickList is not responsive > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Thu Dec 5 04:40:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:40:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928821#comment-12928821 ] Juraj H?ska commented on RF-13400: ---------------------------------- Added steps to reproduce. > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Thu Dec 5 04:44:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:44:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928823#comment-12928823 ] Juraj H?ska commented on RF-13400: ---------------------------------- The same problem with responsiveness have other new components as well. OrderingList and Autocomplete. I guess that it is the same issue. Tell me if you want separated issues for all of them. > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Thu Dec 5 04:52:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 04:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13242) ajaxcomplete event is called before javascriptServiceCompleted event In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928827#comment-12928827 ] Ji?? ?tefek commented on RF-13242: ---------------------------------- [~lfryc], could you give me a tip how/where could I verify this behavior? > ajaxcomplete event is called before javascriptServiceCompleted event > -------------------------------------------------------------------- > > Key: RF-13242 > URL: https://issues.jboss.org/browse/RF-13242 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > The events / attributes / JS service invocations should be as follow: > * {{@onbeforedomupdate}} > * {{ajaxbeforedomupdate}} > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} > * *{{ajaxcomplete}}* > But they are: > * {{ajaxbeforedomupdate}} > * {{@onbeforedomupdate}} > * *{{ajaxcomplete}}* > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} -- 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 From jira-events at lists.jboss.org Thu Dec 5 05:06:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 05:06:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928841#comment-12928841 ] Luk?? Fry? commented on RF-13199: --------------------------------- The solution is marking test deployments as testable=false > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.skin/ITBlueSkySkin/org_richfaces_skin_ITBlueSkySkin/] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.ui.extendedDataTable/ITDisablingBuiltinSortingAndFiltering/org_richfaces_ui_extendedDataTable_ITDisablingBuiltinSortingAndFiltering/] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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 From jira-events at lists.jboss.org Thu Dec 5 05:06:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 05:06:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13417: ---------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Labels: warp > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 05:06:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 05:06:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13417: ------------------------------- Assignee: Luk?? Fry? > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: warp > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 05:35:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 05:35:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928859#comment-12928859 ] Luk?? Fry? commented on RF-13248: --------------------------------- The tests almost pass on WildFly Beta2-SNAPSHOT, so I think we should wait for WildFly CR1. > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From jira-events at lists.jboss.org Thu Dec 5 05:53:05 2013 From: jira-events at lists.jboss.org (Gustavo Ehrhardt (JIRA)) Date: Thu, 5 Dec 2013 05:53:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13419) FileUpload doesn't fire the listener when deployed with Myfaces tomahawk In-Reply-To: References: Message-ID: Gustavo Ehrhardt created RF-13419: ------------------------------------- Summary: FileUpload doesn't fire the listener when deployed with Myfaces tomahawk Key: RF-13419 URL: https://issues.jboss.org/browse/RF-13419 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.4, 4.3.3 Environment: Tomcat 7.0.47 jdk1.6.0_45 Windows 7 Mojarra 2.1.26 tomahawk 1.1.14 Reporter: Gustavo Ehrhardt FileUpload doesn't fire the listener when deployed with Myfaces tomahawk. When I declare the MyFaces extension filter in web.xml the listener method is never called after the upload is completed. -- 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 From jira-events at lists.jboss.org Thu Dec 5 05:57:06 2013 From: jira-events at lists.jboss.org (Gustavo Ehrhardt (JIRA)) Date: Thu, 5 Dec 2013 05:57:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13419) FileUpload doesn't fire the listener when deployed with Myfaces tomahawk In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gustavo Ehrhardt updated RF-13419: ---------------------------------- Attachment: UploadFile.rar Complete project to reproduce the issue. Just add the richfaces jar. > FileUpload doesn't fire the listener when deployed with Myfaces tomahawk > ------------------------------------------------------------------------ > > Key: RF-13419 > URL: https://issues.jboss.org/browse/RF-13419 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.3, 4.3.4 > Environment: Tomcat 7.0.47 > jdk1.6.0_45 > Windows 7 > Mojarra 2.1.26 > tomahawk 1.1.14 > Reporter: Gustavo Ehrhardt > Labels: myfaces, tomahawk, upload > Attachments: UploadFile.rar > > > FileUpload doesn't fire the listener when deployed with Myfaces tomahawk. > When I declare the MyFaces extension filter in web.xml the listener method is never called after the upload is completed. -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:10:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13242) ajaxcomplete event is called before javascriptServiceCompleted event In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928863#comment-12928863 ] Luk?? Fry? commented on RF-13242: --------------------------------- Hey [~jstefek], the scenario is verified here in framework tests: https://github.com/richfaces/richfaces/blob/master/framework/src/test/integration/org/richfaces/integration/javascript/ITJavaScriptServiceAjax.java#L114 > ajaxcomplete event is called before javascriptServiceCompleted event > -------------------------------------------------------------------- > > Key: RF-13242 > URL: https://issues.jboss.org/browse/RF-13242 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > The events / attributes / JS service invocations should be as follow: > * {{@onbeforedomupdate}} > * {{ajaxbeforedomupdate}} > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} > * *{{ajaxcomplete}}* > But they are: > * {{ajaxbeforedomupdate}} > * {{@onbeforedomupdate}} > * *{{ajaxcomplete}}* > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:16:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:16:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: Juraj H?ska created RF-13420: -------------------------------- Summary: Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged Key: RF-13420 URL: https://issues.jboss.org/browse/RF-13420 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: showcase Affects Versions: 5.0.0.Alpha2 Environment: Firefox, Chrome JBoss AS 7.1.1.Final Reporter: Juraj H?ska Priority: Minor Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. {code:none} 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. {code} Steps to reproduce: # deploy showcase # clean the browser cache # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky # look for the WARNING in the JBoss AS console Notes: * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:18:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13420: ----------------------------- Description: Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. {code:none} 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. {code} Steps to reproduce: # deploy showcase # clean the browser cache # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky # look for the WARNING in the JBoss AS console Notes: * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged was: Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. {code:none} 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. {code} Steps to reproduce: # deploy showcase # clean the browser cache # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky # look for the WARNING in the JBoss AS console Notes: * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:20:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:20:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928864#comment-12928864 ] Juraj H?ska commented on RF-13420: ---------------------------------- I tried to add the mime type to {{web.xml}}. According to [this|http://stackoverflow.com/a/5142316] stackoverflow thread, I used this one: {code:xml} woff application/font-woff {code} After applying this fix the WARNING is *not* logged anymore. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928864#comment-12928864 ] Juraj H?ska edited comment on RF-13420 at 12/5/13 6:21 AM: ----------------------------------------------------------- I tried to add the mime type to {{web.xml}}. According to [this|http://stackoverflow.com/a/5142316] stackoverflow thread, I used this one: {code:xml} woff application/font-woff {code} After applying this fix the WARNING is *not* logged anymore. Do you think it is a proper solution ? We had similar problem reported here: RF-13380. But IMHO it is a different case, as there loading the resources finished with HTTP 404, this finishes with 200. was (Author: jhuska): I tried to add the mime type to {{web.xml}}. According to [this|http://stackoverflow.com/a/5142316] stackoverflow thread, I used this one: {code:xml} woff application/font-woff {code} After applying this fix the WARNING is *not* logged anymore. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928865#comment-12928865 ] Juraj H?ska commented on RF-13420: ---------------------------------- Tomcat 7 is *not * logging such a WARNING. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Thu Dec 5 06:26:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 06:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928865#comment-12928865 ] Juraj H?ska edited comment on RF-13420 at 12/5/13 6:25 AM: ----------------------------------------------------------- Tomcat 7 is *not* logging such a WARNING. was (Author: jhuska): Tomcat 7 is *not * logging such a WARNING. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Thu Dec 5 08:30:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 08:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13199. ----------------------------- Resolution: Done > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.skin/ITBlueSkySkin/org_richfaces_skin_ITBlueSkySkin/] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/job/richfaces-5.0-ff-wildfly80/1/testReport/junit/org.richfaces.ui.extendedDataTable/ITDisablingBuiltinSortingAndFiltering/org_richfaces_ui_extendedDataTable_ITDisablingBuiltinSortingAndFiltering/] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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 From jira-events at lists.jboss.org Thu Dec 5 08:30:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 08:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13417) Some warp-based framework tests fail on WildFly with exception 'Could not inject members' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13417. ----------------------------- Resolution: Done Applied workaround - we will wait for upstream fix, then we can use member classes again. > Some warp-based framework tests fail on WildFly with exception 'Could not inject members' > ----------------------------------------------------------------------------------------- > > Key: RF-13417 > URL: https://issues.jboss.org/browse/RF-13417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha2 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: warp > Fix For: 5.0.0.Alpha3 > > > Exception and cause: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValue > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > {code} > Failed tests: > {code} > org.richfaces.ui.region.ITExecuteJSFAjax.testDefaults > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteJSFAjax.testExecuteThis > org.richfaces.ui.region.ITExecuteRichAjax.testDefaults > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteAll > org.richfaces.ui.region.ITExecuteRichAjax.testExecuteThis > org.richfaces.ui.region.ITRegionJSFAjax.testDefaults > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteAll > org.richfaces.ui.region.ITRegionJSFAjax.testExecuteThis > org.richfaces.ui.region.ITRegionRichAjax.testDefaults > org.richfaces.ui.region.ITRegionRichAjax.testExecuteAll > org.richfaces.ui.region.ITRegionRichAjax.testExecuteForm > org.richfaces.ui.region.ITRegionRichAjax.testExecuteThis > org.richfaces.ui.menu.ITDropDownMenuItem.testServer > {code} > Full stack trace: > {code} > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestEnrichmentWatcher.rememberFieldValues(LifecycleTestEnrichmentWatcher.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.beforeTest(LifecycleTestClassExecutor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.executeTest(LifecycleTestDriver.java:89) > at org.jboss.arquillian.warp.impl.server.test.LifecycleTestDriver.fireTest(LifecycleTestDriver.java:73) > at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerImpl.fireEvent(LifecycleManagerImpl.java:41) > at org.jboss.arquillian.warp.impl.server.execution.WarpLifecycle.execute(WarpLifecycle.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.WarpRequestProcessor.processWarpRequest(WarpRequestProcessor.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:144) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:117) > at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:90) > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:238) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:225) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:71) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:144) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:649) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalArgumentException: Can not set org.richfaces.ui.region.RegionBean field org.richfaces.ui.region.AbstractRegionTest$SetupExecute.region to org.richfaces.ui.region.AbstractRegionTest$SetupExecute > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) > at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) > at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:55) > at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:75) > at java.lang.reflect.Field.set(Field.java:741) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) > ... 115 more > {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 From jira-events at lists.jboss.org Thu Dec 5 08:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 08:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928896#comment-12928896 ] Luk?? Fry? commented on RF-13040: --------------------------------- components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. I think it is related to RF-13197. > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Thu Dec 5 08:36:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 5 Dec 2013 08:36:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928896#comment-12928896 ] Luk?? Fry? edited comment on RF-13040 at 12/5/13 8:34 AM: ---------------------------------------------------------- components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. I think it is related to RF-13197. The same issue with Showcase. was (Author: lfryc): components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. I think it is related to RF-13197. > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From jira-events at lists.jboss.org Thu Dec 5 08:42:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 08:42:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13409) PlotClickEvent - toString method return value needs better formatting and is not platform independent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13409: ----------------------------- Priority: Minor (was: Major) > PlotClickEvent - toString method return value needs better formatting and is not platform independent > ----------------------------------------------------------------------------------------------------- > > Key: RF-13409 > URL: https://issues.jboss.org/browse/RF-13409 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 5.0.0.Alpha3 > > > {{PlotClickEvent}} {{toString}} method needs some improvements: > * there is missing space in returned value > * it is not platform independent - uses {{\n}} as line separator. > Steps to reproduce: > 1. load latest showcase chard demo for event handling: > This can be seen in showcase: > http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on some point > 3. See the missing space in the msg. -- 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 From jira-events at lists.jboss.org Thu Dec 5 08:50:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Dec 2013 08:50:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928905#comment-12928905 ] Matej Novotny commented on RF-13230: ------------------------------------ I tried to reproduce this issue but I am not sure what behaviour should be expected. I tried it with ViewScoped bean first (later on I tried with Conversation too). Now following the steps in description (for 4.3.3)... Changing the column ordering - JSON String is correctly passed to the bean and stored. Setting its value to null using ajax - used a4j:commandButton, set to null, variable was null Rerender component - nothing happened, table is still modified Full page refresh - nothing happened , table is still modified Access page url again - table is loaded in default setup This seems like the current table modifications are stored in a session or so as long as I don't switch from one page to another. Is the tableState meant to work as this issue describes it or is it a way to get hold of the table format to store it for future use (eg. when user comes back to website, the table will load based on last stored state)? Back to Conversation bean, I tried to reproduce it with this one too and got the same result. However I cannot be sure I implemented it correctly since I never did it before. So [~ibenjes] could you provide a simple example where this feature was working for you with older RF? Without that I don't think I can reproduce this. > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:02:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:02:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13242) ajaxcomplete event is called before javascriptServiceCompleted event In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928908#comment-12928908 ] Ji?? ?tefek commented on RF-13242: ---------------------------------- thanks Lukas > ajaxcomplete event is called before javascriptServiceCompleted event > -------------------------------------------------------------------- > > Key: RF-13242 > URL: https://issues.jboss.org/browse/RF-13242 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > The events / attributes / JS service invocations should be as follow: > * {{@onbeforedomupdate}} > * {{ajaxbeforedomupdate}} > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} > * *{{ajaxcomplete}}* > But they are: > * {{ajaxbeforedomupdate}} > * {{@onbeforedomupdate}} > * *{{ajaxcomplete}}* > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:04:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13242) ajaxcomplete event is called before javascriptServiceCompleted event In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13242. ---------------------------- closing, verified. > ajaxcomplete event is called before javascriptServiceCompleted event > -------------------------------------------------------------------- > > Key: RF-13242 > URL: https://issues.jboss.org/browse/RF-13242 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > The events / attributes / JS service invocations should be as follow: > * {{@onbeforedomupdate}} > * {{ajaxbeforedomupdate}} > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} > * *{{ajaxcomplete}}* > But they are: > * {{ajaxbeforedomupdate}} > * {{@onbeforedomupdate}} > * *{{ajaxcomplete}}* > * JavaScriptService invocation > * {{javascriptServiceComplete}} > * {{@oncomplete}} -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:12:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Dec 2013 09:12:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13421) Input number slider: attribute render on nested r:ajax doesn't work In-Reply-To: References: Message-ID: Pavol Pitonak created RF-13421: ---------------------------------- Summary: Input number slider: attribute render on nested r:ajax doesn't work Key: RF-13421 URL: https://issues.jboss.org/browse/RF-13421 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-input, regression Affects Versions: 5.0.0.Alpha2 Environment: RichFaces 5.0.0.Alpha2 Metamer 5.0.0.Alpha2 EAP 6.1.1, JBoss AS 7.1.1 Mojarra 2.1.19, 2.1.7 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21/24 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid # open developer tools in browser # change value on slider result: * output below slider is not updated reason: * output's span element has id form:containerRichDataGrid:3:output * response to Ajax requests contains different ID {code} form:containerRichDataGrid:0:output {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 From jira-events at lists.jboss.org Thu Dec 5 09:12:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Dec 2013 09:12:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13253) Move richwidgets resources from org.richfaces/widgets to richwidgets library In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13253. ------------------------------ Verified, resources were moved. Closing issue. > Move richwidgets resources from org.richfaces/widgets to richwidgets library > ---------------------------------------------------------------------------- > > Key: RF-13253 > URL: https://issues.jboss.org/browse/RF-13253 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > This is the idea which will clarify the relation and allow to use shorter resource paths. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:16:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:16:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets - not rendered In-Reply-To: References: Message-ID: Juraj H?ska created RF-13422: -------------------------------- Summary: Showcase - chart demos on tablets - not rendered Key: RF-13422 URL: https://issues.jboss.org/browse/RF-13422 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska The demo for charts is not rendered correctly on tablets. There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:18:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Attachment: chartWrongRendered.PNG > Showcase - chart demos on tablets - not rendered > ------------------------------------------------ > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:18:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:18:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Attachment: jsErrorsChart.PNG > Showcase - chart demos on tablets - not rendered > ------------------------------------------------ > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:20:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:20:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Steps to Reproduce: # load http://showcaselatest-richfaces.rhcloud.com/ in tablet device # find demo for charts # see the error messages being reported > Showcase - chart demos on tablets - not rendered > ------------------------------------------------ > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Steps to Reproduce: # load http://showcaselatest-richfaces.rhcloud.com/ in tablet/mobile device # find demo for charts # see the error messages being reported was: # load http://showcaselatest-richfaces.rhcloud.com/ in tablet device # find demo for charts # see the error messages being reported > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:24:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Summary: Showcase - chart demos on tablets/mobiles - not rendered (was: Showcase - chart demos on tablets - not rendered) > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:26:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Dec 2013 09:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13315. ------------------------------ Verified. The destroy method was later removed in [RF-13375|https://issues.jboss.org/browse/RF-13375]. Closing this issue. > bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method > ---------------------------------------------------------------------------------------------- > > Key: RF-13315 > URL: https://issues.jboss.org/browse/RF-13315 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {code} > $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) { > {code} > {code} > destroy : function() { > {code} > should be {{_destroy}}. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:32:05 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Dec 2013 09:32:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13423) Slider: value change listener doesn't work when component is inside collapsible sub table In-Reply-To: References: Message-ID: Pavol Pitonak created RF-13423: ---------------------------------- Summary: Slider: value change listener doesn't work when component is inside collapsible sub table Key: RF-13423 URL: https://issues.jboss.org/browse/RF-13423 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, regression Affects Versions: 5.0.0.Alpha2 Environment: RichFaces 5.0.0.Alpha2 Metamer 5.0.0.Alpha2 EAP 6.1.1, JBoss AS 7.1.1 Mojarra 2.1.19, 2.1.7 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richCollapsibleSubTable # change value on slider result: * value change listener is not called, there should be similar output in page's header among phases {code} * 1 value changed: 2 -> -2 {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 From jira-events at lists.jboss.org Thu Dec 5 09:45:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Dec 2013 09:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13421) Input number slider/spinner: attribute render on nested r:ajax doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13421: ------------------------------- Summary: Input number slider/spinner: attribute render on nested r:ajax doesn't work (was: Input number slider: attribute render on nested r:ajax doesn't work) > Input number slider/spinner: attribute render on nested r:ajax doesn't work > --------------------------------------------------------------------------- > > Key: RF-13421 > URL: https://issues.jboss.org/browse/RF-13421 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0.Alpha2 > Metamer 5.0.0.Alpha2 > EAP 6.1.1, JBoss AS 7.1.1 > Mojarra 2.1.19, 2.1.7 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21/24 > Reporter: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid > # open developer tools in browser > # change value on slider > result: > * output below slider is not updated > reason: > * output's span element has id form:containerRichDataGrid:3:output > * response to Ajax requests contains different ID > {code} > form:containerRichDataGrid:0:output > {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 From jira-events at lists.jboss.org Thu Dec 5 09:45:06 2013 From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Dec 2013 09:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13421) Input number slider/spinner: attribute render on nested r:ajax doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13421: ------------------------------- Description: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid # open developer tools in browser # change value on slider result: * output below slider is not updated * there is the same problem with spinner reason: * output's span element has id form:containerRichDataGrid:3:output * response to Ajax requests contains different ID {code} form:containerRichDataGrid:0:output {code} was: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid # open developer tools in browser # change value on slider result: * output below slider is not updated reason: * output's span element has id form:containerRichDataGrid:3:output * response to Ajax requests contains different ID {code} form:containerRichDataGrid:0:output {code} > Input number slider/spinner: attribute render on nested r:ajax doesn't work > --------------------------------------------------------------------------- > > Key: RF-13421 > URL: https://issues.jboss.org/browse/RF-13421 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0.Alpha2 > Metamer 5.0.0.Alpha2 > EAP 6.1.1, JBoss AS 7.1.1 > Mojarra 2.1.19, 2.1.7 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21/24 > Reporter: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid > # open developer tools in browser > # change value on slider > result: > * output below slider is not updated > * there is the same problem with spinner > reason: > * output's span element has id form:containerRichDataGrid:3:output > * response to Ajax requests contains different ID > {code} > form:containerRichDataGrid:0:output > {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 From jira-events at lists.jboss.org Thu Dec 5 09:57:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:57:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Steps to Reproduce: # clear the browser cache # load http://showcaselatest-richfaces.rhcloud.com/ in tablet/mobile device # find demo for charts # see the error messages being reported was: # load http://showcaselatest-richfaces.rhcloud.com/ in tablet/mobile device # find demo for charts # see the error messages being reported > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. -- 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 From jira-events at lists.jboss.org Thu Dec 5 09:57:08 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 09:57:08 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Description: The demo for charts is not rendered correctly on tablets. There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. RichWidgets demo on tablets works as expected. Note that subsequent refresh of the demo page load the charts correctly. Then it breaks after the browser cache clearing. was: The demo for charts is not rendered correctly on tablets. There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. RichWidgets demo on tablets works as expected. > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. > Note that subsequent refresh of the demo page load the charts correctly. Then it breaks after the browser cache clearing. -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:01:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 10:01:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13422: ----------------------------- Steps to Reproduce: # clear the browser cache # load http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=chart&skin=blueSky in tablet/mobile device # find demo for charts # see the error messages being reported was: # clear the browser cache # load http://showcaselatest-richfaces.rhcloud.com/ in tablet/mobile device # find demo for charts # see the error messages being reported > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. > Note that subsequent refresh of the demo page load the charts correctly. Then it breaks after the browser cache clearing. -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:01:06 2013 From: jira-events at lists.jboss.org (Immo Benjes (JIRA)) Date: Thu, 5 Dec 2013 10:01:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928943#comment-12928943 ] Immo Benjes commented on RF-13230: ---------------------------------- We store the table state in the database, so each time the user navigates to the page they get the table in the same state they left it in. If they e.g. moved Column B to the first position and set the ordering of e.g. Column B to descending then that is stored in the database and next time they come back Column B is still in the first position. However the ordering of the first page (you need a table with multiple pages and the datascroller) is the default (it should be descending). When you navigate to the second page of the table the ordering is suddenly correct, when you navigate back to the first page is is suddenly in descending order as well. Didn't I add some test code on the forum for this issue? https://community.jboss.org/thread/232647 > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:14:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Dec 2013 10:14:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13421) Input number slider/spinner: attribute render on nested r:ajax doesn't work in repeating panels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13421: ------------------------------- Summary: Input number slider/spinner: attribute render on nested r:ajax doesn't work in repeating panels (was: Input number slider/spinner: attribute render on nested r:ajax doesn't work) > Input number slider/spinner: attribute render on nested r:ajax doesn't work in repeating panels > ----------------------------------------------------------------------------------------------- > > Key: RF-13421 > URL: https://issues.jboss.org/browse/RF-13421 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0.Alpha2 > Metamer 5.0.0.Alpha2 > EAP 6.1.1, JBoss AS 7.1.1 > Mojarra 2.1.19, 2.1.7 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21/24 > Reporter: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid > # open developer tools in browser > # change value on slider > result: > * output below slider is not updated > * there is the same problem with spinner > reason: > * output's span element has id form:containerRichDataGrid:3:output > * response to Ajax requests contains different ID > {code} > form:containerRichDataGrid:0:output > {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 From jira-events at lists.jboss.org Thu Dec 5 10:20:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 10:20:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13424) Showcase - autocomplete demo resources are not loaded correctly In-Reply-To: References: Message-ID: Juraj H?ska created RF-13424: -------------------------------- Summary: Showcase - autocomplete demo resources are not loaded correctly Key: RF-13424 URL: https://issues.jboss.org/browse/RF-13424 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska Showcase Autocomplete demo resources are not loaded correctly when working with clear browser cache. It can be noticed as wrongly rendered suggestion list. (please see the screenshots) After subsequent load refresh the resources are loaded correctly. -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 10:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13424) Showcase - autocomplete demo resources are not loaded correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13424: ----------------------------- Attachment: autocompleteMobile.PNG > Showcase - autocomplete demo resources are not loaded correctly > --------------------------------------------------------------- > > Key: RF-13424 > URL: https://issues.jboss.org/browse/RF-13424 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: autocompleteMobile.PNG > > > Showcase Autocomplete demo resources are not loaded correctly when working with clear browser cache. > It can be noticed as wrongly rendered suggestion list. (please see the screenshots) > After subsequent load refresh the resources are loaded correctly. -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:24:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 10:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13424) Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13424: ----------------------------- Summary: Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets (was: Showcase - autocomplete demo resources are not loaded correctly) Steps to Reproduce: #clear the browser mobile cache #load page on mobile device: http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky #see the broken rendering of the autocomplete suggestion list when typed something in it > Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets > --------------------------------------------------------------------------------- > > Key: RF-13424 > URL: https://issues.jboss.org/browse/RF-13424 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: autocompleteMobile.PNG > > > Showcase Autocomplete demo resources are not loaded correctly when working with clear browser cache. > It can be noticed as wrongly rendered suggestion list. (please see the screenshots) > After subsequent load refresh the resources are loaded correctly. -- 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 From jira-events at lists.jboss.org Thu Dec 5 10:35:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 10:35:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13424) Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928956#comment-12928956 ] Juraj H?ska commented on RF-13424: ---------------------------------- It is the same for all new components. Please tell me if you can reproduce it. I will file one issue for all and close these as duplicated issues. IMHO it is caused by the same problem. > Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets > --------------------------------------------------------------------------------- > > Key: RF-13424 > URL: https://issues.jboss.org/browse/RF-13424 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Attachments: autocompleteMobile.PNG > > > Showcase Autocomplete demo resources are not loaded correctly when working with clear browser cache. > It can be noticed as wrongly rendered suggestion list. (please see the screenshots) > After subsequent load refresh the resources are loaded correctly. -- 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 From jira-events at lists.jboss.org Thu Dec 5 13:14:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 13:14:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13425) autocomplete - attribute token does not work with multiple tokens In-Reply-To: References: Message-ID: Juraj H?ska created RF-13425: -------------------------------- Summary: autocomplete - attribute token does not work with multiple tokens Key: RF-13425 URL: https://issues.jboss.org/browse/RF-13425 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Reporter: Juraj H?ska -- 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 From jira-events at lists.jboss.org Thu Dec 5 13:16:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 5 Dec 2013 13:16:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13425) autocomplete - attribute token does not work with multiple tokens In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13425: ----------------------------- Description: When setting token attribute of autocomplete to: , (comma and space), then only comma work. Setting token to space only, works as expected. I believe this issue is caused by the upstream issue: https://github.com/richwidgets/richwidgets/issues/158 Steps to Reproduce: # Issue can be quickly seen also in RichFaces showcase: http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=autocomplete&skin=blueSky # Try to type in the middle one autocomplete input, and try to separate the entered value with space. It does not work. Affects Version/s: 5.0.0.Alpha2 > autocomplete - attribute token does not work with multiple tokens > ----------------------------------------------------------------- > > Key: RF-13425 > URL: https://issues.jboss.org/browse/RF-13425 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > When setting token attribute of autocomplete to: , (comma and space), then only comma work. > Setting token to space only, works as expected. > I believe this issue is caused by the upstream issue: > https://github.com/richwidgets/richwidgets/issues/158 -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:13:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:13:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13400. -------------------------------- Resolution: Done Looking at the linked sample, the problem is the header and footer tables in the metamer pages. I recommend you make a responsive page template for metamer, and use that when testing mobile components with metamer. IOW we can't expect the component to behave responsively when placed on a page with fixed-width elements (eg. tables). > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:13:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:13:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13400: -------------------------------- > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:13:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:13:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13400. -------------------------------- Resolution: Rejected > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:17:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:17:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13418) After sorting on extendedDataTable the contextMenu is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13418: ------------------------------- Fix Version/s: 5-Tracking > After sorting on extendedDataTable the contextMenu is broken > ------------------------------------------------------------ > > Key: RF-13418 > URL: https://issues.jboss.org/browse/RF-13418 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu, component-selects > Affects Versions: 4.3.4 > Environment: Win7 IE9 / FF 25.0.1 > Reporter: Mike K > Fix For: 5-Tracking > > > After sorting on extendedDataTable the contextMenu is not shown anymore > Detailled description and code here: > https://community.jboss.org/message/803276#803276 > Maybe related to https://issues.jboss.org/browse/RF-11973 -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:17:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:17:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13419) FileUpload doesn't fire the listener when deployed with Myfaces tomahawk In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13419: ------------------------------- Fix Version/s: 5-Tracking > FileUpload doesn't fire the listener when deployed with Myfaces tomahawk > ------------------------------------------------------------------------ > > Key: RF-13419 > URL: https://issues.jboss.org/browse/RF-13419 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.3, 4.3.4 > Environment: Tomcat 7.0.47 > jdk1.6.0_45 > Windows 7 > Mojarra 2.1.26 > tomahawk 1.1.14 > Reporter: Gustavo Ehrhardt > Labels: myfaces, tomahawk, upload > Fix For: 5-Tracking > > Attachments: UploadFile.rar > > > FileUpload doesn't fire the listener when deployed with Myfaces tomahawk. > When I declare the MyFaces extension filter in web.xml the listener method is never called after the upload is completed. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:17:07 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:17:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13420: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > Fix For: 5.0.0.Alpha3 > > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:19:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:19:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13420) Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929081#comment-12929081 ] Brian Leathem commented on RF-13420: ------------------------------------ +1 [~jhuska] that mime-mapping looks like the correct one. > Showcase - WARNING No mime type could be found for file fontawesome-webfont.woff is logged > ------------------------------------------------------------------------------------------ > > Key: RF-13420 > URL: https://issues.jboss.org/browse/RF-13420 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha2 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Minor > Fix For: 5.0.0.Alpha3 > > > Following WARNING is being logged to JBoss AS console when demos for {{pickList}} or {{orderingList}} are loaded. > {code:none} > 12:10:08,859 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--0.0.0.0-8080-1) JSF1091: No mime type could be found for file font-awesome/font/fontawesome-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml. > {code} > Steps to reproduce: > # deploy showcase > # clean the browser cache > # load the demo for e.g. pickList: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=pickList&skin=blueSky > # look for the WARNING in the JBoss AS console > Notes: > * the http response with file font-awesome/font/fontawesome-webfont.woff finish with 200 OK. > * this WARNING is logged only with the first page load after the browser cache cleaning, then it is served from cache and WARNING is not logged -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:19:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:19:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13421) Input number slider/spinner: attribute render on nested r:ajax doesn't work in repeating panels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13421: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Input number slider/spinner: attribute render on nested r:ajax doesn't work in repeating panels > ----------------------------------------------------------------------------------------------- > > Key: RF-13421 > URL: https://issues.jboss.org/browse/RF-13421 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0.Alpha2 > Metamer 5.0.0.Alpha2 > EAP 6.1.1, JBoss AS 7.1.1 > Mojarra 2.1.19, 2.1.7 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21/24 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha3 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richDataGrid > # open developer tools in browser > # change value on slider > result: > * output below slider is not updated > * there is the same problem with spinner > reason: > * output's span element has id form:containerRichDataGrid:3:output > * response to Ajax requests contains different ID > {code} > form:containerRichDataGrid:0:output > {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 From jira-events at lists.jboss.org Fri Dec 6 02:19:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:19:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13422) Showcase - chart demos on tablets/mobiles - not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13422: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Showcase - chart demos on tablets/mobiles - not rendered > -------------------------------------------------------- > > Key: RF-13422 > URL: https://issues.jboss.org/browse/RF-13422 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > Attachments: chartWrongRendered.PNG, jsErrorsChart.PNG > > > The demo for charts is not rendered correctly on tablets. > There are JS errors, which can be found in the attachment. It seems like the chart size is counted in a wrong way, when the screen is smaller and it is trying to create line with 0 height. > RichWidgets demo on tablets works as expected. > Note that subsequent refresh of the demo page load the charts correctly. Then it breaks after the browser cache clearing. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:19:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:19:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13423) Slider: value change listener doesn't work when component is inside collapsible sub table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13423: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Slider: value change listener doesn't work when component is inside collapsible sub table > ----------------------------------------------------------------------------------------- > > Key: RF-13423 > URL: https://issues.jboss.org/browse/RF-13423 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0.Alpha2 > Metamer 5.0.0.Alpha2 > EAP 6.1.1, JBoss AS 7.1.1 > Mojarra 2.1.19, 2.1.7 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 31.0.1650.57 @ Linux x86_64, Firefox 17/21 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha3 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simple.xhtml?templates=richCollapsibleSubTable > # change value on slider > result: > * value change listener is not called, there should be similar output in page's header among phases > {code} > * 1 value changed: 2 -> -2 > {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 From jira-events at lists.jboss.org Fri Dec 6 02:21:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:21:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13424) Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13424: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Showcase - autocomplete demo resources are not loaded correctly on mobile/tablets > --------------------------------------------------------------------------------- > > Key: RF-13424 > URL: https://issues.jboss.org/browse/RF-13424 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: mobile, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > Attachments: autocompleteMobile.PNG > > > Showcase Autocomplete demo resources are not loaded correctly when working with clear browser cache. > It can be noticed as wrongly rendered suggestion list. (please see the screenshots) > After subsequent load refresh the resources are loaded correctly. -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:21:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 02:21:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13425) autocomplete - attribute token does not work with multiple tokens In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13425: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > autocomplete - attribute token does not work with multiple tokens > ----------------------------------------------------------------- > > Key: RF-13425 > URL: https://issues.jboss.org/browse/RF-13425 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > > When setting token attribute of autocomplete to: , (comma and space), then only comma work. > Setting token to space only, works as expected. > I believe this issue is caused by the upstream issue: > https://github.com/richwidgets/richwidgets/issues/158 -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:40:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 02:40:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13254) Images in online Component Reference are missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13254. ------------------------------ Verified, closing issue. > Images in online Component Reference are missing > ------------------------------------------------ > > Key: RF-13254 > URL: https://issues.jboss.org/browse/RF-13254 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Images in Component Reference are missing, see e.g. http://docs.jboss.org/richfaces/nightly_5_0_X/Component_Reference/en-US/html_single/#sect-Component_Reference-Panels-tabPanel -- 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 From jira-events at lists.jboss.org Fri Dec 6 02:53:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 02:53:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13255) Autocomplete - cachedAjax isn't implemented In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13255. ------------------------------ Verified in Metamer. Closing issue. > Autocomplete - cachedAjax isn't implemented > ------------------------------------------- > > Key: RF-13255 > URL: https://issues.jboss.org/browse/RF-13255 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From jira-events at lists.jboss.org Fri Dec 6 03:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 03:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13400. ---------------------------- Strange that it works on the desktop. I have created RFPL-3142 to provide a responsive template for Metamer. Closing this one. > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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 From jira-events at lists.jboss.org Fri Dec 6 03:39:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 03:39:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10618) autocomplete: unnesessary request on item selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-10618. ---------------------------- Verified that it does not apply for 5.Alpa2 > autocomplete: unnesessary request on item selection > --------------------------------------------------- > > Key: RF-10618 > URL: https://issues.jboss.org/browse/RF-10618 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Milestone6 > Reporter: Ilya Shaikovsky > Assignee: Pavol Pitonak > Priority: Minor > Labels: needs-qe > > {code} > > autoFill="false" selectFirst="false" id="ac2" > value="#{autocompleteBean.svalue}" var="a" > autocompleteList="#{autocompleteBean.autocompleteList}"> > > > > {code} > # focus input > # type a - Ajax request sent and list populated - OK > # select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request. > This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters. -- 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 From jira-events at lists.jboss.org Fri Dec 6 03:39:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 03:39:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10618) autocomplete: unnesessary request on item selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-10618: ----------------------------- Fix Version/s: (was: 5.0.0.Alpha2) > autocomplete: unnesessary request on item selection > --------------------------------------------------- > > Key: RF-10618 > URL: https://issues.jboss.org/browse/RF-10618 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Milestone6 > Reporter: Ilya Shaikovsky > Assignee: Pavol Pitonak > Priority: Minor > Labels: needs-qe > > {code} > > autoFill="false" selectFirst="false" id="ac2" > value="#{autocompleteBean.svalue}" var="a" > autocompleteList="#{autocompleteBean.autocompleteList}"> > > > > {code} > # focus input > # type a - Ajax request sent and list populated - OK > # select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request. > This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters. -- 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 From jira-events at lists.jboss.org Fri Dec 6 03:47:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 03:47:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11103) org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-11103. ---------------------------- Verified. Closing. > org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-11103 > URL: https://issues.jboss.org/browse/RF-11103 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Reporter: u j > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I tried > {code} > > org.richfaces.skin > plain > > {code} > > and the skinning seems to be disabled, but I get > {code} > 14:44:21,584 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > 14:45:38,493 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (1) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] > {code} > I found a note > http://echelog.matzon.dk/logs/browse/richfaces/1306706400 > 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 From jira-events at lists.jboss.org Fri Dec 6 03:54:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 03:54:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13260) Autocomplete - remove onlist* event handlers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13260. ------------------------------ Verified, closing issue. > Autocomplete - remove onlist* event handlers > -------------------------------------------- > > Key: RF-13260 > URL: https://issues.jboss.org/browse/RF-13260 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > I believe those onlist* mouse and keyboard handlers are not necessary with exposing rich jQuery UI Autocomplete event API: > http://api.jqueryui.com/autocomplete/ > In 4.3, those events could be used for intercepting process of menu manipulation, but the new events are so rich that the list handlers are not necessary. > One can potentially use such a code to register event handler: > {code} > #{r:jquery('autocomplete')}.autocomplete('menu').on('click', ); > {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 From jira-events at lists.jboss.org Fri Dec 6 04:08:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:08:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13261) Autocomplete: introduce onfocus, onselect, onopen, onclose, onsearch, onresponse event handlers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13261. ------------------------------ Verified, closing issue. > Autocomplete: introduce onfocus, onselect, onopen, onclose, onsearch, onresponse event handlers > ----------------------------------------------------------------------------------------------- > > Key: RF-13261 > URL: https://issues.jboss.org/browse/RF-13261 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > Those event handlers are exposed by jQuery UI Autocomplete: > http://api.jqueryui.com/autocomplete/ -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:32:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 04:32:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-11543) Refactor ResourceMappingFeature to Service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-11543. ---------------------------- Verified. Closing. > Refactor ResourceMappingFeature to Service > ------------------------------------------ > > Key: RF-11543 > URL: https://issues.jboss.org/browse/RF-11543 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Milestone3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > ResourceMappingFeature class currently provides utilities for determining current configuration of resource mapping (enablement, location, mappingFile). > Since referenced context-param configurations can be only literals, it does make sense to cache configuration, then it needs to be refactored from static to Service and use configuration holder. -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:34:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:34:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13262) autocomplete: @autofill=true doesn't work when @token is setup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny reopened RF-13262: -------------------------------- Reopening this issue because it is related to [RF-13415|https://issues.jboss.org/browse/RF-13415] (link added to issue link desc.). The autofill attribute does not work on its own so it cannot be verified whether it works with @token or not. > autocomplete: @autofill=true doesn't work when @token is setup > -------------------------------------------------------------- > > Key: RF-13262 > URL: https://issues.jboss.org/browse/RF-13262 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha1 > Environment: EAP 6.1 > FF 21, Chrome 30 > Reporter: Ji?? ?tefek > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > Neither moving to an item by mouse nor by keys fills the value to the input. -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:50:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:50:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13267) Remove the RichWidgets github submodule and instead copy/paste the widget resources into RichFaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13267. ------------------------------ Verified, closing issue. > Remove the RichWidgets github submodule and instead copy/paste the widget resources into RichFaces > -------------------------------------------------------------------------------------------------- > > Key: RF-13267 > URL: https://issues.jboss.org/browse/RF-13267 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Remove the RichWidgets github submodule and instead copy/paste the wodget resources into RichFaces. -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:52:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13268) Typo in LookAheadObjectInputStream.java In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13268. ------------------------------ Verified, closing issue. > Typo in LookAheadObjectInputStream.java > --------------------------------------- > > Key: RF-13268 > URL: https://issues.jboss.org/browse/RF-13268 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.4 > Environment: Any > Reporter: Fab Mars > Assignee: Fab Mars > Priority: Trivial > Labels: core > Fix For: 4.3.5, 5.0.0.Alpha2 > > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > On the loadWhitelist method, stream.close() catch, the message should be "Error closing the resource-serialization.properties file". Git pull request attached. -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:54:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13283) Move the chart components from the sandbox into the framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13283. ------------------------------ Verified, closing issue. > Move the chart components from the sandbox into the framework > ------------------------------------------------------------- > > Key: RF-13283 > URL: https://issues.jboss.org/browse/RF-13283 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 From jira-events at lists.jboss.org Fri Dec 6 04:58:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 04:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13269) Autocomplete: remove styling classes other than @styleClass In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13269. ------------------------------ Verified, closing issue. > Autocomplete: remove styling classes other than @styleClass > ----------------------------------------------------------- > > Key: RF-13269 > URL: https://issues.jboss.org/browse/RF-13269 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > > We can always use CSS/LESS to style other parts of component. -- 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 From jira-events at lists.jboss.org Fri Dec 6 05:01:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 05:01:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13270) Split event handlers from AjaxProps to AjaxEventsProps to allow its reusing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13270. ------------------------------ Verified, closing issue. > Split event handlers from AjaxProps to AjaxEventsProps to allow its reusing > --------------------------------------------------------------------------- > > Key: RF-13270 > URL: https://issues.jboss.org/browse/RF-13270 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > E.g. Autocomplete defines those methods and could leverage common 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 From jira-events at lists.jboss.org Fri Dec 6 05:18:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 05:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13273) Font-awesome fonts not included in resource optimisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13273. ------------------------------ Verified, no 404 errors in the console with resource optimization. Disabling optimization causes no problems either. Closing issue. > Font-awesome fonts not included in resource optimisation > -------------------------------------------------------- > > Key: RF-13273 > URL: https://issues.jboss.org/browse/RF-13273 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The showcase sample for the pickList and orderingList logs the following error in the browser console: > {code} > GET http://localhost:8080/org.richfaces.resources/javax.faces.resource/org.rich?timized/5.0.0-SNAPSHOT/Packed/packed/font/fontawesome-webfont.woff?v=3.2.1 404 (Not Found) component-sample.jsf?demo=pickList&skin=blueSky:1 > GET http://localhost:8080/org.richfaces.resources/javax.faces.resource/org.rich?ptimized/5.0.0-SNAPSHOT/Packed/packed/font/fontawesome-webfont.ttf?v=3.2.1 404 (Not Found) :8080/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/Packed/packed/font/fontawesome-webfont.ttf?v=3.2.1:1 > GET http://localhost:8080/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/5.0.0-SNAPSHOT/Packed/packed/font/fontawesome-webfont.svg 404 (Not Found) :8080/org.richfaces.resources/javax.faces.resource/org.richfaces.optimized/?OT/Packed/packed/font/fontawesome-webfont.svg#fontawesomeregular?v=3.2.1:1 > {code} > After disabling the resource optimisation in the web.xml as follows: > {code} > > org.richfaces.resourceOptimization.enabled > false > > {code} > The showcase samples load fine. -- 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 From jira-events at lists.jboss.org Fri Dec 6 06:10:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Fri, 6 Dec 2013 06:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13276) Optimized resources should be generated into generated-resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929136#comment-12929136 ] Matej Novotny commented on RF-13276: ------------------------------------ I am unable to verify this issue because I am not sure what was the problem and how does this solution work. I am not sure about the expected output either but I presume the goal is to have the _optimizied-resources_ in _target/generated-resources_, however so far it is places in _generated-*sources*_ (see [this link|https://github.com/richfaces/richfaces/blob/master/framework/pom.xml#L45] ) [~bleathem] do you think you could give me a bit more in depth explanation so I could verify this? > Optimized resources should be generated into generated-resources > ---------------------------------------------------------------- > > Key: RF-13276 > URL: https://issues.jboss.org/browse/RF-13276 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_. -- 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 From jira-events at lists.jboss.org Fri Dec 6 06:56:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 06:56:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13276) Optimized resources should be generated into generated-resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929148#comment-12929148 ] Brian Leathem commented on RF-13276: ------------------------------------ Write, your observations indicate that this is indeed working as expected. You can close the issue. > Optimized resources should be generated into generated-resources > ---------------------------------------------------------------- > > Key: RF-13276 > URL: https://issues.jboss.org/browse/RF-13276 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_. -- 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 From jira-events at lists.jboss.org Fri Dec 6 06:56:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 06:56:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13276) Optimized resources should be generated into generated-resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929148#comment-12929148 ] Brian Leathem edited comment on RF-13276 at 12/6/13 6:55 AM: ------------------------------------------------------------- Right, your observations indicate that this is indeed working as expected. You can close the issue. was (Author: bleathem): Write, your observations indicate that this is indeed working as expected. You can close the issue. > Optimized resources should be generated into generated-resources > ---------------------------------------------------------------- > > Key: RF-13276 > URL: https://issues.jboss.org/browse/RF-13276 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_. -- 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 From jira-events at lists.jboss.org Fri Dec 6 07:48:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 07:48:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13426) Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 In-Reply-To: References: Message-ID: Juraj H?ska created RF-13426: -------------------------------- Summary: Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 Key: RF-13426 URL: https://issues.jboss.org/browse/RF-13426 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.5.0.Alpha1 Reporter: Juraj H?ska Priority: Minor In showcase footer page section, there is _RichFaces Framework by JBoss by Red Hat, version 5.0.0.Alpha2_. It should be with 4.5.0.Alpha1. The version is so because it is retrieved from {{VersionBean}}, which is from the 5.0.0.Alpha2 framework. IMHO it can cause some misunderstanding, or do we want to stress that the core is from RF 5 ? -- 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 From jira-events at lists.jboss.org Fri Dec 6 08:45:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 08:45:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12214) Pack plain skin with UI components distribution (the resource plugin needs to be fixed) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12214. ---------------------------- Verified with both 4.5.0.Alpha1 and 5.0.0.Alpha2. I verified it on showcase with plain skin and resource optimization enabled. Closing. > Pack plain skin with UI components distribution (the resource plugin needs to be fixed) > --------------------------------------------------------------------------------------- > > Key: RF-12214 > URL: https://issues.jboss.org/browse/RF-12214 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.2.1.Final > Reporter: Nicolas Daniels > Assignee: Luk?? Fry? > Priority: Minor > Labels: needs-qe > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The plain skin is not packed/compresses as other styles, mainly because images generation is failing due to null property values. > It could be good to have it as well. Beside it, probably that image generation with null value should be handled. > Of course, any failed image generation should not be referenced in resulting css. > (Fyi, currently, generating plain skin is working despite the warnings but missing images are still referenced in resulting css. This is not really good for resources optimization ;-)) -- 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 From jira-events at lists.jboss.org Fri Dec 6 08:56:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 08:56:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12292) "this" in oncomplete of a4j:commandButton returns window object. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12292. ---------------------------- Verified. Closing. > "this" in oncomplete of a4j:commandButton returns window object. > ---------------------------------------------------------------- > > Key: RF-12292 > URL: https://issues.jboss.org/browse/RF-12292 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final > Environment: Windows XP SP3, Weblogic 10.3.5, JSF 2.0.4, RF 4.2.2 Final > Reporter: Nikolai Alexeev > Assignee: Luk?? Fry? > Priority: Minor > Labels: a4j_commandbutton > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using "this" operator in oncomplete attribute of a4j:commandButton user gets window object instead of expected button object. In RF3 everything was as expected. -- 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 From jira-events at lists.jboss.org Fri Dec 6 08:58:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 08:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12487) Change namespace http://richfaces.org/core to http://richfaces.org/rich once refactoring ends In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12487. ---------------------------- Verified. Closing. > Change namespace http://richfaces.org/core to http://richfaces.org/rich once refactoring ends > --------------------------------------------------------------------------------------------- > > Key: RF-12487 > URL: https://issues.jboss.org/browse/RF-12487 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Blocker > Labels: rf5-build > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The namespace must be identical with current {{rich:}} one to allow fluent migration to M2. -- 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 From jira-events at lists.jboss.org Fri Dec 6 09:00:08 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 09:00:08 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12784) Showcase readme - update deployment from eclipse part In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12784. ---------------------------- Verified also with 5.0.0.Alpha2 > Showcase readme - update deployment from eclipse part > ----------------------------------------------------- > > Key: RF-12784 > URL: https://issues.jboss.org/browse/RF-12784 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final, 5-Tracking > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Fix For: 4.3.4, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial: > An user needs to be aware of: > * select correct maven profile > * alter the deployment assembly > * be aware of wrong context root load in the eclipse browser > I will send pull request for this one. -- 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 From jira-events at lists.jboss.org Fri Dec 6 09:19:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 09:19:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12802. ---------------------------- Verified. Closing. > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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 From jira-events at lists.jboss.org Fri Dec 6 09:50:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 09:50:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12811) VDL Documentation: rich:calendar is missing attribute "maxlength" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12811. ---------------------------- Verified. Closing. > VDL Documentation: rich:calendar is missing attribute "maxlength" > ----------------------------------------------------------------- > > Key: RF-12811 > URL: https://issues.jboss.org/browse/RF-12811 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Reporter: Mijo Repusic > Priority: Trivial > Labels: documentation > Fix For: 4.3.5, 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The documentation for the element rich:calendar is missing the attribute maxlength. > IDEs who honor the documentation (example Netbeans 7.3) are marking the element as incorrect. -- 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 From jira-events at lists.jboss.org Fri Dec 6 09:52:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 09:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12822) Create fun tests for JSF AJAX submission and JavaScriptService callbacks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12822. ---------------------------- Verified. Closing. > Create fun tests for JSF AJAX submission and JavaScriptService callbacks > ------------------------------------------------------------------------ > > Key: RF-12822 > URL: https://issues.jboss.org/browse/RF-12822 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.0.Final > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:01:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:01:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12936) Use jQuery in non-conflicting way In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12936. ---------------------------- Verified. Closing. > Use jQuery in non-conflicting way > --------------------------------- > > Key: RF-12936 > URL: https://issues.jboss.org/browse/RF-12936 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. > However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. > I suggest to use following trick: > {code:title=richfaces.js} > window.RichFaces = window.RichFaces || {}; > RichFaces.jQuery = RichFaces.jQuery || window.jQuery; > //encapsulation > (function($, rf) { > // free to use $ here > }(RichFaces.jQuery, RichFaces)); > {code} > It will allow: > * provide own jQuery for RichFaces (using _jQuery.noConflict()_) > * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:03:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:03:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12952) Favor Props interfaces over attrs.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-12952. ---------------------------- Closing. > Favor Props interfaces over attrs.xml > ------------------------------------- > > Key: RF-12952 > URL: https://issues.jboss.org/browse/RF-12952 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We should favor {{*Props}} interfaces since they are refactorable. -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:30:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13019) Placeholder disappears after form reset In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13019. ---------------------------- Verified [here|https://github.com/jhuska/richfaces-sanbox/tree/RF-13019]. Closing. > Placeholder disappears after form reset > --------------------------------------- > > Key: RF-13019 > URL: https://issues.jboss.org/browse/RF-13019 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.2 > Reporter: Atanu Mukherjee > Assignee: Michal Petrov > Fix For: 5.0.0.Alpha2 > > > I have the following code inside a form - > {code} > > > > > {code} > The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out. -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:46:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:46:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13053) Showcase: push doesn't work on EAP 6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13053. ---------------------------- Verified also for 5.0.0.Alpha2. Closing. > Showcase: push doesn't work on EAP 6.1 > -------------------------------------- > > Key: RF-13053 > URL: https://issues.jboss.org/browse/RF-13053 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Fix For: 4.3.4, 5.0.0.Alpha2 > > > EAP 6.1 has more strict conditions for user passwords so we need to update JMS password in both web.xml and readme.md. It has to contain one number and one special character. -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:52:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13063) RichFacesInputNumberSlider setValueByDragging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929226#comment-12929226 ] Juraj H?ska commented on RF-13063: ---------------------------------- Verified also in 5.0.0.Alpha2. Just a note: in 5.Alpha2 you can access the method as: {{mySlider.advanced().dragHandleToPointInTrace(55)}}, or just use {{mySlider.slideToValue(double)}}. Closing. > RichFacesInputNumberSlider setValueByDragging > --------------------------------------------- > > Key: RF-13063 > URL: https://issues.jboss.org/browse/RF-13063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: qe > Affects Versions: 4.3.2 > Reporter: Bernard Labno > Assignee: Ji?? ?tefek > Priority: Minor > Fix For: 4.3.4, 5.0.0.Alpha2 > > > In richfaces-qa/page-fragments there is RichFacesInputNumberSlider fragment. It would be great to be able to test setting value as percentage of width implemented as dragging the handle. > One can do it like that: > {code} > ((JavascriptExecutor) GrapheneContext.getProxy()).executeScript("arguments[0].scrollIntoView(true);", weightSlider.getNumberSlider().getRoot()); > waitGui(); > final int width = weightSlider.getNumberSlider().getWidth(); > final int where = (int) (width * percentage); > final WebElement handle = weightSlider.getNumberSlider().getHandleElement(); > final Action action = new Actions(GrapheneContext.getProxy()).clickAndHold(handle) > .moveToElement(weightSlider.getNumberSlider().getRoot(), where, 0) > .release(handle) > .build(); > {code} > It is very important to bring component into view before dragging. > If you do not do that and component is very far to the right (you need to scroll to the right to see it) then calculations are wrong. -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:52:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:52:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13063) RichFacesInputNumberSlider setValueByDragging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13063. ---------------------------- > RichFacesInputNumberSlider setValueByDragging > --------------------------------------------- > > Key: RF-13063 > URL: https://issues.jboss.org/browse/RF-13063 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: qe > Affects Versions: 4.3.2 > Reporter: Bernard Labno > Assignee: Ji?? ?tefek > Priority: Minor > Fix For: 4.3.4, 5.0.0.Alpha2 > > > In richfaces-qa/page-fragments there is RichFacesInputNumberSlider fragment. It would be great to be able to test setting value as percentage of width implemented as dragging the handle. > One can do it like that: > {code} > ((JavascriptExecutor) GrapheneContext.getProxy()).executeScript("arguments[0].scrollIntoView(true);", weightSlider.getNumberSlider().getRoot()); > waitGui(); > final int width = weightSlider.getNumberSlider().getWidth(); > final int where = (int) (width * percentage); > final WebElement handle = weightSlider.getNumberSlider().getHandleElement(); > final Action action = new Actions(GrapheneContext.getProxy()).clickAndHold(handle) > .moveToElement(weightSlider.getNumberSlider().getRoot(), where, 0) > .release(handle) > .build(); > {code} > It is very important to bring component into view before dragging. > If you do not do that and component is very far to the right (you need to scroll to the right to see it) then calculations are wrong. -- 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 From jira-events at lists.jboss.org Fri Dec 6 10:54:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 10:54:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13072) Upgrade to Warp Alpha3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13072. ---------------------------- In the meantime upgraded to Alpha5. Verified. Closing. > Upgrade to Warp Alpha3 > ---------------------- > > Key: RF-13072 > URL: https://issues.jboss.org/browse/RF-13072 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:06:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:06:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13074) BehaviorsTagHandlerDelegateFactoryImpl causes NullPointerException on WildFly Alpha1 (JSF 2.2) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13074. ---------------------------- Verified with WildFly Beta1. Closing. > BehaviorsTagHandlerDelegateFactoryImpl causes NullPointerException on WildFly Alpha1 (JSF 2.2) > ---------------------------------------------------------------------------------------------- > > Key: RF-13074 > URL: https://issues.jboss.org/browse/RF-13074 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:10:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:10:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13075) Use RichFaces Widgets repository as submodule for Framework repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13075. ---------------------------- Verified. Closing. In the meantime it was decided to not have widgets as submodule. > Use RichFaces Widgets repository as submodule for Framework repository > ---------------------------------------------------------------------- > > Key: RF-13075 > URL: https://issues.jboss.org/browse/RF-13075 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:16:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:16:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13077. ---------------------------- Verified. Closing. > Allow programatically configure Resource Mapping by exposing a service interface > -------------------------------------------------------------------------------- > > Key: RF-13077 > URL: https://issues.jboss.org/browse/RF-13077 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.). > {code:java} > public interface ResourceMapper { > /** > * @return null when no mapping should be involved > public ResourceMapping mapResource(ResourceKey key); > } > public interface ResourceMapping { > URL getURL(FacesContext context); > } > public interface StaticURLResourceMapping implements ResourceMapping { > URL getURL(); > } > public class FacesResourceMapping implements ResourceMapping { > public ResourceKey getResourceKey() { > ... > } > } > {code} > This way people may decide e.g. move all resources from given resource library to another library. > This is related to RF-11543. -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:20:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:20:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13078) Map all 'org.richfaces' resources (and other RF resources) to ResourceServlet In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13078. ---------------------------- Verified. Closing. > Map all 'org.richfaces' resources (and other RF resources) to ResourceServlet > ----------------------------------------------------------------------------- > > Key: RF-13078 > URL: https://issues.jboss.org/browse/RF-13078 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Some resources heavily uses relative resource links, e.g. font-awesome references fonts. > We could provide static-resource-mapping.properties file > We could leverage a mapping service proposed in RF-13077. -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13082. ---------------------------- Verified. Closing. > Change the orderingList component to use the new orderingList widget > -------------------------------------------------------------------- > > Key: RF-13082 > URL: https://issues.jboss.org/browse/RF-13082 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Attributes to be dropped in the RF5 implementation: > * disabledClass > * headerClass > * itemClass > * selectItemClass > * listWidth > * onlist* > It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_). > Similarly the width CSS attributes are better set with CSS styles, rather than via facelet attributes. > We will drop the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover? -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13083) Change the pickList component to use the new pickList widget In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13083. ---------------------------- Verified. Closing. > Change the pickList component to use the new pickList widget > ------------------------------------------------------------ > > Key: RF-13083 > URL: https://issues.jboss.org/browse/RF-13083 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 From jira-events at lists.jboss.org Fri Dec 6 11:28:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Dec 2013 11:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13084) Change the autocomplete component to use the new autocomplete widget In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13084. ---------------------------- Verified. Closing. > Change the autocomplete component to use the new autocomplete widget > -------------------------------------------------------------------- > > Key: RF-13084 > URL: https://issues.jboss.org/browse/RF-13084 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 From jira-events at lists.jboss.org Fri Dec 6 16:58:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 16:58:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13262) autocomplete: @autofill=true doesn't work when @token is setup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13262: ------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > autocomplete: @autofill=true doesn't work when @token is setup > -------------------------------------------------------------- > > Key: RF-13262 > URL: https://issues.jboss.org/browse/RF-13262 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha1 > Environment: EAP 6.1 > FF 21, Chrome 30 > Reporter: Ji?? ?tefek > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > > Neither moving to an item by mouse nor by keys fills the value to the input. -- 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 From jira-events at lists.jboss.org Fri Dec 6 17:02:05 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Dec 2013 17:02:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13426) Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13426: ------------------------------- Fix Version/s: 4.5.0.Alpha2 > Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 > ---------------------------------------------------------------------------- > > Key: RF-13426 > URL: https://issues.jboss.org/browse/RF-13426 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5.0.Alpha2 > > > In showcase footer page section, there is _RichFaces Framework by JBoss by Red Hat, version 5.0.0.Alpha2_. > It should be with 4.5.0.Alpha1. > The version is so because it is retrieved from {{VersionBean}}, which is from the 5.0.0.Alpha2 framework. > IMHO it can cause some misunderstanding, or do we want to stress that the core is from RF 5 ? -- 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 From jira-events at lists.jboss.org Mon Dec 9 02:10:06 2013 From: jira-events at lists.jboss.org (Andreas Hahne (JIRA)) Date: Mon, 9 Dec 2013 02:10:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13392) TreeSelectionChangeEvent always triggered during Apply Request Phase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Hahne updated RF-13392: ------------------------------- Workaround Description: In this situation, setting the attribute {{execute}} for {{rich:tree}} to {{@this}} and specifing the {{rich:panel}}'s ID in the {{render}} attribute solved the problem. > TreeSelectionChangeEvent always triggered during Apply Request Phase > -------------------------------------------------------------------- > > Key: RF-13392 > URL: https://issues.jboss.org/browse/RF-13392 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.3.3 > Reporter: Andreas Hahne > Labels: richfaces, selectionChangeListener, tree > Fix For: 5-Tracking > > Attachments: tree.zip > > > When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false. > This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely. -- 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 From jira-events at lists.jboss.org Mon Dec 9 04:54:05 2013 From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA)) Date: Mon, 9 Dec 2013 04:54:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller In-Reply-To: References: Message-ID: Anton Bogoslavskyi created RF-13427: --------------------------------------- Summary: ED, Datatable: table needs to define the number of rows itself when using dataScroller Key: RF-13427 URL: https://issues.jboss.org/browse/RF-13427 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.3.3 Reporter: Anton Bogoslavskyi Attachments: data-3.png, datatable-1.png I need using pagination for extendedDataTable control. My row's height depends on the data it contains. I need the table to be constant height, so I specify the height in css. I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. Both situations are not user friendly. Actually on each page I need the maximum rows number to fit the height. -- 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 From jira-events at lists.jboss.org Mon Dec 9 04:54:05 2013 From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA)) Date: Mon, 9 Dec 2013 04:54:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Bogoslavskyi updated RF-13427: ------------------------------------ Attachment: datatable-1.png data-3.png > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:22:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929553#comment-12929553 ] Luk?? Fry? commented on RF-13062: --------------------------------- [~jhuska] the provided sample works fine on WildFly 8.0.0.Beta2-SNAPSHOT (you can obtain binary e.g. here: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20WildFly-cb/ ), so I guess it will be fixed in 8.0.0.CR1. (Please check once 8.0.0.CR1 is available) Additionally, I have reviewed the framework tests and all tests related to validation successfully pass. > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:22:07 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:22:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13062. ----------------------------- Resolution: Cannot Reproduce Bug > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:24:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:24:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929555#comment-12929555 ] Luk?? Fry? commented on RF-13062: --------------------------------- Note: there was a fix into [sample provided by jhuska|https://github.com/jhuska/richfaces-sanbox/tree/RF-13062] necessary: the ValidationBean needs to be moved under src/main/java. > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:28:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:28:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13062) r:validator stops working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929555#comment-12929555 ] Luk?? Fry? edited comment on RF-13062 at 12/9/13 10:26 AM: ----------------------------------------------------------- Note: there was a fix into [sample provided by jhuska|https://github.com/jhuska/richfaces-sanbox/tree/RF-13062] necessary: the ValidationBean needs to be moved under src/main/java - fixed in [this pull request|https://github.com/jhuska/richfaces-sanbox/pull/2]. was (Author: lfryc): Note: there was a fix into [sample provided by jhuska|https://github.com/jhuska/richfaces-sanbox/tree/RF-13062] necessary: the ValidationBean needs to be moved under src/main/java. > r:validator stops working > ------------------------- > > Key: RF-13062 > URL: https://issues.jboss.org/browse/RF-13062 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 5.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:34:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:34:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13317: ---------------------------- Fix Version/s: 5.0.0.Alpha3 > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:36:09 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:36:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13317: ---------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 (was: RichFaces 4.3.5 Sprint 1) > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Pavel Slegr > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:36:09 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:36:09 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13317: ------------------------------- Assignee: Luk?? Fry? (was: Pavel Slegr) > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:38:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:38:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929560#comment-12929560 ] Luk?? Fry? commented on RF-13197: --------------------------------- https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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 From jira-events at lists.jboss.org Mon Dec 9 10:40:06 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 9 Dec 2013 10:40:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13317: ---------------------------- Description: I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: When the response comes back, the data is fine but I get a JSF error saying bq. During update: javax.faces.ViewState not found Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: {quote} Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. {quote} was: I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: When the response comes back, the data is fine but I get a JSF error saying bq. During update: javax.faces.ViewState not found Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says: {quote} Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. {quote} > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From jira-events at lists.jboss.org Mon Dec 9 13:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Dec 2013 13:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929593#comment-12929593 ] Brian Leathem commented on RF-13427: ------------------------------------ Given that the server does not know the cell-height content at the time the response is rendered, there is no way to tailor the number of rows rendered to the content height. I suggest you rethink your layout constraint for a fixed hight table. Can you propose a solution (conceptually) for the problem you are describing? > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- 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 From jira-events at lists.jboss.org Mon Dec 9 13:04:06 2013 From: jira-events at lists.jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Dec 2013 13:04:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13427: ------------------------------- Labels: waiting_on_user (was: ) > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Labels: waiting_on_user > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- 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 From jira-events at lists.jboss.org Tue Dec 10 02:22:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 02:22:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13276) Optimized resources should be generated into generated-resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13276. ------------------------------ Verified, closing issue. > Optimized resources should be generated into generated-resources > ---------------------------------------------------------------- > > Key: RF-13276 > URL: https://issues.jboss.org/browse/RF-13276 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_. -- 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 From jira-events at lists.jboss.org Tue Dec 10 02:37:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 02:37:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13281) orderingList: ordering button's text overflows the button on Firefox In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13281. ------------------------------ Verified, works correctly on FF now. Closing issue. > orderingList: ordering button's text overflows the button on Firefox > -------------------------------------------------------------------- > > Key: RF-13281 > URL: https://issues.jboss.org/browse/RF-13281 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Environment: RichFaces 5.0.0-SNAPSHOT > Firefox 24 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Attachments: OL.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The ordering button's text overflows the button. > Works in Chrome. -- 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 From jira-events at lists.jboss.org Tue Dec 10 02:47:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 02:47:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13282. ------------------------------ Verified, closing issue. > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From jira-events at lists.jboss.org Tue Dec 10 02:54:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 02:54:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13285) The new autocomplete component's CSS does not play nicely with the RichFaces showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13285. ------------------------------ Verified, closing issue. > The new autocomplete component's CSS does not play nicely with the RichFaces showcase > ------------------------------------------------------------------------------------- > > Key: RF-13285 > URL: https://issues.jboss.org/browse/RF-13285 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > There are some sizing and visibility issues that need to be addressed, likely by changing the showcase applications's custom CSS (this was done for the picklist component for example). -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:03:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:03:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13286) Remove the deprecated attributes from the AbstractOrderingComponent parent class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13286. ------------------------------ Verified, closing issue. > Remove the deprecated attributes from the AbstractOrderingComponent parent class > -------------------------------------------------------------------------------- > > Key: RF-13286 > URL: https://issues.jboss.org/browse/RF-13286 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The _AbstractOrderingComponent_ parent class defines attributes common to the orderingList and pickList components. This issue addresses the removal of the attributes as defined by the issues RF-13082 and RF-13083. > While removing these attributes, investigate if the _AbstractOrderingComponent_ class could be better represented as a *Props 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 From jira-events at lists.jboss.org Tue Dec 10 03:15:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:15:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13291) Optimized resource ordering is missing resources after recent changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13291. ------------------------------ Verified, closing issue. > Optimized resource ordering is missing resources after recent changes > --------------------------------------------------------------------- > > Key: RF-13291 > URL: https://issues.jboss.org/browse/RF-13291 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > With the application of commit [0855b6|https://github.com/richfaces/richfaces/commit/0855b61d55533ad9c1b31555f222608911806cb0] resource optimisation is incorrectly omitting some resources. For instance the resource base-component.js is not packaged in packed.js. > This is may be related to the use of resource libraries (_reslibs_) such as base-component.library.properties that interfere with the Resource Optimisation inspection of resource dependencies. -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:18:05 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:18:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13295) Autocomplete: css file missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13295. ------------------------------ Verified, closing issue. > Autocomplete: css file missing > ------------------------------ > > Key: RF-13295 > URL: https://issues.jboss.org/browse/RF-13295 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > result: > * autocomplete's CSS file is missing which causes the component not to render correctly > * this is present in head section of page source > {code:xml} > > {code} > * this error is present in browser console > {quote} > GET http://localhost:8080/metamer/faces/components/richAutocomplete/RES_NOT_FOUND 404 (Not Found) > {quote} -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:26:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:26:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13296) Autocomplete - clientFilterFunction doesn't work in showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13296. ------------------------------ Verified, closing issue. > Autocomplete - clientFilterFunction doesn't work in showcase > ------------------------------------------------------------ > > Key: RF-13296 > URL: https://issues.jboss.org/browse/RF-13296 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > The demo does not work at all, I guess the clientFilterfunction functionality is broken. -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:30:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:30:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13297) Autocomplete - demo with cachedAjax does not update options after first request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13297. ------------------------------ Verified, closing issue. > Autocomplete - demo with cachedAjax does not update options after first request > ------------------------------------------------------------------------------- > > Key: RF-13297 > URL: https://issues.jboss.org/browse/RF-13297 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > Once the suggestion list is opened for first search request, it's not updated anymore. It's related to caching functionality. -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:36:07 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:36:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added license headers to all sources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13299. ------------------------------ Verified, closing issue. > Page Fragments: added license headers to all sources > ---------------------------------------------------- > > Key: RF-13299 > URL: https://issues.jboss.org/browse/RF-13299 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Issue mentioned during impl review: > https://github.com/richfaces/richfaces/pull/55 -- 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 From jira-events at lists.jboss.org Tue Dec 10 03:53:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 03:53:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid of typetools dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13337. ------------------------------ Verified, closing issue. > Page fragments: get rid of typetools dependency > ----------------------------------------------- > > Key: RF-13337 > URL: https://issues.jboss.org/browse/RF-13337 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/]. -- 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 From jira-events at lists.jboss.org Tue Dec 10 04:10:07 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 04:10:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid of commons-lang dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13335. ------------------------------ Verified, closing issue. > Page fragments: get rid of commons-lang dependency > -------------------------------------------------- > > Key: RF-13335 > URL: https://issues.jboss.org/browse/RF-13335 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. > I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java]. -- 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 From jira-events at lists.jboss.org Tue Dec 10 04:10:07 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 04:10:07 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid of json-simple dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13336. ------------------------------ Verified, closing issue. > Page fragments: get rid of json-simple dependency > ------------------------------------------------- > > Key: RF-13336 > URL: https://issues.jboss.org/browse/RF-13336 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html]. -- 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 From jira-events at lists.jboss.org Tue Dec 10 04:24:05 2013 From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 10 Dec 2013 04:24:05 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13428) RF5 documentation mentions 'RichFaces 4' In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13428: ------------------------------- Summary: RF5 documentation mentions 'RichFaces 4' Key: RF-13428 URL: https://issues.jboss.org/browse/RF-13428 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 5.0.0.Alpha2 Reporter: Luk?? Fry? Assignee: Luk?? Fry? Fix For: 5.0.0.Alpha2 -- 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 From jira-events at lists.jboss.org Tue Dec 10 06:53:06 2013 From: jira-events at lists.jboss.org (Matej Novotny (JIRA)) Date: Tue, 10 Dec 2013 06:53:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine module dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13300. ------------------------------ Verified, closing issue. > Page Fragments: refine module dependencies > ------------------------------------------ > > Key: RF-13300 > URL: https://issues.jboss.org/browse/RF-13300 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > During the review, I have found out we may need to fine module dependencies: > https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441 > ---- > {code} > joda-time:2.3 > - DateTime > commons-lang:2.6 > - Validate.isTrue > - StringEscapeUtils.unescapeJava > json-simple:1.1.1 > - JSONParser > org.jodah:typetools:0.3.0 > - TypeResolver.resolveRawArguments > {code} > I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}. > I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. > I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java]. > {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html]. > I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/]. -- 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 From issues at jboss.org Tue Dec 10 10:53:36 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 10:53:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13134) Tie RichFaces 4.5 Components to CDK 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13134. ---------------------------- Verified. Closing. > Tie RichFaces 4.5 Components to CDK 4.5 > --------------------------------------- > > Key: RF-13134 > URL: https://issues.jboss.org/browse/RF-13134 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > This will allow: > * build Compoents on windows (RF-13022) > * have RF5 and RF4.5 Componets build with same CDK -- 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 From issues at jboss.org Tue Dec 10 11:03:38 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:03:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929950#comment-12929950 ] Juraj H?ska commented on RF-13147: ---------------------------------- I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yest I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Tue Dec 10 11:05:37 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:05:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929950#comment-12929950 ] Juraj H?ska edited comment on RF-13147 at 12/10/13 11:04 AM: ------------------------------------------------------------- I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. was (Author: jhuska): I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yest I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Tue Dec 10 11:05:37 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:05:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929950#comment-12929950 ] Juraj H?ska edited comment on RF-13147 at 12/10/13 11:04 AM: ------------------------------------------------------------- I am verifying the issue for *RF 4.5*. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. was (Author: jhuska): I am verifying the issue. I have encounter following fact: some of the *.js files contains closure as described above, but some other contains a very slightly different one: {code:none} (function ($, rf) { rf.ui = rf.ui || {}; .... })(RichFaces.jQuery, window.RichFaces); {code} I guess it is only a cosmetic difference. Am I right ? It is by default searched in window object ? If yes, I would close this issue. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Tue Dec 10 11:17:38 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:17:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reopened RF-13147: ------------------------------ I am reopening the issue because it was not changed for these two files in RF5: * ordering-list-bridge.js * pick-list-bridge.js > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Tue Dec 10 11:21:41 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:21:41 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13186. ---------------------------- Verified. Closing. > Showcase 4.5.x fails > -------------------- > > Key: RF-13186 > URL: https://issues.jboss.org/browse/RF-13186 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1 > > > [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5 > [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components > [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples > Builds and deploys fine. > Examples that do not work: > * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within "- > * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization > * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces > * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource) > * inputs/rich:inplaceInput - ditto > * selects/rich:inplaceSelect - ditto > * output/rich:tooltip - ditto > When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}} > h5. resource optimization turned off > h6. Issue with Validator > - org.richfaces.validator.FacesObjectDescriptor.getMessage() > - collision between RF4.5 and RF5 > the interface is the same in both versions but the Message class is in different packages in the two > h6. Issue with menus > - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils() > - probably the same problem -- 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 From issues at jboss.org Tue Dec 10 11:41:36 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Dec 2013 11:41:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13213) RichFaces 4.5 CSV should share logic with RichFaces 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13213. ---------------------------- Verified. Closing. > RichFaces 4.5 CSV should share logic with RichFaces 5 > ----------------------------------------------------- > > Key: RF-13213 > URL: https://issues.jboss.org/browse/RF-13213 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1 > > > The Client-Side Validation is a service on client which should share logic between RichFaces 5 and RichFaces 4.5 otherwise component validation won't be coordinated. -- 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 From issues at jboss.org Tue Dec 10 12:45:40 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 10 Dec 2013 12:45:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929997#comment-12929997 ] Luk?? Fry? commented on RF-13317: --------------------------------- We are not able to simply fix this issue as the the straight-forward fix involves JSF-implementation-specific detail: the viewStateId is computed by [{{com.sun.faces.util.Util#getViewStateId(FacesContext)}}|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/main/java/com/sun/faces/context/PartialViewContextImpl.java#L451]. ---- The right fix I have in mind could be leveraging the fact RichFaces doesn't need to re-implement PartialViewContextImpl, instead, it could just use DeferredEndingPartialResponseWriter which will add RichFaces {{}} and {{JavaScriptService}} scripts at the end of the partial response. This would guard us against possible future changes, however it's not certain whether we won't perceive regressions. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Tue Dec 10 13:03:39 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 10 Dec 2013 13:03:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13168: ------------------------------- Assignee: (was: Luk?? Fry?) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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 From issues at jboss.org Tue Dec 10 13:03:40 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Tue, 10 Dec 2013 13:03:40 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render after ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13390: ------------------------------- Assignee: (was: Luk?? Fry?) > Region fails to render after ajax request > ----------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > > > > > > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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 From issues at jboss.org Tue Dec 10 13:41:37 2013 From: issues at jboss.org (Prakatheesh K (JIRA)) Date: Tue, 10 Dec 2013 13:41:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12351) rich:extendedDataTable frozen columns cause alternating row color to be out of sync with unfrozen part of table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930013#comment-12930013 ] Prakatheesh K commented on RF-12351: ------------------------------------ Is there any work around for this issue? > rich:extendedDataTable frozen columns cause alternating row color to be out of sync with unfrozen part of table > --------------------------------------------------------------------------------------------------------------- > > Key: RF-12351 > URL: https://issues.jboss.org/browse/RF-12351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final, 4.2.2.Final > Environment: Tomcat 6.0.18, JSF 2.1.5, Rich Faces 4.2.0 > Reporter: Marc Sansa > Labels: extendedDataTable > Fix For: 5-Tracking > > > The rich:extendedDataTable component, has a problem when I specify 1 or more frozen columns and use the rowClasses property to specify alternating row colors: When the table has an odd number of rows, the row colors of the frozen column section is out of sync with the unfrozen rows of the remainder of the table. Everything is fine when the table has an even number of rows or I don't use frozen columns. > Below is an excerpt of the extendedDataTable declaration which causes the issue: > rowClasses="standardTable_Row1,standardTable_Row2" > ..... > frozenColumns="3" > ...... > > -- 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 From issues at jboss.org Tue Dec 10 14:25:39 2013 From: issues at jboss.org (H G (JIRA)) Date: Tue, 10 Dec 2013 14:25:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930023#comment-12930023 ] H G commented on RF-13282: -------------------------- I still have problem related to render multiple forms (another form) in specific with r:jsFunction. The viewState in the second form disappear. As a workaround can be used only one form, but this is ugly, specially when using modals. > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Tue Dec 10 14:29:39 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 10 Dec 2013 14:29:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13147. -------------------------------- Resolution: Done [~jhuska] we will not respin 5.0.0.Alpha2 for this, and we want to track that this issue was (for the most part) addressed in 5.0.0.Alpha3. For this reason I am resolving this issue. Would you mind filing a new issue for 5.0.0.Alpha3 with the remaining re-factorings that you've uncovered? Nice catch btw! > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Tue Dec 10 14:29:39 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 10 Dec 2013 14:29:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12351) rich:extendedDataTable frozen columns cause alternating row color to be out of sync with unfrozen part of table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930026#comment-12930026 ] Brian Leathem commented on RF-12351: ------------------------------------ No, these is currently no known workaround for this issue. We hope to address this in an upcoming RF 5 alpha when we address the client-side implementation of the EDT. > rich:extendedDataTable frozen columns cause alternating row color to be out of sync with unfrozen part of table > --------------------------------------------------------------------------------------------------------------- > > Key: RF-12351 > URL: https://issues.jboss.org/browse/RF-12351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.0.Final, 4.2.2.Final > Environment: Tomcat 6.0.18, JSF 2.1.5, Rich Faces 4.2.0 > Reporter: Marc Sansa > Labels: extendedDataTable > Fix For: 5-Tracking > > > The rich:extendedDataTable component, has a problem when I specify 1 or more frozen columns and use the rowClasses property to specify alternating row colors: When the table has an odd number of rows, the row colors of the frozen column section is out of sync with the unfrozen rows of the remainder of the table. Everything is fine when the table has an even number of rows or I don't use frozen columns. > Below is an excerpt of the extendedDataTable declaration which causes the issue: > rowClasses="standardTable_Row1,standardTable_Row2" > ..... > frozenColumns="3" > ...... > > -- 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 From issues at jboss.org Tue Dec 10 14:31:37 2013 From: issues at jboss.org (H G (JIRA)) Date: Tue, 10 Dec 2013 14:31:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930028#comment-12930028 ] H G commented on RF-13282: -------------------------- I don't know if it was reported already this bug for RF 4.5/5. I hope that can be fixed in Alpha 2 or have to wait jsf 2.3 (https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790) > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Tue Dec 10 14:31:37 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 10 Dec 2013 14:31:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930029#comment-12930029 ] Brian Leathem commented on RF-13282: ------------------------------------ [~mechtatel] this is not a relevant thread for your comment. Would you mind posting to the RichFaces user forum? > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Wed Dec 11 03:21:39 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Dec 2013 03:21:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13431) Rename JavaScript closures which references to RichFaces object to rf in pickList resources In-Reply-To: References: Message-ID: Juraj H?ska created RF-13431: -------------------------------- Summary: Rename JavaScript closures which references to RichFaces object to rf in pickList resources Key: RF-13431 URL: https://issues.jboss.org/browse/RF-13431 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component Affects Versions: 5.0.0.Alpha2 Reporter: Juraj H?ska Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. However, resources for {{pickList}} were omitted: * ordering-list-bridge.js * pick-list-bridge.js -- 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 From issues at jboss.org Wed Dec 11 03:21:39 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Dec 2013 03:21:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13431) Rename JavaScript closures which references to RichFaces object to rf in pickList resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13431: ----------------------------- Description: Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. However, resources for {{pickList}} were omitted: * ordering-list-bridge.js * pick-list-bridge.js Please consider also [this|https://issues.jboss.org/browse/RF-13147?focusedCommentId=12929950&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12929950] comment, when resolving this issue - using of window object reference was: Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. However, resources for {{pickList}} were omitted: * ordering-list-bridge.js * pick-list-bridge.js > Rename JavaScript closures which references to RichFaces object to rf in pickList resources > ------------------------------------------------------------------------------------------- > > Key: RF-13431 > URL: https://issues.jboss.org/browse/RF-13431 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > > Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. > However, resources for {{pickList}} were omitted: > * ordering-list-bridge.js > * pick-list-bridge.js > Please consider also [this|https://issues.jboss.org/browse/RF-13147?focusedCommentId=12929950&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12929950] comment, when resolving this issue - using of window object reference -- 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 From issues at jboss.org Wed Dec 11 04:16:38 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:16:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13318) Update Autocomplete with refactored Autocomplete widget In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13318. ------------------------------ > Update Autocomplete with refactored Autocomplete widget > ------------------------------------------------------- > > Key: RF-13318 > URL: https://issues.jboss.org/browse/RF-13318 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 04:18:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:18:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13432) Upgrade framework build to JSF 2.2 In-Reply-To: References: Message-ID: Luk?? Fry? created RF-13432: ------------------------------- Summary: Upgrade framework build to JSF 2.2 Key: RF-13432 URL: https://issues.jboss.org/browse/RF-13432 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: third-party Affects Versions: 5.0.0.Alpha3 Reporter: Luk?? Fry? Fix For: 5.0.0.Alpha3 -- 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 From issues at jboss.org Wed Dec 11 04:18:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:18:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update OrderingList/PickList with refactored Widgets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13320. ------------------------------ > Update OrderingList/PickList with refactored Widgets > ---------------------------------------------------- > > Key: RF-13320 > URL: https://issues.jboss.org/browse/RF-13320 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 04:20:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:20:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename bridges, bridge-base and templates file names to use dashes instead of camelCase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13321. ------------------------------ > Rename bridges, bridge-base and templates file names to use dashes instead of camelCase > --------------------------------------------------------------------------------------- > > Key: RF-13321 > URL: https://issues.jboss.org/browse/RF-13321 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > We have renamed orderingList/pickList to ordering-list/pick-list in RW. > I think we should update naming in RF. -- 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 From issues at jboss.org Wed Dec 11 04:22:32 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:22:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should be used in CDK templates instead of $ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13330. ------------------------------ > RichFaces.jQuery should be used in CDK templates instead of $ > ------------------------------------------------------------- > > Key: RF-13330 > URL: https://issues.jboss.org/browse/RF-13330 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery. > https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44 > https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92 -- 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 From issues at jboss.org Wed Dec 11 04:26:33 2013 From: issues at jboss.org (Holger Walter (JIRA)) Date: Wed, 11 Dec 2013 04:26:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13433) extendeddatatable: Column resizing and column reordering not working for RTL languages In-Reply-To: References: Message-ID: Holger Walter created RF-13433: ---------------------------------- Summary: extendeddatatable: Column resizing and column reordering not working for RTL languages Key: RF-13433 URL: https://issues.jboss.org/browse/RF-13433 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.3.4 Environment: ALL Reporter: Holger Walter For the extendeddatatable column resizing and column reordering are not working correctly for RTL (right-to-left) languages. a) Column resizing In case you try to increase the width of one column, RF does in fact decrease the width of the left side neighbor column. In case of decreasing the width, RF increases the width of the neighbor. b) Column reordering When dragging a column to a new position an arrow is shown at the place where it is intended to be inserted. However, after releasing the mouse, the columns is inserted at another place. In case you cannot fix these issues soon, please provide at least the possibility to disable columns reordering. Column resizing can be disabled by CSS. -- 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 From issues at jboss.org Wed Dec 11 04:38:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:38:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13342) archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13342. ---------------------------- verified, closing. > archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample > ------------------------------------------------------------------------------------------------------- > > Key: RF-13342 > URL: https://issues.jboss.org/browse/RF-13342 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Ji?? ?tefek > Priority: Trivial > Fix For: 4.3.5, 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 04:40:36 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:40:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server handlers throws exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13333. ------------------------------ Verified > Charts: click server handlers throws exception > ---------------------------------------------- > > Key: RF-13333 > URL: https://issues.jboss.org/browse/RF-13333 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Macko > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > Steps to reproduce: > 1. open r:chart -> Event handling demo > http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky > 2. click on one of points on the chart > FAIL: there is an error in the server console > {{NoSuchMethodException: Read method for property 'JSONArray' not found}} > Stack trace: > {code} > 13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript > at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:] > at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:] > at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:] > at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:] > at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:] > at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found > at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:] > at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:] > ... 37 more > {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 From issues at jboss.org Wed Dec 11 04:42:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:42:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList - maxListHeight & minListHeight need to have set units along with number to work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13346. ---------------------------- verified, closing > orderingList - maxListHeight & minListHeight need to have set units along with number to work > --------------------------------------------------------------------------------------------- > > Key: RF-13346 > URL: https://issues.jboss.org/browse/RF-13346 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {{pickList}} attributes: > * {{minListHeight}} and {{maxListHeight}} > need to have set units along with the number value (e.g. 200px) in order to work correctly. > In RF4 and in RichWidgets, these attributes can be left without units. -- 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 From issues at jboss.org Wed Dec 11 04:44:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:44:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13351) orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13351. ---------------------------- verified, closing. > orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute > ----------------------------------------------------------------------------------------------- > > Key: RF-13351 > URL: https://issues.jboss.org/browse/RF-13351 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. -- 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 From issues at jboss.org Wed Dec 11 04:44:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change package from .tests.page.fragments.impl to .fragments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13338. ------------------------------ > Page Fragments: change package from .tests.page.fragments.impl to .fragments > ---------------------------------------------------------------------------- > > Key: RF-13338 > URL: https://issues.jboss.org/browse/RF-13338 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 04:44:34 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:44:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13363) Sync latest page fragments changes from RF-qa repository to RF repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13363. ---------------------------- verified, closing > Sync latest page fragments changes from RF-qa repository to RF repository > ------------------------------------------------------------------------- > > Key: RF-13363 > URL: https://issues.jboss.org/browse/RF-13363 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha2 > > > After porting all changes delete the page-fragments submodule from richfaces-qa repository. > Make it depended on the RF's page fragments. -- 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 From issues at jboss.org Wed Dec 11 04:46:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:46:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13357. ------------------------------ Verified > Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version > -------------------------------------------------------------------------------------------- > > Key: RF-13357 > URL: https://issues.jboss.org/browse/RF-13357 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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 From issues at jboss.org Wed Dec 11 04:56:35 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Dec 2013 04:56:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13147) Rename all occurences JavaScript closures which references to RichFaces object to rf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13147. ---------------------------- I have filed RF-13431. Verified. Closing. > Rename all occurences JavaScript closures which references to RichFaces object to rf > ------------------------------------------------------------------------------------ > > Key: RF-13147 > URL: https://issues.jboss.org/browse/RF-13147 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > It will unify sources and make easier to scan through files: > {code} > (function ($, rf) { > rf.ui = rf.ui || {}; > .... > })(RichFaces.jQuery, RichFaces); > {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 From issues at jboss.org Wed Dec 11 04:58:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 04:58:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push registered as $.fn.push overrides jQuery function In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13374. ------------------------------ > RichFaces push registered as $.fn.push overrides jQuery function > ---------------------------------------------------------------- > > Key: RF-13374 > URL: https://issues.jboss.org/browse/RF-13374 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > > The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function. > The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins. -- 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 From issues at jboss.org Wed Dec 11 05:00:35 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 05:00:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13219) Document cloning of richfaces git repository together with its submodules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13219. ---------------------------- verified, but was replaced after [RF-13253|https://issues.jboss.org/browse/RF-13253], [RF-13267|https://issues.jboss.org/browse/RF-13267] and now there is no need to add the '--recursive' switch. closing. > Document cloning of richfaces git repository together with its submodules > ------------------------------------------------------------------------- > > Key: RF-13219 > URL: https://issues.jboss.org/browse/RF-13219 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > To successfully build a RichFaces repository, one needs to clone in with its submodules, issuing: > {{git clone --recursive https://github.com/richfaces/richfaces.git}} > Repository submodules are not cloned if that parameter is not passed. > Could we update the doc to contain this information ? E.g. the {{README.md}} of repository, and the Developer Guide ? -- 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 From issues at jboss.org Wed Dec 11 05:06:32 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 05:06:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13375. ------------------------------ > Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom > ----------------------------------------------------------------------------------------------- > > Key: RF-13375 > URL: https://issues.jboss.org/browse/RF-13375 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup. -- 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 From issues at jboss.org Wed Dec 11 05:06:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 05:06:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13396. ------------------------------ > Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2 > ---------------------------------------------- > > Key: RF-13396 > URL: https://issues.jboss.org/browse/RF-13396 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.5-Tracking, 5-Tracking > Reporter: Matej Novotny > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > Identify what changes/features need to be ported from RF 4.5 TO RF 5. > Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224]) > If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5. -- 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 From issues at jboss.org Wed Dec 11 05:16:36 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 05:16:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13228) Resource Optimizer throws NPE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13228. ---------------------------- verified, closing. > Resource Optimizer throws NPE > ----------------------------- > > Key: RF-13228 > URL: https://issues.jboss.org/browse/RF-13228 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > https://api.travis-ci.org/jobs/11964202/log.txt?deansi=true > {code} > Sep 30, 2013 2:44:47 PM org.richfaces.resource.optimizer.ResourceGenerator execute > SEVERE: null > java.util.concurrent.ExecutionException: java.lang.NullPointerException > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) > at java.util.concurrent.FutureTask.get(FutureTask.java:111) > at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:436) > at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297) > at java.lang.Thread.run(Thread.java:724) > Caused by: java.lang.NullPointerException > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:356) > at org.richfaces.resource.optimizer.resource.handler.impl.DynamicResourceHandler.createResource(DynamicResourceHandler.java:85) > at org.richfaces.resource.optimizer.resource.handler.impl.AbstractResourceHandler.createResource(AbstractResourceHandler.java:42) > at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.createResource(ResourceTaskFactoryImpl.java:72) > at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.checkResource(ResourceTaskFactoryImpl.java:120) > at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.call(ResourceTaskFactoryImpl.java:154) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > ... 1 more > {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 From issues at jboss.org Wed Dec 11 05:36:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 05:36:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13098. ---------------------------- verified, closing. just a note that the reproducer is in master branch in both 4.3.x and 5 Metamer and the branch 'RF-13098' is now deleted. > 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 > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.4, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component > Having a > {code} > > {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 From issues at jboss.org Wed Dec 11 05:44:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 05:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13231) RF 5, tree component missing resource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13231. ---------------------------- closing > RF 5, tree component missing resource > ------------------------------------- > > Key: RF-13231 > URL: https://issues.jboss.org/browse/RF-13231 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux > Chrome 29.0.1547.76 @ Linux x86_64 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Using Metamer I accesed a tree component (see steps to reproduce) and it did not render properly, therefore the tree was not usable. > The error message in web console was: > GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/org.richfaces/iteration/tree/tree.ecss 500 (Internal Server Error) > This may be also connected to https://issues.jboss.org/browse/RF-13200 -- 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 From issues at jboss.org Wed Dec 11 06:24:35 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 06:24:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13434: -------------------------------- Summary: archetypes: change the namespace of richfaces components Key: RF-13434 URL: https://issues.jboss.org/browse/RF-13434 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 5.0.0.Alpha2 Reporter: Ji?? ?tefek After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} -- 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 From issues at jboss.org Wed Dec 11 06:36:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 06:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13035) Simpleapp Archetype: mobile version shows modal dialog In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13035. ---------------------------- Verified with RF 5, closing. > Simpleapp Archetype: mobile version shows modal dialog > ------------------------------------------------------- > > Key: RF-13035 > URL: https://issues.jboss.org/browse/RF-13035 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.1.0.Final, 5.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.4, 5.0.0.Alpha2 > > Attachments: modal-iphone.png, richfaces-simpleapp-jee6.war, simpleapp-modal.png > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > When the simpleapp archetype is built with "-Dmobile-optimized=true", the welcome page shows modal dialog (see screenshot). -- 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 From issues at jboss.org Wed Dec 11 06:36:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 06:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13434: ----------------------------- Priority: Critical (was: Major) > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Priority: Critical > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} -- 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 From issues at jboss.org Wed Dec 11 06:40:34 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 06:40:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13402) JavaScript error thrown for the orderingList in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13402. ------------------------------ > JavaScript error thrown for the orderingList in the showcase > ------------------------------------------------------------ > > Key: RF-13402 > URL: https://issues.jboss.org/browse/RF-13402 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Viewing the orderingLIst in the showcase yields the JavaScript error: > {code} > Uncaught TypeError: Object [object Object] has no method 'detach' > {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 From issues at jboss.org Wed Dec 11 06:42:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 06:42:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13193) Rename the resource library to account for RF 4/5 resource overlap In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13193. ---------------------------- verified, closing. > Rename the resource library to account for RF 4/5 resource overlap > ------------------------------------------------------------------ > > Key: RF-13193 > URL: https://issues.jboss.org/browse/RF-13193 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Brian Leathem > Assignee: Michal Petrov > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Rename the RichFaces resource library name to something like: _org.richfaces.ui_, or _org.richfaces.widgets_. This will allow RF 4 and RF 5 components to co-exist when resource names overlap. -- 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 From issues at jboss.org Wed Dec 11 06:46:34 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 06:46:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13235) Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13235. ---------------------------- Verified, closing. > Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13235 > URL: https://issues.jboss.org/browse/RF-13235 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > The row key generation for Tree stopped to work: > *got:*
> *expected:*
> ---- > The cause was that rowKeyConverter resolves to null, so plain toString on rowKey is used. > I was wondering why rowKeyConverter isn't resolved for Tree in Showcase - the problem is that CDK generates this attribute and thus its implementation in AbstractTree (which is the correct way of rowKeyResolution) isn't used at all. > I'm pretty sure this is caused by refactoring from tree-model-props.xml to use Java interfaces TreeProps and TreeCommonProps: > https://github.com/richfaces/richfaces/commit/62ab0fe3f00b44a166b522ecb71e1733897aeebe > However it's not clear why the rowKeyConverter wasn't generated in RF 4.3 when it wasn't marked as generate=false: > https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/resources/META-INF/cdk/attributes/tree-model-props.xml#L48 > Note that in RF 5 it is generated because UIAdaptor has @Attribute which defaults to generate=true: > https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/iteration/UIDataAdaptor.java#L612 > Workaround is marking rowKeyConverter as generate=false in AbstracTree (or maybe RowKeyConverter), but we should rather investigate why this issue happens. > ---- > This issue has bigger potential since during refactoring of properties, [~bleathem] could work with the same assumption as I did ^. -- 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 From issues at jboss.org Wed Dec 11 06:50:32 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 06:50:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13237. ------------------------------ > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 07:00:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:00:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930197#comment-12930197 ] Luk?? Fry? commented on RF-13317: --------------------------------- I have tried to apply a naive fix leveraging {{Util#getViewStateId()}} and it fixed few more framework tests. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Wed Dec 11 07:12:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:12:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13180. ---------------------------- closing > Autocomplete: ajax doesn't work with change event > ------------------------------------------------- > > Key: RF-13180 > URL: https://issues.jboss.org/browse/RF-13180 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > # type "a" into input > # select Alabama > result: > * ajax request is not fired > * output is not updated > * when "change" event in r:ajax is changed to "blur", the use-case 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 From issues at jboss.org Wed Dec 11 07:14:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:14:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13182) Autocomplete: attributes style and styleClass missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13182. ---------------------------- verified, closing. > Autocomplete: attributes style and styleClass missing > ----------------------------------------------------- > > Key: RF-13182 > URL: https://issues.jboss.org/browse/RF-13182 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Component autocomplete is missing two attributes - style and styleClass. There attributes were present in 5.0.0.Alpha1. -- 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 From issues at jboss.org Wed Dec 11 07:16:36 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:16:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13183) Autocomplete: behavior of component with tokens changed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13183. ---------------------------- verified, closing. > Autocomplete: behavior of component with tokens changed > ------------------------------------------------------- > > Key: RF-13183 > URL: https://issues.jboss.org/browse/RF-13183 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved) > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > # type "a" into input > # select Alabama > result: > * output contains "Alabama," but should be "Alabama" > * it would output "Alabama" in 5.0.0.Alpha1 > * this behavior is influenced by "tokens" attribute -- 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 From issues at jboss.org Wed Dec 11 07:22:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:22:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13184) Autocomplete: hide attribute layout since it is auto-detected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13184. ---------------------------- verified, closing. > Autocomplete: hide attribute layout since it is auto-detected > ------------------------------------------------------------- > > Key: RF-13184 > URL: https://issues.jboss.org/browse/RF-13184 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved) > # set layout=div in autocomplete.xhtml > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > # type "a" into input > result: > * ajax request is fired > * status in page's header shows "ERROR" -- 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 From issues at jboss.org Wed Dec 11 07:28:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:28:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13223) Upgrade to jsf-test 1.1.7 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13223. ---------------------------- verified, closing. > Upgrade to jsf-test 1.1.7 > ------------------------- > > Key: RF-13223 > URL: https://issues.jboss.org/browse/RF-13223 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - unit > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > Fixes issue with getPathInfo -- 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 From issues at jboss.org Wed Dec 11 07:44:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13218) Check existence of src/main/widgets with enforcer plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13218. ---------------------------- verified, closing. the plugin is not present after changes from RF-13253, RF-13267. > Check existence of src/main/widgets with enforcer plugin > -------------------------------------------------------- > > Key: RF-13218 > URL: https://issues.jboss.org/browse/RF-13218 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Michal Petrov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RichFaces 5 may fail when {{src/main/widgets}} aren't checked out properly. > I suggest to use enforcer plugin to check that e.g. {{src/main/widgets/Gruntfile.js}} file exists: > http://maven.apache.org/enforcer/enforcer-rules/requireFilesExist.html -- 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 From issues at jboss.org Wed Dec 11 07:46:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:46:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13204) Loading of com.jqueryui library fails, most of the components which depend on it do not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13204. ---------------------------- closing > Loading of com.jqueryui library fails, most of the components which depend on it do not work > -------------------------------------------------------------------------------------------- > > Key: RF-13204 > URL: https://issues.jboss.org/browse/RF-13204 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality, resource handling > Affects Versions: 5.0.0.Alpha2 > Environment: JBoss AS 7.1.1.Final, Tomcat 7 > Chrome, Firefox > Reporter: Juraj H?ska > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > > When loading page with components which {{@ResourceDependency}} links to library {{com.jqueryui}}, following error is rendered into the AS console: > {code} > 11:15:08,155 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, jquery.ui.core.js, from library, com.jqueryui. > {code} > There is an error on browser console (This one e.g. for DaD): > {code} > GET http://localhost:8080/showcase/richfaces/RES_NOT_FOUND 404 (Not Found) component-sample.jsf:23 > Uncaught TypeError: Object [object Object] has no method 'draggable' > {code} > Following components are affected: > # DaD > # Calendar > # Autocomplete > # Focus > Those components functionality is broken. -- 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 From issues at jboss.org Wed Dec 11 07:58:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 07:58:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13191) The RichFaces base deployment for integration tests incorrectly disables control skinning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13191. ---------------------------- verified, closing. > The RichFaces base deployment for integration tests incorrectly disables control skinning > ----------------------------------------------------------------------------------------- > > Key: RF-13191 > URL: https://issues.jboss.org/browse/RF-13191 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > See: https://github.com/richfaces/richfaces/blob/master/build/build-resources/src/main/java/org/richfaces/deployment/Deployment.java#L95 > Integration test environments should as closely as possible follow real environments. Since this parameter can be over-ridden in an individual deployment (see below), I recommend we remove this configuration in the default deployment. > {code} > deployment.webXml(new Function() { > public WebAppDescriptor apply(WebAppDescriptor descriptor) { > descriptor.getOrCreateContextParam() > .paramName("org.richfaces.enableControlSkinning") > .paramValue("false"); > return descriptor; > } > }); > {code} > Note: after making this change, all tests will need to be run, and any tests that rely on this configuration will have to be adjusted to set the context-param on their individual deployment. -- 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 From issues at jboss.org Wed Dec 11 08:00:37 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 08:00:37 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13160) Refactor the InputNumber* components into abstract classes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13160. ---------------------------- verified, closing > Refactor the InputNumber* components into abstract classes > ---------------------------------------------------------- > > Key: RF-13160 > URL: https://issues.jboss.org/browse/RF-13160 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The InputNumberSpinner and InputNumberSlider components are generated via xml in a faces-config.xml file. While this is clever, it means we have two components that are created differently from all the others, making them harder to manage. Additionally the xml is not conducive to refactoring, and the method relies on an xml format for shared attribute definitions, making it difficult to move forward with RF-12952. > I propose re-implementing those components as Abstract components, like the majority of other RichFaces CDK components. -- 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 From issues at jboss.org Wed Dec 11 08:50:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 08:50:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13131) Upgrade Arquillian Components: Core 1.1 / Graphene 2.0 / Drone 1.2 / Arquillian Warp Alpha5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13131. ---------------------------- verified, closing > Upgrade Arquillian Components: Core 1.1 / Graphene 2.0 / Drone 1.2 / Arquillian Warp Alpha5 > ------------------------------------------------------------------------------------------- > > Key: RF-13131 > URL: https://issues.jboss.org/browse/RF-13131 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > We need to release Warp Alpha5 first. -- 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 From issues at jboss.org Wed Dec 11 08:52:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 08:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13132) Upgrade JBoss Java EE BOMs to 3.0.2.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13132. ---------------------------- verified in rf 5, closing > Upgrade JBoss Java EE BOMs to 3.0.2.Final > ----------------------------------------- > > Key: RF-13132 > URL: https://issues.jboss.org/browse/RF-13132 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.3.4, 5.0.0.Alpha2 > > > The need for an upgrade for identified here: WFK2-27 -- 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 From issues at jboss.org Wed Dec 11 09:00:39 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:00:39 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13143) RichFaces 5: change components namespace from http://richfaces.org/rich to http://richfaces.org In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13143. ---------------------------- verified, closing. (namespace in archetypes was not refactored, created RF-13434) > RichFaces 5: change components namespace from http://richfaces.org/rich to http://richfaces.org > ----------------------------------------------------------------------------------------------- > > Key: RF-13143 > URL: https://issues.jboss.org/browse/RF-13143 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > > As we are in process of adopting RichFaces 5 by RichFaces 4.5 Components (RF-13114), we need to change the namespace so that those two won't conflict. > {{http://richfaces.org}} seems like easy to remember and concise solution (as we have agreed on team meeting 2013-08-08. -- 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 From issues at jboss.org Wed Dec 11 09:06:33 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:06:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13181) Autocomplete: suggestion list is not valid HTML code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13181. ---------------------------- verified, closing. > Autocomplete: suggestion list is not valid HTML code > ---------------------------------------------------- > > Key: RF-13181 > URL: https://issues.jboss.org/browse/RF-13181 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml > # type "a" into input > # check suggestion list's markup > result: > * Autocomplete generates an unsorted list (ul) with several list items (li), one for each suggestion. However, inside each li, there is yet another li which is not allowed by HTML. > {code:xml} > > {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 From issues at jboss.org Wed Dec 11 09:12:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 09:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13399) RichFaces can't be built with Maven 3.1.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13399. ------------------------------ I can't reproduce anymore > RichFaces can't be built with Maven 3.1.1 > ----------------------------------------- > > Key: RF-13399 > URL: https://issues.jboss.org/browse/RF-13399 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > -- 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 From issues at jboss.org Wed Dec 11 09:14:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 09:14:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13129) Bind Widget Bridge reference to the DOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13129. ---------------------------- verified, closing. > Bind Widget Bridge reference to the DOM > --------------------------------------- > > Key: RF-13129 > URL: https://issues.jboss.org/browse/RF-13129 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Following alghoritm looks for the RichFaces component root and re-directs event source to this root: > https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/richfaces.js#L686 > However bridge code isn't registered to the DOM in the way RichFaces 4 using BaseComponent are. > I suggest to bind the reference to the DOM using jQuery.data. -- 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 From issues at jboss.org Wed Dec 11 09:30:32 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 11 Dec 2013 09:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13370. ------------------------------ > Charts - server-side improvements > --------------------------------- > > Key: RF-13370 > URL: https://issues.jboss.org/browse/RF-13370 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Luk?? Macko > Assignee: Luk?? Macko > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > * rename attribute *clickListener* in chart and series tag to *plotClickListner* > * send request to server only if a server-side listener is attached > * particular series server-side listeners (called only for particular series events) > * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean) -- 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 From issues at jboss.org Wed Dec 11 13:24:36 2013 From: issues at jboss.org (Holger Walter (JIRA)) Date: Wed, 11 Dec 2013 13:24:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit In-Reply-To: References: Message-ID: Holger Walter created RF-13435: ---------------------------------- Summary: extendedatatable: Scrolling position is lost after submit Key: RF-13435 URL: https://issues.jboss.org/browse/RF-13435 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.3.4 Environment: ALL Reporter: Holger Walter Issue is similar to RF-5312. In EDT, the current scrolling position is lost (reset to 0) after a submit. Steps to reproduce: 1. Use the showcase for the EDT(version 4.3.4) 2. Adapt the xhtml file by adding a simple submit button ( ) 3. Activate the 'ajax loading' checkbox 4. Scroll down in the table 5. Press the new submit button 6. The scrolling position is lost This might sound as a minor problem, but in case of using the EDT with ajax data loading, a user can scroll quite far until he may find the row on which he wants to do some actions. If the scrolling position is reset to 0 after each submit, it gets quite tedious for a user scrolling every time to this old position in the table. I've seen that the current position is already stored in componentState, but unfortunately it is getting reset on submit. I already tried a workaround, by using the 'onready' event of the EDT after a submit to trigger scrolling to the desired position with javascript but this does not work reliably on one hand, and triggers an additional ajax call which may cause that messages in h:messages are lost. -- 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 From issues at jboss.org Wed Dec 11 13:28:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Dec 2013 13:28:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930515#comment-12930515 ] Brian Leathem commented on RF-13435: ------------------------------------ [~wlh] is this a regression? Did it work for you as expected in previous 4.3.x versions? > extendedatatable: Scrolling position is lost after submit > --------------------------------------------------------- > > Key: RF-13435 > URL: https://issues.jboss.org/browse/RF-13435 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: extendeddatatable, richfaces, scroll > > Issue is similar to RF-5312. > In EDT, the current scrolling position is lost (reset to 0) after a submit. > Steps to reproduce: > 1. Use the showcase for the EDT(version 4.3.4) > 2. Adapt the xhtml file by adding a simple submit button ( ) > 3. Activate the 'ajax loading' checkbox > 4. Scroll down in the table > 5. Press the new submit button > 6. The scrolling position is lost > This might sound as a minor problem, but in case of using the EDT with ajax data loading, a user can scroll quite far until he may find the row on which he wants to do some actions. If the scrolling position is reset to 0 after each submit, it gets quite tedious for a user scrolling every time to this old position in the table. > I've seen that the current position is already stored in componentState, but unfortunately it is getting reset on submit. > I already tried a workaround, by using the 'onready' event of the EDT after a submit to trigger scrolling to the desired position with javascript but this does not work reliably on one hand, and triggers an additional ajax call which may cause that messages in h:messages are lost. -- 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 From issues at jboss.org Wed Dec 11 15:06:32 2013 From: issues at jboss.org (Holger Walter (JIRA)) Date: Wed, 11 Dec 2013 15:06:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930539#comment-12930539 ] Holger Walter commented on RF-13435: ------------------------------------ I tested only with 4.3.4. If it helps I can test with older versions e.g. 4.2.3 as well and give you feedback. > extendedatatable: Scrolling position is lost after submit > --------------------------------------------------------- > > Key: RF-13435 > URL: https://issues.jboss.org/browse/RF-13435 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: extendeddatatable, richfaces, scroll > > Issue is similar to RF-5312. > In EDT, the current scrolling position is lost (reset to 0) after a submit. > Steps to reproduce: > 1. Use the showcase for the EDT(version 4.3.4) > 2. Adapt the xhtml file by adding a simple submit button ( ) > 3. Activate the 'ajax loading' checkbox > 4. Scroll down in the table > 5. Press the new submit button > 6. The scrolling position is lost > This might sound as a minor problem, but in case of using the EDT with ajax data loading, a user can scroll quite far until he may find the row on which he wants to do some actions. If the scrolling position is reset to 0 after each submit, it gets quite tedious for a user scrolling every time to this old position in the table. > I've seen that the current position is already stored in componentState, but unfortunately it is getting reset on submit. > I already tried a workaround, by using the 'onready' event of the EDT after a submit to trigger scrolling to the desired position with javascript but this does not work reliably on one hand, and triggers an additional ajax call which may cause that messages in h:messages are lost. -- 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 From issues at jboss.org Wed Dec 11 16:04:32 2013 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 11 Dec 2013 16:04:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13434: ----------------------------- Description: After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} but all archetypes use the old one. (was: After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}}) > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Priority: Critical > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} but all archetypes use the old one. -- 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 From issues at jboss.org Thu Dec 12 04:42:33 2013 From: issues at jboss.org (barbara b (JIRA)) Date: Thu, 12 Dec 2013 04:42:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: barbara b created RF-13436: ------------------------------ Summary: Upgrade CKEditor to 4.3 Key: RF-13436 URL: https://issues.jboss.org/browse/RF-13436 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha1, 4.3.4 Reporter: barbara b All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Thu Dec 12 05:38:33 2013 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Dec 2013 05:38:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930656#comment-12930656 ] Matej Novotny commented on RF-13230: ------------------------------------ [~ibenjes], I tried using your example but came across several problems. I made some changes to make the example fully working. The function sort() is working but requires two arguments, column ID and sort order (eg. descending/descending). The conversation scoped bean you are using does not seem to have any effect as you do not start/end conversation eg. it behaves as view scoped if I am not mistaken - still I used it to reproduce the problem. Also I removed the Logger as it is not needed for the example. Now to the result. I used Metamer (our testing app) with 4.3.3.Final and current 4.3.x. The bug described in the forum can be found in *both* versions, so it is *not regression*. In both version there is a problem you just described that the state does not affect first page unless you use data scroller. Without data scroller everything works correctly. I will add a tests for this issue to 4.3.x and also check it in version 5 and report further details. By the way, the forum link you gave leads to RF-13226 and not this issue, is that a copy of this isue then? (problem seems pretty much the same) > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From issues at jboss.org Thu Dec 12 07:56:35 2013 From: issues at jboss.org (Immo Benjes (JIRA)) Date: Thu, 12 Dec 2013 07:56:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930717#comment-12930717 ] Immo Benjes commented on RF-13230: ---------------------------------- Sorry I confused the issues here. Two different bugs, the forum is indeed for RF-13226. You wrote: {code} Changing the column ordering - JSON String is correctly passed to the bean and stored. Setting its value to null using ajax - used a4j:commandButton, set to null, variable was null Rerender component - nothing happened, table is still modified {code} The table should be back to default state when you reset the tableState and that is not happening. > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From issues at jboss.org Thu Dec 12 08:56:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 08:56:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930753#comment-12930753 ] Luk?? Fry? commented on RF-13317: --------------------------------- The resolution should try to address RF-12865. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Thu Dec 12 08:58:32 2013 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Thu, 12 Dec 2013 08:58:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13437) contextMenu: support hiding by clicking outside only In-Reply-To: References: Message-ID: Lutz Ulrich created RF-13437: -------------------------------- Summary: contextMenu: support hiding by clicking outside only Key: RF-13437 URL: https://issues.jboss.org/browse/RF-13437 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Reporter: Lutz Ulrich Priority: Minor Currently (until version 4.3.4), context menus always disappear when the mouse cursor is moved outside the menu. It should be possible to restrict hiding the menu when the user clicks somewhere else, like in many other applications, like Windows Explorer. I was able to achieve this behavior by unbinding the event handler for mouseleave via extra scripting. {{RichFaces.Event.unbindById(menu.id, 'mouseleave');}} (Note that the code only prevents hiding the main menu on mouseleave. Sub-menus / menuGroups are still closed on mouseleave.) But it would be better if the contextMenu would support an attribute for turning on 'hide by outside click only'. -- 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 From issues at jboss.org Thu Dec 12 10:40:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 10:40:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930815#comment-12930815 ] Luk?? Fry? commented on RF-13282: --------------------------------- Just to be clear, the issue [~mechtatel] is talking about is probably RF-13317. > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Thu Dec 12 11:12:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928896#comment-12928896 ] Luk?? Fry? edited comment on RF-13040 at 12/12/13 11:11 AM: ------------------------------------------------------------ components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. It is likely caused by WFLY-2638. was (Author: lfryc): components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. I think it is related to RF-13197. The same issue with Showcase. > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From issues at jboss.org Thu Dec 12 11:12:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13040: ---------------------------- Environment: WildFly 8.0.0.Beta1 (was: WildFly 8.0.0.Alpha1) > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Beta1 > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From issues at jboss.org Thu Dec 12 11:12:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13040) Examples don't work on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13040: ---------------------------- Environment: WildFly 8.0.0.Beta2-SNAPSHOT (was: WildFly 8.0.0.Beta1) > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Beta2-SNAPSHOT > Reporter: Jan Papousek > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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 From issues at jboss.org Thu Dec 12 11:16:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:16:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930842#comment-12930842 ] Luk?? Fry? commented on RF-13197: --------------------------------- Imho this is duplicate of RF-13317 > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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 From issues at jboss.org Thu Dec 12 11:22:33 2013 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Dec 2013 11:22:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930843#comment-12930843 ] Matej Novotny commented on RF-13230: ------------------------------------ Ok I can see what you mean now. I re-used the sample and added a4j:commandButton calling a bean method (setting state to null) and rendering the table. But try as I might I cannot make this working on 4.3.3.Final where you claim this should work (obviously it does not work on 4.3.x either). I even tried using differently annotated beans (managed, session or view scoped) but with no effect. Therefore so far, this seems to be a bug but not a regression. If you really got this working on 4.3.3 I wonder if you would have a working sample to show. Until then I am removing the regression label. Also I will write a test for this issue so we are able to resolve this problem. > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From issues at jboss.org Thu Dec 12 11:22:33 2013 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Dec 2013 11:22:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13230: ------------------------------- Labels: (was: regression) > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From issues at jboss.org Thu Dec 12 11:28:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:28:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930846#comment-12930846 ] Luk?? Fry? commented on RF-13248: --------------------------------- Some smoke tests still fails on WildFly 8.0, thus I'm postponing a switch to WildFly 8.0 as a default container. Feature branch: https://github.com/richfaces/richfaces/tree/RF-13248-smoke-tests-on-wildfly80 > Switch RichFaces smoke tests to run on WildFly 8 by default > ----------------------------------------------------------- > > Key: RF-13248 > URL: https://issues.jboss.org/browse/RF-13248 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means: > * tweaking TravisCI configuration > Note that tests have problem to pass on WildFly Beta1: > {code} > Tests run: 34, Failures: 1, Errors: 16, Skipped: 1 > {code} > so we need to analyze a cause of the failure first. -- 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 From issues at jboss.org Thu Dec 12 11:30:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13437) contextMenu: support hiding by clicking outside only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13437: ------------------------------- Fix Version/s: 5-Tracking > contextMenu: support hiding by clicking outside only > ---------------------------------------------------- > > Key: RF-13437 > URL: https://issues.jboss.org/browse/RF-13437 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Lutz Ulrich > Priority: Minor > Fix For: 5-Tracking > > > Currently (until version 4.3.4), context menus always disappear when the mouse cursor is moved outside the menu. It should be possible to restrict hiding the menu when the user clicks somewhere else, like in many other applications, like Windows Explorer. > I was able to achieve this behavior by unbinding the event handler for mouseleave via extra scripting. > {{RichFaces.Event.unbindById(menu.id, 'mouseleave');}} > (Note that the code only prevents hiding the main menu on mouseleave. > Sub-menus / menuGroups are still closed on mouseleave.) > But it would be better if the contextMenu would support an attribute for turning on 'hide by outside click only'. > -- 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 From issues at jboss.org Thu Dec 12 11:30:32 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13432) Upgrade framework build to JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated RF-13432: ---------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Upgrade framework build to JSF 2.2 > ---------------------------------- > > Key: RF-13432 > URL: https://issues.jboss.org/browse/RF-13432 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > -- 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 From issues at jboss.org Thu Dec 12 11:30:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13437) contextMenu: support hiding by clicking outside only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930847#comment-12930847 ] Brian Leathem commented on RF-13437: ------------------------------------ A reasonable request. Thanks for taking the time to fill out a Feature request jira. > contextMenu: support hiding by clicking outside only > ---------------------------------------------------- > > Key: RF-13437 > URL: https://issues.jboss.org/browse/RF-13437 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu > Reporter: Lutz Ulrich > Priority: Minor > Fix For: 5-Tracking > > > Currently (until version 4.3.4), context menus always disappear when the mouse cursor is moved outside the menu. It should be possible to restrict hiding the menu when the user clicks somewhere else, like in many other applications, like Windows Explorer. > I was able to achieve this behavior by unbinding the event handler for mouseleave via extra scripting. > {{RichFaces.Event.unbindById(menu.id, 'mouseleave');}} > (Note that the code only prevents hiding the main menu on mouseleave. > Sub-menus / menuGroups are still closed on mouseleave.) > But it would be better if the contextMenu would support an attribute for turning on 'hide by outside click only'. > -- 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 From issues at jboss.org Thu Dec 12 11:30:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:30:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13436: ------------------------------- Fix Version/s: 5-Tracking > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13436 > URL: https://issues.jboss.org/browse/RF-13436 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Labels: rich_editor > Fix For: 5-Tracking > > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- 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 From issues at jboss.org Thu Dec 12 11:30:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:30:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13432) Upgrade framework build to JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? resolved RF-13432. ----------------------------- Resolution: Done https://github.com/richfaces/richfaces/commit/4437b869f325c54f43023be8f1de9513c3ea45b9 > Upgrade framework build to JSF 2.2 > ---------------------------------- > > Key: RF-13432 > URL: https://issues.jboss.org/browse/RF-13432 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > -- 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 From issues at jboss.org Thu Dec 12 11:30:33 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 12 Dec 2013 11:30:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13432) Upgrade framework build to JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned RF-13432: ------------------------------- Assignee: Luk?? Fry? > Upgrade framework build to JSF 2.2 > ---------------------------------- > > Key: RF-13432 > URL: https://issues.jboss.org/browse/RF-13432 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 5.0.0.Alpha3 > > -- 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 From issues at jboss.org Thu Dec 12 11:34:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:34:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13434: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} but all archetypes use the old one. -- 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 From issues at jboss.org Thu Dec 12 11:36:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930852#comment-12930852 ] Brian Leathem commented on RF-13435: ------------------------------------ No, that's fine, thanks [~wlh]. Thanks for the clarification. > extendedatatable: Scrolling position is lost after submit > --------------------------------------------------------- > > Key: RF-13435 > URL: https://issues.jboss.org/browse/RF-13435 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: extendeddatatable, richfaces, scroll > > Issue is similar to RF-5312. > In EDT, the current scrolling position is lost (reset to 0) after a submit. > Steps to reproduce: > 1. Use the showcase for the EDT(version 4.3.4) > 2. Adapt the xhtml file by adding a simple submit button ( ) > 3. Activate the 'ajax loading' checkbox > 4. Scroll down in the table > 5. Press the new submit button > 6. The scrolling position is lost > This might sound as a minor problem, but in case of using the EDT with ajax data loading, a user can scroll quite far until he may find the row on which he wants to do some actions. If the scrolling position is reset to 0 after each submit, it gets quite tedious for a user scrolling every time to this old position in the table. > I've seen that the current position is already stored in componentState, but unfortunately it is getting reset on submit. > I already tried a workaround, by using the 'onready' event of the EDT after a submit to trigger scrolling to the desired position with javascript but this does not work reliably on one hand, and triggers an additional ajax call which may cause that messages in h:messages are lost. -- 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 From issues at jboss.org Thu Dec 12 11:36:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13434: ---------------------------------- Assignee: Brian Leathem > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} but all archetypes use the old one. -- 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 From issues at jboss.org Thu Dec 12 11:36:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 11:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13435: ------------------------------- Fix Version/s: 5-Tracking > extendedatatable: Scrolling position is lost after submit > --------------------------------------------------------- > > Key: RF-13435 > URL: https://issues.jboss.org/browse/RF-13435 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: extendeddatatable, richfaces, scroll > Fix For: 5-Tracking > > > Issue is similar to RF-5312. > In EDT, the current scrolling position is lost (reset to 0) after a submit. > Steps to reproduce: > 1. Use the showcase for the EDT(version 4.3.4) > 2. Adapt the xhtml file by adding a simple submit button ( ) > 3. Activate the 'ajax loading' checkbox > 4. Scroll down in the table > 5. Press the new submit button > 6. The scrolling position is lost > This might sound as a minor problem, but in case of using the EDT with ajax data loading, a user can scroll quite far until he may find the row on which he wants to do some actions. If the scrolling position is reset to 0 after each submit, it gets quite tedious for a user scrolling every time to this old position in the table. > I've seen that the current position is already stored in componentState, but unfortunately it is getting reset on submit. > I already tried a workaround, by using the 'onready' event of the EDT after a submit to trigger scrolling to the desired position with javascript but this does not work reliably on one hand, and triggers an additional ajax call which may cause that messages in h:messages are lost. -- 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 From issues at jboss.org Thu Dec 12 12:04:32 2013 From: issues at jboss.org (H G (JIRA)) Date: Thu, 12 Dec 2013 12:04:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930871#comment-12930871 ] H G commented on RF-13282: -------------------------- I posted in the forum, this is the thread https://community.jboss.org/thread/235296. This is JSF main bug and probably is the root of multiple RF reported and unreported issues related to render second form. > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Thu Dec 12 12:52:32 2013 From: issues at jboss.org (H G (JIRA)) Date: Thu, 12 Dec 2013 12:52:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13282) Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930900#comment-12930900 ] H G commented on RF-13282: -------------------------- I think the most closest bug is https://issues.jboss.org/browse/RF-10963 > Port the RichFaces 4.3.4 fixes to RichFaces 4.5/5.0 > --------------------------------------------------- > > Key: RF-13282 > URL: https://issues.jboss.org/browse/RF-13282 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- 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 From issues at jboss.org Thu Dec 12 13:26:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 13:26:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-10956) Archetypes: GAE archetype references missing taglib resource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-10956. -------------------------------- Fix Version/s: (was: 5-Future) Resolution: Won't Fix The GAE Archetype is no longer being maintained. > Archetypes: GAE archetype references missing taglib resource > ------------------------------------------------------------ > > Key: RF-10956 > URL: https://issues.jboss.org/browse/RF-10956 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.0.0.Final > Reporter: Nick Belaevski > > See details on forum. -- 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 From issues at jboss.org Thu Dec 12 13:30:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 13:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13429) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13429: ------------------------------- Summary: archetypes: change the namespace of richfaces components (was: archetype kitchensink-test throws exception) > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13429 > URL: https://issues.jboss.org/browse/RF-13429 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Environment: EAP 6.1 > Reporter: Matej Novotny > Fix For: 5.0.0.Alpha2 > > > This is an issue which originated from RFPL-3074. > Kitchensink does not work at all, when deployed and accessed from desktop (tested on EAP 6.1) there is an exception in server console. > When accessed from mobile no exception is thrown, however the content is not visible. > {code} > 16:26:14,109 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/kitchensink-test].[FacesServlet]] (http-/0.0.0.0:8080-6) JBWEB000236: Servlet.service() for servlet FacesServlet threw exception: javax.el.ELException: JBWEB006009: Function ''r:component'' not found > at org.apache.el.lang.ExpressionBuilder.visit(ExpressionBuilder.java:209) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.parser.SimpleNode.accept(SimpleNode.java:148) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.prepare(ExpressionBuilder.java:166) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:184) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:226) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:68) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.weld.util.el.ForwardingExpressionFactory.createValueExpression(ForwardingExpressionFactory.java:49) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > at org.jboss.weld.el.WeldExpressionFactory.createValueExpression(WeldExpressionFactory.java:50) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > at com.sun.faces.facelets.el.ELText$ELTextVariable.apply(ELText.java:203) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.el.ELText$ELTextComposite.apply(ELText.java:184) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.AttributeInstruction.apply(AttributeInstruction.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.UIInstructionHandler.apply(UIInstructionHandler.java:141) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:164) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:902) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [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.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.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 From issues at jboss.org Thu Dec 12 13:30:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 13:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13434) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13434. -------------------------------- Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Duplicate Issue > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13434 > URL: https://issues.jboss.org/browse/RF-13434 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Priority: Critical > > After RF-13143 the namespace of RF 5 components has changed to {{http://richfaces.org}} but all archetypes use the old one. -- 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 From issues at jboss.org Thu Dec 12 13:30:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 13:30:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13430) archetype simpleapp warning message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13430. -------------------------------- Fix Version/s: (was: 5.0.0.Alpha2) Resolution: Duplicate Issue > archetype simpleapp warning message > ----------------------------------- > > Key: RF-13430 > URL: https://issues.jboss.org/browse/RF-13430 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Environment: EAP 6.1 > Firefox > Reporter: Matej Novotny > > This issue originated from RFPL-3074. > There is a small issue that simpleapp archetype displays warning when accessed for the first time after deployment. This happens for both, desktop and mobile version. > {code:xml} > Warning: This page calls for XML namespace http://richfaces.org/rich declared with prefix r but no taglibrary exists for that namespace. > {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 From issues at jboss.org Thu Dec 12 14:40:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 14:40:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13429) archetypes: change the namespace of richfaces components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13429. -------------------------------- Assignee: Brian Leathem Resolution: Done > archetypes: change the namespace of richfaces components > -------------------------------------------------------- > > Key: RF-13429 > URL: https://issues.jboss.org/browse/RF-13429 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha2 > Environment: EAP 6.1 > Reporter: Matej Novotny > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > This is an issue which originated from RFPL-3074. > Kitchensink does not work at all, when deployed and accessed from desktop (tested on EAP 6.1) there is an exception in server console. > When accessed from mobile no exception is thrown, however the content is not visible. > {code} > 16:26:14,109 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/kitchensink-test].[FacesServlet]] (http-/0.0.0.0:8080-6) JBWEB000236: Servlet.service() for servlet FacesServlet threw exception: javax.el.ELException: JBWEB006009: Function ''r:component'' not found > at org.apache.el.lang.ExpressionBuilder.visit(ExpressionBuilder.java:209) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.parser.SimpleNode.accept(SimpleNode.java:148) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.prepare(ExpressionBuilder.java:166) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:184) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:226) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:68) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.weld.util.el.ForwardingExpressionFactory.createValueExpression(ForwardingExpressionFactory.java:49) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > at org.jboss.weld.el.WeldExpressionFactory.createValueExpression(WeldExpressionFactory.java:50) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > at com.sun.faces.facelets.el.ELText$ELTextVariable.apply(ELText.java:203) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.el.ELText$ELTextComposite.apply(ELText.java:184) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.AttributeInstruction.apply(AttributeInstruction.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.UIInstructionHandler.apply(UIInstructionHandler.java:141) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:164) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:902) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [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.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.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 From issues at jboss.org Thu Dec 12 15:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 15:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13226) Restoring table sorting on extendedDataTable does not work when a dataScroller is present In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13226: ------------------------------- Summary: Restoring table sorting on extendedDataTable does not work when a dataScroller is present (was: Restoring table sorting on extendedDataTable does not work) > Restoring table sorting on extendedDataTable does not work when a dataScroller is present > ----------------------------------------------------------------------------------------- > > Key: RF-13226 > URL: https://issues.jboss.org/browse/RF-13226 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Labels: extendedDataTable > Fix For: 5-Tracking > > > If you persist the table state of a rich:extendedDataTable the sorting order is not restored when you reload the page if the extendedDataTable has a rich:dataScroller. > However when you use the dataScroller to go to the 2nd page and then back to the 1st page the sorting is correct again. > > This causes a second problem (which I haven't managed to isolate yet) that actions in the table (e.g. calling an action method and passing in the column var) does not work. Please note this does work in the example code below, but not in our real live table. If I go to the 2nd page all links in that table work. > See https://community.jboss.org/thread/232647 -- 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 From issues at jboss.org Thu Dec 12 15:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 15:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13230: ------------------------------- Fix Version/s: 5-Tracking (was: 4.3.5) > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Fix For: 5-Tracking > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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 From issues at jboss.org Thu Dec 12 15:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 15:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13431) Rename JavaScript closures which references to RichFaces object to rf in pickList resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13431: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Rename JavaScript closures which references to RichFaces object to rf in pickList resources > ------------------------------------------------------------------------------------------- > > Key: RF-13431 > URL: https://issues.jboss.org/browse/RF-13431 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > > Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. > However, resources for {{pickList}} were omitted: > * ordering-list-bridge.js > * pick-list-bridge.js > Please consider also [this|https://issues.jboss.org/browse/RF-13147?focusedCommentId=12929950&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12929950] comment, when resolving this issue - using of window object reference -- 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 From issues at jboss.org Thu Dec 12 15:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 15:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13431) Rename JavaScript closures which references to RichFaces object to rf in pickList resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13431: ------------------------------- Component/s: component-selects (was: component) > Rename JavaScript closures which references to RichFaces object to rf in pickList resources > ------------------------------------------------------------------------------------------- > > Key: RF-13431 > URL: https://issues.jboss.org/browse/RF-13431 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj H?ska > Fix For: 5.0.0.Alpha3 > > > Almost all occurrences of JS closures which references to RichFaces object were renamed to rf - with resolving RF-13147. > However, resources for {{pickList}} were omitted: > * ordering-list-bridge.js > * pick-list-bridge.js > Please consider also [this|https://issues.jboss.org/browse/RF-13147?focusedCommentId=12929950&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12929950] comment, when resolving this issue - using of window object reference -- 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 From issues at jboss.org Thu Dec 12 15:10:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 15:10:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13433) extendeddatatable: Column resizing and column reordering not working for RTL languages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13433: ------------------------------- Fix Version/s: 5-Tracking > extendeddatatable: Column resizing and column reordering not working for RTL languages > -------------------------------------------------------------------------------------- > > Key: RF-13433 > URL: https://issues.jboss.org/browse/RF-13433 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: richfaces > Fix For: 5-Tracking > > > For the extendeddatatable column resizing and column reordering are not working correctly for RTL (right-to-left) languages. > a) Column resizing > In case you try to increase the width of one column, RF does in fact decrease the width of the left side neighbor column. In case of decreasing the width, RF increases the width of the neighbor. > b) Column reordering > When dragging a column to a new position an arrow is shown at the place where it is intended to be inserted. However, after releasing the mouse, the columns is inserted at another place. > In case you cannot fix these issues soon, please provide at least the > possibility to disable columns reordering. > Column resizing can be disabled by CSS. -- 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 From issues at jboss.org Thu Dec 12 16:02:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 16:02:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-9557) TabPanel: scrolling of tabs and popup list for choosing implementation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-9557. ------------------------------- Fix Version/s: (was: 5-Future) Resolution: Incomplete Description > TabPanel: scrolling of tabs and popup list for choosing implementation > ---------------------------------------------------------------------- > > Key: RF-9557 > URL: https://issues.jboss.org/browse/RF-9557 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Ilya Shaikovsky > > not implemented in M4. feature moved to next iterations. -- 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 From issues at jboss.org Thu Dec 12 20:02:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 20:02:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13438) Update jboss-parent In-Reply-To: References: Message-ID: Brian Leathem created RF-13438: ---------------------------------- Summary: Update jboss-parent Key: RF-13438 URL: https://issues.jboss.org/browse/RF-13438 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 5.0.0.Alpha3 -- 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 From issues at jboss.org Thu Dec 12 20:04:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 20:04:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13438) Update jboss-parent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13438: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Update jboss-parent > ------------------- > > Key: RF-13438 > URL: https://issues.jboss.org/browse/RF-13438 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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 From issues at jboss.org Thu Dec 12 20:04:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 20:04:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13438) Update jboss-parent In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13438. -------------------------------- Resolution: Done > Update jboss-parent > ------------------- > > Key: RF-13438 > URL: https://issues.jboss.org/browse/RF-13438 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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 From issues at jboss.org Thu Dec 12 20:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Dec 2013 20:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931003#comment-12931003 ] Brian Leathem commented on RF-13317: ------------------------------------ [~lfryc] have you yet pushed your changes to github? Can you link to the branch here? I see this branch: > https://github.com/richfaces/richfaces/tree/RF-13317-jsf22-view-state-update However the last commit there is for the PoC workaround with the com.sun class. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Fri Dec 13 08:18:33 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 08:18:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13257) PhotoAlbum bugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13257. -------------------------------- Resolution: Done > PhotoAlbum bugs > --------------- > > Key: RF-13257 > URL: https://issues.jboss.org/browse/RF-13257 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Fix For: 4.3.5 > > > PhotoAlbum 4.3.x known bugs: > * uploading file to album (image isn't saved to DB) > * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog) -- 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 From issues at jboss.org Fri Dec 13 08:28:32 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 08:28:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13439) Photoalbum - update help section In-Reply-To: References: Message-ID: Michal Petrov created RF-13439: ---------------------------------- Summary: Photoalbum - update help section Key: RF-13439 URL: https://issues.jboss.org/browse/RF-13439 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 4.3.4 Reporter: Michal Petrov Assignee: Michal Petrov * The help stylesheets link to docbook resources that were removed from RF. * The help popups need updating ** The code and the pictures may not display the current state of the app ** New popups for the social integration should probably be added. -- 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 From issues at jboss.org Fri Dec 13 08:28:32 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 08:28:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13439) Photoalbum - update help section In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13439: ------------------------------- Fix Version/s: 4.3.5 > Photoalbum - update help section > -------------------------------- > > Key: RF-13439 > URL: https://issues.jboss.org/browse/RF-13439 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > > * The help stylesheets link to docbook resources that were removed from RF. > * The help popups need updating > ** The code and the pictures may not display the current state of the app > ** New popups for the social integration should probably be added. -- 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 From issues at jboss.org Fri Dec 13 08:36:32 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 08:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13440) Photoalbum - fix packing of resources In-Reply-To: References: Message-ID: Michal Petrov created RF-13440: ---------------------------------- Summary: Photoalbum - fix packing of resources Key: RF-13440 URL: https://issues.jboss.org/browse/RF-13440 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha1 Reporter: Michal Petrov The resource plugin configuration needs to be updated to work with the changes done to RF 5 resources. -- 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 From issues at jboss.org Fri Dec 13 10:04:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 10:04:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13439) Photoalbum - update help section In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931152#comment-12931152 ] Brian Leathem commented on RF-13439: ------------------------------------ {quote} The help stylesheets link to docbook resources that were removed from RF {quote} What's the consequence of this? Are we missing content, or just images? As we resolve this, we should have the goal of making the photoalbum examples self-contained. > Photoalbum - update help section > -------------------------------- > > Key: RF-13439 > URL: https://issues.jboss.org/browse/RF-13439 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > > * The help stylesheets link to docbook resources that were removed from RF. > * The help popups need updating > ** The code and the pictures may not display the current state of the app > ** New popups for the social integration should probably be added. -- 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 From issues at jboss.org Fri Dec 13 10:06:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 10:06:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13440) Photoalbum - fix packing of resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931155#comment-12931155 ] Brian Leathem commented on RF-13440: ------------------------------------ Thanks for reporting this [~mpetrov]. Just to make sure we are on the same page: let's hold off on the RF 5 photoalbum fixes for now and focus on the RF 4 version. > Photoalbum - fix packing of resources > ------------------------------------- > > Key: RF-13440 > URL: https://issues.jboss.org/browse/RF-13440 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Michal Petrov > > The resource plugin configuration needs to be updated to work with the changes done to RF 5 resources. -- 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 From issues at jboss.org Fri Dec 13 10:26:32 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 10:26:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13439) Photoalbum - update help section In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931163#comment-12931163 ] Michal Petrov commented on RF-13439: ------------------------------------ There are some images missing, like [here|https://github.com/richfaces4/dev-examples/blob/master/photoalbum/src/main/webapp/resources/stylesheet/help/documentation.css#L215]. But I've looked at the RF3 demo and the image isn't there either so I don't really know where it was supposed to come from. > Photoalbum - update help section > -------------------------------- > > Key: RF-13439 > URL: https://issues.jboss.org/browse/RF-13439 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > > * The help stylesheets link to docbook resources that were removed from RF. > * The help popups need updating > ** The code and the pictures may not display the current state of the app > ** New popups for the social integration should probably be added. -- 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 From issues at jboss.org Fri Dec 13 10:38:33 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Dec 2013 10:38:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13440) Photoalbum - fix packing of resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931174#comment-12931174 ] Michal Petrov commented on RF-13440: ------------------------------------ (It's @michpetrov) I'm working on RF4, I was just comparing the two versions after merge and found this. > Photoalbum - fix packing of resources > ------------------------------------- > > Key: RF-13440 > URL: https://issues.jboss.org/browse/RF-13440 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Michal Petrov > > The resource plugin configuration needs to be updated to work with the changes done to RF 5 resources. -- 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 From issues at jboss.org Fri Dec 13 10:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 10:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13440) Photoalbum - fix packing of resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931181#comment-12931181 ] Brian Leathem commented on RF-13440: ------------------------------------ {quote} (It's @michpetrov) {quote} lol - thanks! {quote} I'm working on RF4, I was just comparing the two versions after merge and found this. {quote} +1 - just making sure. > Photoalbum - fix packing of resources > ------------------------------------- > > Key: RF-13440 > URL: https://issues.jboss.org/browse/RF-13440 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Michal Petrov > > The resource plugin configuration needs to be updated to work with the changes done to RF 5 resources. -- 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 From issues at jboss.org Fri Dec 13 12:48:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:48:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13317: ------------------------------- Fix Version/s: (was: 4.3.5) > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13247: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Priority: Minor > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13397: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > a4j:push not working with Internet Explorer >= 10 > ------------------------------------------------- > > Key: RF-13397 > URL: https://issues.jboss.org/browse/RF-13397 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.4 > Environment: Any where Internet Explorer 10 or above is available > Reporter: Tobias Seppenhauser > Labels: richfaces > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. > Unfortunately I can't see any error in the Javascript console. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13358) rich:panelMenuGroup allowing actions executions even if originally disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13358: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > rich:panelMenuGroup allowing actions executions even if originally disabled > --------------------------------------------------------------------------- > > Key: RF-13358 > URL: https://issues.jboss.org/browse/RF-13358 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.4 > Environment: Linux, AS 7.1.1 Brontes, FF 25 with FireBug addOn > Reporter: Pavel Slegr > Assignee: Pavel Slegr > Priority: Critical > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > related to https://issues.jboss.org/browse/RF-12813 > This can be possibly a security hole, as the second component piece is discovered to allow tampering actions through JS. > I suggest to try out on other components as well !!! > with following example > {code} > { > > > > > > > > } > {code} > the group43 element is intended to be disabled and thus not allowing any actions execution on it > Once tampered with > {code} > { > new RichFaces.ui.PanelMenuGroup("f:group43",{"collapseEvent":"click","unselectable":false,"selectable":false,"name":"group43","ajax":{"incId":"1"} ,"stylePrefix":"rf\u002Dpm\u002Dgr","expanded":false,"expandEvent":"click","disabled":false,"mode":"client"} ) > } > {code} > It is possible to expand the group and execute further actions on its children elements -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and Warp in 4.3 branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13310: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Upgrade Graphene and Warp in 4.3 branch > --------------------------------------- > > Key: RF-13310 > URL: https://issues.jboss.org/browse/RF-13310 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.5 > Reporter: Luk?? Fry? > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue. > Why we want to upgrade: > * Graphene = Final version API changes changes > * Warp = ease of debugging > I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik. -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13298) Richfaces BOM manages a non Maven Central dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13298: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Richfaces BOM manages a non Maven Central dependency > ---------------------------------------------------- > > Key: RF-13298 > URL: https://issues.jboss.org/browse/RF-13298 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.2, 4.3.3, 4.3.4 > Reporter: Rafael Benevides > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Richfaces BOMs http://repo1.maven.org/maven2/org/richfaces/richfaces-bom/4.3.4.Final/richfaces-bom-4.3.4.Final.pom manages the following GAV: > org.richfaces.ui.common:richfaces-ui-common-api:${version.richfaces} which is not present on Maven Central ( http://search.maven.org/#search%7Cga%7C1%7Crichfaces-ui-common-api ) > BOM should have this scope changed or declare a https://repository.jboss.org/nexus repository -- 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 From issues at jboss.org Fri Dec 13 12:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13358) rich:panelMenuGroup allowing actions executions even if originally disabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13358: ------------------------------- Original Estimate: 1 hour (was: 30 minutes) Remaining Estimate: 1 hour (was: 30 minutes) > rich:panelMenuGroup allowing actions executions even if originally disabled > --------------------------------------------------------------------------- > > Key: RF-13358 > URL: https://issues.jboss.org/browse/RF-13358 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.4 > Environment: Linux, AS 7.1.1 Brontes, FF 25 with FireBug addOn > Reporter: Pavel Slegr > Assignee: Pavel Slegr > Priority: Critical > Fix For: 4.3.5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > related to https://issues.jboss.org/browse/RF-12813 > This can be possibly a security hole, as the second component piece is discovered to allow tampering actions through JS. > I suggest to try out on other components as well !!! > with following example > {code} > { > > > > > > > > } > {code} > the group43 element is intended to be disabled and thus not allowing any actions execution on it > Once tampered with > {code} > { > new RichFaces.ui.PanelMenuGroup("f:group43",{"collapseEvent":"click","unselectable":false,"selectable":false,"name":"group43","ajax":{"incId":"1"} ,"stylePrefix":"rf\u002Dpm\u002Dgr","expanded":false,"expandEvent":"click","disabled":false,"mode":"client"} ) > } > {code} > It is possible to expand the group and execute further actions on its children elements -- 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 From issues at jboss.org Fri Dec 13 12:50:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:50:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 13 12:52:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13266: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Fri Dec 13 12:52:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13252) a4j:ajax includes jsf.js script twice In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13252: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > a4j:ajax includes jsf.js script twice > ------------------------------------- > > Key: RF-13252 > URL: https://issues.jboss.org/browse/RF-13252 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Reporter: Jon?? Trantina > Fix For: 4.3.5 > > Attachments: reproducer.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When a4j:script is used in the page like so: > {noformat} > > > > {noformat} > Then two script tags pointing to jsf.js are added to the page, once in the head by the inclusion of @ResourceDependency [1], and once again by Overriding the ClientBehaviorRenderer#getScript method [2,3]. > Note, that according to Brian, resolving this without introducing any functional regressions may require the resolution of RF-12270 [4]. > [1] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L53 > [2] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L123 > [3] https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/java/javax/faces/render/ClientBehaviorRenderer.java#L95 > [4] https://issues.jboss.org/browse/RF-12270 -- 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 From issues at jboss.org Fri Dec 13 12:52:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 12:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13220) Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13220: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Quickstart - Remove references to AS 7.1 in the RichFaces quickstarts > --------------------------------------------------------------------- > > Key: RF-13220 > URL: https://issues.jboss.org/browse/RF-13220 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Assignee: Vineet Reynolds > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The readme files provide instruction on how to run quickstarts on both AS 7.1 and EAP 6. Quickstarts now target EAP 6.1, so we need to remove references to AS 7.1. -- 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 From issues at jboss.org Fri Dec 13 13:06:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 13:06:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13397: ------------------------------- Sprint: (was: RichFaces 4.3.5 Sprint 1) > a4j:push not working with Internet Explorer >= 10 > ------------------------------------------------- > > Key: RF-13397 > URL: https://issues.jboss.org/browse/RF-13397 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.4 > Environment: Any where Internet Explorer 10 or above is available > Reporter: Tobias Seppenhauser > Labels: richfaces > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. > Unfortunately I can't see any error in the Javascript console. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky -- 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 From issues at jboss.org Fri Dec 13 13:06:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 13:06:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13266: ------------------------------- Original Estimate: 2 hours (was: 1 hour) Remaining Estimate: 2 hours (was: 1 hour) > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Fri Dec 13 13:06:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 13:06:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Original Estimate: 2 hours (was: 1 hour) Remaining Estimate: 2 hours (was: 1 hour) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 13 13:06:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 13:06:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13247: ---------------------------------- Assignee: Brian Leathem > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Fri Dec 13 13:08:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 13:08:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13364: ---------------------------------- Assignee: Brian Leathem > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From issues at jboss.org Fri Dec 13 18:06:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 18:06:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931315#comment-12931315 ] Brian Leathem commented on RF-13247: ------------------------------------ Upgrading from to Guava 15 requires migrating from MapMaker to CacheBuilder. This is fairly straightforward as described in the article: https://code.google.com/p/guava-libraries/wiki/MapMakerMigration After performing the migration I am getting a build-time failure, despite synchornizing the guava (and sisu-guice) libraries between the CDK and the framework: {code} [ERROR] Failed to execute goal org.richfaces.cdk:maven-richfaces-resources-plugin:4.3.5-SNAPSHOT:process (packed-resources) on project static-resources: Execution packed-resources of goal org.richfaces.cdk:maven-richfaces-resources-plugin:4.3.5-SNAPSHOT:process failed: An API incompatibility was encountered while executing org.richfaces.cdk:maven-richfaces-resources-plugin:4.3.5-SNAPSHOT:process: java.lang.NoSuchMethodError: com.google.common.cache.CacheBuilder.build(Lcom/google/common/cache/CacheLoader;)Lcom/google/common/cache/LoadingCache; [ERROR] ----------------------------------------------------- [ERROR] realm = plugin>org.richfaces.cdk:maven-richfaces-resources-plugin:4.3.5-SNAPSHOT [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/home/bleathem/.m2/repository/org/richfaces/cdk/maven-richfaces-resources-plugin/4.3.5-SNAPSHOT/maven-richfaces-resources-plugin-4.3.5-SNAPSHOT.jar [ERROR] urls[1] = file:/home/bleathem/.m2/repository/org/sonatype/sisu/sisu-inject-bean/2.3.0/sisu-inject-bean-2.3.0.jar [ERROR] urls[2] = file:/home/bleathem/.m2/repository/org/sonatype/sisu/sisu-guice/3.1.0/sisu-guice-3.1.0-no_aop.jar [ERROR] urls[3] = file:/home/bleathem/.m2/repository/org/sonatype/sisu/sisu-guava/0.9.9/sisu-guava-0.9.9.jar [ERROR] urls[4] = file:/home/bleathem/.m2/repository/org/sonatype/aether/aether-util/1.13.1/aether-util-1.13.1.jar [ERROR] urls[5] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar [ERROR] urls[6] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar [ERROR] urls[7] = file:/home/bleathem/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar [ERROR] urls[8] = file:/home/bleathem/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar [ERROR] urls[9] = file:/home/bleathem/.m2/repository/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar [ERROR] urls[10] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-11/plexus-archiver-1.0-alpha-11.jar [ERROR] urls[11] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-3/plexus-io-1.0-alpha-3.jar [ERROR] urls[12] = file:/home/bleathem/.m2/repository/org/apache/maven/shared/file-management/1.2.1/file-management-1.2.1.jar [ERROR] urls[13] = file:/home/bleathem/.m2/repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar [ERROR] urls[14] = file:/home/bleathem/.m2/repository/junit/junit/4.8.2/junit-4.8.2.jar [ERROR] urls[15] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar [ERROR] urls[16] = file:/home/bleathem/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.2/plexus-velocity-1.1.2.jar [ERROR] urls[17] = file:/home/bleathem/.m2/repository/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.jar [ERROR] urls[18] = file:/home/bleathem/.m2/repository/commons-collections/commons-collections/2.0/commons-collections-2.0.jar [ERROR] urls[19] = file:/home/bleathem/.m2/repository/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar [ERROR] urls[20] = file:/home/bleathem/.m2/repository/velocity/velocity/1.4/velocity-1.4.jar [ERROR] urls[21] = file:/home/bleathem/.m2/repository/velocity/velocity-dep/1.4/velocity-dep-1.4.jar [ERROR] urls[22] = file:/home/bleathem/.m2/repository/org/reflections/reflections/0.9.5/reflections-0.9.5.jar [ERROR] urls[23] = file:/home/bleathem/.m2/repository/javassist/javassist/3.12.1.GA/javassist-3.12.1.GA.jar [ERROR] urls[24] = file:/home/bleathem/.m2/repository/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.jar [ERROR] urls[25] = file:/home/bleathem/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar [ERROR] urls[26] = file:/home/bleathem/.m2/repository/com/google/guava/guava/15.0/guava-15.0.jar [ERROR] urls[27] = file:/home/bleathem/.m2/repository/javax/el/el-api/1.0/el-api-1.0.jar [ERROR] urls[28] = file:/home/bleathem/.m2/repository/com/sun/el/el-ri/1.0/el-ri-1.0.jar [ERROR] urls[29] = file:/home/bleathem/workspace/richfaces/richfaces4/core/impl/target/richfaces-core-impl-4.3.5-SNAPSHOT.jar [ERROR] urls[30] = file:/home/bleathem/workspace/richfaces/richfaces4/core/api/target/richfaces-core-api-4.3.5-SNAPSHOT.jar [ERROR] urls[31] = file:/home/bleathem/.m2/repository/net/sourceforge/cssparser/cssparser/0.9.5/cssparser-0.9.5.jar [ERROR] urls[32] = file:/home/bleathem/.m2/repository/org/w3c/css/sac/1.3/sac-1.3.jar [ERROR] urls[33] = file:/home/bleathem/.m2/repository/com/yahoo/platform/yui/yuicompressor/2.3.6/yuicompressor-2.3.6.jar [ERROR] urls[34] = file:/home/bleathem/.m2/repository/org/glassfish/javax.faces/2.1.19/javax.faces-2.1.19.jar [ERROR] Number of foreign imports: 1 [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]] [ERROR] [ERROR] ----------------------------------------------------- [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :static-resources {code} > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Fri Dec 13 20:16:35 2013 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Dec 2013 20:16:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931321#comment-12931321 ] Luk?? Fry? commented on RF-13317: --------------------------------- Here is the updated branch: https://github.com/richfaces/richfaces/tree/RF-13317-jsf22-view-state-update Still I haven't re-implemented functionality under {{ExtendedPartialViewContextImpl#RenderVisitCallback}}, which specifically addresses meta component rendering. I'm not sure yet where to re-connect meta-component rendering to Mojarra's {{PartialViewContextImpl}} without rewriting {{processPartial}} method. It's possible that we will need to wrap this method, call its super implementation and then render meta components. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Priority: Critical > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I'm using several {{}} fields in a {{}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/nonav/docs/2.2/javadocs/javax/faces/render/ResponseStateManager.html#VIEW_STATE_PARAM] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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 From issues at jboss.org Fri Dec 13 21:22:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 21:22:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931325#comment-12931325 ] Brian Leathem commented on RF-13247: ------------------------------------ Upgrading {{version.maven-core}} to 3.1.1 gets past the above error, but introduces a new one. This issue is out of scope for 4.3.5. We'll investigate a fix in RichFaces 5 and backport as appropriate. > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.5 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Fri Dec 13 21:22:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 21:22:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13247: ------------------------------- Fix Version/s: 5-Tracking (was: 4.3.5) > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Assignee: Brian Leathem > Priority: Minor > Fix For: 5-Tracking > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Fri Dec 13 21:22:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Dec 2013 21:22:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13247: ------------------------------- Original Estimate: 2 hours (was: 15 minutes) Remaining Estimate: 2 hours (was: 15 minutes) > Upgrade the RichFaces guava dependency to version 15.0 > ------------------------------------------------------ > > Key: RF-13247 > URL: https://issues.jboss.org/browse/RF-13247 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Jeremy Landis > Assignee: Brian Leathem > Priority: Minor > Fix For: 5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue. > Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl -- 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 From issues at jboss.org Mon Dec 16 07:16:36 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 16 Dec 2013 07:16:36 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak resolved RF-13250. -------------------------------- Resolution: Cannot Reproduce Bug Resolving because I cannot reproduce. Please feel free to reopen as soon as you have some additional information for reproducing. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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 From issues at jboss.org Mon Dec 16 10:00:38 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 16 Dec 2013 10:00:38 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13441) contextMenu - when showEvent is dblclick then context menu disappear after invoking In-Reply-To: References: Message-ID: Juraj H?ska created RF-13441: -------------------------------- Summary: contextMenu - when showEvent is dblclick then context menu disappear after invoking Key: RF-13441 URL: https://issues.jboss.org/browse/RF-13441 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 5.0.0.Alpha2 Environment: * RichFaces 5.0.0-SNAPSHOT * Metamer 5.0.0-SNAPSHOT * JBoss Application Server: Weld Integration 7.1.1.Final * JBoss AS 7.1.1.Final * OpenJDK Runtime Environment 1.7.0_45-mockbuild_2013_10_16_17_47-b00 @ Linux * Chrome 30.0.1599.114 @ Linux x86_64, Firefox Reporter: Juraj H?ska Please see steps to reproduce this issue. It is not a regression. It did not work in e.g. 4.3.3. neither. -- 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 From issues at jboss.org Mon Dec 16 10:02:33 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 16 Dec 2013 10:02:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13441) contextMenu - when showEvent is dblclick then context menu disappear after invoking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13441: ----------------------------- Steps to Reproduce: # deploy Metamer and load: http://localhost:8080/metamer/faces/components/richContextMenu/simple.xhtml # setup {{showEvent}} to _dblclick_ # make double click on the targetPanel1 (the green one) # see that contextMenu is displayed but subsequently disappears was: # deploy Metamer and load: http://localhost:8080/metamer/faces/components/richContextMenu/simple.xhtml # setup {{showEvent}} to _dblclick_ # make double click on the targetPanel1 (the green one) # see that contextMenu is displayed but consequently disappears > contextMenu - when showEvent is dblclick then context menu disappear after invoking > ----------------------------------------------------------------------------------- > > Key: RF-13441 > URL: https://issues.jboss.org/browse/RF-13441 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 5.0.0.Alpha2 > Environment: * RichFaces 5.0.0-SNAPSHOT > * Metamer 5.0.0-SNAPSHOT > * JBoss Application Server: Weld Integration 7.1.1.Final > * JBoss AS 7.1.1.Final > * OpenJDK Runtime Environment 1.7.0_45-mockbuild_2013_10_16_17_47-b00 @ Linux > * Chrome 30.0.1599.114 @ Linux x86_64, Firefox > Reporter: Juraj H?ska > > Please see steps to reproduce this issue. > It is not a regression. It did not work in e.g. 4.3.3. neither. -- 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 From issues at jboss.org Mon Dec 16 13:50:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Dec 2013 13:50:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13441) contextMenu - when showEvent is dblclick then context menu disappear after invoking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13441: ------------------------------- Fix Version/s: 5-Tracking > contextMenu - when showEvent is dblclick then context menu disappear after invoking > ----------------------------------------------------------------------------------- > > Key: RF-13441 > URL: https://issues.jboss.org/browse/RF-13441 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 5.0.0.Alpha2 > Environment: * RichFaces 5.0.0-SNAPSHOT > * Metamer 5.0.0-SNAPSHOT > * JBoss Application Server: Weld Integration 7.1.1.Final > * JBoss AS 7.1.1.Final > * OpenJDK Runtime Environment 1.7.0_45-mockbuild_2013_10_16_17_47-b00 @ Linux > * Chrome 30.0.1599.114 @ Linux x86_64, Firefox > Reporter: Juraj H?ska > Fix For: 5-Tracking > > > Please see steps to reproduce this issue. > It is not a regression. It did not work in e.g. 4.3.3. neither. -- 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 From issues at jboss.org Tue Dec 17 01:44:33 2013 From: issues at jboss.org (Michael Abele (JIRA)) Date: Tue, 17 Dec 2013 01:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: Michael Abele created RF-13442: ---------------------------------- Summary: iterationStatusVar not working in header/footer of extendedDataTable Key: RF-13442 URL: https://issues.jboss.org/browse/RF-13442 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha2 Reporter: Michael Abele interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. Example code: {code} #{iter.index} {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 From issues at jboss.org Tue Dec 17 04:06:34 2013 From: issues at jboss.org (=?UTF-8?Q?Osman_Y=C3=BCksel_=28JIRA=29?=) Date: Tue, 17 Dec 2013 04:06:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13443) Rerender after Ajax Request in Internet Explorer 11 In-Reply-To: References: Message-ID: Osman Y?ksel created RF-13443: --------------------------------- Summary: Rerender after Ajax Request in Internet Explorer 11 Key: RF-13443 URL: https://issues.jboss.org/browse/RF-13443 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.3.4.Final Reporter: Osman Y?ksel Priority: Critical By using a4j:Funtcion in combination with "rerender" this is not working on Internet Explorer 11. The problem ist, that after Ajax-Request the Result in XML can not be correct append to the body. (Affects in version 3.3.4 Final) Reason is simple: Microsoft has changed the User-Agent for Internet Explorer 11 Before: IE10: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0) Now: IE11: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko Details: http://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.85).aspx In richfaces-imp.jar there is the AJAX.js-File wich rerender the result ofthe Ajax-Request. Here is also Sarissa to identify the Browser. Because of missing "msie", Sarissa can not identifiy an Internet Explorer 11 as an Internet Explorer. That means, tha AJAX.js in "richfaces-imp/ort/ajax4jsf/javascript/scripts" has to be modify. Before: Sarissa._SARISSA_IS_IE = document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1 Now: Sarissa._SARISSA_IS_IE = (document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1) || (navigator.userAgent.toLowerCase().indexOf("like gecko") > -1 && navigator.userAgent.toLowerCase().indexOf("11.") > -1); -- 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 From issues at jboss.org Tue Dec 17 08:32:35 2013 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Dec 2013 08:32:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13154) Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932054#comment-12932054 ] RH Bugzilla Integration commented on RF-13154: ---------------------------------------------- Petr Mensik changed the Status of [bug 1002971|https://bugzilla.redhat.com/show_bug.cgi?id=1002971] from ON_QA to VERIFIED > Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6) > --------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13154 > URL: https://issues.jboss.org/browse/RF-13154 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3 > Environment: EAP 6.1.1.ER7 > Reporter: Ken Finnigan > Assignee: Brian Leathem > Fix For: 4.3.4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs: > {code} > 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Running the exact same showcase example war on EAP 6.1.0.GA works fine. -- 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 From issues at jboss.org Tue Dec 17 11:31:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 11:31:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 4.3.5) > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From issues at jboss.org Tue Dec 17 11:31:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 11:31:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Fix Version/s: (was: 5.0.0.Alpha3) > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From issues at jboss.org Tue Dec 17 11:33:35 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 11:33:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Fix Version/s: 4.3.6 > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.6 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- 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 From issues at jboss.org Tue Dec 17 11:33:35 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 11:33:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13442: ---------------------------------- Assignee: Pavol Pitonak QE please confirm. > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Pavol Pitonak > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 17 11:33:35 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 11:33:35 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13443) Rerender after Ajax Request in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13443: ------------------------------- Fix Version/s: 3.Future > Rerender after Ajax Request in Internet Explorer 11 > --------------------------------------------------- > > Key: RF-13443 > URL: https://issues.jboss.org/browse/RF-13443 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.3.4.Final > Reporter: Osman Y?ksel > Priority: Critical > Fix For: 3.Future > > > By using a4j:Funtcion in combination with "rerender" this is not working on Internet Explorer 11. The problem ist, that after Ajax-Request the Result in XML can not be correct append to the body. (Affects in version 3.3.4 Final) > Reason is simple: > Microsoft has changed the User-Agent for Internet Explorer 11 > Before: > IE10: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0) > Now: > IE11: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko > Details: http://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.85).aspx > In richfaces-imp.jar there is the AJAX.js-File wich rerender the result ofthe Ajax-Request. Here is also Sarissa to identify the Browser. > Because of missing "msie", Sarissa can not identifiy an Internet Explorer 11 as an Internet Explorer. > That means, tha AJAX.js in "richfaces-imp/ort/ajax4jsf/javascript/scripts" has to be modify. > Before: > Sarissa._SARISSA_IS_IE = document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1 > Now: > Sarissa._SARISSA_IS_IE = (document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1) || (navigator.userAgent.toLowerCase().indexOf("like gecko") > -1 && navigator.userAgent.toLowerCase().indexOf("11.") > -1); -- 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 From issues at jboss.org Tue Dec 17 14:01:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 14:01:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932169#comment-12932169 ] Brian Leathem commented on RF-13266: ------------------------------------ This is weird, because the interface [{{org.jboss.weld.util.el.ForwardingMethodExpression}}|https://github.com/weld/core/blob/1.1/impl/src/main/java/org/jboss/weld/util/el/ForwardingMethodExpression.java#L27] extends the [{{javax.el.MethodExpression}}|http://docs.oracle.com/javaee/6/api/javax/el/MethodExpression.html] interface which in turn extends the [{{javax.el.Expression}}|http://docs.oracle.com/javaee/6/api/javax/el/Expression.html] interface which is present in the [serialisation whitelist|https://github.com/richfaces4/core/blob/master/impl/src/main/resources/org/richfaces/resource/resource-serialization.properties#L1]. > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Matej Novotny > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Tue Dec 17 14:37:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 14:37:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13266. -------------------------------- Assignee: Brian Leathem (was: Matej Novotny) Resolution: Done The first demo worked fine for me on EAP 6.1.1 (as expected), the 2nd demo failed. I corrected the problem by adding the primitive Array types to the whitelistClassNameCache in the LookAheadObjectInputStream class. [~manovotn] please verify this on EAP 6 [~fabmars] if you could, please try this on Glassfish. By tomorrow you should be able to download the SNAPSHOT build from the JBoss SNAPSHOTS repo: https://repository.jboss.org/nexus/content/repositories/snapshots/org/richfaces/ > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Tue Dec 17 14:37:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 14:37:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13266: ------------------------------- Labels: needs-qe regression (was: regression) > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Tue Dec 17 14:53:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 14:53:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932181#comment-12932181 ] Brian Leathem commented on RF-13278: ------------------------------------ thanks for the verification. {quote} I can confirm that it is a regression against 4.3.3.Final. {quote} I'm interpreting this to mean it worked in _4.3.3.Final_, and is broken in _4.3.4.Final_. Is this a correct interpretation [~jhuska]? > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Tue Dec 17 14:59:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 14:59:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932183#comment-12932183 ] Brian Leathem commented on RF-13278: ------------------------------------ Diff between 4.3.3 and 4.3.4: Core: https://github.com/richfaces4/core/compare/4.3.3.20130710-Final...4.3.4.20130919-Final Components: https://github.com/richfaces4/components/compare/4.3.3.20130710-Final...4.3.4.20130919-Final The regression is likely related to this fix of RF-13107. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Tue Dec 17 19:46:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 19:46:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932238#comment-12932238 ] Brian Leathem commented on RF-13278: ------------------------------------ This fails for me in TF 5 as well, I believe it's because [~jhuska] checked before the 4.3.4 fixes were ported to 5. Can you confirm that it is indeed broken in RF 5 [~jhuska]? > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Tue Dec 17 20:16:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Dec 2013 20:16:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932246#comment-12932246 ] Brian Leathem commented on RF-13278: ------------------------------------ I added a reproducing framework test in the RichFaces 5 repository: https://github.com/richfaces/richfaces/commit/43b9211c81307c623f8d0fbba4483056234e6f36 > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Wed Dec 18 01:53:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Dec 2013 01:53:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932263#comment-12932263 ] Brian Leathem commented on RF-13278: ------------------------------------ This use case can be achieved by specifying the _tabPanel_ as a render target. As of the 4.3.4 release, only the active tab (and the tab headers) will be rendered. [~alsha] is this sufficient to meet your requirements? > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Wed Dec 18 04:39:33 2013 From: issues at jboss.org (Alexey Shakov (JIRA)) Date: Wed, 18 Dec 2013 04:39:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932309#comment-12932309 ] Alexey Shakov commented on RF-13278: ------------------------------------ I use this as workaround at the moment - it means much more performance overhead for my use case > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Wed Dec 18 05:19:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 18 Dec 2013 05:19:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13442: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) I could reproduce in Metamer. There is the same problem in r:dataGrid and r:dataTable. > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Wed Dec 18 09:41:32 2013 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Wed, 18 Dec 2013 09:41:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13444) r:fileUpload throws IOException "Request prolog cannot be read" In-Reply-To: References: Message-ID: Juergen Zimmermann created RF-13444: --------------------------------------- Summary: r:fileUpload throws IOException "Request prolog cannot be read" Key: RF-13444 URL: https://issues.jboss.org/browse/RF-13444 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha2 Reporter: Juergen Zimmermann I tried f:fileUpload with the latest WildFly snapshot. When uploading a jpeg file I get this stacktrace. Maybe, RF-13061 is back in town... {code} SEVERE [org.richfaces.log.Application] (default task-6) Exception parsing multipart request: Request prolog cannot be read: org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:75) [jsf-impl-2.2.4-jbossorg-1.jar:] at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:56) [jsf-impl-2.2.4-jbossorg-1.jar:] at java.util.Collections$UnmodifiableMap.get(Collections.java:1339) [rt.jar:1.7.0_45] at com.sun.faces.application.view.MultiViewHandler.calculateRenderKitId(MultiViewHandler.java:220) [jsf-impl-2.2.4-jbossorg-1.jar:] at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at com.sun.faces.context.FacesContextImpl.isPostback(FacesContextImpl.java:212) [jsf-impl-2.2.4-jbossorg-1.jar:] at javax.faces.context.FacesContextWrapper.isPostback(FacesContextWrapper.java:461) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:193) [jsf-impl-2.2.4-jbossorg-1.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.4-jbossorg-1.jar:] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:121) [jsf-impl-2.2.4-jbossorg-1.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198) [jsf-impl-2.2.4-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:67) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:239) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:226) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:145) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:654) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] Caused by: java.io.IOException: Request prolog cannot be read at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] ... 43 more {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 From issues at jboss.org Thu Dec 19 05:00:32 2013 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 19 Dec 2013 05:00:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932554#comment-12932554 ] Matej Novotny commented on RF-13266: ------------------------------------ For verification I used EAP 6.1.1 and refactored the example to use RF 4.3.5.Snapshot (all I needed to alter was version and repository URL). Both demos are now working properly, the first one showing a functional link to a PDF file, the other displaying an image. > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Thu Dec 19 07:48:33 2013 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 19 Dec 2013 07:48:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13439) Photoalbum - update help section In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13439. -------------------------------- Resolution: Done > Photoalbum - update help section > -------------------------------- > > Key: RF-13439 > URL: https://issues.jboss.org/browse/RF-13439 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > > * The help stylesheets link to docbook resources that were removed from RF. > * The help popups need updating > ** The code and the pictures may not display the current state of the app > ** New popups for the social integration should probably be added. -- 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 From issues at jboss.org Thu Dec 19 08:16:33 2013 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 19 Dec 2013 08:16:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932611#comment-12932611 ] Juraj H?ska commented on RF-13278: ---------------------------------- [~bleathem] : Yes, you are right. I can confirm that it is broken in RF 5-SNAPSHOT as well. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 01:18:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Dec 2013 01:18:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932773#comment-12932773 ] Brian Leathem commented on RF-13278: ------------------------------------ To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel at ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 01:20:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Dec 2013 01:20:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932773#comment-12932773 ] Brian Leathem edited comment on RF-13278 at 12/20/13 1:19 AM: -------------------------------------------------------------- To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel at ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_ ? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. was (Author: bleathem): To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel at ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 01:20:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Dec 2013 01:20:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Workaround Description: Specify the parent _tabPanel_ component as a render target. (was: refresh enclosing rich:tabPanel component) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 01:20:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 20 Dec 2013 01:20:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932773#comment-12932773 ] Brian Leathem edited comment on RF-13278 at 12/20/13 1:19 AM: -------------------------------------------------------------- To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel at ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _much more performance overhead_? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. was (Author: bleathem): To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel at ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_ ? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 04:32:33 2013 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 20 Dec 2013 04:32:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13266: ------------------------------- Labels: regression (was: needs-qe regression) > mediaOutput not working anymore on Glassfish3 and EAP6.1 > -------------------------------------------------------- > > Key: RF-13266 > URL: https://issues.jboss.org/browse/RF-13266 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45 > Reporter: Fab Mars > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3. > I have 2 mediaOutput in my code, none works. > The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression > The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get > SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B > I'm preparing a reproducer on github and will share the url in the next comment. -- 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 From issues at jboss.org Fri Dec 20 04:36:32 2013 From: issues at jboss.org (Alexey Shakov (JIRA)) Date: Fri, 20 Dec 2013 04:36:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932826#comment-12932826 ] Alexey Shakov commented on RF-13278: ------------------------------------ In my use case I have an active tab with a large tree and I need to refresh an inactive tab header on certain operations. Refreshing the tabPanel completely means rerendering of the large tree, placed in active tab. Only the traffic overhead is easily 1000x higher in the case (tree has a very verbose markup) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Fri Dec 20 10:01:33 2013 From: issues at jboss.org (Michael Abele (JIRA)) Date: Fri, 20 Dec 2013 10:01:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13445) extendedDataTable: Sort icons and 'column move' icon gone In-Reply-To: References: Message-ID: Michael Abele created RF-13445: ---------------------------------- Summary: extendedDataTable: Sort icons and 'column move' icon gone Key: RF-13445 URL: https://issues.jboss.org/browse/RF-13445 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha2 Reporter: Michael Abele Please check extendedDataTable Demo: http://showcase5-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky - Built-In Sorting: Icons for sort direction are gone - Basic usage: If you drop a column the little blue arrow showing the new column position is gone -- 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 From issues at jboss.org Fri Dec 20 19:01:32 2013 From: issues at jboss.org (Masafumi Miura (JIRA)) Date: Fri, 20 Dec 2013 19:01:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13446) Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel In-Reply-To: References: Message-ID: Masafumi Miura created RF-13446: ----------------------------------- Summary: Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel Key: RF-13446 URL: https://issues.jboss.org/browse/RF-13446 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.1.SP3 Reporter: Masafumi Miura *Description of problem:* Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. *Version-Release number of selected component (if applicable):* Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. *Steps to Reproduce:* 1. Deploy the attached richfaces-demo.war to EAP 5.1.2 2. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) 3. Click the button "test" at the bottom of the page. *Actual results:* It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. {code} SCRIPT16389: Unspecified error controls-scrollable-data-table.js, line 62 character 23 {code} *Expected results:* No javascript error happens. *Additional info:* The reported customer is using one-off patch was created from BZ#982322 branch. http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ -- 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 From issues at jboss.org Mon Dec 23 06:54:32 2013 From: issues at jboss.org (Glauber Matos (JIRA)) Date: Mon, 23 Dec 2013 06:54:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13447) At least three days the url http://showcase.richfaces.org/ is down. In-Reply-To: References: Message-ID: Glauber Matos created RF-13447: ---------------------------------- Summary: At least three days the url http://showcase.richfaces.org/ is down. Key: RF-13447 URL: https://issues.jboss.org/browse/RF-13447 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Reporter: Glauber Matos Priority: Blocker -- 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 From issues at jboss.org Mon Dec 23 10:44:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 10:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13447) At least three days the url http://showcase.richfaces.org/ is down. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13447. -------------------------------- Resolution: Done Thanks for reporting the problem. I have corrected the showcase deployment, and it is operational now. > At least three days the url http://showcase.richfaces.org/ is down. > ------------------------------------------------------------------- > > Key: RF-13447 > URL: https://issues.jboss.org/browse/RF-13447 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Glauber Matos > Priority: Blocker > -- 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 From issues at jboss.org Mon Dec 23 10:44:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 10:44:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13447) At least three days the url http://showcase.richfaces.org/ is down. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13447: ---------------------------------- Assignee: Brian Leathem > At least three days the url http://showcase.richfaces.org/ is down. > ------------------------------------------------------------------- > > Key: RF-13447 > URL: https://issues.jboss.org/browse/RF-13447 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Glauber Matos > Assignee: Brian Leathem > Priority: Blocker > -- 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 From issues at jboss.org Mon Dec 23 11:12:32 2013 From: issues at jboss.org (Mustafa Musaji (JIRA)) Date: Mon, 23 Dec 2013 11:12:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933124#comment-12933124 ] Mustafa Musaji commented on RF-13216: ------------------------------------- [~bleathem] I've tried to reach out to [~tkonishi] to find out about this. Not heard anything so please go ahead and close this JIRA. > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Labels: gss, waiting_on_user > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > > > > > > > > > > > > > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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 From issues at jboss.org Mon Dec 23 12:17:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 12:17:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933133#comment-12933133 ] Brian Leathem commented on RF-13278: ------------------------------------ Thanks for the clarification [~alsha]. Reverting back to the pre-4.3.4 tree visiting pattern would be a step backwards. I suggest we address this use case by creating a new meta-component for the tabPanel: {{@headers}} which would render that tab headers explicitly when the component is built. > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:38:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:38:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 4.3.5) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Labels: regression > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:40:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:40:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Labels: (was: regression) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:40:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:40:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Issue Type: Feature Request (was: Bug) > rich:tab : label, placed in header-facet, can not be refreshed per ajax > ----------------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:40:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:40:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add suppor for a 'headers' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Summary: Add suppor for a 'headers' meta-component to the rich:tabPanel (was: rich:tab : label, placed in header-facet, can not be refreshed per ajax) > Add suppor for a 'headers' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:40:34 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:40:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Summary: Add support for a 'headers' meta-component to the rich:tabPanel (was: Add suppor for a 'headers' meta-component to the rich:tabPanel) > Add support for a 'headers' meta-component to the rich:tabPanel > --------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:42:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:42:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13278: ---------------------------------- Assignee: Brian Leathem > Add support for a 'headers' meta-component to the rich:tabPanel > --------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Mon Dec 23 19:54:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:54:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13445) extendedDataTable: Sort icons and 'column move' icon gone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13445: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > extendedDataTable: Sort icons and 'column move' icon gone > --------------------------------------------------------- > > Key: RF-13445 > URL: https://issues.jboss.org/browse/RF-13445 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Fix For: 5.0.0.Alpha3 > > > Please check extendedDataTable Demo: > http://showcase5-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > - Built-In Sorting: Icons for sort direction are gone > - Basic usage: If you drop a column the little blue arrow showing the new column position is gone -- 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 From issues at jboss.org Mon Dec 23 19:54:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:54:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13445) extendedDataTable: Sort icons and 'column move' icon gone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13445: ------------------------------- Component/s: resource handling > extendedDataTable: Sort icons and 'column move' icon gone > --------------------------------------------------------- > > Key: RF-13445 > URL: https://issues.jboss.org/browse/RF-13445 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Fix For: 5.0.0.Alpha3 > > > Please check extendedDataTable Demo: > http://showcase5-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > - Built-In Sorting: Icons for sort direction are gone > - Basic usage: If you drop a column the little blue arrow showing the new column position is gone -- 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 From issues at jboss.org Mon Dec 23 19:54:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:54:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13445) extendedDataTable: Sort icons and 'column move' icon gone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13445: ------------------------------- Labels: regression (was: ) > extendedDataTable: Sort icons and 'column move' icon gone > --------------------------------------------------------- > > Key: RF-13445 > URL: https://issues.jboss.org/browse/RF-13445 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Labels: regression > Fix For: 5.0.0.Alpha3 > > > Please check extendedDataTable Demo: > http://showcase5-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > - Built-In Sorting: Icons for sort direction are gone > - Basic usage: If you drop a column the little blue arrow showing the new column position is gone -- 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 From issues at jboss.org Mon Dec 23 19:54:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:54:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13444) r:fileUpload throws IOException "Request prolog cannot be read" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13444: ------------------------------- Labels: jsf22 (was: ) > r:fileUpload throws IOException "Request prolog cannot be read" > --------------------------------------------------------------- > > Key: RF-13444 > URL: https://issues.jboss.org/browse/RF-13444 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juergen Zimmermann > Labels: jsf22 > > I tried f:fileUpload with the latest WildFly snapshot. When uploading a jpeg file I get this stacktrace. Maybe, RF-13061 is back in town... > {code} > SEVERE [org.richfaces.log.Application] (default task-6) Exception parsing multipart request: Request prolog cannot be read: org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:75) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:56) [jsf-impl-2.2.4-jbossorg-1.jar:] > at java.util.Collections$UnmodifiableMap.get(Collections.java:1339) [rt.jar:1.7.0_45] > at com.sun.faces.application.view.MultiViewHandler.calculateRenderKitId(MultiViewHandler.java:220) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.context.FacesContextImpl.isPostback(FacesContextImpl.java:212) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.context.FacesContextWrapper.isPostback(FacesContextWrapper.java:461) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:193) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:121) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:67) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:239) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:226) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:145) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:654) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > ... 43 more > {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 From issues at jboss.org Mon Dec 23 19:54:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:54:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13444) r:fileUpload throws IOException "Request prolog cannot be read" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13444: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > r:fileUpload throws IOException "Request prolog cannot be read" > --------------------------------------------------------------- > > Key: RF-13444 > URL: https://issues.jboss.org/browse/RF-13444 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Reporter: Juergen Zimmermann > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I tried f:fileUpload with the latest WildFly snapshot. When uploading a jpeg file I get this stacktrace. Maybe, RF-13061 is back in town... > {code} > SEVERE [org.richfaces.log.Application] (default task-6) Exception parsing multipart request: Request prolog cannot be read: org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:75) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.context.RequestParameterMap.get(RequestParameterMap.java:56) [jsf-impl-2.2.4-jbossorg-1.jar:] > at java.util.Collections$UnmodifiableMap.get(Collections.java:1339) [rt.jar:1.7.0_45] > at com.sun.faces.application.view.MultiViewHandler.calculateRenderKitId(MultiViewHandler.java:220) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at javax.faces.application.ViewHandlerWrapper.calculateRenderKitId(ViewHandlerWrapper.java:157) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.context.FacesContextImpl.isPostback(FacesContextImpl.java:212) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.context.FacesContextWrapper.isPostback(FacesContextWrapper.java:461) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:193) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:121) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198) [jsf-impl-2.2.4-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:67) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:239) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:226) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:145) [undertow-servlet-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:654) [undertow-core-1.0.0.Beta28.jar:1.0.0.Beta28] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.io.IOException: Request prolog cannot be read > at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148) [richfaces-5.0.0.Alpha2.jar:5.0.0.Alpha2] > ... 43 more > {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 From issues at jboss.org Mon Dec 23 19:56:33 2013 From: issues at jboss.org (Michael Abele (JIRA)) Date: Mon, 23 Dec 2013 19:56:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13445) extendedDataTable: Sort icons and 'column move' icon gone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933168#comment-12933168 ] Michael Abele commented on RF-13445: ------------------------------------ Ich bin bis zum 07.01.2014 nicht im B?ro und habe nur eingeschr?nkten Zugriff auf meine E-Mails. In dringenden F?llen wenden Sie sich bitte telefonisch an unsere Zentrale unter der Nummer +49-7191-90590 oder senden Sie eine E-Mail an info at aqcon.com. I am not in the office until January 7th 2013 and I have only limited access to my mail account. In urgent cases please call +49-7191-90590 or send a mail to info at aqcon.com. > extendedDataTable: Sort icons and 'column move' icon gone > --------------------------------------------------------- > > Key: RF-13445 > URL: https://issues.jboss.org/browse/RF-13445 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Labels: regression > Fix For: 5.0.0.Alpha3 > > > Please check extendedDataTable Demo: > http://showcase5-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > - Built-In Sorting: Icons for sort direction are gone > - Basic usage: If you drop a column the little blue arrow showing the new column position is gone -- 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 From issues at jboss.org Mon Dec 23 19:58:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:58:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933169#comment-12933169 ] Brian Leathem commented on RF-13442: ------------------------------------ I question the validity of having the iterationStatusVar available in the header/footer, since during the header/footer render the iteration has not started/completed. [~ma.aqcon] can you please further justify your use case? > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Mon Dec 23 19:58:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 19:58:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13442: ------------------------------- Labels: waiting_on_user (was: ) > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Labels: waiting_on_user > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Mon Dec 23 20:00:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 23 Dec 2013 20:00:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13216. -------------------------------- Resolution: Won't Fix > PoupPanel doesn't disappear when rendered="false" and rerender it. > ------------------------------------------------------------------ > > Key: RF-13216 > URL: https://issues.jboss.org/browse/RF-13216 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.3 > Reporter: Takayuki Konishi > Labels: gss, waiting_on_user > Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip > > > If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions. > {code:xml} > > > > > > > > > > > > > {code} > In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. > Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final. > Note: > In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function. -- 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 From issues at jboss.org Mon Dec 23 20:02:33 2013 From: issues at jboss.org (Masafumi Miura (JIRA)) Date: Mon, 23 Dec 2013 20:02:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13446) Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masafumi Miura updated RF-13446: -------------------------------- Security: Public (was: JBoss Internal) > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13446 > URL: https://issues.jboss.org/browse/RF-13446 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.1.SP3 > Reporter: Masafumi Miura > Assignee: Brian Leathem > Attachments: RF-13446.patch > > > *Description of problem:* > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. > *Version-Release number of selected component (if applicable):* > Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. > *Steps to Reproduce:* > 1. Deploy the attached richfaces-demo.war to EAP 5.1.2 > 2. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) > 3. Click the button "test" at the bottom of the page. > *Actual results:* > It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. > {code} > SCRIPT16389: Unspecified error > controls-scrollable-data-table.js, line 62 character 23 > {code} > *Expected results:* > No javascript error happens. > *Additional info:* > The reported customer is using one-off patch was created from BZ#982322 branch. > http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ -- 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 From issues at jboss.org Mon Dec 23 20:08:33 2013 From: issues at jboss.org (Masafumi Miura (JIRA)) Date: Mon, 23 Dec 2013 20:08:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13446) Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masafumi Miura updated RF-13446: -------------------------------- Description: *Description of problem:* Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. *Version-Release number of selected component (if applicable):* Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. *Steps to Reproduce:* 1. Modify the following two files of richfaces-demo.war: - Edit WAR/templates/main.xhtml and change from: {code}
Body
#{environment.version}
{code} to: {code} Body {code} - Edit WAR/richfaces/scrollableDataTable/examples/scrollableDataTable.xhtml and add rich:simpleTogglePanel and a4j:commandButton which rerender the rich:scrollableDataTable. Please note that the original template uses a html table to wrap the facelet body. The error won't show if the facelet body is wrapped with the html body until you resize the browser window. 2. Deploy modified richfaces-demo.war to EAP 5.1.2 3. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) 4. Click the button "test" at the bottom of the page. *Actual results:* It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. {code} SCRIPT16389: Unspecified error controls-scrollable-data-table.js, line 62 character 23 {code} *Expected results:* No javascript error happens. *Additional info:* The reported customer is using one-off patch was created from BZ#982322 branch. http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ was: *Description of problem:* Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. *Version-Release number of selected component (if applicable):* Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. *Steps to Reproduce:* 1. Deploy the attached richfaces-demo.war to EAP 5.1.2 2. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) 3. Click the button "test" at the bottom of the page. *Actual results:* It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. {code} SCRIPT16389: Unspecified error controls-scrollable-data-table.js, line 62 character 23 {code} *Expected results:* No javascript error happens. *Additional info:* The reported customer is using one-off patch was created from BZ#982322 branch. http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13446 > URL: https://issues.jboss.org/browse/RF-13446 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.1.SP3 > Reporter: Masafumi Miura > Assignee: Brian Leathem > Attachments: RF-13446.patch > > > *Description of problem:* > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. > *Version-Release number of selected component (if applicable):* > Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. > *Steps to Reproduce:* > 1. Modify the following two files of richfaces-demo.war: > - Edit WAR/templates/main.xhtml and change from: > {code} > class="content_container" width="100%"> > > > > > > >
>
> 		> > Body > > > >
class="footer-text">#{environment.version}
> >
> {code} > to: > {code} > Body > {code} > - Edit WAR/richfaces/scrollableDataTable/examples/scrollableDataTable.xhtml and add rich:simpleTogglePanel and a4j:commandButton which rerender the > rich:scrollableDataTable. Please note that the original template uses a html table to wrap the facelet body. The error won't show if the facelet body is wrapped with the html body until you resize the browser window. > 2. Deploy modified richfaces-demo.war to EAP 5.1.2 > 3. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) > 4. Click the button "test" at the bottom of the page. > *Actual results:* > It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. > {code} > SCRIPT16389: Unspecified error > controls-scrollable-data-table.js, line 62 character 23 > {code} > *Expected results:* > No javascript error happens. > *Additional info:* > The reported customer is using one-off patch was created from BZ#982322 branch. > http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ -- 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 From issues at jboss.org Tue Dec 24 04:50:34 2013 From: issues at jboss.org (Christophe Noel (JIRA)) Date: Tue, 24 Dec 2013 04:50:34 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12510) jsFunction data called before completittion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933178#comment-12933178 ] Christophe Noel commented on RF-12510: -------------------------------------- I would say that the main concern about the issue, is that onComplete is called also twice ! (tested on Liferay 6.1.2ga3, Richfaces 4.3.2.Final with jsFunction). > jsFunction data called before completittion > ------------------------------------------- > > Key: RF-12510 > URL: https://issues.jboss.org/browse/RF-12510 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.2.Final > Environment: Tomcat 6.0.X > Reporter: Jan Pernica > Fix For: 5-Tracking > > > When a4j:jsFunction is called then function on data is called twice. Once before action and then after action. How to disable it? RF 3.3.3 have called it just once. > {code} > > {code} > So that myBean.data is called before action call and after action call. How to prevent 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 From issues at jboss.org Tue Dec 24 05:24:32 2013 From: issues at jboss.org (Michael Abele (JIRA)) Date: Tue, 24 Dec 2013 05:24:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933182#comment-12933182 ] Michael Abele commented on RF-13442: ------------------------------------ This would be an easy way to display the number of rows in table footer... > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Labels: waiting_on_user > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 24 12:20:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:20:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-12510) jsFunction data called before completittion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741430#comment-12741430 ] Brian Leathem edited comment on RF-12510 at 12/24/13 12:19 PM: --------------------------------------------------------------- I found following workaroud: {code} class MyBean { public void blankAction(){ //does nothing } public DataObject action(){ // executes action and initializes dataObject return dataObject; } } {code} was (Author: tishaishy): I found following workaroud: class MyBean { public void blankAction(){ //does nothing } public DataObject action(){ // executes action and initializes dataObject return dataObject; } } > jsFunction data called before completittion > ------------------------------------------- > > Key: RF-12510 > URL: https://issues.jboss.org/browse/RF-12510 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.2.Final > Environment: Tomcat 6.0.X > Reporter: Jan Pernica > Fix For: 5-Tracking > > > When a4j:jsFunction is called then function on data is called twice. Once before action and then after action. How to disable it? RF 3.3.3 have called it just once. > {code} > > {code} > So that myBean.data is called before action call and after action call. How to prevent 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 From issues at jboss.org Tue Dec 24 12:52:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13448) Add javadoc to the SequenceIterationStatus class In-Reply-To: References: Message-ID: Brian Leathem created RF-13448: ---------------------------------- Summary: Add javadoc to the SequenceIterationStatus class Key: RF-13448 URL: https://issues.jboss.org/browse/RF-13448 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-tables, doc Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 5.0.0.Alpha3 The SequenceIterationStatus class would benefit from the addition of javadoc. -- 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 From issues at jboss.org Tue Dec 24 12:52:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:52:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13448) Add javadoc to the SequenceIterationStatus class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13448: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Add javadoc to the SequenceIterationStatus class > ------------------------------------------------ > > Key: RF-13448 > URL: https://issues.jboss.org/browse/RF-13448 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-tables, doc > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The SequenceIterationStatus class would benefit from the addition of javadoc. -- 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 From issues at jboss.org Tue Dec 24 12:54:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:54:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Fix Version/s: 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > Add support for a 'headers' meta-component to the rich:tabPanel > --------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Tue Dec 24 12:54:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:54:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13278: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 (was: RichFaces 4.3.5 Sprint 1) > Add support for a 'headers' meta-component to the rich:tabPanel > --------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- 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 From issues at jboss.org Tue Dec 24 12:58:32 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 12:58:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13448) Add javadoc to the SequenceIterationStatus class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13448. -------------------------------- Resolution: Done > Add javadoc to the SequenceIterationStatus class > ------------------------------------------------ > > Key: RF-13448 > URL: https://issues.jboss.org/browse/RF-13448 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-tables, doc > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The SequenceIterationStatus class would benefit from the addition of javadoc. -- 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 From issues at jboss.org Tue Dec 24 13:12:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 13:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933194#comment-12933194 ] Brian Leathem commented on RF-13442: ------------------------------------ Looking at the iteration status more closely: https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/iteration/SequenceIterationStatus.java The following properties would make sense in the context of the header/footer: * begin * end * count * rowCount The following would not make sense * index * first * last * even * odd Having access to the begin, end, count, and rowCount values in the header and footer would indeed make sense. the other properties could just resolve to null. > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Labels: waiting_on_user > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 24 13:12:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 13:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13442: ------------------------------- Labels: (was: waiting_on_user) > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 24 13:12:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 13:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13442: ------------------------------- Fix Version/s: 5-Tracking > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Fix For: 5-Tracking > > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 24 13:12:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 13:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13442: ------------------------------- Issue Type: Feature Request (was: Bug) > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Fix For: 5-Tracking > > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Tue Dec 24 13:12:33 2013 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 24 Dec 2013 13:12:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13442) iterationStatusVar not working in header/footer of extendedDataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13442: ------------------------------- Component/s: component-tables > iterationStatusVar not working in header/footer of extendedDataTable > -------------------------------------------------------------------- > > Key: RF-13442 > URL: https://issues.jboss.org/browse/RF-13442 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 5.0.0.Alpha2 > Reporter: Michael Abele > Assignee: Brian Leathem > Fix For: 5-Tracking > > > interationStatusVar attribute is available in columns of r:extendedDataTable but not in footer or header part of the table. This would be very useful to display messages like "15 rows loaded" in a table footer. > Example code: > {code} > > #{iter.index} > > > > {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 From issues at jboss.org Wed Dec 25 03:38:33 2013 From: issues at jboss.org (Javier Gonzales (JIRA)) Date: Wed, 25 Dec 2013 03:38:33 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13449) rich:fileuload progress not displaying In-Reply-To: References: Message-ID: Javier Gonzales created RF-13449: ------------------------------------ Summary: rich:fileuload progress not displaying Key: RF-13449 URL: https://issues.jboss.org/browse/RF-13449 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.4 Reporter: Javier Gonzales On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0. http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.8620246561853033. -- 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 From issues at jboss.org Thu Dec 26 13:19:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:19:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: Luca Stancapiano created RF-13450: ------------------------------------- Summary: page attribute on dataScroller doesn't work with a request scope Key: RF-13450 URL: https://issues.jboss.org/browse/RF-13450 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-ScrollableDataTable Affects Versions: 4.3.4 Environment: java 6 on jboss as 7.1 Reporter: Luca Stancapiano Attachments: scrollablesample.zip Here the dataTable with a dataScroller: ... Here the definition of the currentPage bean: currentPage prova.CurrentPage request Here the currentPage bean: package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Thu Dec 26 13:19:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:19:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated RF-13450: ---------------------------------- Attachment: scrollablesample.zip I attach a sample project with the problem > page attribute on dataScroller doesn't work with a request scope > ---------------------------------------------------------------- > > Key: RF-13450 > URL: https://issues.jboss.org/browse/RF-13450 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.3.4 > Environment: java 6 on jboss as 7.1 > Reporter: Luca Stancapiano > Labels: datatable, scrollable > Attachments: scrollablesample.zip > > > Here the dataTable with a dataScroller: > page="#{currentPage.page}" /> > id="table" rows="10"> > > > > > > > ... > > Here the definition of the currentPage bean: > > currentPage > prova.CurrentPage > request > > Here the currentPage bean: > package prova; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class CurrentPage { > > private int page = 1; > public int getPage() { > return page; > } > public void setPage(int page) { > this.page = page; > } > } > the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Thu Dec 26 13:21:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:21:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated RF-13450: ---------------------------------- Description: Here the dataTable with a dataScroller: {code} ... {code} Here the definition of the currentPage bean: currentPage prova.CurrentPage request Here the currentPage bean: package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok was: Here the dataTable with a dataScroller: ... Here the definition of the currentPage bean: currentPage prova.CurrentPage request Here the currentPage bean: package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok > page attribute on dataScroller doesn't work with a request scope > ---------------------------------------------------------------- > > Key: RF-13450 > URL: https://issues.jboss.org/browse/RF-13450 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.3.4 > Environment: java 6 on jboss as 7.1 > Reporter: Luca Stancapiano > Labels: datatable, scrollable > Attachments: scrollablesample.zip > > > Here the dataTable with a dataScroller: > {code} > page="#{currentPage.page}" /> > id="table" rows="10"> > > > > > > > ... > > {code} > Here the definition of the currentPage bean: > > currentPage > prova.CurrentPage > request > > Here the currentPage bean: > package prova; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class CurrentPage { > > private int page = 1; > public int getPage() { > return page; > } > public void setPage(int page) { > this.page = page; > } > } > the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Thu Dec 26 13:21:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:21:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated RF-13450: ---------------------------------- Description: Here the dataTable with a dataScroller: {code} ... {code} Here the definition of the currentPage bean: {code} currentPage prova.CurrentPage request {code} Here the currentPage bean: {code} package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } {code} the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok was: Here the dataTable with a dataScroller: {code} ... {code} Here the definition of the currentPage bean: currentPage prova.CurrentPage request Here the currentPage bean: package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok > page attribute on dataScroller doesn't work with a request scope > ---------------------------------------------------------------- > > Key: RF-13450 > URL: https://issues.jboss.org/browse/RF-13450 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.3.4 > Environment: java 6 on jboss as 7.1 > Reporter: Luca Stancapiano > Labels: datatable, scrollable > Attachments: scrollablesample.zip > > > Here the dataTable with a dataScroller: > {code} > page="#{currentPage.page}" /> > id="table" rows="10"> > > > > > > > ... > > {code} > Here the definition of the currentPage bean: > {code} > > currentPage > prova.CurrentPage > request > > {code} > Here the currentPage bean: > {code} > package prova; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class CurrentPage { > > private int page = 1; > public int getPage() { > return page; > } > public void setPage(int page) { > this.page = page; > } > } > {code} > the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Thu Dec 26 13:23:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:23:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated RF-13450: ---------------------------------- Description: Here the dataTable with a dataScroller: {code} ... {code} Here the definition of the currentPage bean: {code} currentPage prova.CurrentPage request {code} Here the currentPage bean: {code} package prova; public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } {code} the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok was: Here the dataTable with a dataScroller: {code} ... {code} Here the definition of the currentPage bean: {code} currentPage prova.CurrentPage request {code} Here the currentPage bean: {code} package prova; import javax.enterprise.context.RequestScoped; import javax.inject.Named; @Named @RequestScoped public class CurrentPage { private int page = 1; public int getPage() { return page; } public void setPage(int page) { this.page = page; } } {code} the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok > page attribute on dataScroller doesn't work with a request scope > ---------------------------------------------------------------- > > Key: RF-13450 > URL: https://issues.jboss.org/browse/RF-13450 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.3.4 > Environment: java 6 on jboss as 7.1 > Reporter: Luca Stancapiano > Labels: datatable, scrollable > Attachments: scrollablesample.zip > > > Here the dataTable with a dataScroller: > {code} > page="#{currentPage.page}" /> > id="table" rows="10"> > > > > > > > ... > > {code} > Here the definition of the currentPage bean: > {code} > > currentPage > prova.CurrentPage > request > > {code} > Here the currentPage bean: > {code} > package prova; > public class CurrentPage { > > private int page = 1; > public int getPage() { > return page; > } > public void setPage(int page) { > this.page = page; > } > } > {code} > the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Thu Dec 26 13:25:32 2013 From: issues at jboss.org (Luca Stancapiano (JIRA)) Date: Thu, 26 Dec 2013 13:25:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13450) page attribute on dataScroller doesn't work with a request scope In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated RF-13450: ---------------------------------- Attachment: scrollablesample.zip > page attribute on dataScroller doesn't work with a request scope > ---------------------------------------------------------------- > > Key: RF-13450 > URL: https://issues.jboss.org/browse/RF-13450 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.3.4 > Environment: java 6 on jboss as 7.1 > Reporter: Luca Stancapiano > Labels: datatable, scrollable > Attachments: scrollablesample.zip, scrollablesample.zip > > > Here the dataTable with a dataScroller: > {code} > page="#{currentPage.page}" /> > id="table" rows="10"> > > > > > > > ... > > {code} > Here the definition of the currentPage bean: > {code} > > currentPage > prova.CurrentPage > request > > {code} > Here the currentPage bean: > {code} > package prova; > public class CurrentPage { > > private int page = 1; > public int getPage() { > return page; > } > public void setPage(int page) { > this.page = page; > } > } > {code} > the 'page' attribute in the dataScroller configuration doesn't work if set to 'request' scope. The buttons rewind and forward are blocked and it doesn't work. If I configure it with a 'session' scope that's ok -- 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 From issues at jboss.org Fri Dec 27 03:24:32 2013 From: issues at jboss.org (Seyed Mohammad Hosein Jamali (JIRA)) Date: Fri, 27 Dec 2013 03:24:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13451) Persian Datepicker/Calendar In-Reply-To: References: Message-ID: Seyed Mohammad Hosein Jamali created RF-13451: ------------------------------------------------- Summary: Persian Datepicker/Calendar Key: RF-13451 URL: https://issues.jboss.org/browse/RF-13451 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Affects Versions: 5.0.0.Alpha1 Reporter: Seyed Mohammad Hosein Jamali Provides Persian Datepicker/Calendar for RichFaces 5 -- 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 From issues at jboss.org Fri Dec 27 03:28:32 2013 From: issues at jboss.org (Seyed Mohammad Hosein Jamali (JIRA)) Date: Fri, 27 Dec 2013 03:28:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13451) Persian Datepicker/Calendar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seyed Mohammad Hosein Jamali updated RF-13451: ---------------------------------------------- Affects Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > Persian Datepicker/Calendar > --------------------------- > > Key: RF-13451 > URL: https://issues.jboss.org/browse/RF-13451 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha2 > Reporter: Seyed Mohammad Hosein Jamali > Labels: persian,calendar,datepicker > Original Estimate: 6 weeks > Remaining Estimate: 6 weeks > > Provides Persian Datepicker/Calendar for RichFaces 5 -- 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 From issues at jboss.org Fri Dec 27 06:09:32 2013 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Fri, 27 Dec 2013 06:09:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: Lutz Ulrich created RF-13452: -------------------------------- Summary: UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor Key: RF-13452 URL: https://issues.jboss.org/browse/RF-13452 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility Affects Versions: 4.3.4 Environment: Mojarra 2.1.?? - 2.1.26 Reporter: Lutz Ulrich Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. For completion, here is a stack trace: {quote} Schwerwiegend: java.lang.NullPointerException at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) {quote} -- 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 From issues at jboss.org Mon Dec 30 01:11:32 2013 From: issues at jboss.org (Javier Gonzales (JIRA)) Date: Mon, 30 Dec 2013 01:11:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13449) rich:fileuload progress not displaying In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javier Gonzales updated RF-13449: --------------------------------- Description: On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0. http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.8620246561853033. was: On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0. http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.8620246561853033. > rich:fileuload progress not displaying > -------------------------------------- > > Key: RF-13449 > URL: https://issues.jboss.org/browse/RF-13449 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Javier Gonzales > > On my local environment with IE 9 the progress bar works fine. Once the application is deployed in higher environments then the progress bar does not display at all. I've also noticed this same issue in the showcases with the same browser IE9 (I've tried other browsers and also experiencing the same problem, IE10/11, Chrome 31.0, etc). After some debugging I've noticed that when the application makes the following request, the response is always 0. > http://showcase.richfaces.org/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.8620246561853033. -- 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 From issues at jboss.org Tue Dec 31 09:03:32 2013 From: issues at jboss.org (Roman Chigvintsev (JIRA)) Date: Tue, 31 Dec 2013 09:03:32 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] (RF-13453) There is no way to extend class org.richfaces.renderkit.ExtendedDataTableRenderer properly In-Reply-To: References: Message-ID: Roman Chigvintsev created RF-13453: -------------------------------------- Summary: There is no way to extend class org.richfaces.renderkit.ExtendedDataTableRenderer properly Key: RF-13453 URL: https://issues.jboss.org/browse/RF-13453 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.4 Reporter: Roman Chigvintsev It's impossible to override some methods of class {{org.richfaces.renderkit.ExtendedDataTableRenderer}} (e.g. {{void encodeBody(RendererState state)}}) because internal classes and enums have private access level. -- 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