[JBoss JIRA] Created: (RF-11000) Hit miss for class loader cost performance problem in Richfaces 4.1.0.
by Pawel J. (JIRA)
Hit miss for class loader cost performance problem in Richfaces 4.1.0.
----------------------------------------------------------------------
Key: RF-11000
URL: https://issues.jboss.org/browse/RF-11000
Project: RichFaces
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 4.1.0.Milestone1
Environment: Linux, Java 6
Reporter: Pawel J.
Priority: Minor
There are scenarios when resources are retrieved during no partial
request processing:
1) JSF html renderer (such as ScriptRenderer from faces) require to
know resources names to include them to html/head,
2) Resources content request.
We have two types of resources: dynamic and static. Predefined dynamic
resources (such as StateHolderResource) are read using class loader as
they are java classes. Static resources are kept in resources folder
as part of richfaces release jars (jquery.js, richfaces.js, etc).
There is a special case with compiled css that is consider as dynamic
resources but is not important in our case.
The problem appears when we try to load static resources using dynamic
loader. This make unnecessary lookup in java class loader space which
cost time and of course we miss the call as static resources not
exists there.
Statistics that shows class loader hits for every richfaces/ajax4jsf no partial request that will be eliminated after patch:
Resource::jquery.js::loading::timens::558000 ns::timems::0.558
ms::all::1.561496 sec
Resource::richfaces.js::loading::timens::490000 ns::timems::0.49
ms::all::1.561986 sec
Resource::richfaces-base-component.js::loading::timens::593000
ns::timems::0.593 ms::all::1.563672 sec
Resource::richfaces-queue.js::loading::timens::672000
ns::timems::0.672 ms::all::1.56435 sec
Resource::richfaces-event.js::loading::timens::3292000
ns::timems::3.292 ms::all::1.569386 sec
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (RF-11415) Metamer: rich:messages: doesn't display all messages (@globalOnly problem)
by Ján Jamrich (JIRA)
Metamer: rich:messages: doesn't display all messages (@globalOnly problem)
--------------------------------------------------------------------------
Key: RF-11415
URL: https://issues.jboss.org/browse/RF-11415
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79
Metamer 4.1.0.20110910-M2 r.unknown
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.19
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
Reporter: Ján Jamrich
Example page for rich:messages contains 2 messages (ok, really there are 3 messages components).
First with @for, second with @globalOnly (to avoid interference between functionality of each of them). Then third rich:messages component is without any attribute set.
Next, there is button on page which set couple of FacesMessages in actionListener method.
Following FacesMessages are added to FacesContext:
- 1 with SEVERITY_ERROR and without binding to any component (global)
- 1 with SEVERITY_WARN and without binding to any component (global)
- 2 with SEVERITY_ERROR, and bound to input1 and (second) to input2
- 2 with SEVERITY_WARN and bound to input1 and (second) to input2
When set attributes to following values:
- @globalOnly=false
- @for=''
and click on button which generates FacesMessages, then expect in second messages (with attribute @globalOnly, and without @for attribute) all messages displayed (all messages bound to component + global messages since @globalOnly=false tells that we are not expecting only global messages).
But in fact, there is displayed only one message - without binding to component (global). It mean we are missing all messages bound to some component, and secondly, we are missing messages with SEVERITY_WARN at all!
What is important, in third rich:messages component without any attributes (except ID) are not displayed these messages as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (RF-10473) Push: invalid 'Max re-connection reached.' error
by Nick Belaevski (JIRA)
Push: invalid 'Max re-connection reached.' error
------------------------------------------------
Key: RF-10473
URL: https://issues.jboss.org/browse/RF-10473
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.0.0.CR1
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 4.0.0.CR1
Open push-demo in Chrome & FF. Toggle arbitrary channel in Chrome in fast temp & many times -> Firefox stops receiving messages after some time, console contains 'Max re-connection reached.' message.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (RF-11081) Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null
by Ján Jamrich (JIRA)
Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null
--------------------------------------------------------------------------------
Key: RF-11081
URL: https://issues.jboss.org/browse/RF-11081
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT r.22533
Metamer 4.1.0-SNAPSHOT r.22533
Mojarra 2.0.4-b09
Apache Tomcat 7.0.12
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Ján Jamrich
With swithType set to "ajax" or not set (null) tab switch doesn't work (tab don't get switched).
With option "server" tab switching works, but another issue influences behavior.
Its important note that this happens only for dynamically created tabs. (For statically created tabs works tab switching correctly).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month