[JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13603:
-------------------------------
Steps to Reproduce:
# Get RF 5 kitchensink archetype and build it with JDK 6
# Start JBoss AS 7.1 with Java 6 and deploy kitchensink app
# See console for errors
_______________________________________
ORIGINAL STEPS TO REPRODUCE
1. Use this in web.xml:
{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}
2. Deploy
was:
1. Use this in web.xml:
{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}
2. Deploy
> 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
>
> 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-13603) unsupported classversion 51.0 while deploying ear
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13603:
------------------------------------
Verified, I managed to reproduce this issue.
I used kitchensink archetype (5.0.0.Alpha3) which I built with JDK 6 and deployed to JBoss AS 7.1 (again using Java 6). Even without changing the web.xml file I am getting very similar compatibility error (this one comes from Skinbean, but there are more such errors in log, all of them throwing UnsupportedClassVersionError).
{code}
13:57:27,188 WARN [org.jboss.modules] (MSC service thread 1-7) Failed to define class org.richfaces.skin.SkinBean in Module "deployment.kitchensink-test.war:main" from Service Module Loader: java.lang.UnsupportedClassVersionError: org/richfaces/skin/SkinBean : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_24]
at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_24]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.6.0_24]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.loadModuleClass(Module.java:517) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
at org.jboss.as.web.deployment.jsf.JsfManagedBeanProcessor.deploy(JsfManagedBeanProcessor.java:107)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
13:57:27,221 ERROR [org.jboss.web] (MSC service thread 1-7) JBAS018211: Could not load JSF managed bean class: org.richfaces.skin.SkinBean
{code}
I will modify steps to reproduce accordingly to my findings. If there is anything else I can do, let me know.
> 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
>
> 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-13514) Support file upload progress tracking in Servlets >= 3.0 environment
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13514:
------------------------------------
[~jhuska], after my commits, are there any remaining issues on WildFly 8 Final? As far as AS 7.1.1 is concerned it seems there are issues with more components than just fileUpload.
> Support file upload progress tracking in Servlets >= 3.0 environment
> --------------------------------------------------------------------
>
> Key: RF-13514
> URL: https://issues.jboss.org/browse/RF-13514
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-input, core
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> We currently support two approaches for file upload:
> * Servlets 2.5: own request form data parser [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java]
> * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}}
> However as we have discussed RF-13444, we had to finally do a trade-off of limiting support of file progress tracking. I.e. in Servlets 3.0 we have no simple way how to track file upload progress since getParts() returns data for completed request.
> There are several possible outcomes:
> 1) drop server-side file upload progress tracking and leverage XHR2/HTML5 that has built-in ability to track progress
> * imho we are already prepared to switch to XHR2 and client-side progress (possibly leveraging some third-party widget) since [all major browsers support it at least one version back|http://caniuse.com/#feat=xhr2]
> * existing implementation: http://www.script-tutorials.com/pure-html5-file-upload/
> 2) use a {{ServletFilter}} to wrap a request as our {{FileUploadFacesContextFactory}} currently do and so have an earlier access to the request object
> * this principle has a drawback - we have to ensure our filter has high-enough priority so the servlet container won't touch the request body yet
--
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-13605) a4j:ajax button click event gets lost
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13605:
------------------------------------
Like [~avijra] said in the mail, I'm not sure this should be considered a bug. What happens is that the onblur triggers a rerender and so a part of DOM, button included, is replaced. The click on the original button either never happens to begin with, or is not executed since the button doesn't exist any more. Given that the ajax request may take a while to come back I assume the click might still register sometimes.
{code}
<body>
<script type="text/javascript">
refresh = function() {
var html = $('<input type="text" onblur="console.log(\'a\'); refresh()">'
+ '<button onclick="console.log(\'b\'); return false">Click</button>');
var form = $('#form');
form.html(html);
}
</script>
<form id="form">
<input type="text" onblur="console.log('a'); refresh()">
<button onclick="console.log('b'); return false">Click</button>
</form>
</body>
{code}
As far as I understand this should do essentially the same thing, albeit without ajax. The click doesn't trigger either.
> a4j:ajax button click event gets lost
> -------------------------------------
>
> Key: RF-13605
> URL: https://issues.jboss.org/browse/RF-13605
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.6
> Reporter: abhishek vijra
>
> Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints.
> Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior.
--
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-13605) a4j:ajax button click event gets lost
by abhishek vijra (JIRA)
[ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.s... ]
abhishek vijra updated RF-13605:
--------------------------------
> a4j:ajax button click event gets lost
> -------------------------------------
>
> Key: RF-13605
> URL: https://issues.jboss.org/browse/RF-13605
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.6
> Reporter: abhishek vijra
>
> Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints.
> Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior.
--
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-13605) a4j:ajax button click event gets lost
by abhishek vijra (JIRA)
abhishek vijra created RF-13605:
-----------------------------------
Summary: a4j:ajax button click event gets lost
Key: RF-13605
URL: https://issues.jboss.org/browse/RF-13605
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.6
Reporter: abhishek vijra
Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints.
Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior.
--
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 Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13595:
------------------------------------
Indeed, the instanceof check is incorrect. I have already fixed that.
> 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
> Assignee: Matej Novotny
> 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-12132) Richfaces queue not cleared after js error in oncomplete attribute
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12132?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-12132:
----------------------------------
Assignee: Jiří Štefek (was: Pavol Pitonak)
Jiri, please try to reproduce.
> 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
> Assignee: Jiří Štefek
> Labels: needs-qe
> 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
[JBoss JIRA] (RF-13604) rich:editor is flickering on mouse hover
by Serge Rogatch (JIRA)
[ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.s... ]
Serge Rogatch 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:
<!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).
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