August 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12441) DnD: default indicator doesn't work

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-12441: ---------------------------------- Summary: DnD: default indicator doesn't work Key: RF-12441 URL: https://issues.jboss.org/browse/RF-12441 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-drag/drop, regression Affects Versions: 4.3.0.Milestone1 Environment: RichFaces 4.3.0-SNAPSHOT Metamer 4.3.0-SNAPSHOT Mojarra 2.1.7 JBoss AS 7.1.2.Final-redhat-1 Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux Chrome 21.0.1180.81 @ Linux x86_64 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richDragSource/simple.xhtml # drag the first rectagle (#1: type=drg1) to the left yellow target # repeat it once again result: * drag indicator is attached to the "body" element in DOM twice, custom indicators work correctly * see attached images, the generated code isn't the same (4.3.0-SNAPSHOT vs. 4.2.2.Final) -- This message is automatically generated by JIRA. 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, 6 months

2
6
0 / 0

[JBoss JIRA] (RF-11711) a4j:queue - attributes onsubmit, oncomplete, onevent does not work

by Lukáš Fryč (Created) (JIRA)

a4j:queue - attributes onsubmit, oncomplete, onevent does not work ------------------------------------------------------------------ Key: RF-11711 URL: https://issues.jboss.org/browse/RF-11711 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.1.0.CR1 Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

9
14
0 / 0

[JBoss JIRA] (RF-12353) Incorrect documentation/taglib on <a4j:param>

by Alexander Kiselyov (JIRA)

Alexander Kiselyov created RF-12353: --------------------------------------- Summary: Incorrect documentation/taglib on <a4j:param> Key: RF-12353 URL: https://issues.jboss.org/browse/RF-12353 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, doc Affects Versions: 4.2.2.Final, 4.2.0.Final Environment: no matter Reporter: Alexander Kiselyov Priority: Minor Technical background (RichFaces developers can easy skip it): ---- <a4j:param> performs setting of its value into an expression specified in "assignTo" attribute. As this component is set as Action listener for ActionSource parent - org.richfaces.component.AbstractParameter.processAction(ActionEvent) is called. This method directly retrieves request parameter with this parameter's name/clientId: String requestValue = context.getExternalContext().getRequestParameterMap().get(getName()); and then, if converter's not found, sets it as a value of an expression, specified in "assignTo": {code} if (requestValue != null) { Class<?> type = updateBinding.getType(elContext); Converter converter = createConverter(context, type); ... } if (null != convertedValue) { updateBinding.setValue(elContext, convertedValue); } {code} When our expression value has reifiable type, for which JSF (or app developer) has registered a converter (for instance - Boolean) - all's peachy keen. But when developer uses, e.g., Map - expression's type (got in updateBinding.getType(ELContext)) is Object, and we're starting to receive strings in Map, which is probably parameterized with anything. Also this situation applies to "non-standard" reference types (user-declared JavaBean, for instance). {code} org.richfaces.view.facelets.html.ParameterHandler: org.richfaces.view.facelets.html.ParameterHandler.ActionParamMetaRule.applyRule(String, TagAttribute, MetadataTarget): ... else if ("converter".equals(name)) { if (attribute.isLiteral()) { return new LiteralConverterMetadata(attribute.getValue()); } else { return new DynamicConverterMetadata(attribute); } } ... {code} I.e. <a4j:param> tag handler designed to accept "converter" attribute, which can appropriately convert value, passed from client. ---- [a4j:param VDL Doc|http://docs.jboss.org/richfaces/4.2.X/4.2.2.Final/vdldoc/a4j/param.html] has no mention of it, and value/assignTo attributes type specified as "java.lang.Object". a4j.taglib.xml has no mention of it, so developers have no chance to discover it, e.g., through the content assist, [Rich Component Reference|http://docs.jboss.org/richfaces/4.2.X/4.2.2.Final/Component_Ref...] has only two sentences about it, which are *very easy to miss*. Also, [RichFaces Showcase|http://showcase.richfaces.org/richfaces/component-sample.jsf?dem...] contains no example, which uses "converter" attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
5
0 / 0

[JBoss JIRA] (RF-12327) NPE in calendar if enableManualInput=true

by Paul Dijou (JIRA)

12 years, 6 months

3
16
0 / 0

[JBoss JIRA] Created: (RF-10620) Remove or externalize maven-javascript-plugin 3rd party software from RichFaces

by Jay Balunas (JIRA)

