February 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8189) Move repository.exadel.com from .m2/settings to profiles.jboss-qa.xml

by Lukas Fryc (JIRA)

Move repository.exadel.com from .m2/settings to profiles.jboss-qa.xml --------------------------------------------------------------------- Key: RF-8189 URL: https://jira.jboss.org/jira/browse/RF-8189 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: QA-environment Reporter: Lukas Fryc Assignee: Lukas Fryc Priority: Minor Exadel repository shoudn't be in global settings for hudson, but it will be placed in profiles.jboss-qa.xml in hudson. Modify the hudson .m2/settings.xml and profiles.jboss-qa.xml accordingly. -- 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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (RF-7977) RF demo - ftest - TooltipDataTableTestCase - class for table's header changed

by Lukas Fryc (JIRA)

RF demo - ftest - TooltipDataTableTestCase - class for table's header changed ----------------------------------------------------------------------------- Key: RF-7977 URL: https://jira.jboss.org/jira/browse/RF-7977 Project: RichFaces Issue Type: Bug Components: QA-environment, functional-tests Affects Versions: 3.3.2.GA Environment: RF 3.3.2.SR1 Reporter: Lukas Fryc Assignee: Lukas Fryc Priority: Minor Fix For: 3.3.3.CR1 There was @class='rich-table', but it was extended by white-space to @class='rich-table '. Change xpath in ftest. -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (RF-7976) RF demo - ftest - ExtendedDataTable - 'rich-table' class was removed

by Lukas Fryc (JIRA)

RF demo - ftest - ExtendedDataTable - 'rich-table' class was removed -------------------------------------------------------------------- Key: RF-7976 URL: https://jira.jboss.org/jira/browse/RF-7976 Project: RichFaces Issue Type: Bug Components: QA-environment, functional-tests Affects Versions: 3.3.2.GA Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 3.3.3.CR1 Xpathes needs to be modified since 'rich-table' class was removed from extdt structure. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (RF-7970) Richfaces-demo functional test - CalendarTestCase - The name of the month is not localized

by Lukas Fryc (JIRA)

Richfaces-demo functional test - CalendarTestCase - The name of the month is not localized ------------------------------------------------------------------------------------------ Key: RF-7970 URL: https://jira.jboss.org/jira/browse/RF-7970 Project: RichFaces Issue Type: Bug Components: functional-tests Affects Versions: 3.3.2.GA Environment: richfaces-demo-3.3.2-20090930.204720-132.war JBoss 5.1.0.GA Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 3.3.2.SP1 The calendar uses bad check of Calendar's german localization - it works in September (for de and en same), but not in October (for de it's Oktober) -- 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

16 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (RF-8349) Review docs with missing skinning images

by Sean Rogers (JIRA)

Review docs with missing skinning images ---------------------------------------- Key: RF-8349 URL: https://jira.jboss.org/jira/browse/RF-8349 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.3.3.CR1 Reporter: Sean Rogers Assignee: Sean Rogers Fix For: Future Component descriptions in current docs no longer have diagrams showing skinned elements. Investigate these changes and make decisions for future docs. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (RF-8337) AJAX: a4j:* components are not working in 4.x trunk

by Nick Belaevski (JIRA)

AJAX: a4j:* components are not working in 4.x trunk --------------------------------------------------- Key: RF-8337 URL: https://jira.jboss.org/jira/browse/RF-8337 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Pavel Yaschenko Priority: Blocker Fix For: 4.0.0.ALPHA2 a4j:* components are not submitting parameters correctly due to issues in queue script. Reproducible on richfaces-demo. -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-8340) Always same id created for embedded tags while interating over table entries

by Manuel Fehlhammer (JIRA)

