[JBoss JIRA] Created: (RF-11445) Client side validation should search for inputs inside a component
by José Freitas (JIRA)
Client side validation should search for inputs inside a component
------------------------------------------------------------------
Key: RF-11445
URL: https://issues.jboss.org/browse/RF-11445
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Milestone2
Reporter: José Freitas
Client side validation should search for inputs inside a component to look for its value instead of collecting the value directly from the component, based on its id.
That would basically help csv system to work with composite components like seamfaces:inputcontainer and some primefaces components.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (RF-11156) a4j:push Performance problem in CDI sample of push in showcase
by Lukáš Fryč (Commented) (JIRA)
[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-11156:
---------------------------------
I assume the behavior which is Jura experiencing is caused by number of connections opened to server and server/browser connection is not closed right after aborting XHR long-polling request.
The behavior is though not real world scenario and users can toggle the number of connections in application server configuration if needed.
We can't generally change number of concurrent connections per session in Showcase example, so closing this issue as partially completed.
Note that this affects only particular browsers and it is nothing we can do about.
> a4j:push Performance problem in CDI sample of push in showcase
> --------------------------------------------------------------
>
> Key: RF-11156
> URL: https://issues.jboss.org/browse/RF-11156
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.1.0.Milestone1
> Environment: richfaces-showcase 4.1.0-Snapshot, containers - JBoss AS 6 and 7
> Reporter: Juraj Huska
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 4.1.0.Milestone3
>
>
> When there is more than 5 consumers windows, it causes performance problems(take up to 20 seconds to render message on consumer), at least from the beginning, after some messsages like 3-4 the performance is improved on AS 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (RF-11409) showcase - aj4:push - all samples - when push is done then NullPointerException is thrown but the expected result of push is there
by Juraj Huska (JIRA)
showcase - aj4:push - all samples - when push is done then NullPointerException is thrown but the expected result of push is there
----------------------------------------------------------------------------------------------------------------------------------
Key: RF-11409
URL: https://issues.jboss.org/browse/RF-11409
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.1.0.Milestone2
Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
container - Tomcat 7.0.20
browser - Chrome 13, IE 9, FF 3.6
Reporter: Juraj Huska
When push is done on all samples for aj4:push in showcase, then NullPointerException is thrown but the expected result of push is there. So the functionality is correct, only on the server console exception is thrown, with this stacktrace:
{code}
SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
java.lang.NullPointerException
at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:81)
at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:115)
at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestDestroyed(ForwardingServletListener.java:42)
at org.apache.catalina.core.StandardContext.fireRequestDestroyEvent(StandardContext.java:6008)
at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:281)
at org.apache.coyote.http11.AbstractHttp11Processor.asyncDispatch(AbstractHttp11Processor.java:1220)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:511)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
This exception is thrown after each push execution, and it is not broken after first trowing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months