Remove or externalize maven-javascript-plugin 3rd party software from RichFaces ------------------------------------------------------------------------------- Key: RF-10620 URL: https://issues.jboss.org/browse/RF-10620 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.0.0.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 4.Next See source and details at maven-javascript-plugin. For these external sources we need to: * Verify why we are building and using these. ** Does not seem to be used in our source at all * Determine how to either only depend on external sources, or pull these out into their own project to be built separately. ** If a separate project with completely out of RichFaces, or in the /build/resources area. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
21
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functinoality to the rich:select component

by Brian Leathem (Created) (JIRA)

Add autocomplete functinoality to the rich:select component ----------------------------------------------------------- Key: RF-11453 URL: https://issues.jboss.org/browse/RF-11453 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-selects Reporter: Brian Leathem Fix For: 4.2.0.Tracking Add an "autocompleteMethod" to rich:select -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
7
0 / 0

[JBoss JIRA] (RF-12222) RF 4.2.1: Instatiation exception when PartialStateSaving=false

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12222: -------------------------------- Summary: RF 4.2.1: Instatiation exception when PartialStateSaving=false Key: RF-12222 URL: https://issues.jboss.org/browse/RF-12222 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: regression Affects Versions: 4.2.1.Final Environment: RichFaces 4.2.1.SNAPSHOT Metamer 4.2.1.SNAPSHOT Mojarra 2.1.7-jbossorg-1 JBoss AS 7.1.1.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 12.0 @ Linux x86_64 Reporter: Jiří Štefek When you set PartialStateSaving in web.xml to false (true works fine) in RF 4.2.1 (in RF 4.2.0 is everything fine) then you'll have problems with Instatiation exception. See workaround for more informations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] (RF-12363) Allow managed Arquillian in-container tests execution with TomEE

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12363: ------------------------------- Summary: Allow managed Arquillian in-container tests execution with TomEE Key: RF-12363 URL: https://issues.jboss.org/browse/RF-12363 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 4.3.0.Milestone1 Reporter: Lukáš Fryč For MyFaces integration testing, we are using TomEE container, which allow us to configure tests with single dependency (no additional libraries are necessary to provide as for Servlet containers like Tomcat). But there are only {{embedded}} and {{remote}} adapters for Arquillian integration: http://svn.apache.org/viewvc/openejb/trunk/openejb/arquillian/ As we need to run tests on real container, we would need {{managed}} version of TomEE container. {{embedded}} container is not enough, since it doesn't have to provide real feedback - see [Danger of Embedded Containers|http://arquillian.org/blog/2012/04/13/the-danger-of-embedded-c...]. ---- Some reports adapter for Tomcat 7 should work almost fine with TomEE: https://community.jboss.org/thread/199103 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
9
0 / 0

[JBoss JIRA] (RF-12426) rich:collapsibleSubTable - does not works very well under IE and Firefox - Bad rendering and javascript error

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12426: ------------------------------- Summary: rich:collapsibleSubTable - does not works very well under IE and Firefox - Bad rendering and javascript error Key: RF-12426 URL: https://issues.jboss.org/browse/RF-12426 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.2.Final Environment: Mojarra 2.1.12 - Firefox 14.1 and IE 8 - RAD 8.0.0.4 - WAS 8.0.0.x - Spring 3.0.6 Reporter: Jean ANDRE We have a collapsibleSubTable inside table which is inside a tab (see screen capture) created dynamically. Without the collapsibleSubTable, the table is displayed well but as soon as the add this subTable, everything is going wrong. Under firefox we got the following error messages: TypeError: RichFaces.ui.CollapsibleSubTable is not a constructor TypeError: source is null if (source.nodeType) { inside the source richfaces.js.jsf if (type == "string") { // id element = document.getElementById(source); } else if (type == "object") { 42 >>>>>>>>>>>>>>>>>if (source.nodeType) { // DOM element Under IE, the rendering is worst and IE is not able to show the detail of the error except this: Line: 168838013 Erreur : Objet attendu -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
12
0 / 0

[JBoss JIRA] (RF-12219) Push: Test that messages do not become stale in a queue

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12219: ------------------------------- Summary: Push: Test that messages do not become stale in a queue Key: RF-12219 URL: https://issues.jboss.org/browse/RF-12219 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.1.Final Reporter: Lukáš Fryč According to the [Forum reference], we can have problems with stale messages. I would suggest to write tests for following scenarios and check that queue is destroyed properly: * view expires * client leaves the page with {{a4j:push}} without proper clean up * ... Let's brainstorm other scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
56
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2012