August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13136) a4j:log with mode=console doesn't take log level into consideration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13136?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13136. ----------------------------- Resolution: Done > a4j:log with mode=console doesn't take log level into consideration > ------------------------------------------------------------------- > > Key: RF-13136 > URL: https://issues.jboss.org/browse/RF-13136 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > > Here the log.js [logs message to browser console|https://github.com/richfaces4/components/blob/4.3.3.20130710-Fina...] > but it ignores [log level check|https://github.com/richfaces4/components/blob/4.3.3.20130710-Final/...] which happens only for other modes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13137) a4j:log - wrong log levels in attribute description

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13137?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13137. ----------------------------- Resolution: Done > a4j:log - wrong log levels in attribute description > --------------------------------------------------- > > Key: RF-13137 > URL: https://issues.jboss.org/browse/RF-13137 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > > The description is: > {code} > Sets the logging level, can be one of "ERROR", "FATAL", "INFO", "WARN", "ALL" > {code} > but should be: > {code} > Sets the logging level, can be one of 'debug', 'info', 'warn', 'error'. > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13138) a4j:log - should print partial-response value in a level=debug, but prints [Object] instead

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13138?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13138: ---------------------------- Description: {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 <input id=form:j_idt9 ...> log.js.jsf?ln=org.richfaces:160 RichFaces: Received 'beforedomupdate' event from <input id=form:j_idt9 ...> 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@malformedXML' event from <input id=form:j_idt9 ...> 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 <input id=form:j_idt9 ...> {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.A...] generated jQuery object, which is in turn printed as {{[Object]}}. was: {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 <input id=form:j_idt9 ...> log.js.jsf?ln=org.richfaces:160 RichFaces: Received 'beforedomupdate' event from <input id=form:j_idt9 ...> 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@malformedXML' event from <input id=form:j_idt9 ...> 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 <input id=form:j_idt9 ...> {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.A...] generated jQuery object, which is in turn printed as {{[Object]}}. > 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 <input id=form:j_idt9 ...> log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'beforedomupdate' event from <input id=form:j_idt9 ...> 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@malformedXML' event from <input id=form:j_idt9 ...> 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 <input id=form:j_idt9 ...> > {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.A...] 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13138) a4j:log - should print partial-response value in a level=debug, but prints [Object] instead

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13138?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13138: ---------------------------- Fix Version/s: 5.0.0.Alpha1 Affects Version/s: 4.3.3 > 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 <input id=form:j_idt9 ...> log.js.jsf?ln=org.richfaces:160 > RichFaces: Received 'beforedomupdate' event from <input id=form:j_idt9 ...> 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@malformedXML' event from <input id=form:j_idt9 ...> 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 <input id=form:j_idt9 ...> > {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.A...] 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13138) a4j:log - should print partial-response value in a level=debug, but prints [Object] instead

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13138: ------------------------------- Summary: 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) Reporter: Lukáš Fryč {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 <input id=form:j_idt9 ...> log.js.jsf?ln=org.richfaces:160 RichFaces: Received 'beforedomupdate' event from <input id=form:j_idt9 ...> 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@malformedXML' event from <input id=form:j_idt9 ...> 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 <input id=form:j_idt9 ...> {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.A...] 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13137) a4j:log - wrong log levels in attribute description

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13137: ------------------------------- Summary: a4j:log - wrong log levels in attribute description Key: RF-13137 URL: https://issues.jboss.org/browse/RF-13137 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.3.4 The description is: {code} Sets the logging level, can be one of "ERROR", "FATAL", "INFO", "WARN", "ALL" {code} but should be: {code} Sets the logging level, can be one of 'debug', 'info', 'warn', 'error'. {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13033) inputNumberSlider, inputNumberSpinner: @label is not working

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13033?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13033: ---------------------------------- Thanks for clarification [~bleathem]. I tried it and it is working. You can close this issue. Just 1 Question: why does the label attribute only work with jsf (f:validateLength, ...) validators? > inputNumberSlider, inputNumberSpinner: @label is not working > ------------------------------------------------------------ > > Key: RF-13033 > URL: https://issues.jboss.org/browse/RF-13033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, doc > Affects Versions: 3.3.2.CR1, 4.3.2, 5.0.0.Alpha1 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > These two components have attribute @label. > And it doesn't work -- there is no sign of it on the page source. > Where should it be displayed? Should it replace the default value? > Or should this attribute be deleted? > Please also update the VDL-DOC in all cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13136) a4j:log with mode=console doesn't take log level into consideration

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13136?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13136: ---------------------------- Description: Here the log.js [logs message to browser console|https://github.com/richfaces4/components/blob/4.3.3.20130710-Fina...] but it ignores [log level check|https://github.com/richfaces4/components/blob/4.3.3.20130710-Final/...] which happens only for other modes. > a4j:log with mode=console doesn't take log level into consideration > ------------------------------------------------------------------- > > Key: RF-13136 > URL: https://issues.jboss.org/browse/RF-13136 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > > Here the log.js [logs message to browser console|https://github.com/richfaces4/components/blob/4.3.3.20130710-Fina...] > but it ignores [log level check|https://github.com/richfaces4/components/blob/4.3.3.20130710-Final/...] which happens only for other modes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13136) a4j:log with mode=console doesn't take log level into consideration

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13136: ------------------------------- Summary: a4j:log with mode=console doesn't take log level into consideration Key: RF-13136 URL: https://issues.jboss.org/browse/RF-13136 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.3.3 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.3.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13095) extendedDataTable tableState setter not called on column resize/reorder

by Salvo Isaja (JIRA)

[ https://issues.jboss.org/browse/RF-13095?page=com.atlassian.jira.plugin.s... ] Salvo Isaja commented on RF-13095: ---------------------------------- Brian, I'm no longer able to reproduce the problem and now the setter is called for me, even downgrading from 4.3.3 back to 4.3.2. Unfortunately my project was not under version control, so I can't check against the code as it was when I filed this issue. It's likely it was due to my fault, as I've messed around with transient views, request-only backing beans and fiddling with the request parameters to fool JSF and make it accept my postbacks even in the stateless case (see also issue RF-13093). By the way, the tableState setter is called even in this scenario, now. If the reporter of RF-13126 has not a counterexample, please feel free to close this issue. Thank you for your help. > extendedDataTable tableState setter not called on column resize/reorder > ----------------------------------------------------------------------- > > Key: RF-13095 > URL: https://issues.jboss.org/browse/RF-13095 > 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, tested on Firefox 22 and Chrome 28. > Reporter: Salvo Isaja > Assignee: Brian Leathem > Labels: waiting_on_user > Fix For: 4.3.4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Not sure if this qualifies as a bug or a feature request. > I have an extendedDataTable with the tableState attribute bound to a String property of a backing bean (tried both a request scoped bean on a transient view and a session scoped bean on a stateful view). > When resizing or reordering columns, an Ajax request is posted to the server, and I correctly see the new column layouts in the request, but the setter of the tableState property in the backing bean is not called. If I execute @form on a a4j:commandLink or commandButton, it is called instead. > 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2013