Always same id created for embedded tags while interating over table entries ---------------------------------------------------------------------------- Key: RF-8340 URL: https://jira.jboss.org/jira/browse/RF-8340 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-ScrollableDataTable Affects Versions: 3.3.2.SR1 Environment: MS Vista 64bit, IE8 Reporter: Manuel Fehlhammer While iterating over the collection entries and creating rows, ScrollableDataTable always assigns the same id to embedded images. Example: <rich:scrollableDataTable value="#{userReportManager.allUserReports}" var="userReport"> <rich:column id="type"> <f:facet name="header"><h:outputText styleClass="headerText" value="#{bundle.tableHeaderReportType}"/></f:facet> <h:graphicImage id="employeeWorkdayReportIcon" value="images/time_sheet_16.png"/> <rich:toolTip for="employeeWorkdayReportIcon" value="#{bundle.employeeWorkdayReportTitle}" /> </rich:column> for all rows the id=j_id26:userReportList:0:employeeWorkdayReportIcon for the graphicImage is created. I expect the counter in the middle of the id-String to be incremented. Because of this bug the rich:tooltip for the image does not function. -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8107) Development: extended dataTable "no data" facet support

by Anton Belevich (JIRA)

Development: extended dataTable "no data" facet support ------------------------------------------------------- Key: RF-8107 URL: https://jira.jboss.org/jira/browse/RF-8107 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Konstantin Mishin Fix For: 4.0.0.ALPHA2 -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-4415) Application does not work in Weblogic 10gR3

by Cesar Perez (JIRA)

Application does not work in Weblogic 10gR3 ------------------------------------------- Key: RF-4415 URL: https://jira.jboss.org/jira/browse/RF-4415 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1, 3.2.2 Environment: Windows XP SP3, Oracle Weblogic 10g R3, JSF 1.2, Richfaces 3.2.1 and 3.2.2 and probably older version. Reporter: Cesar Perez If I use RichFaces 3.2.1 and even 3.2.2CR3 with JSP as my view handler I cannot open a JSP page, even if it doesn't contains any RF tags. This happens on Weblogic 10 and the latest 10g R3. In Tomcat the code works just fine without any issues. I created an example eclipse project that shows this issue under Weblogic 10g R3. It contains a configuration to use either JSP or Facelets for the view. If you open the .xhtml file the page will be displayed just fine but if you try to open the JSP an exception is thrown. In Weblogic I created a new domain with all the default options and I am deploying the application through Eclipse but I have also tried deploying a WAR/EAR getting the same exception when I try to access the JSP. Also you can remove all the facelets configuration and just leave JSP to handle the view, the exception will be thrown too. The only possible fix I have found is to use facelets instead of JSP but in the project I am working on that's just not possible. The example project is here: http://rs420l3.rapidshare.com/cgi-bin/upload.cgi?rsuploadid=3180178713302... The stacktrace is: java.lang.IllegalStateException: Servlet response already use stream, Writer not possible at org.ajax4jsf.webapp.FilterServletResponseWrapper.getWriter(FilterServletResponseWrapper.java:226) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:186) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:547) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:189) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:547) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:547) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:189) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:503) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:251) at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:159) at jsp_servlet.__index._jspService(__index.java:72) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) -- 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

16 years, 2 months

8
23
0 / 0

[JBoss JIRA] Created: (RF-8343) Add fallback to a4j:commandLink and a4j:commandButton in case javascript is disabled (e.g. SEO support)

by Thomas Goettlich (JIRA)

Add fallback to a4j:commandLink and a4j:commandButton in case javascript is disabled (e.g. SEO support) ------------------------------------------------------------------------------------------------------- Key: RF-8343 URL: https://jira.jboss.org/jira/browse/RF-8343 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 3.3.2.SR1 Reporter: Thomas Goettlich Currently, a4j:commandLink and a4j:commandButton only support ajax requests which might not work if javascript is disabled. Thus, user who have stricter security in place or search engine robots can't follow those links. If would be good, if both aj4:commandLink and a4j:commandButton would support ajax as well as non-ajax request, e.g. by using the Hijax approach (http://www.informit.com/articles/article.aspx?p=789762). -- 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

16 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2010