[JBoss JIRA] (RF-13114) PoC: port RichFaces 4.5 UI Components to work with RichFaces 5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13114?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13114.
-----------------------------
Resolution: Done
> PoC: port RichFaces 4.5 UI Components to work with RichFaces 5
> --------------------------------------------------------------
>
> Key: RF-13114
> URL: https://issues.jboss.org/browse/RF-13114
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> * open branches in own fork of
> ** richfaces5 (master)
> ** richfaces-components (4.5.x)
> ** richfaces-showcase (master)
> * modifications required
> ** change RF5 namespace -> http://richfaces.org/core
> ** change parents/bom in components 4.5 to depend on RF5 framework / build-bom
> *** remove all dependencies on 4.3.x (4.3.3-SNAPSHOT)
> ** change Java API of Components 4.5 to depend on RF5 Core API
> ** use the RF5 and RF4.5 UI Components in Showcase branch (4.5.0-SNAPSHOT)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-11469 at 9/25/13 1:08 PM:
----------------------------------------------------------
Sample for reproduction in RichFaces 5: https://github.com/lfryc/richfaces/tree/RF-11469-autocomplete-fails-to-ev...
was (Author: lfryc):
Sample for reproduction in RichFaces 5: https://github.com/richfaces/richfaces/tree/RF-11469-autocomplete-fails-t...
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 4.3.5
>
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (RF-13223) Upgrade to jsf-test 1.1.7
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13223:
-------------------------------
Summary: Upgrade to jsf-test 1.1.7
Key: RF-13223
URL: https://issues.jboss.org/browse/RF-13223
Project: RichFaces
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: tests - unit
Affects Versions: 5.0.0.Alpha2
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
Fix For: 5.0.0.Alpha2
Fixes issue with getPathInfo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (RF-13221) Incorrect XML encoding in AJAX response
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13221?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13221:
--------------------------------
Description:
Consider the following example:
{noformat}
<h:form>
<a4j:commandButton render="@form" value="rerender me"/>
<script src="path_to_some_script?param=asd&important=param"></script>
</h:form>
{noformat}
when commandButton is clicked, the form is rerendered and the response looks like this:
{noformat}
<partial-response><changes><update id="someID"><![CDATA[
...
<script src="path_to_some_script?param=asd&important=param"></script>
]]</ ... >
{noformat}
But this is wrong. Because script tag is already in CDATA, so there is no need for XML encoding for '&' entity.
This further causes script loading to fail (performed by jsf.js), whenever parameters are needed (e.g. portal environment),
because script is downloaded from {noformat}"path_to_some_script?param=asd&important=param" {noformat}
instead of {noformat}"path_to_some_script?param=asd&important=param"{noformat}.
Another very similar issue is when CDATA element is present in a re-rendered fragment. Example:
{noformat}
<h:form>
<a4j:commandButton render="@form" value="rerender me"/>
<style type="text/css">
/* <![CDATA[ */
.somecssclass {...}
/* ]] */
</style>
</h:form>
{noformat}
The AJAX response then looks like so:
{noformat}
<partial-response><changes><update id="someID"><![CDATA[
...
<![CDATA[
...
]]
...
]]</ ... >
{noformat}
And this is incorrect XML, since CDATA cannot contain ']]', so the response is discarded.
was:
Consider the following example:
{noformat}
<h:form>
<a4j:commandButton render="@form" value="rerender me"/>
<script src="path_to_some_script?param=asd&important=param"></script>
</h:form>
{noformat}
when commandButton is clicked, the form is rerendered and the response looks like this:
{noformat}
<partial-response><changes><update id="someID"><![CDATA[
...
<script src="path_to_some_script?param=asd&important=param"></script>
]]</ ... >
{noformat}
But this is wrong. Because script tag is already in CDATA, so there is no need for XML encoding for '&' entity.
This further causes script loading to fail (performed by jsf.js), whenever parameters are needed (e.g. portal environment),
because script is downloaded from ""path_to_some_script?param=asd&important=param"
instead of ""path_to_some_script?param=asd&important=param".
Another very similar issue is when CDATA element is present in a re-rendered fragment. Example:
{noformat}
<h:form>
<a4j:commandButton render="@form" value="rerender me"/>
<style type="text/css">
/* <![CDATA[ */
.somecssclass {...}
/* ]] */
</style>
</h:form>
{noformat}
The AJAX response then looks like so:
{noformat}
<partial-response><changes><update id="someID"><![CDATA[
...
<![CDATA[
...
]]
...
]]</ ... >
{noformat}
And this is incorrect XML, since CDATA cannot contain ']]', so the response is discarded.
> Incorrect XML encoding in AJAX response
> ---------------------------------------
>
> Key: RF-13221
> URL: https://issues.jboss.org/browse/RF-13221
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Jonáš Trantina
>
> Consider the following example:
> {noformat}
> <h:form>
> <a4j:commandButton render="@form" value="rerender me"/>
> <script src="path_to_some_script?param=asd&important=param"></script>
> </h:form>
> {noformat}
> when commandButton is clicked, the form is rerendered and the response looks like this:
> {noformat}
> <partial-response><changes><update id="someID"><![CDATA[
> ...
> <script src="path_to_some_script?param=asd&important=param"></script>
> ]]</ ... >
> {noformat}
> But this is wrong. Because script tag is already in CDATA, so there is no need for XML encoding for '&' entity.
> This further causes script loading to fail (performed by jsf.js), whenever parameters are needed (e.g. portal environment),
> because script is downloaded from {noformat}"path_to_some_script?param=asd&important=param" {noformat}
> instead of {noformat}"path_to_some_script?param=asd&important=param"{noformat}.
> Another very similar issue is when CDATA element is present in a re-rendered fragment. Example:
> {noformat}
> <h:form>
> <a4j:commandButton render="@form" value="rerender me"/>
> <style type="text/css">
> /* <![CDATA[ */
> .somecssclass {...}
> /* ]] */
> </style>
> </h:form>
> {noformat}
> The AJAX response then looks like so:
> {noformat}
> <partial-response><changes><update id="someID"><![CDATA[
> ...
> <![CDATA[
> ...
> ]]
> ...
> ]]</ ... >
> {noformat}
> And this is incorrect XML, since CDATA cannot contain ']]', so the response is discarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months