[JBoss JIRA] Created: (RF-7351) Regression: "messages: globalOnly does not work properly"
by Joseph Miller (JIRA)
Regression: "messages: globalOnly does not work properly"
---------------------------------------------------------
Key: RF-7351
URL: https://jira.jboss.org/jira/browse/RF-7351
Project: RichFaces
Issue Type: Bug
Components: component, regression
Affects Versions: 3.3.1
Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA
Reporter: Joseph Miller
Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page.
My page template has:
<rich:messages globalOnly="true" id="page-messages">
...
</rich:messages>
and the controls have:
<rich:message for="my-control-id" id="my-control-id-message">
...
</rich:message>
I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :(
--
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, 8 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, 8 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, 8 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, 8 months
[JBoss JIRA] (RF-11801) ClientValidatorImpl ClssCastException in restoreState (StateHolderSaver not an Object[])
by Giovanni Pelosi (Created) (JIRA)
ClientValidatorImpl ClssCastException in restoreState (StateHolderSaver not an Object[])
----------------------------------------------------------------------------------------
Key: RF-11801
URL: https://issues.jboss.org/browse/RF-11801
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.CR1
Reporter: Giovanni Pelosi
when i do an ajax submit on a form with <rich:validator /> inputs fields (h:inputText)
(defined in a composite component), i got this exception:
ClassCastException
in org.richfaces.component.behavior.ClientValidatorImpl.restoreState at line 357
@Override
public void restoreState(FacesContext context, Object state) {
if (context == null) {
throw new NullPointerException();
}
if (state != null) {
==> Object[] values = (Object[]) state;
super.restoreState(context, values[0]);
if (values.length != 1) {
groups = (Class<?>[]) values[1];
// If we saved state last time, save state again next time.
clearInitialState();
}
}
}
because state is an instance of javax.faces.component.StateHolderSaver
RF 4.1CR1
MOJARRA 2.1.3
JBoss 7.0.2
--
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, 8 months
[JBoss JIRA] Created: (RF-5765) ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol.
by Andrei Markavtsov (JIRA)
ExtendedDataTable: Drag and Drop for columns does not work if column id contain '-' symbol.
-------------------------------------------------------------------------------------------
Key: RF-5765
URL: https://jira.jboss.org/jira/browse/RF-5765
Project: RichFaces
Issue Type: Bug
Environment: RF 3.3.0
Reporter: Andrei Markavtsov
Assignee: Nick Belaevski
<h:form id="form">
<rich:extendedDataTable value="#{test3.rows}" var="row" tableState="#{test3.tableState}">
<rich:columns
sortBy="#{row[ind]}"
sortOrder="#{column.ordering}"
filterBy="#{row[ind]}"
filterValue="#{column.filterValue}"
id="column-#{column.name}"
value="#{test3.columns}"
label="#{column.name}"
var="column"
index="ind">
<f:facet name="header">
<h:outputText value="#{column.name}" />
</f:facet>
<h:outputText value="#{row[ind]}" />
</rich:columns>
</rich:extendedDataTable>
</h:form>
Erroneus code: AbstractExtendedTableRenderer.doDecode(1239).
--
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, 8 months