May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12903) Optimize resources during Framework build (avoid unnecessary step and assembly); rename richfaces-framework.jar to richfaces.jar

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12903?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12903. ---------------------------- Verified. Closing. > Optimize resources during Framework build (avoid unnecessary step and assembly); rename richfaces-framework.jar to richfaces.jar > -------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12903 > URL: https://issues.jboss.org/browse/RF-12903 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12937) Introduce a profile for running framework tests against JBoss EAP

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12937?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12937. ---------------------------- Verified for 5.Alpha1 as well. Closing. > Introduce a profile for running framework tests against JBoss EAP > ----------------------------------------------------------------- > > Key: RF-12937 > URL: https://issues.jboss.org/browse/RF-12937 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.2, 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12982) Move optimized resources to resource/org.richfaces.optimized and mapping to optimizedResourcesMapping

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12982?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12982. ---------------------------- Verified. Closing. > Move optimized resources to resource/org.richfaces.optimized and mapping to optimizedResourcesMapping > ----------------------------------------------------------------------------------------------------- > > Key: RF-12982 > URL: https://issues.jboss.org/browse/RF-12982 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12843) Apply unix style line-endings to the entire codebase

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12843?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12843. ----------------------------- verified in 5.0.0.Alpha1 > Apply unix style line-endings to the entire codebase > ---------------------------------------------------- > > Key: RF-12843 > URL: https://issues.jboss.org/browse/RF-12843 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Having only unix-style line-endings in place will ease the backporting of issues from 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12933) rich:tooltip replace 'defaultContent' facet in docs and examples with 'loading'

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12933?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12933. ----------------------------- > rich:tooltip replace 'defaultContent' facet in docs and examples with 'loading' > ------------------------------------------------------------------------------- > > Key: RF-12933 > URL: https://issues.jboss.org/browse/RF-12933 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.2.1.Final > Reporter: Guillaume Morin-Brassard > Assignee: Brian Leathem > Fix For: 4.3.2, 5.0.0.Alpha1 > > > The rich:tooltip defaultContent facet is not working. See you showcase for a proof. > The default content is always "Loading...". > My version is the 4.2.1 Final but i see it is still not working in the 4.3.1 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes do not work

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12839. ----------------------------- verified that the given commits are present in 5.0.0.Alpha1 > Toggle panels: ajax-related attributes do not work > -------------------------------------------------- > > Key: RF-12839 > URL: https://issues.jboss.org/browse/RF-12839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 4.3.2-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4 > JBoss AS 7.1.3.Final-redhat-4 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 25.0.1364.160 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # set oncomplete to "alert('complete')" > # switch to tab 2 and back to tab 1 > result: > * alert should be diplayed but isn't > * tabs are correctly switched > * worked fine in 4.2.3.Final > * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status > * affected components: tab, toggle panel item, accordion item -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12931) rich:fileupload broken with jsf.js changes in Mojarra 2.1.21

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12931?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12931. ----------------------------- verified in 5.0.0.Alpha1 > rich:fileupload broken with jsf.js changes in Mojarra 2.1.21 > ------------------------------------------------------------ > > Key: RF-12931 > URL: https://issues.jboss.org/browse/RF-12931 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-input > Affects Versions: 4.3.1 > Environment: Glassfish 3.2.1.1, Tomcat 7.0.35 > Mojarra 2.1.21 > Chrome 26, Firefox 20 > Reporter: Frederick Kämpfer > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > On recent versions of Mojarra the following simple fileupload facelet page produces an javascript error: > {code:xml} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:rich="http://richfaces.org/rich" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:c="http://java.sun.com/jsp/jstl/core"> > <f:view> > <h:head> > </h:head> > <h:body> > <script type="text/javascript"> > jsf.ajax.addOnError(function(e) { > console.log(e); > alert("An error occured:\n" + e.errorName + '\n' + e.description); > }); > </script> > <h:form> > <rich:fileUpload/> > </h:form> > </h:body> > </f:view> > </html> > {code} > The problem seems to be that the context.element parameter is undefined in jsf.ajax.response. Probably due to RichFaces' Javascript extensions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12998) Showcase - resource handling errors for all demos on Tomcat 7

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12998?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12998. ---------------------------- I have verified Showcase on all supported containers. Closing. > Showcase - resource handling errors for all demos on Tomcat 7 > ------------------------------------------------------------- > > Key: RF-12998 > URL: https://issues.jboss.org/browse/RF-12998 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: regression, resource handling, showcase > Affects Versions: 5.0.0.Alpha1 > Environment: Tomcat 7 > Reporter: Juraj Húska > Assignee: Brian Leathem > Priority: Blocker > Fix For: 5.0.0.Alpha1 > > Attachments: resourceWrong.png > > > This is noticeable after resolving RF-12996 locally. > There are lot of resource not found and JQUery not defined JS errors when loading showcase on Tomcat 7. It is so for all demos. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12996) Showcase - deployment on Tomcat 7 with errors

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12996?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12996. ---------------------------- Verified. Closing. > Showcase - deployment on Tomcat 7 with errors > --------------------------------------------- > > Key: RF-12996 > URL: https://issues.jboss.org/browse/RF-12996 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: regression, showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Blocker > Fix For: 5.0.0.Alpha1 > > > *Showcase can not be successfully deployed on Tomcat 7.* > There are errors on the console log: > {code:title=Tomcat 7} > May 21, 2013 11:07:04 AM org.apache.catalina.loader.WebappClassLoader validateJarFile > INFO: validateJarFile(/home/jhuska/workspace_java/jboss/richfaces/qa/showcase-ftest/target/apache-tomcat-7.0.39/webapps/showcase/ > WEB-INF/lib/jboss-el-api_2.2_spec-1.0.1.Final.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/ > el/Expression.class > May 21, 2013 11:07:04 AM org.apache.catalina.loader.WebappClassLoader validateJarFile > INFO: validateJarFile(/home/jhuska/workspace_java/jboss/richfaces/qa/showcase-ftest/target/apache-tomcat-7.0.39/webapps/showcase/ > WEB-INF/lib/jboss-servlet-api_3.0_spec-1.0.1.Final.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: j > avax/servlet/Servlet.class > SEVERE: Exception starting filter PushFilter > java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1713) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1558) > at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:527) > at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:509) > at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:137) > at org.jboss.weld.environment.tomcat7.ForwardingInstanceManager.newInstance(ForwardingInstanceManager.java:26) > at org.jboss.weld.environment.tomcat7.WeldForwardingInstanceManager.newInstance(WeldForwardingInstanceManager.java:62) > at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260) > at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:107) > at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4746) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5399) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:542) > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1462) > 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:601) > at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:301) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791) > at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1445) > at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:677) > at org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:435) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > May 21, 2013 11:07:18 AM org.apache.catalina.core.StandardContext startInternal > SEVERE: Error filterStart > May 21, 2013 11:07:18 AM org.apache.catalina.core.StandardContext startInternal > SEVERE: Context [/showcase] startup failed due to previous errors > {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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12935) Fix resolution of framework tests' artifacts with version enforced

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12935?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12935. ----------------------------- verified in 5.0.0.Alpha1 > Fix resolution of framework tests' artifacts with version enforced > ------------------------------------------------------------------ > > Key: RF-12935 > URL: https://issues.jboss.org/browse/RF-12935 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > Fix For: 4.3.2, 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

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2013