[JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13611:
-------------------------------
Fix Version/s: 4.5-Tracking
(was: 4.3.7)
> RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final
> ---------------------------------------------------------
>
> Key: RF-13611
> URL: https://issues.jboss.org/browse/RF-13611
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 5.0.0.Alpha3
> Reporter: Juergen Zimmermann
> Fix For: 4.5-Tracking
>
>
> I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone.
> {code}
> ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod@31e23242
> at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158)
> at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237)
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174)
> at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133)
> at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107)
> at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59)
> at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393)
> at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> ... 3 more
> {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
10 years, 2 months
[JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13537:
-------------------------------
Fix Version/s: 4.5-Tracking
(was: 4.3.7)
> Autocomplete: onbegin attribute ignored
> ---------------------------------------
>
> Key: RF-13537
> URL: https://issues.jboss.org/browse/RF-13537
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.5
> Reporter: alexey plotnikov
> Fix For: 4.5-Tracking
>
>
> "onbegin" attribute of rich:autocomplete is always ignored!
> I suggest next fix:
> In file Autocomplete.js:
> {code}
> var callAjax = function(event, callback) {
> ...
> this.isFirstAjax = false;
> //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log
> var params = {};
> params[this.id + ".ajax"] = "1";
> rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess});
> }
> {code}
> for fixing, we must replace on
> {code}
> var callAjax = function(event, callback) {
> ...
> this.isFirstAjax = false;
> //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log
> var params = {};
> params[this.id + ".ajax"] = "1";
> var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess};
> if (this.options.onbegin != undefined) {
> parameters_extended.begin = this.options.onbegin;
> }
> rf.ajax(this.id, event, parameters_extended);
> }
> {code}
> I can create pull request if everything ok.
--
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
10 years, 2 months
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13615:
------------------------------------
Interesting find [~wlh]. If you are interested in doing more debugging to help us narrow down the problem, refer to this client-side debugging howto:
https://github.com/richfaces/richfaces/wiki/Debugging-RichFaces
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
> Reporter: Holger Walter
>
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
> Best regards
> wlh
--
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
10 years, 2 months
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Holger Walter (JIRA)
Holger Walter created RF-13615:
----------------------------------
Summary: ExtendedDataTable: double ajax request on scrolling
Key: RF-13615
URL: https://issues.jboss.org/browse/RF-13615
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.3.5
Environment: Problem can be tested in richfaces showcase.
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
Reporter: Holger Walter
Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist
1. Go to the extendedDataTable showcase
2. Turn on ajax loading.
3. Open the debugger of your browser and watch the network communication
4. Scroll down in the table untli new data has to be fetched.
=> one POST request is sent. This is fine.
5. Change the width of a column in the table.
=> one POST request is sent. This is fine.
6. Scroll again in the table untli new data has to be fetched.
-> 2 POST requests are sent. WHY?
>From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
Best regards
wlh
--
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
10 years, 2 months
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13615:
-------------------------------
Affects Version/s: 4.3.6
(was: 4.3.5)
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
> Reporter: Holger Walter
>
> Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
> Best regards
> wlh
--
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
10 years, 2 months
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Holger Walter (JIRA)
[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ]
Holger Walter updated RF-13615:
-------------------------------
Description:
1. Go to the extendedDataTable showcase
2. Turn on ajax loading.
3. Open the debugger of your browser and watch the network communication
4. Scroll down in the table untli new data has to be fetched.
=> one POST request is sent. This is fine.
5. Change the width of a column in the table.
=> one POST request is sent. This is fine.
6. Scroll again in the table untli new data has to be fetched.
-> 2 POST requests are sent. WHY?
>From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
Best regards
wlh
was:
Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist
1. Go to the extendedDataTable showcase
2. Turn on ajax loading.
3. Open the debugger of your browser and watch the network communication
4. Scroll down in the table untli new data has to be fetched.
=> one POST request is sent. This is fine.
5. Change the width of a column in the table.
=> one POST request is sent. This is fine.
6. Scroll again in the table untli new data has to be fetched.
-> 2 POST requests are sent. WHY?
>From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
Best regards
wlh
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
> Reporter: Holger Walter
>
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
> Best regards
> wlh
--
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
10 years, 2 months
[JBoss JIRA] (RF-13469) RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName()
by H G (JIRA)
[ https://issues.jboss.org/browse/RF-13469?page=com.atlassian.jira.plugin.s... ]
H G updated RF-13469:
---------------------
Affects Version/s: 5.0.0.Alpha3
> RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName()
> --------------------------------------------------------------------
>
> Key: RF-13469
> URL: https://issues.jboss.org/browse/RF-13469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3
> Environment: WildFly CR1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.4
> WildFly B1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.3
> Firefox 26.0
> Reporter: H G
> Labels: libraryName, npe, pickList, resource
> Fix For: 5.0.0.Alpha4
>
>
> An exception is handled. The exception is related to the source code "resource.getLibraryName()" from ResourceServletMapping
> Link to exception - https://community.jboss.org/message/852156
--
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
10 years, 2 months