December 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10074) Showcase: drag-and-drop sample doesn't work

by Pavol Pitonak (JIRA)

Showcase: drag-and-drop sample doesn't work ------------------------------------------- Key: RF-10074 URL: https://issues.jboss.org/browse/RF-10074 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Milestone5 Environment: RichFaces/Showcase 4.0.0.20101220-M5 JBoss AS 6 CR1 Reporter: Pavol Pitonak 1. deploy Showcase to JBoss AS 6 CR1 2. open http://localhost:8080/richfaces-showcase/richfaces/component-sample.jsf?d... result: javax.faces.view.facelets.TagException: /richfaces/dragDrop/samples/dragDrop-sample.xhtml @41,49 <rich:dragBehavior> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: dragBehavior at com.sun.faces.facelets.compiler.CompilationManager.pushTag(CompilationManager.java:289) at com.sun.faces.facelets.compiler.SAXCompiler$CompilationHandler.startElement(SAXCompiler.java:228) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:195) at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:388) at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:364) at com.sun.faces.facelets.compiler.Compiler.compile(Compiler.java:122) at com.sun.faces.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:294) at com.sun.faces.facelets.impl.DefaultFaceletFactory.access$100(DefaultFaceletFactory.java:89) at com.sun.faces.facelets.impl.DefaultFaceletFactory$1.newInstance(DefaultFaceletFactory.java:159) at com.sun.faces.facelets.impl.DefaultFaceletFactory$1.newInstance(DefaultFaceletFactory.java:158) at com.sun.faces.facelets.impl.DefaultFaceletCache$1.newInstance(DefaultFaceletCache.java:79) at com.sun.faces.facelets.impl.DefaultFaceletCache$1.newInstance(DefaultFaceletCache.java:75) at com.sun.faces.util.ExpiringConcurrentCache$1.call(ExpiringConcurrentCache.java:95) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at com.sun.faces.util.ExpiringConcurrentCache.get(ExpiringConcurrentCache.java:110) at com.sun.faces.facelets.impl.DefaultFaceletCache.getFacelet(DefaultFaceletCache.java:115) at com.sun.faces.facelets.impl.DefaultFaceletCache.getFacelet(DefaultFaceletCache.java:58) at com.sun.faces.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:245) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:362) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:342) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:196) at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:104) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:162) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:89) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:79) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:304) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:363) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:342) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:196) at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:104) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:99) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:174) at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:392) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:363) at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:104) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:131) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:55) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:162) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:114) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:156) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:89) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:94) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:79) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:304) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:363) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:342) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:196) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:151) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:89) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:79) at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:148) at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:734) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:96) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:135) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:309) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) at java.lang.Thread.run(Thread.java:636) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] Created: (RF-4464) inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs.

by Mikhail Vitenkov (JIRA)

inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs. ----------------------------------------------------------------------------------------------- Key: RF-4464 URL: https://jira.jboss.org/jira/browse/RF-4464 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.52(3.3.0) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Add following code on the page(rich:tabPanel with two tabs, which contained inputNumberSlider component): <h:form> <rich:tabPanel switchType="client"> <rich:tab label="First"> Here is tab #1 <rich:inputNumberSlider value="10" /> </rich:tab> <rich:tab label="Second"> Here is tab #2 <rich:inputNumberSlider value="20" /> </rich:tab> </rich:tabPanel> <h:commandButton action="submit" value="Submit" /> </h:form> #2. Navigate to the page. #3. Go to "Second" tab. #4. Set pointer to max(100) value. #5. Return to the "First" tab & click "Submit" button(see #1) #6. Navigate to "Second" tab again & verify position of slider's pointer. #8. Enter '80' in component's input & press 'Enter'. #9. Turn back to "First" tab & press "Submit". Actual behavior: #6: Pointer is at the right border of component's input. See attachment. #9: Pointer moves to left. Screenshot described #6 issue is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
15
0 / 0

[JBoss JIRA] Created: (RF-9726) rich:dataScroller on rich:dataTable - switching pages doesn't work (MyFaces)

by Lukas Fryc (JIRA)

rich:dataScroller on rich:dataTable - switching pages doesn't work (MyFaces) ---------------------------------------------------------------------------- Key: RF-9726 URL: https://jira.jboss.org/browse/RF-9726 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone4 Environment: RichFaces 4.0.0.20101107-M4 r.19981 Metamer 4.0.0.20101107-M4 r.19986 Apache MyFaces JSF-2.0 Core Impl 2.0.2 Apache Tomcat 6.0.29 OpenJDK Runtime Environment 1.6.0_18-b18 @Linux Chrome 7.0.517.44 @ Win32 Reporter: Lukas Fryc Attachments: Screenshot-23.png 1. scroller in table footer - You have to click twice to one page number to rerender content 2. scroller outside table (above the table) - You have to click twice to rerender content 3. scroller outside table (above the table) - current page isn't shown well - the active item doesn't change when switching pages 4. Generated markup replacements are sometimes wrong (see screenshot) when clicking to the scroller outside table (above the table) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
11
0 / 0

