[JBoss JIRA] Created: (RF-11115) a4j:push CDI Push sample in demo of push component in showcase does not work on tomcat 6
by Juraj Huska (JIRA)
a4j:push CDI Push sample in demo of push component in showcase does not work on tomcat 6
----------------------------------------------------------------------------------------
Key: RF-11115
URL: https://issues.jboss.org/browse/RF-11115
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: examples
Affects Versions: 4.1.0.Milestone2
Environment: richfaces-showcase-4.1.0-SNAPSHOT, apache-tomcat-6.0.32
Reporter: Juraj Huska
Assignee: Lukáš Fryč
Sample for CDI Push in demo of aj4:push component does not work on tomcat6. It throws this exception:
/richfaces/push/samples/pushCdi-sample.xhtml @12,59 action="#{pushBean.sendMessage(message)}" Error Parsing: #{pushBean.sendMessage(message)}
Stacktrace:
javax.faces.view.facelets.TagAttributeException: /richfaces/push/samples/pushCdi-sample.xhtml @12,59 action="#{pushBean.sendMessage(message)}" Error Parsing: #{pushBean.sendMessage(message)}
at com.sun.faces.facelets.tag.TagAttributeImpl.getMethodExpression(TagAttributeImpl.java:232)
at com.sun.faces.facelets.tag.jsf.ActionSourceRule$ActionMapper2.applyMetadata(ActionSourceRule.java:104)
at com.sun.faces.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:81)
at javax.faces.view.facelets.MetaTagHandler.setAttributes(MetaTagHandler.java:129)
at javax.faces.view.facelets.DelegatingMetaTagHandler.setAttributes(DelegatingMetaTagHandler.java:102)
at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.setAttributes(BehaviorsAddingComponentHandlerWrapper.java:113)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.doNewComponentActions(ComponentTagHandlerDelegateImpl.java:402)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:159)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:166)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:82)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:108)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:166)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:82)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:108)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:103)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:178)
at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366)
at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:108)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184)
at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:167)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:82)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:308)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:367)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:346)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:82)
at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:744)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.richfaces.webapp.PushFilter.doFilter(PushFilter.java:130)
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.core.StandardHostValve.invoke(StandardHostValve.java:127)
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:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.el.ELException: Error Parsing: #{pushBean.sendMessage(message)}
at org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:147)
at org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:172)
at org.apache.el.lang.ExpressionBuilder.createMethodExpression(ExpressionBuilder.java:223)
at org.apache.el.ExpressionFactoryImpl.createMethodExpression(ExpressionFactoryImpl.java:57)
at org.jboss.weld.util.el.ForwardingExpressionFactory.createMethodExpression(ForwardingExpressionFactory.java:43)
at org.jboss.weld.el.WeldExpressionFactory.createMethodExpression(WeldExpressionFactory.java:62)
at com.sun.faces.facelets.tag.TagAttributeImpl.getMethodExpression(TagAttributeImpl.java:222)
... 80 more
Caused by: org.apache.el.parser.ParseException: Encountered " "(" "( "" at line 1, column 23.
Was expecting one of:
"}" ...
"." ...
"[" ...
">" ...
"gt" ...
"<" ...
"lt" ...
">=" ...
"ge" ...
"<=" ...
"le" ...
"==" ...
"eq" ...
"!=" ...
"ne" ...
"&&" ...
"and" ...
"||" ...
"or" ...
"*" ...
"+" ...
"-" ...
"/" ...
"div" ...
"%" ...
"mod" ...
at org.apache.el.parser.ELParser.generateParseException(ELParser.java:2142)
at org.apache.el.parser.ELParser.jj_consume_token(ELParser.java:2024)
at org.apache.el.parser.ELParser.DeferredExpression(ELParser.java:113)
at org.apache.el.parser.ELParser.CompositeExpression(ELParser.java:40)
at org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:115)
... 86 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (RF-11120) datatable.ecss: background-repeat on .rf-dt-hdr-c is not set
by Val Blant (JIRA)
datatable.ecss: background-repeat on .rf-dt-hdr-c is not set
------------------------------------------------------------
Key: RF-11120
URL: https://issues.jboss.org/browse/RF-11120
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Reporter: Val Blant
Style _.rf-dt-hdr-c_ inside _datatable.ecss_ is missing a definition for _background-repeat_. This results in vertical wrapping of the gradient on data table header cells (I'll attach an image).
Please add the following declaration to the style:
{code}
background-repeat: repeat-x;
{code}
For now, this style can be overridden with that additional line in the user CSS as a workaround.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (RF-10853) dataScroller: do not works with a4j:status properly
by Ilya Shaikovsky (JIRA)
dataScroller: do not works with a4j:status properly
---------------------------------------------------
Key: RF-10853
URL: https://issues.jboss.org/browse/RF-10853
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
1) do not works properly with form scoped default status. onstart called but onstop - not.
Problem seems in dataScroller because the same case with the button works see [1]
2) do not works at all using status="status". Seems just not implemented.
[1]
<rich:popupPanel id="splash" autosized="true" width="200" height="80" moveable="false" resizeable="false">
<f:facet name="header"><h:outputText value="WAIT" /></f:facet>
<h:outputText value="WAIT!" />
</rich:popupPanel>
<h:form id="form">
<a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" />
<h:panelGrid columnClasses="acent">
<rich:dataScroller for="table" maxPages="5" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="#{userBean.age}">
................
</rich:dataTable>
<rich:dataScroller for="table" maxPages="5" status="status"/>
</h:panelGrid>
<a4j:commandButton ></a4j:commandButton>
</h:form>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (RF-11111) <a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0
by Bastian Ulke (JIRA)
<a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0
---------------------------------------------------------------------------------------------
Key: RF-11111
URL: https://issues.jboss.org/browse/RF-11111
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Final
Environment: WinXP; 6.0.0.Final; RichFaces 4.0.0
Reporter: Bastian Ulke
I have got the following tree:
<rich:tree var="item" id="someTree" selectionType="ajax" toggleType="ajax" treeSelectionChangeListener="#{someBean.selectionChanged}"
selectionChangeListener="#{someBean.selectionChanged}">
<rich:treeModelRecursiveAdaptor roots="#{someBean.entities}"
nodes="#{someBean.getSomeSubItems(item.id)}">
<rich:treeNode>
<a4j:outputPanel>
<h:outputText value="#{item.fullName}" />
</a4j:outputPanel>
</rich:treeNode>
</rich:treeModelRecursiveAdaptor>
</rich:tree>
And a status indicator:
<a4j:status layout="block" startStyleClass="startAjax" >
<f:facet name="start">
<img src="ajax-loader.gif" />
</f:facet
</a4j:status>
The combination works well for selecting (!) a node: When the AJAX-request is sent, it displays the gif, when it is received, it is removed. Unfortunatly, when performing a toggle on a node, the gif is displayed but never removed, although the data is correctly received and the view is updated. I added some alert('..') messages for the on{success|error|stop}-Properties of the <a4j:status> - same again: well fired for the selection of a particular node; but none ever executed for toggling.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (RF-11134) ComponentIdResolver does not resolve clientId correctly
by Val Blant (JIRA)
ComponentIdResolver does not resolve clientId correctly
-------------------------------------------------------
Key: RF-11134
URL: https://issues.jboss.org/browse/RF-11134
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Reporter: Val Blant
Please consider the following test code:
{code}
<rich:dataTable id="testTable"
value="#{dataTableTestBackingBean.rowsModel}"
var="rowVar">
<f:facet name="header">
<rich:column>
<h:outputText value="Column 1" />
</rich:column>
</f:facet>
<rich:column>
<h:inputText id="valTest" value="#{rowVar.col1}" >
<a4j:ajax
event="blur"
render="testColumn, footerTest"
limitRender="true"
execute="@this" />
</h:inputText>
</rich:column>
<rich:column>
<h:outputText id="testColumn" value="#{dataTableTestBackingBean.footerValue}" />
</rich:column>
<f:facet name="footer">
<rich:column>
<h:outputText id="footerTest" value="#{dataTableTestBackingBean.footerValue}" />
</rich:column>
</f:facet>
</rich:dataTable>
{code}
This example will fail with the following Javascript error in the browser:
{color:red}
{quote}
Error: During update: formId:testTable:0:footerTest not found
{quote}
{color}
This is expected, b/c the correct id for the footer is _formId:testTable:footerTest_.
The bug is in _org.richfaces.context.ComponentIdResolver_. Here is what happens:
# The _RenderComponentCallback_ is executed on the input component (_'valTest'_ in the example) and it reads the list of short ids to render from the attached Ajax Behavior. Note that we got here by walking the parent data table model, so the current rowKey is 0
# _RenderComponentCallback_ asks _ComponentIdResolver_ to resolve short ids into client IDs
# _ComponentIdResolver_ starts ascending up the tree from _'valTest'_ and looking at facets and children until it finds _'footerTest'_.
# At this point it asks for the clientId of _'footerTest'_ w/o regard for the fact that the data model has a rowKey that is set 0
So, we get the wrong id b/c we call UiData.getClientId() outside of the normal walking order of that model.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (RF-11125) a4j:ajax listener method expression behaves differently for one or zero parameter methods
by James G (JIRA)
a4j:ajax listener method expression behaves differently for one or zero parameter methods
-----------------------------------------------------------------------------------------
Key: RF-11125
URL: https://issues.jboss.org/browse/RF-11125
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Final
Environment: MyFace 2.0.7, Tomcat 6, Richfaces 4.0
Reporter: James G
When using a4j:ajax and setting the listener to a bean method, the call works correctly if the bean method has one parameter of type AjaxBehaviorEvent. If the method has no parameters then it may not be called correctly. This situation occurs if the method expression uses a variable scoped in facelets. For example using a ui:param under a ui:decorate. The method expression for one parameter is created using a call to ExpressionFactory.createMethodExpression( faceletContext, ... ) but the method expression for zero parameters is created using ExpressionFactory.createMethodExpression( elContext, ... ). The elContext does not contain the facelet variable mapping and so will not impart this to the method expression. This needs to be refactory to pass in the faceletContext when creating the zero parameter method expression.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months