[JBoss JIRA] (RF-12523) a4j:commandButton generates duplicated context path using a resource value expression within image attribute
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12523?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-12523:
----------------------------------
I have just sent the same pull request to the richfaces5 repository.
> a4j:commandButton generates duplicated context path using a resource value expression within image attribute
> ------------------------------------------------------------------------------------------------------------
>
> Key: RF-12523
> URL: https://issues.jboss.org/browse/RF-12523
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.2.2.Final, 4.3.0.M1
> Environment: Windows 7 Professional, JBoss AS 6.1.0.Final, Mojarra 2.1.7
> Reporter: Andreas Owczarek
> Assignee: Juraj Húska
> Labels: testcase_provided
> Fix For: 5-Tracking
>
>
> a4j:commandButton produces an extra context path prefix for the image resource path, when it is used with the value expression {code}#{resource['library:file']}{code} for the image attribute.
> {code:xml|title=Example code}
> <a4j:commandButton image="#{resource['icons:icon.gif']}" value="#{resource['icons:icon.gif']}"/>
> {code}
> {code:xml|title=Generated Result code}
> <input type="image" alt="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" src="/com.example.my.context.path/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" value="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" onclick="RichFaces.ajax("j_idt76",event,{"incId":"1"} );return false;" name="j_idt76" id="j_idt76">
> {code}
> The generated code show the correct value for the expression within the generated button label, but the image could not be located correctly because of the wrong generated image resource path.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12759) rich:hotkey doesn't work with a4j:commandButton
by Edilmar Alves (JIRA)
[ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.s... ]
Edilmar Alves commented on RF-12759:
------------------------------------
I attached two simple files... test.xhtml with 2 hotkeys (Ctrl+A that doesn't work and Ctrl+B that works fine) and test.java (controller that does nothing in openPanel() method, but in my real code it has some code).
> rich:hotkey doesn't work with a4j:commandButton
> -----------------------------------------------
>
> Key: RF-12759
> URL: https://issues.jboss.org/browse/RF-12759
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.2.3.Final
> Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1
> Reporter: Edilmar Alves
> Labels: hotkey, waiting_on_user
> Attachments: test.java, test.xhtml
>
>
> When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12759) rich:hotkey doesn't work with a4j:commandButton
by Edilmar Alves (JIRA)
[ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.s... ]
Edilmar Alves updated RF-12759:
-------------------------------
Attachment: test.java
test.xhtml
> rich:hotkey doesn't work with a4j:commandButton
> -----------------------------------------------
>
> Key: RF-12759
> URL: https://issues.jboss.org/browse/RF-12759
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.2.3.Final
> Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1
> Reporter: Edilmar Alves
> Labels: hotkey, waiting_on_user
> Attachments: test.java, test.xhtml
>
>
> When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale
by Dupont Dupont (JIRA)
[ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.s... ]
Dupont Dupont updated RF-12764:
-------------------------------
Description:
Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
{code}
Uncaught SyntaxError: Unexpected identifier.
{code}
It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
To reproduce it, just add the following line in your jsf messages properties :
{code}
javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
{code}
And add a rich:select in your JSF page.
We end up with the javascript :
{code}
RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} });
{code}
This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
Resolved locally by modifying AddCSVMessageScript#appendcript
But perhaps I've missed some side effects.
{code:java}
@Override
public void appendScript(Appendable target) throws IOException {
String summary = facesMessage.getSummary();
String detail = facesMessage.getDetail();
int severity = facesMessage.getSeverity().getOrdinal();
StringBuilder builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, summary);
summary = builder.toString();
builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, detail);
detail = builder.toString();
String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
target.append(script);
}
{code}
was:
Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
{code}
Uncaught SyntaxError: Unexpected identifier.
{code}
It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
To reproduce it, just add the following line in your jsf messages properties :
{code}
javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
{code}
And add a rich:select in your JSF page.
This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
Resolved locally by modifying AddCSVMessageScript#appendcript
But perhaps I've missed some side effects.
{code:java}
@Override
public void appendScript(Appendable target) throws IOException {
String summary = facesMessage.getSummary();
String detail = facesMessage.getDetail();
int severity = facesMessage.getSeverity().getOrdinal();
StringBuilder builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, summary);
summary = builder.toString();
builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, detail);
detail = builder.toString();
String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
target.append(script);
}
{code}
> rich:select - javascript error when using myfaces with french locale
> --------------------------------------------------------------------
>
> Key: RF-12764
> URL: https://issues.jboss.org/browse/RF-12764
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.CR2
> Reporter: Dupont Dupont
>
> Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
> {code}
> Uncaught SyntaxError: Unexpected identifier.
> {code}
> It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
> To reproduce it, just add the following line in your jsf messages properties :
> {code}
> javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
> {code}
> And add a rich:select in your JSF page.
> We end up with the javascript :
> {code}
> RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} });
> {code}
> This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
> Resolved locally by modifying AddCSVMessageScript#appendcript
> But perhaps I've missed some side effects.
> {code:java}
> @Override
> public void appendScript(Appendable target) throws IOException {
> String summary = facesMessage.getSummary();
> String detail = facesMessage.getDetail();
> int severity = facesMessage.getSeverity().getOrdinal();
> StringBuilder builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, summary);
> summary = builder.toString();
> builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, detail);
> detail = builder.toString();
>
> String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
> target.append(script);
> }
> {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
12 years, 10 months
[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale
by Dupont Dupont (JIRA)
[ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.s... ]
Dupont Dupont updated RF-12764:
-------------------------------
Affects Version/s: 4.3.0.CR2
> rich:select - javascript error when using myfaces with french locale
> --------------------------------------------------------------------
>
> Key: RF-12764
> URL: https://issues.jboss.org/browse/RF-12764
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.CR2
> Reporter: Dupont Dupont
>
> Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
> {code}
> Uncaught SyntaxError: Unexpected identifier.
> {code}
> It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
> To reproduce it, just add the following line in your jsf messages properties :
> {code}
> javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
> {code}
> And add a rich:select in your JSF page.
> This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
> Resolved locally by modifying AddCSVMessageScript#appendcript
> But perhaps I've missed some side effects.
> {code:java}
> @Override
> public void appendScript(Appendable target) throws IOException {
> String summary = facesMessage.getSummary();
> String detail = facesMessage.getDetail();
> int severity = facesMessage.getSeverity().getOrdinal();
> StringBuilder builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, summary);
> summary = builder.toString();
> builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, detail);
> detail = builder.toString();
>
> String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
> target.append(script);
> }
> {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
12 years, 10 months
[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale
by Dupont Dupont (JIRA)
Dupont Dupont created RF-12764:
----------------------------------
Summary: rich:select - javascript error when using myfaces with french locale
Key: RF-12764
URL: https://issues.jboss.org/browse/RF-12764
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Dupont Dupont
Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
{code}
Uncaught SyntaxError: Unexpected identifier.
{code}
It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
To reproduce it, just add the following line in your jsf messages properties :
{code}
javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
{code}
And add a rich:select in your JSF page.
This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
Resolved locally by modifying AddCSVMessageScript#appendcript
But perhaps I've missed some side effects.
{code:java}
@Override
public void appendScript(Appendable target) throws IOException {
String summary = facesMessage.getSummary();
String detail = facesMessage.getDetail();
int severity = facesMessage.getSeverity().getOrdinal();
StringBuilder builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, summary);
summary = builder.toString();
builder = new StringBuilder();
ScriptUtils.appendEncodedString(builder, detail);
detail = builder.toString();
String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
target.append(script);
}
{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
12 years, 10 months
[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale
by Dupont Dupont (JIRA)
[ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.s... ]
Dupont Dupont updated RF-12764:
-------------------------------
Issue Type: Bug (was: Feature Request)
> rich:select - javascript error when using myfaces with french locale
> --------------------------------------------------------------------
>
> Key: RF-12764
> URL: https://issues.jboss.org/browse/RF-12764
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Dupont Dupont
>
> Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error :
> {code}
> Uncaught SyntaxError: Unexpected identifier.
> {code}
> It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote.
> To reproduce it, just add the following line in your jsf messages properties :
> {code}
> javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide.
> {code}
> And add a rich:select in your JSF page.
> This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes).
> Resolved locally by modifying AddCSVMessageScript#appendcript
> But perhaps I've missed some side effects.
> {code:java}
> @Override
> public void appendScript(Appendable target) throws IOException {
> String summary = facesMessage.getSummary();
> String detail = facesMessage.getDetail();
> int severity = facesMessage.getSeverity().getOrdinal();
> StringBuilder builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, summary);
> summary = builder.toString();
> builder = new StringBuilder();
> ScriptUtils.appendEncodedString(builder, detail);
> detail = builder.toString();
>
> String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity);
> target.append(script);
> }
> {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
12 years, 10 months
[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12717 at 1/28/13 8:09 AM:
-----------------------------------------------------------
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO non-important files, settings and *reproduced the issue on it as well*. This application can be found [here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on [this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the {{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original attached sample*.
Is this a valid workaround ?
The steps to reproduce the issue on my applications are the same as for the original attached sample.
Just on metamer one needs to load: http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
was (Author: jhuska):
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO non-important files, settings and *reproduced the issue on it as well*. This application can be found [here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on [this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the {{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original attached sample*.
The steps to reproduce the issue on my applications are the same as for the original attached sample.
Just on metamer one needs to load: http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
> “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12717
> URL: https://issues.jboss.org/browse/RF-12717
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Brian Leathem
> Fix For: 4.3.0.Final
>
> Attachments: sample.rar
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12717 at 1/28/13 8:10 AM:
-----------------------------------------------------------
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO non-important files, settings and *reproduced the issue on it as well*. This application can be found [here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on [this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the {{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original attached sample*.
Is the step 5 a valid workaround ?
The steps to reproduce the issue on my applications are the same as for the original attached sample.
Just on metamer one needs to load: http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
was (Author: jhuska):
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO non-important files, settings and *reproduced the issue on it as well*. This application can be found [here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on [this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the {{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original attached sample*.
Is this a valid workaround ?
The steps to reproduce the issue on my applications are the same as for the original attached sample.
Just on metamer one needs to load: http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
> “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12717
> URL: https://issues.jboss.org/browse/RF-12717
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Brian Leathem
> Fix For: 4.3.0.Final
>
> Attachments: sample.rar
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly.
--
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
12 years, 10 months
[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-12717:
----------------------------------
This is my story:
# I have removed all Spring dependencies from the provided sample and also other IMHO non-important files, settings and *reproduced the issue on it as well*. This application can be found [here|https://github.com/jhuska/RF-12717].
# I have also tried to reproduce the issue on Metamer, on [this|https://github.com/richfaces/qa/tree/RF-12717] branch. I have used the same source code, but *for the first time I was not successful.*
# I was looking for differences, and it seems that the only one important is: context param {{javax.faces.PARTIAL_STATE_SAVING}} set to {{false}} in the application from the first step.
# I *can reproduce the issue on metamer* as well by setting this context param to the {{false}} in metamer's {{web.xml}}.
# The issue *disappears* by setting this context param to {{true}} on the *original attached sample*.
The steps to reproduce the issue on my applications are the same as for the original attached sample.
Just on metamer one needs to load: http://localhost:8080/metamer/faces/components/richDataTable/rf-12717.xhtml
> “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12717
> URL: https://issues.jboss.org/browse/RF-12717
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Juraj Húska
> Fix For: 4.3.0.Final
>
> Attachments: sample.rar
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly.
--
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
12 years, 10 months