[JBoss JIRA] Created: (RF-9427) core-demo is not deployable to JBoss AS 6 M5
by Lukas Fryc (JIRA)
core-demo is not deployable to JBoss AS 6 M5
--------------------------------------------
Key: RF-9427
URL: https://jira.jboss.org/browse/RF-9427
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Milestone3
Environment: http://anonsvn.jboss.org/repos/richfaces/tags/4.0.0.20101004-M3/examples/...
OpenJDK Runtime Environment (IcedTea6 1.8.1) (6b18-1.8.1-0ubuntu1)
JBoss AS 6.0.0 M5
Reporter: Lukas Fryc
20:06:36,629 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to PostClassLoader: name=vfs:///home/lfryc/Apps/jboss-6.0.0.20100911-M5/server/default/deploy/core-demo.war state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/lfryc/Apps/jboss-6.0.0.20100911-M5/server/default/deploy/core-demo.war
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [:1.6.0_18]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) [:1.6.0_18]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) [:1.6.0_18]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) [:1.6.0_18]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) [:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_18]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]
Caused by: java.lang.Error: Error visiting "/home/lfryc/Apps/jboss-6.0.0.20100911-M5/server/default/deploy/core-demo.war/WEB-INF/lib/guava-r05.jar/com/google/common/collect/LinkedListMultimap$ValueForKeyIterator.class"
at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:268) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5]
at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:102) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
at org.jboss.deployers.vfs.plugins.classloader.VFSDeploymentClassLoaderPolicyModule.visit(VFSDeploymentClassLoaderPolicyModule.java:181) [:2.2.0.Alpha7]
at org.jboss.scanning.plugins.DeploymentUnitScanner.scan(DeploymentUnitScanner.java:111) [:1.0.0.Alpha6]
at org.jboss.scanning.spi.helpers.UrlScanner.scan(UrlScanner.java:96) [:1.0.0.Alpha6]
at org.jboss.scanning.deployers.ScanningDeployer.deploy(ScanningDeployer.java:90) [:1.0.0.Alpha6]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7]
... 36 more
Caused by: java.lang.RuntimeException: Error visiting resource: VFSResourceContext @ com/google/common/collect/LinkedListMultimap$ValueForKeyIterator.class / BaseClassLoader@2a74c252{vfs:///home/lfryc/Apps/jboss-6.0.0.20100911-M5/server/default/deploy/core-demo.war}, visitor: org.jboss.scanning.annotations.plugins.GenericAnnotationVisitor@3c6508fd
at org.jboss.scanning.plugins.visitor.IgnoreSetErrorHandler.handleError(IgnoreSetErrorHandler.java:56) [:1.0.0.Alpha6]
at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:91) [:1.0.0.Alpha6]
at org.jboss.scanning.annotations.plugins.AnnotationsScanningPlugin.visit(AnnotationsScanningPlugin.java:89) [:1.0.0.Alpha6]
at org.jboss.scanning.spi.helpers.ScanningPluginWrapper.visit(ScanningPluginWrapper.java:112) [:1.0.0.Alpha6]
at org.jboss.classloading.plugins.visitor.FederatedResourceVisitor.visit(FederatedResourceVisitor.java:101) [jboss-classloading.jar:2.2.0.Alpha8]
at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:264) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
... 48 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at org.jboss.reflect.plugins.ConstructorInfoImpl.<init>(ConstructorInfoImpl.java:95) [jboss-reflect.jar:2.2.0.Alpha9]
at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.<init>(ReflectConstructorInfoImpl.java:68) [jboss-reflect.jar:2.2.0.Alpha9]
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getConstructors(IntrospectionTypeInfoFactoryImpl.java:174) [jboss-reflect.jar:2.2.0.Alpha9]
at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredConstructors(ClassInfoImpl.java:446) [jboss-reflect.jar:2.2.0.Alpha9]
at org.jboss.scanning.plugins.visitor.ClassHierarchyResourceVisitor.handleClass(ClassHierarchyResourceVisitor.java:79) [:1.0.0.Alpha6]
at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.doVisit(ReflectResourceVisitor.java:108) [:1.0.0.Alpha6]
at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:86) [:1.0.0.Alpha6]
... 52 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-9430) Form based Queues nested in iteration components are omitted
by Lukas Fryc (JIRA)
Form based Queues nested in iteration components are omitted
------------------------------------------------------------
Key: RF-9430
URL: https://jira.jboss.org/browse/RF-9430
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Milestone3
Environment: * RichFaces 4.0.0.20101004-M3 r.19446
* Metamer 4.0.0.20101004-M3 r.19455
* Mojarra 2.0.2-FCS
* Apache Tomcat 6.0.26
* OpenJDK Runtime Environment 1.6.0_18-b18 @ Linux
* Firefox 3.6.10 @ Linux
Reporter: Lukas Fryc
If you have h:form inside iteration component and a4j:queue attached inside that form, the settings of such form based queue aren't applied properly:
the global queue settings are used instead.
Such behavior can be reproduced in Metamer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-9371) a4j:ajax: attribute onerror doesn't work
by Pavol Pitonak (JIRA)
a4j:ajax: attribute onerror doesn't work
----------------------------------------
Key: RF-9371
URL: https://jira.jboss.org/browse/RF-9371
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Milestone2
Environment: RichFaces 4.0.0-SNAPSHOT r.19299
Metamer 4.0.0-SNAPSHOT r. 19319
Mojarra 2.0.2-FCS
Java(TM) SE Runtime Environment 1.6.0_21-b06 @ Linux
Chrome 7.0.531.0 @ Linux
Reporter: Pavol Pitonak
The following code shows an alert but the same code with a4j:ajax doesn't work.
<h:inputText>
<f:ajax event="keyup" onerror="alert(1)" listener="#{nonExistingBean.behaviorListener}"/>
</h:inputText>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-9489) Spinner used for filtering data table causes infinite loop
by Pavol Pitonak (JIRA)
Spinner used for filtering data table causes infinite loop
----------------------------------------------------------
Key: RF-9489
URL: https://jira.jboss.org/browse/RF-9489
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, component-tables
Affects Versions: 4.0.0.Milestone3
Environment: RichFaces 4.0.0-SNAPSHOT r.19446
Metamer 4.0.0-SNAPSHOT r.19535
Mojarra 2.0.2-FCS
GlassFish Server Open Source Edition 3.0.1
Java(TM) SE Runtime Environment 1.6.0_21-b06 @ Linux
Chrome 8.0.551.0 @ Linux
Reporter: Pavol Pitonak
Column in a data table filtered using spinner:
<rich:column id="columnNumberOfKids" filter="#{richDataTableBean.filterKidsImpl}">
<f:facet name="header">
<rich:inputNumberSpinner id="columnHeaderNumberOfKidsInput" value="#{richDataTableBean.kidsFilter}" minValue="0" maxValue="5" cycled="true">
<a4j:ajax render="commonGrid" execute="@this"/>
</rich:inputNumberSpinner>
</f:facet>
<h:outputText value="#{record.numberOfKids}" />
</rich:column>
public Filter<?> getFilterKidsImpl() {
return new Filter<Employee>() {
public boolean accept(Employee e) {
int kids = getKidsFilter();
if (e.getNumberOfKids() >= kids) return true;
return false;
}
};
}
When value of the spinner is changed, table is filtered but a lot of requests is fired (probably infinite loop).
http://anonsvn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/appl...
http://anonsvn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/appl...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-9567) rich:autocomplete - add bypassUpdates attribute
by Lukas Fryc (JIRA)
rich:autocomplete - add bypassUpdates attribute
-----------------------------------------------
Key: RF-9567
URL: https://jira.jboss.org/browse/RF-9567
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Milestone3
Reporter: Lukas Fryc
from ML:
rich:autocomplete completion shows validation messages before user request to submit it's value
<a4j:outputPanel ajaxRendered="true"><h:messages /></a4j:outputPanel>
<rich:autocomplete mode="ajax" id="autocomplete" autocompleteMethod="#{...}" value="#{value}">
<f:validateRegexp value="Alabama" />
</a4j:autocomplete>
<rich:commandButton render="@form" execute="autocomplete" />
This code shows the validation message during each ajax request for completion.
I have two ideas how to work it around:
1. rich:autocomplete bypassUpdates=true
2. rich:autocomplete limitRender=true
But both are not implemented attributes in rich:autocomplete.
Ilya commented:
prefer to use bypassUpdates = true as if we will use limitRender - facesMessages will still be in context just not appear on the screen. Even considering that it's not implemented as attribute - it should be still possible to define as request parameter in autocomplete js. Please create jira for it. And if possible and not took much time we should have it in near release I think.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months