[JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11
by Walter Maidub (JIRA)
[ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.s... ]
Walter Maidub commented on RF-13602:
------------------------------------
sorry, QE?
> Problem with ajax request in Internet Explorer 11
> -------------------------------------------------
>
> Key: RF-13602
> URL: https://issues.jboss.org/browse/RF-13602
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.0.0.Final
> Environment: Windows 2008, JBoss AS 7.x
> Reporter: Walter Maidub
> Assignee: Pavol Pitonak
> Labels: ie11
>
> I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it.
> {code}
> <rich:select id="tipoArchivo" value="#{Bean.tipoArchivo}"
> required="true" listWidth="320px" styleClass="rf-select-large-width">
> <f:selectItems value="#{Bean.Catalogo}" />
> <a4j:ajax event="selectitem"
> execute="@this"
> render="upload,seccionCarga"
> listener="#{Bean.activarPanelCarga}" />
> </rich:select>
>
> <h:panelGrid columns="1">
> <h:panelGroup id="seccionCarga">
> <rich:panel bodyClass="info" titleStyleClass="rf-p-hdr" >
>
> <f:facet name="header">
> <h:outputText value="Detalle del archivo Cargado" />
> </f:facet>
>
> <h:panelGrid columns="2" columnClasses="columnOnCenter,columnOnCenter">
> <h:panelGroup style="text-align:center;display:block;width:550px;height:35px">
> <div align="center">
> <rich:fileUpload id="upload"
> styleClass="top"
> .
> .
> .
> {code}
>
> The problem is that the FileUploader remains disabled, it is as if the panel had not been updated.
>
> Generally <a4j:ajax event="selectitem"> requests fail, this only in IE 11.0.4 (KB2925418)
>
> Currently there is a filter to ensure compatibility with IE 8.
>
> When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly.
>
> The configuration of the environment is:
> Richfaces 4.0.0.
> IE11
> JSF2
> Eclipse Kepler
>
> Is there any way to correct the problems with these ajax requests?
--
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
11 years, 11 months
[JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13602:
----------------------------------
Assignee: Pavol Pitonak
QE, please verify
> Problem with ajax request in Internet Explorer 11
> -------------------------------------------------
>
> Key: RF-13602
> URL: https://issues.jboss.org/browse/RF-13602
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.0.0.Final
> Environment: Windows 2008, JBoss AS 7.x
> Reporter: Walter Maidub
> Assignee: Pavol Pitonak
> Labels: ie11, waiting_on_user
>
> I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it.
> {code}
> <rich:select id="tipoArchivo" value="#{Bean.tipoArchivo}"
> required="true" listWidth="320px" styleClass="rf-select-large-width">
> <f:selectItems value="#{Bean.Catalogo}" />
> <a4j:ajax event="selectitem"
> execute="@this"
> render="upload,seccionCarga"
> listener="#{Bean.activarPanelCarga}" />
> </rich:select>
>
> <h:panelGrid columns="1">
> <h:panelGroup id="seccionCarga">
> <rich:panel bodyClass="info" titleStyleClass="rf-p-hdr" >
>
> <f:facet name="header">
> <h:outputText value="Detalle del archivo Cargado" />
> </f:facet>
>
> <h:panelGrid columns="2" columnClasses="columnOnCenter,columnOnCenter">
> <h:panelGroup style="text-align:center;display:block;width:550px;height:35px">
> <div align="center">
> <rich:fileUpload id="upload"
> styleClass="top"
> .
> .
> .
> {code}
>
> The problem is that the FileUploader remains disabled, it is as if the panel had not been updated.
>
> Generally <a4j:ajax event="selectitem"> requests fail, this only in IE 11.0.4 (KB2925418)
>
> Currently there is a filter to ensure compatibility with IE 8.
>
> When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly.
>
> The configuration of the environment is:
> Richfaces 4.0.0.
> IE11
> JSF2
> Eclipse Kepler
>
> Is there any way to correct the problems with these ajax requests?
--
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
11 years, 11 months
[JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13602:
-------------------------------
Labels: ie11 (was: ie11 waiting_on_user)
> Problem with ajax request in Internet Explorer 11
> -------------------------------------------------
>
> Key: RF-13602
> URL: https://issues.jboss.org/browse/RF-13602
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.0.0.Final
> Environment: Windows 2008, JBoss AS 7.x
> Reporter: Walter Maidub
> Assignee: Pavol Pitonak
> Labels: ie11
>
> I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it.
> {code}
> <rich:select id="tipoArchivo" value="#{Bean.tipoArchivo}"
> required="true" listWidth="320px" styleClass="rf-select-large-width">
> <f:selectItems value="#{Bean.Catalogo}" />
> <a4j:ajax event="selectitem"
> execute="@this"
> render="upload,seccionCarga"
> listener="#{Bean.activarPanelCarga}" />
> </rich:select>
>
> <h:panelGrid columns="1">
> <h:panelGroup id="seccionCarga">
> <rich:panel bodyClass="info" titleStyleClass="rf-p-hdr" >
>
> <f:facet name="header">
> <h:outputText value="Detalle del archivo Cargado" />
> </f:facet>
>
> <h:panelGrid columns="2" columnClasses="columnOnCenter,columnOnCenter">
> <h:panelGroup style="text-align:center;display:block;width:550px;height:35px">
> <div align="center">
> <rich:fileUpload id="upload"
> styleClass="top"
> .
> .
> .
> {code}
>
> The problem is that the FileUploader remains disabled, it is as if the panel had not been updated.
>
> Generally <a4j:ajax event="selectitem"> requests fail, this only in IE 11.0.4 (KB2925418)
>
> Currently there is a filter to ensure compatibility with IE 8.
>
> When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly.
>
> The configuration of the environment is:
> Richfaces 4.0.0.
> IE11
> JSF2
> Eclipse Kepler
>
> Is there any way to correct the problems with these ajax requests?
--
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
11 years, 11 months
[JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11
by Walter Maidub (JIRA)
[ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.s... ]
Walter Maidub commented on RF-13602:
------------------------------------
Sorry, We download Richfaces 4.3.6.Final.zip
Regards
> Problem with ajax request in Internet Explorer 11
> -------------------------------------------------
>
> Key: RF-13602
> URL: https://issues.jboss.org/browse/RF-13602
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.0.0.Final
> Environment: Windows 2008, JBoss AS 7.x
> Reporter: Walter Maidub
> Labels: ie11, waiting_on_user
>
> I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it.
> {code}
> <rich:select id="tipoArchivo" value="#{Bean.tipoArchivo}"
> required="true" listWidth="320px" styleClass="rf-select-large-width">
> <f:selectItems value="#{Bean.Catalogo}" />
> <a4j:ajax event="selectitem"
> execute="@this"
> render="upload,seccionCarga"
> listener="#{Bean.activarPanelCarga}" />
> </rich:select>
>
> <h:panelGrid columns="1">
> <h:panelGroup id="seccionCarga">
> <rich:panel bodyClass="info" titleStyleClass="rf-p-hdr" >
>
> <f:facet name="header">
> <h:outputText value="Detalle del archivo Cargado" />
> </f:facet>
>
> <h:panelGrid columns="2" columnClasses="columnOnCenter,columnOnCenter">
> <h:panelGroup style="text-align:center;display:block;width:550px;height:35px">
> <div align="center">
> <rich:fileUpload id="upload"
> styleClass="top"
> .
> .
> .
> {code}
>
> The problem is that the FileUploader remains disabled, it is as if the panel had not been updated.
>
> Generally <a4j:ajax event="selectitem"> requests fail, this only in IE 11.0.4 (KB2925418)
>
> Currently there is a filter to ensure compatibility with IE 8.
>
> When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly.
>
> The configuration of the environment is:
> Richfaces 4.0.0.
> IE11
> JSF2
> Eclipse Kepler
>
> Is there any way to correct the problems with these ajax requests?
--
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
11 years, 11 months
[JBoss JIRA] (RF-11417) Tab: investigate why @action does not work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-11417:
------------------------------------
My apologies [~Trims] for the delayed follow-up, I was busy preparing-for/attending the DevNation conference recently.
[~ppitonak] please verify the update Pull request.
> Tab: investigate why @action does not work
> ------------------------------------------
>
> Key: RF-11417
> URL: https://issues.jboss.org/browse/RF-11417
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.1.0.CR1
> Reporter: Lukáš Fryč
> Fix For: 5-Tracking
>
>
> Determine why rich:tab @action has not been implemented.
> Verify that its implementation can't affect current applications (and try to find possible workaround).
> Implement @action and @actionListener.
--
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
11 years, 11 months
[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 commented on RF-13611:
------------------------------------
The method that returns null:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
{code}
public Reception getReception() {
return null;
}
{code}
> 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
>
> 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
11 years, 11 months