[JBoss JIRA] Created: (RF-8283) AjaxViewRoot is giving misleading information when a component with id from areasToProcess is not found in components tree
by Piotr Witusowski (JIRA)
AjaxViewRoot is giving misleading information when a component with id from areasToProcess is not found in components tree
--------------------------------------------------------------------------------------------------------------------------
Key: RF-8283
URL: https://jira.jboss.org/jira/browse/RF-8283
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.3.3.BETA1
Reporter: Piotr Witusowski
Priority: Minor
Around line 248 one can find:
{code}
Set<String> areasToProcess = ajaxContext.getAjaxAreasToProcess();
if(null != areasToProcess){
for (String areaId : areasToProcess) {
boolean areaProcessed = invokeOnComponent(context, areaId, invokerCallback);
if(!areaProcessed){
_log.warn("No component found to process for clientId "+ajaxSingleClientId);
}
}
}
{code}
It gives misleading information that it is component with ajaxSingleClientId missing but actually it is areaId. Consider changing line 254 to:
{code}
_log.warn("No component found to process for clientId "+areaId);
{code}
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-8223) ExtendedDataTable duplicate Id exception
by Alex Kolonitsky (JIRA)
ExtendedDataTable duplicate Id exception
----------------------------------------
Key: RF-8223
URL: https://jira.jboss.org/jira/browse/RF-8223
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JSF 2.0
Reporter: Alex Kolonitsky
Assignee: Alex Kolonitsky
For exapmle below
<f:view>
<h:form id="form">
<rich:extendedDataTable id="table">
<rich:column >Hello</rich:column>
</rich:extendedDataTable>
</h:form>
</f:view>
I have exception
java.lang.IllegalStateException: duplicate Id for a component form:table:j_id3
org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:68)
org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
org.ajax4jsf.application.TreeStructureNode.apply(TreeStructureNode.java:92)
org.ajax4jsf.application.AjaxStateManager.getTreeStructureToSave(AjaxStateManager.java:194)
org.ajax4jsf.application.AjaxStateManager.buildViewState(AjaxStateManager.java:520)
org.ajax4jsf.application.AjaxStateManager.saveSerializedView(AjaxStateManager.java:473)
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:615)
--
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
14 years, 9 months
[JBoss JIRA] Created: (RF-8204) AjaxStateManager: view id sequence is increased for AJAX requests under JSF 2.0
by Nick Belaevski (JIRA)
AjaxStateManager: view id sequence is increased for AJAX requests under JSF 2.0
-------------------------------------------------------------------------------
Key: RF-8204
URL: https://jira.jboss.org/jira/browse/RF-8204
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core, JSF 2.0, performance
Affects Versions: 3.3.3.BETA1
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Priority: Critical
Fix For: 3.3.3.BETA1
In JSF 1.2.x ResponseStateManager had the only responsibility of reading/writing state according to rendering technology used.
In Sun RI JSF 2.0 ResponseStateManager also has the responsibility of actually storing state in session (the same functionality as implemented in RF AjaxStateManager), that's why it assigns new views sequence number for AJAX requests. MyFaces 2.0 implements this functionality the same as in JSF 1.2
--
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
14 years, 9 months
[JBoss JIRA] Closed: (RF-7603) a4j:form data="#{}" does not populate javascript data variable (data is undefined)
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-7603?page=com.atlassian.jira.plugin... ]
Lukas Fryc closed RF-7603.
--------------------------
> a4j:form data="#{}" does not populate javascript data variable (data is undefined)
> ----------------------------------------------------------------------------------
>
> Key: RF-7603
> URL: https://jira.jboss.org/jira/browse/RF-7603
> Project: RichFaces
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 3.3.2.CR1
> Environment: Gentoo Linux 2.6.24
> Sun Java 1.6.0.0.7
> RichFaces 3.2.1_GA
> Facelets 1.1.14
> Apache Tomcat 6.0 AppServer
> JSF 1.2 RI
> Reporter: Lincoln Baxter III
> Assignee: Andrey Markhel
> Fix For: 3.3.3.CR1
>
> Attachments: UIAjaxForm.java
>
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> When using the a4j:form component, the data="#{managedBean.property}" attribute is not correctly causing the javascript data variable to be populated.
> See example below. data is always undefined, even if the managed bean property is set to a valid value, the alert box shows undefined.
> I verified that when using a4j:commandButton, the data variable is correctly populated, and the alert box displays the value.
> <a4j:form id="themouth" data="#{indexBean.ajaxInputOk}"
> reRender="whispers,earInput,earErrors"
> oncomplete="alert(data)" ajaxSubmit="true">
> <div class="centered paddingLarge"><h:outputText
> id="whispers" styleClass="smallText" value="#{indexBean.whispers}" /></div>
> <div class="centered" id="earWhisper"><a4j:outputPanel id="earErrors">
> <h:message showSummary="true" showDetail="false" for="earInput"
> style="color: red;" />
> </a4j:outputPanel><br />
> <h:inputText id="earInput" autocomplete="off"
> value="#{indexBean.input}"
> validator="#{indexBean.validateWhisper}" required="true">
> </h:inputText> <h:commandButton id="whisperButton"
> action="#{indexBean.doWhisper}" value="whisper" /></div>
> </a4j:form>
--
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
14 years, 9 months
[JBoss JIRA] Commented: (RF-7603) a4j:form data="#{}" does not populate javascript data variable (data is undefined)
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-7603?page=com.atlassian.jira.plugin... ]
Lukas Fryc commented on RF-7603:
--------------------------------
Reproduced in 3.3.3.BETA1, verified in 3.3.3.CR1:
<a4j:form data="${bean.data}" oncomplete="alert(data)" ajaxSubmit="true">
<h:commandButton />
</a4j:form>
> a4j:form data="#{}" does not populate javascript data variable (data is undefined)
> ----------------------------------------------------------------------------------
>
> Key: RF-7603
> URL: https://jira.jboss.org/jira/browse/RF-7603
> Project: RichFaces
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 3.3.2.CR1
> Environment: Gentoo Linux 2.6.24
> Sun Java 1.6.0.0.7
> RichFaces 3.2.1_GA
> Facelets 1.1.14
> Apache Tomcat 6.0 AppServer
> JSF 1.2 RI
> Reporter: Lincoln Baxter III
> Assignee: Andrey Markhel
> Fix For: 3.3.3.CR1
>
> Attachments: UIAjaxForm.java
>
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> When using the a4j:form component, the data="#{managedBean.property}" attribute is not correctly causing the javascript data variable to be populated.
> See example below. data is always undefined, even if the managed bean property is set to a valid value, the alert box shows undefined.
> I verified that when using a4j:commandButton, the data variable is correctly populated, and the alert box displays the value.
> <a4j:form id="themouth" data="#{indexBean.ajaxInputOk}"
> reRender="whispers,earInput,earErrors"
> oncomplete="alert(data)" ajaxSubmit="true">
> <div class="centered paddingLarge"><h:outputText
> id="whispers" styleClass="smallText" value="#{indexBean.whispers}" /></div>
> <div class="centered" id="earWhisper"><a4j:outputPanel id="earErrors">
> <h:message showSummary="true" showDetail="false" for="earInput"
> style="color: red;" />
> </a4j:outputPanel><br />
> <h:inputText id="earInput" autocomplete="off"
> value="#{indexBean.input}"
> validator="#{indexBean.validateWhisper}" required="true">
> </h:inputText> <h:commandButton id="whisperButton"
> action="#{indexBean.doWhisper}" value="whisper" /></div>
> </a4j:form>
--
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
14 years, 9 months