[JBoss JIRA] Created: (RF-8144) MethodExpression not active when command button is added to HtmlModalPanel facet
by Achim Gundermann (JIRA)
MethodExpression not active when command button is added to HtmlModalPanel facet
--------------------------------------------------------------------------------
Key: RF-8144
URL: https://jira.jboss.org/jira/browse/RF-8144
Project: RichFaces
Issue Type: Bug
Components: component-panels-layout-themes
Reporter: Achim Gundermann
Priority: Minor
When I want to add by Java (backing bean) a close button - which also does a bean action (a MethodExpression) to a modal panel - to the header by the facet "control", the bean action is not invoked. Only the modal panel is closed.
Source code fragment:
FacesContext context = FacesContext.getCurrentInstance();
Application application = context.getApplication();
ExpressionFactory expressionFactory = application.getExpressionFactory();
ELContext elContext = FacesContext.getCurrentInstance().getELContext();
HtmlCommandButton errorButton =(HtmlCommandButton) application.createComponent(HtmlCommandButton.COMPONENT_TYPE);
MethodExpression errorMethod = expressionFactory.createMethodExpression(elContext, "#{errorLog.clearNewError}", String.class,
new Class[] {});
errorButton.setActionExpression(errorMethod);
errorButton.setOnclick("Richfaces.hideModalPanel('errorPanel')");
errorButton.setImage("/pages/img/close.bmp");
errorButton.setType("submit");
errorPanel.getFacets().put("controls", errorButton);
The modal panel is closed, but the action method "clearNewError" is not invoked.
When I add the errorButton to a form within the modal panel (but not at the header), both actions - closing the modal panel and invoking the bean action - will be executed.
--
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
15 years
[JBoss JIRA] Created: (RF-8091) extendedDataTable doesn't dsplay properly if height attribute is missing "px"
by Matthew Lieder (JIRA)
extendedDataTable doesn't dsplay properly if height attribute is missing "px"
-----------------------------------------------------------------------------
Key: RF-8091
URL: https://jira.jboss.org/jira/browse/RF-8091
Project: RichFaces
Issue Type: Bug
Components: component-tables
Affects Versions: 3.3.2.SR1
Environment: JSF 1.2, Seam 2.2
Reporter: Matthew Lieder
If the height of the extendedDataTable component is set to just a number it doesn't display properly, but if the number is proceeded by "px" then it works great.
This displays just a one-pixel high line:
<rich:extendedDataTable value="#{testBean.values}" var="val" height="300">
<rich:column>
<f:facet name="header">Value</f:facet>
<h:outputText value="#{val}" />
</rich:column>
</rich:extendedDataTable>
while the following works properly:
<rich:extendedDataTable value="#{testBean.values}" var="val" height="300px">
<rich:column>
<f:facet name="header">Value</f:facet>
<h:outputText value="#{val}" />
</rich:column>
</rich:extendedDataTable>
--
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
15 years
[JBoss JIRA] Created: (RF-7274) CLONE -NullPointerException when uploading with rich:fileUpload
by jerarckill (JIRA)
CLONE -NullPointerException when uploading with rich:fileUpload
---------------------------------------------------------------
Key: RF-7274
URL: https://jira.jboss.org/jira/browse/RF-7274
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.1
Environment: tomcat 6.0.18
facelets 1.1.14
myfaces 1.2.6
Reporter: jerarckill
Assignee: Nick Belaevski
Fix For: 3.3.1
When using rich:fileUpload in the current 3.3.1 Snapshot (20090427) a nullpinter occurs when performing the upload:
javax.faces.FacesException: Exception while decoding component : {Component-Path : [Class: org.ajax4jsf.component.AjaxViewRoot,ViewId: /examples/fileUpload/index.xhtml][Class: org.richfaces.component.html.HtmlTabPanel,Id: j_id71][Class: org.richfaces.component.html.HtmlTab,Id: j_id72][Class: javax.faces.component.html.HtmlForm,Id: j_id74][Class: org.richfaces.component.html.HtmlFileUpload,Id: j_id75]}
at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:583)
at javax.faces.component.UIInput.decode(UIInput.java:231)
at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:709)
at javax.faces.component.UIInput.processDecodes(UIInput.java:149)
at javax.faces.component.UIForm.processDecodes(UIForm.java:65)
at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:705)
at org.richfaces.component.UISwitchablePanel.processDecodes(UISwitchablePanel.java:170)
at org.richfaces.component.UITabPanel.processDecodes(UITabPanel.java:155)
at org.ajax4jsf.component.AjaxViewRoot$1.invokeContextCallback(AjaxViewRoot.java:392)
at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:238)
at org.ajax4jsf.component.AjaxViewRoot.processDecodes(AjaxViewRoot.java:409)
at org.apache.myfaces.lifecycle.ApplyRequestValuesExecutor.execute(ApplyRequestValuesExecutor.java:32)
at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:151)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at de.solseit.framework.base.lifecyle.FrameworkFilter.doFilter(FrameworkFilter.java:265)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:344)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:347)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176)
at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145)
at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:381)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at org.richfaces.renderkit.FileUploadRendererBase.doDecode(FileUploadRendererBase.java:140)
at org.ajax4jsf.renderkit.RendererBase.decode(RendererBase.java:75)
at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:579)
... 45 more
the component is used in this very simple way (no listener-binding, for simplicity):
<rich:fileUpload
maxFilesQuantity="3"
immediateUpload="false"
acceptedTypes="jpg" />
--
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
15 years
[JBoss JIRA] Created: (RF-8051) c:foreach not working in template files
by Marco Huber (JIRA)
c:foreach not working in template files
---------------------------------------
Key: RF-8051
URL: https://jira.jboss.org/jira/browse/RF-8051
Project: RichFaces
Issue Type: Bug
Components: CDK
Affects Versions: 3.3.2.SR1
Environment: Java 6, Windows XP Pro SP2
Reporter: Marco Huber
Using c:foreach in a template file (.jspx) results in strange errors.
1st: The generated class missed a semicolon at the end of the for loop.
After investigation this error in the source, I found out that the velocity template was incorrect (A brake was too much).
2nd: The wrong template was used in the ForEachTemplateElement.java.
if (this.strItems != null) {
indexForCollection++;
templateName = getTemplate1Name();//"FORElement_1.vm");
context.put("items", this.strItems);
context.put("index", new Integer(indexForCollection));
} else {
templateName = getTemplate2Name();//"FORElement_2.vm");
context.put("from", this.strFrom);
context.put("to", this.strTo);
}
Despite the comment in the source the template file names are switch in the getTemplateXXXName methods. After fixing this all work correclty.
I attachted the corrected files, hoping they could be put in the next release.
Regards,
Marco
--
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
15 years