[JBoss JIRA] Updated: (RF-7821) Status: client-side API

by Nick Belaevski (JIRA)

[ https://issues.jboss.org/browse/RF-7821?page=com.atlassian.jira.plugin.sy... ] Nick Belaevski updated RF-7821: ------------------------------- Assignee: Konstantin Mishin (was: Nick Belaevski) Fix Version/s: 4.0.0.CR1 (was: Future_4.X) > Status: client-side API > ----------------------- > > Key: RF-7821 > URL: https://issues.jboss.org/browse/RF-7821 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Konstantin Mishin > Fix For: 4.0.0.CR1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (RF-9560) collapsiblePanel: use 'pointer' cursor over the switch control

by Ilya Shaikovsky (JIRA)

collapsiblePanel: use 'pointer' cursor over the switch control -------------------------------------------------------------- Key: RF-9560 URL: https://jira.jboss.org/browse/RF-9560 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.0.0.Milestone4 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Minor Fix For: Future_4.X currently at least over header. (in future if control and body states for switching will be implemented - should also support that) I think should be M5. especially considering impl complexity -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (RF-5379) Calendar: 'getData' JS API method is not implemented ot does not work

by Andrei Markavtsov (JIRA)

Calendar: 'getData' JS API method is not implemented ot does not work --------------------------------------------------------------------- Key: RF-5379 URL: https://jira.jboss.org/jira/browse/RF-5379 Project: RichFaces Issue Type: Bug Affects Versions: 3.0.0 Environment: RF 3.0.0.SNAPSHOT Reporter: Andrei Markavtsov Assignee: Nick Belaevski The method was described in developer guide : p. 6.27.6. JavaScript API. Currently, $('calendarId').component.getData(date) method causes JS 'is not a function' error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
9
0 / 0

[JBoss JIRA] Created: (RF-9482) rich:calendar backed by String not using custom converter

by Nicola Jones (JIRA)

rich:calendar backed by String not using custom converter --------------------------------------------------------- Key: RF-9482 URL: https://jira.jboss.org/browse/RF-9482 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 3.3.3.Final Environment: Found in RichFaces 3.3.3Final Reporter: Nicola Jones When a rich:calendar is backed by a String property and has a custom converter to change the date pattern of the String to & from a user locale specific pattern, it fails to use the converter when determining or setting the current date. datePattern set on the rich:calendar is a user specific format read from properties. HtmlCalendar getCurrentDate returns the unconverted form property value i.e. not in the user's format. UICalendar then calls getAsDate(currentDate) which detects that the value is a String and not a Date and attempts to convert it to a Date: if (date instanceof String) { DateTimeConverter converter = new DateTimeConverter(); converter.setPattern(this.getDatePattern()); this results in an exception because it's using the date pattern for the calendar which is different to the unconverted format of the current date. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (RF-10046) Core: investigate and implement removal of bound jQuery event handlers on elements deletion by AJAX

by Nick Belaevski (JIRA)

Core: investigate and implement removal of bound jQuery event handlers on elements deletion by AJAX --------------------------------------------------------------------------------------------------- Key: RF-10046 URL: https://issues.jboss.org/browse/RF-10046 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Milestone5 Reporter: Nick Belaevski Assignee: Pavel Yaschenko Priority: Critical Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (RF-2968) Deprecate MethodBinding in favor to MethodExpression

by Nick Belaevski (JIRA)

Deprecate MethodBinding in favor to MethodExpression ---------------------------------------------------- Key: RF-2968 URL: http://jira.jboss.com/jira/browse/RF-2968 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Nick Belaevski Assigned To: Maksim Kaszynski Fix For: 3.2.1 Deprecate MethodBinding/ValueBinding properties in favor to MethodExpression/ValueExpression -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
9
0 / 0

[JBoss JIRA] Created: (RF-9820) Core: richfaces.js should remove event handlers when element is destroyed

by Nick Belaevski (JIRA)

Core: richfaces.js should remove event handlers when element is destroyed ------------------------------------------------------------------------- Key: RF-9820 URL: https://jira.jboss.org/browse/RF-9820 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component, core Affects Versions: 4.0.0.Milestone4 Reporter: Nick Belaevski Assignee: Pavel Yaschenko Fix For: 4.0.0.Milestone5 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2010