[JBoss JIRA] (RF-12060) element is null message when closing tab from an event click
by Jean ANDRE (JIRA)
Jean ANDRE created RF-12060:
-------------------------------
Summary: element is null message when closing tab from an event click
Key: RF-12060
URL: https://issues.jboss.org/browse/RF-12060
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.0.Final
Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final
Reporter: Jean ANDRE
There is a link to RF-11950.
We got the message "element is null" when we send a click event for closing a tab. To retrieve the id of the close button (an image), we use the function getElementById (because of RF-11950). The click function calls a javascript function declared by a4j:jsFunction (see index.hxtml file - close task).
This is the only information we have from firebug. When we close the tab directly by clicking on the close button/image, it works perfectly.
*Note :* Moreover, there is also a strange behavior related to generated id on close button/image. When we specified a fix id on the h:graphicImage, the first id is correct but there is no id on other close button/image from other tabs!???. Having a fix id should trigger a duplicate ID but as the ids are not generated on other tabs, it does not.
{code}
<f:facet name="header">
 <h:outputText value="#{msg[task.uiActivity.headerKey]}"
title="#{msg[task.uiActivity.headerKey]}" />
 <h:graphicImage id="closeTask" value="/images/closeButton.png"
styleClass="closeButton"
onclick="closeTask('#{task.id}');event.stopPropagation();" />
</f:facet>
<f:subview id="#{task.id}-subview">
<ui:include src="#{task.uiActivity.xhtmlFile}" />
</f:subview>
{code}
--
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, 9 months
[JBoss JIRA] (RF-11592) RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope
by Joshua Brookes (Created) (JIRA)
RichFaces 4.1 Milestone changes for fileUpload component incompatible with Apache MyFaces Orchestra conversation scope
----------------------------------------------------------------------------------------------------------------------
Key: RF-11592
URL: https://issues.jboss.org/browse/RF-11592
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Milestone2, 4.1.0.Milestone1, 4.1.0.Milestone3
Environment: Mojarra 2.1.3, JBoss AS 5.0.1, Apache MyFaces Orchestra 1.4, Spring 3.0.4
Reporter: Joshua Brookes
Attachments: fileUploadWeb.zip
There is a compatibility issue with recent changes in RichFaces 4.1 Milestone 1 and Apache MyFaces Orchestra conversation scope feature. When adding the org.apache.myfaces.orchestra.conversation.servlet.ConversationManagerSessionListener listener in web.xml the fileUpload component stops working. This did not pose a problem with RichFaces 4.0.0.Final.
Here is a stacktrace that shows the error:
{code}
Oct 25, 2011 11:45:01 AM org.richfaces.request.MultipartRequest25 parseIfNecessary
SEVERE: Exception parsing multipart request: Request prolog cannot be read
org.richfaces.exception.FileUploadException: Exception parsing multipart request: Request prolog cannot be read
at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:156)
at org.richfaces.request.MultipartRequest25.parseIfNecessary(MultipartRequest25.java:77)
at org.richfaces.request.MultipartRequest25.getParameter(MultipartRequest25.java:114)
at com.sun.faces.context.RequestParameterMap.containsKey(RequestParameterMap.java:99)
at java.util.Collections$UnmodifiableMap.containsKey(Collections.java:1280)
at org.apache.myfaces.orchestra.frameworkAdapter.jsf.JsfFrameworkAdapter.containsRequestParameterAttribute(JsfFrameworkAdapter.java:105)
at org.apache.myfaces.orchestra.conversation.ConversationManager.findConversationContextId(ConversationManager.java:169)
at org.apache.myfaces.orchestra.conversation.ConversationManager.getCurrentRootConversationContext(ConversationManager.java:580)
at org.apache.myfaces.orchestra.lib.jsf.ContextLockRequestHandler.init(ContextLockRequestHandler.java:87)
at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory$1.<init>(OrchestraFacesContextFactory.java:122)
at org.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory.getFacesContext(OrchestraFacesContextFactory.java:103)
at org.apache.myfaces.orchestra.requestParameterProvider.jsf.RequestParameterFacesContextFactory.getFacesContext(RequestParameterFacesContextFactory.java:93)
at org.richfaces.context.FileUploadFacesContextFactory.getFacesContext(FileUploadFacesContextFactory.java:136)
at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:446)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:416)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342)
at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:286)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
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.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Request prolog cannot be read
at org.richfaces.request.MultipartRequestParser.readProlog(MultipartRequestParser.java:270)
at org.richfaces.request.MultipartRequestParser.initialize(MultipartRequestParser.java:172)
at org.richfaces.request.MultipartRequestParser.parse(MultipartRequestParser.java:148)
... 32 more
{code}
--
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, 9 months
[JBoss JIRA] Created: (RF-9345) Richfaces HTTP Header Cache-Control settings, need 'public'
by igor regis (JIRA)
Richfaces HTTP Header Cache-Control settings, need 'public'
-----------------------------------------------------------
Key: RF-9345
URL: https://jira.jboss.org/browse/RF-9345
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: performance
Affects Versions: 3.3.3.Final, 3.3.3.CR1, 3.3.3.BETA1, 3.3.2.SR1, 3.3.2.GA, 3.3.2.CR1, 3.3.1
Environment: This issue affect any web browser according to w3c specification
Reporter: igor regis
If an application is running over https the web browser will only cache on disk, the Richfaces resources, if and only if, the Cache-control header (present on http header) has the value "public" on it. Otherwise the web browser will perform in memory cache, so when user restarts the browser the application will need to request all the resources again.
For applications running on corporative network, manipulating sensitive information, it's mandatory the use of a secure connection through https protocol, and form better performance is necessary for Richfaces to provide it's resources with this "public" mark on cache-control tag.
According the w3c specs (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1) Richfaces resources may be classified as public content with non individual information.
Here (https://community.jboss.org/thread/150732?tstart=0) there is a discussion about this issue, as well as the point on Richfaces source code that need to be changed.
--
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
12 years, 9 months
[JBoss JIRA] Created: (RF-7955) ExtendedDataTable : Only first column correctly resize
by Nicolas Gaudin (JIRA)
ExtendedDataTable : Only first column correctly resize
------------------------------------------------------
Key: RF-7955
URL: https://jira.jboss.org/jira/browse/RF-7955
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.2.GA, 3.3.2.CR1
Environment: JSF RI 1.2_13
Facelets 1.1.14 (with .jspx files)
Glassfish
Jdk 1.6
Reporter: Nicolas Gaudin
Fix For: 3.3.2.GA
Hi,
During my test to deliver, I discovered that the columns of all my EDTs would not resize correctly.
More precisely, the first column resizes without any problem but the others resize WITHOUT resizing the header.
I must mention that my EDT use value binding for dynamic column creation.
My actions that generated this issue:
- moved from jsp to facelets (with jspx extension)
- upgraded to JSF 1.2_13
This affected 3.3.2.CR1, the version I was using.
I then upgraded to 3.3.2.GA to check if this would fix but no luck
Also, I thought that 3.3.2.GA would full scrolling support for EDT (horizontal mainly)
Is that the case?
Could you please confirm?
May thanks in advance
--
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
12 years, 9 months
[JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel
by Jean ANDRE (JIRA)
Jean ANDRE created RF-12052:
-------------------------------
Summary: rich:TabPanel - HTML comments should be supported inside the tabPanel
Key: RF-12052
URL: https://issues.jboss.org/browse/RF-12052
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Jean ANDRE
Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is:
E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase <Null Message>
java.lang.IllegalArgumentException
at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490)
{code}
<rich:tabPanel id="itemView-tabs"
switchType="ajax"
headerPosition="top"
itemChangeListener="#{viewItemController.doItemChangeListener}"
activeItem="#{viewItemController.activeTab}"
immediate="true">
<!-- -->
<!-- SUB-TABS #1 -->
<!-- -->
<rich:tab id="nested-tabs-1" header="#{msg['nested.tab.static.header.1']}">
</rich:tab>
{code}
Thank you.
--
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, 9 months
[JBoss JIRA] (RF-12068) rich:toggleControl: can't use immediate=true
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-12068:
-------------------------------
Summary: rich:toggleControl: can't use immediate=true
Key: RF-12068
URL: https://issues.jboss.org/browse/RF-12068
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-panels-layout-themes
Affects Versions: 4.2.0.Final
Reporter: Lukáš Fryč
The wizard can be created with {{togglePanel}} and {{toggleControl}}.
It can use validation mechanism and Ajax to switch between wizard windows.
----
But when validation fails, you can't use {{toggleControl}} to switch to another panel
like in the sample of Back button - there is no possibility to request {{immediate}} response (shortened lifecycle skipping validation phase).
----
The scenario can be seen in the sample of Showcase - togglePanel - Wizard [1],
and in the QuickStart {{richfaces-validation}} [2].
[1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=toggleP...
[2] https://github.com/lfryc/quickstart/tree/quickstart-28
----
Sample code:
{code}
<rich:togglePanelItem>
<!-- Step 2: name and phone number -->
<h:panelGrid columns="3">
<h:outputLabel for="name" value="Name" />
<h:inputText id="name" value="#{newMember.name}">
<!-- rich:validator needs to be used to trigger client-side validation
after blur event -->
<rich:validator event="blur" />
</h:inputText>
<rich:message for="name" />
<h:outputLabel for="phone" value="Phone #" />
<h:inputText id="phone" value="#{newMember.phoneNumber}">
<!-- rich:validator needs to be used to trigger client-side validation
after blur event -->
<rich:validator event="blur" />
</h:inputText>
<rich:message for="phone" />
</h:panelGrid>
<h:commandButton value="Back">
<rich:toggleControl event="click" targetItem="@prev" />
</h:commandButton>
<h:commandButton value="Continue">
<rich:toggleControl event="click" targetItem="@next" />
</h:commandButton>
</rich:togglePanelItem>
{code}
--
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, 9 months