[JBoss JIRA] (RF-13604) rich:editor is flickering on mouse hover
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13604:
-------------------------------
Steps to Reproduce:
1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration
2. Navigate to directory WebContent/WEB-INF/lib and put the following files there
- cssparser-0.9.9.jar
- guava-r09.jar
- richfaces-components-api-4.3.5.Final.jav
- richfaces-components-ui-4.3.5.Final.jar
- richfaces-core-api-4.3.5.Final.jar
- richfaces-core-impl-4.3.5.Final.jar
- sac-1.3.jar
3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled:
- Dynamic Web Module, version 3.1
- Java, version 1.7
- JavaScript, version 1.0
Click "Apply" button, then click "OK" button.
4. Under WebContent directory, create new XHTML file called test.xhtml with the following content:
{code}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head></h:head>
<h:body>
<h:form>
<rich:editor id="editor" toolbar="full" value="#{editorBean.value}" style="margin-bottom: 1em">
<a4j:ajax event="change" render="panel" status="panelUpdateStatus" />
<a4j:ajax event="dirty" render="panel" status="panelUpdateStatus">
<a4j:attachQueue requestDelay="1000" />
</a4j:ajax>
</rich:editor>
<rich:panel id="panel">
<f:facet name="header">
Output from Editor
<a4j:status name="panelUpdateStatus">
<f:facet name="start">
(Updating)
</f:facet>
</a4j:status>
</f:facet>
<h:outputText escape="false" value="#{editorBean.value}" />
</rich:panel>
</h:form>
</h:body>
</html>
{code}
5. Under Java Resources directory src, create file EditorBean.java with the following content:
{code}
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean(name="editorBean")
@SessionScoped()
public class EditorBean {
private String value = "";
public String getValue() {
return value;
}
public void setValue(String value) {
this.value = value;
}
}
{code}
6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish".
7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659).
8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome).
was:
1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration
2. Navigate to directory WebContent/WEB-INF/lib and put the following files there
- cssparser-0.9.9.jar
- guava-r09.jar
- richfaces-components-api-4.3.5.Final.jav
- richfaces-components-ui-4.3.5.Final.jar
- richfaces-core-api-4.3.5.Final.jar
- richfaces-core-impl-4.3.5.Final.jar
- sac-1.3.jar
3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled:
- Dynamic Web Module, version 3.1
- Java, version 1.7
- JavaScript, version 1.0
Click "Apply" button, then click "OK" button.
4. Under WebContent directory, create new XHTML file called test.xhtml with the following content:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head></h:head>
<h:body>
<h:form>
<rich:editor id="editor" toolbar="full" value="#{editorBean.value}" style="margin-bottom: 1em">
<a4j:ajax event="change" render="panel" status="panelUpdateStatus" />
<a4j:ajax event="dirty" render="panel" status="panelUpdateStatus">
<a4j:attachQueue requestDelay="1000" />
</a4j:ajax>
</rich:editor>
<rich:panel id="panel">
<f:facet name="header">
Output from Editor
<a4j:status name="panelUpdateStatus">
<f:facet name="start">
(Updating)
</f:facet>
</a4j:status>
</f:facet>
<h:outputText escape="false" value="#{editorBean.value}" />
</rich:panel>
</h:form>
</h:body>
</html>
5. Under Java Resources directory src, create file EditorBean.java with the following content:
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
@ManagedBean(name="editorBean")
@SessionScoped()
public class EditorBean {
private String value = "";
public String getValue() {
return value;
}
public void setValue(String value) {
this.value = value;
}
}
6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish".
7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659).
8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome).
> rich:editor is flickering on mouse hover
> ----------------------------------------
>
> Key: RF-13604
> URL: https://issues.jboss.org/browse/RF-13604
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.5
> Environment: Windows 7, Glassfish 4, Java 1.7, JSF2.2, Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659)
> Reporter: Serge Rogatch
> Labels: editor, glassfish, jsf22
>
> Initially the rich:editor component didn't render, throwing some errors in JavaScript ( https://community.jboss.org/message/867978 ), however afterwards I was not able to reproduce that in a newly created project.
--
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-13604) rich:editor is flickering on mouse hover
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13604:
----------------------------------
Assignee: Pavol Pitonak
QE, please verify
> rich:editor is flickering on mouse hover
> ----------------------------------------
>
> Key: RF-13604
> URL: https://issues.jboss.org/browse/RF-13604
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.5
> Environment: Windows 7, Glassfish 4, Java 1.7, JSF2.2, Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659)
> Reporter: Serge Rogatch
> Assignee: Pavol Pitonak
> Labels: editor, glassfish, jsf22
>
> Initially the rich:editor component didn't render, throwing some errors in JavaScript ( https://community.jboss.org/message/867978 ), however afterwards I was not able to reproduce that in a newly created project.
--
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-13603) unsupported classversion 51.0 while deploying ear
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13603:
-------------------------------
Workaround Description: Build with JDK 7
> unsupported classversion 51.0 while deploying ear
> -------------------------------------------------
>
> Key: RF-13603
> URL: https://issues.jboss.org/browse/RF-13603
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 5.0.0.Alpha3
> Environment: Windows 7, Weblogic 10.3.5, JDK 6
> Reporter: Nestor Armando Bohorquez
> Assignee: Matej Novotny
> Labels: ResourceServlet, classversion
> Fix For: 5-Tracking
>
>
> An exception is thrown when applicattion is been deployed:
> {code}
> java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
> at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
> at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
> at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
> at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
> at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
> at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105)
> at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368)
> at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:449)
> at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
> at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
> at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972)
> at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
> at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
> at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
> at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
> at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
> at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
> at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
> at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
> at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
> at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
> at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
> at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
> at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
> at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
> at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
> at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
> at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
> {code}
> I'm using this in the web.xml file.
> {code}
> <servlet>
> <servlet-name>Resource Servlet</servlet-name>
> <servlet-class>org.richfaces.servlet.ResourceServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
> {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-13595) rich:validator doesn't work when loaded via ajax (re-render)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13595:
----------------------------------
Assignee: (was: Matej Novotny)
Thanks [~manovotn]!
> rich:validator doesn't work when loaded via ajax (re-render)
> ------------------------------------------------------------
>
> Key: RF-13595
> URL: https://issues.jboss.org/browse/RF-13595
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.5
> Environment: RF 4.3.5
> Mojarra 2.1.27
> Java 7 Update 51 x64
> Tomcat 7.0.52
> Firefox 28.0 + Firebug
> Reporter: Michael B
> Fix For: 4.5-Tracking
>
> Attachments: validationTest.zip
>
>
> When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx.
> As already described in further detail in a comment to this JIRA here:
> https://issues.jboss.org/browse/RF-12031
> I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton.
> Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar.
> The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText.
> We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering.
> Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ...
--
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-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 commented on RF-13602:
------------------------------------
{quote}
We download richfaces 3.5.6
{quote}
Can you clarify?
> 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
10 years, 2 months
[JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13603:
-------------------------------
Fix Version/s: 5-Tracking
> unsupported classversion 51.0 while deploying ear
> -------------------------------------------------
>
> Key: RF-13603
> URL: https://issues.jboss.org/browse/RF-13603
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 5.0.0.Alpha3
> Environment: Windows 7, Weblogic 10.3.5, JDK 6
> Reporter: Nestor Armando Bohorquez
> Assignee: Matej Novotny
> Labels: ResourceServlet, classversion
> Fix For: 5-Tracking
>
>
> An exception is thrown when applicattion is been deployed:
> {code}
> java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
> at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
> at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
> at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
> at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
> at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
> at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209)
> at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105)
> at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368)
> at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:449)
> at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
> at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
> at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972)
> at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382)
> at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
> at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
> at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
> at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
> at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
> at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
> at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
> at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
> at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
> at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
> at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
> at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
> at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
> at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
> at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
> at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
> {code}
> I'm using this in the web.xml file.
> {code}
> <servlet>
> <servlet-name>Resource Servlet</servlet-name>
> <servlet-class>org.richfaces.servlet.ResourceServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
> {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-13582) Revert the core package re-factoring
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13582:
------------------------------------
Thanks for making progress with this issue [~michpetrov].
To identify any further breakages we should:
1) Build/deploy/run an unmodified richfaces showcase from 4.3.x against RF 4.5 jars (with necessary pom changes)
2) Ask QE to do the same for metamer
If both the above samples/tests run without error then we are in a good position w.r.t. backwards compatibility.
> Revert the core package re-factoring
> ------------------------------------
>
> Key: RF-13582
> URL: https://issues.jboss.org/browse/RF-13582
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to):
> * .servlet (PushServlet, ResourceServlet)
> * .push.cdi (@PUsh)
> * .push. (TopicContext)
> * FileUploadException
> A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures.
--
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-13568) IllegalArgumentException for PushResource.jsf
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13568?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13568:
----------------------------------
Assignee: Pavol Pitonak
QE please co-ordinate with [~juergen.zimmermann] to re-produce this issue, otherwise resolve it as out-of-date.
> IllegalArgumentException for PushResource.jsf
> ---------------------------------------------
>
> Key: RF-13568
> URL: https://issues.jboss.org/browse/RF-13568
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly snapshot with Undertow 1.0.1
> Reporter: Juergen Zimmermann
> Assignee: Pavol Pitonak
>
> Im using the latest WildFly snapshot containing Undertow 1.0.1. I'm getting tons of stacktraces like the following:
> {code}
> [io.undertow.request] UT005023: Exception handling request to /shop/rfRes/org.richfaces.ui.ajax.push.PushResource.jsf: java.lang.IllegalArgumentException: pushTopic request parameter must be present
> at org.richfaces.ui.ajax.push.PushResource.encode(PushResource.java:87) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3]
> at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.1.Final.jar:1.0.1.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.1.Final.jar:1.0.1.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]
> {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-12132) Richfaces queue not cleared after js error in oncomplete attribute
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12132?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12132:
-------------------------------
Assignee: (was: Jiří Štefek)
> Richfaces queue not cleared after js error in oncomplete attribute
> ------------------------------------------------------------------
>
> Key: RF-12132
> URL: https://issues.jboss.org/browse/RF-12132
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.0.Final
> Environment: Myfaces 2.1.6
> Tomcat 6.0.35
> Reporter: Michael Heinen
> Fix For: 5-Tracking
>
>
> Richfaces queue not cleared after js-error in oncomplete attribute
> Submit a <a4j:commandButton> with oncomplete="myNotExistingFuncrtion();"
> The ajax response arrives but the queue is not cleaned up after this due to the javascript error
> Starting from now no further ajax requests are possible because richfaces waits for previous submit results.
> Sample from the richfaces log:
> {code}
> debug[17:10:10.587]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_b
> debug[17:10:10.615]: Queue will wait 0ms before submit
> debug[17:10:10.644]: richfaces.queue: will submit request NOW
> info [17:10:10.671]: Received 'begin' event from <input id=j_id_5:j_id_b ...>
> info [17:10:10.707]: Received 'beforedomupdate' event from <input id=j_id_5:j_id_b ...>
> debug[17:10:10.729]: Server returned responseText: <?xml version="1.0" encoding="utf-8"?><partial-response><changes><update id="j_id_5:details"><![CDATA[<span id="j_id_5:details"> Content List: []</span>]]></update><update id="javax.faces.ViewState"><![CDATA[Ks5ELN5RlWC9cOr14o5TwKjJIsvsN15m6RRwvmJhzzDPVRu0CANZgn6X/WbW2yDmQr2WO23dULmn wieWEZBuLjpr9cB6Sh1pkPwozKCTGwOuq4ArOM3fSIO8zbDCP7orMXRzfA== ]]></update><extension id="org.richfaces.extension"><complete>myNotExistingFuncrtion();;</complete></extension></changes></partial-response>
> info [17:10:10.758]: Listing content of response changes element:
> Element update for id=j_id_5:details
> <update id="j_id_5:details"><![CDATA[<span id="j_id_5:details"> Content List: []</span>]]></update>
> Element update for id=javax.faces.ViewState
> <update id="javax.faces.ViewState"><![CDATA[Ks5ELN5RlWC9cOr14o5TwKjJIsvsN15m6RRwvmJhzzDPVRu0CANZgn6X/WbW2yDmQr2WO23dULmn wieWEZBuLjpr9cB6Sh1pkPwozKCTGwOuq4ArOM3fSIO8zbDCP7orMXRzfA== ]]></update>
> Element extension for id=org.richfaces.extension
> <extension id="org.richfaces.extension"><complete>myNotExistingFuncrtion();;</complete></extension>
> debug[17:10:19.143]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_a
> debug[17:10:19.171]: Queue will wait 0ms before submit
> debug[17:10:19.201]: richfaces.queue: Waiting for previous submit results
> {code}
> A request without javascript error ends with:
> {code}
> debug[17:20:22.033]: richfaces.queue: ajax submit successfull
> debug[17:20:22.075]: richfaces.queue: Nothing to submit
> info [17:20:22.117]: Received 'success' event from <input id=j_id_5:j_id_b ...>
> info [17:20:22.155]: Received 'complete' event from <input id=j_id_5:j_id_b ...>
> {code}
> I expect that the queue is cleaned up independent of javascript errors during oncomplete.
> Otherwise applications are not useable anymore.
--
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