[
https://jira.jboss.org/jira/browse/RF-8283?page=com.atlassian.jira.plugin...
]
Piotr Witusowski updated RF-8283:
---------------------------------
Description:
Around line 248 one can find:
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);
}
}
}
It gives misleading information that it is component with ajaxSingleClientId missing but
actually it is areaId. Consider changing line 254 to:
_log.warn("No component found to process for clientId "+areaId);
was:
Around line 248 one can find:
{noformat}
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);
}
}
}
{noformat}
It gives misleading information that it is component with ajaxSingleClientId missing but
actually it is areaId. Consider changing line 254 to:
{noformat}
_log.warn("No component found to process for clientId "+areaId);
{noformat}
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:
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);
}
}
}
It gives misleading information that it is component with ajaxSingleClientId missing but
actually it is areaId. Consider changing line 254 to:
_log.warn("No component found to process for clientId "+areaId);
--
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