[JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13564:
-------------------------------
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
> rich:pickList shows an outline when clicked
> -------------------------------------------
>
> Key: RF-13564
> URL: https://issues.jboss.org/browse/RF-13564
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.5
> Reporter: alexey plotnikov
> Priority: Trivial
> Fix For: 4.3.7
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pi...].
> I found a solution:
> in file template "picklist.template.xml"
> {code}
> ...
> <div id="#{clientId}" tabindex="-1" class="#{concatClasses('rf-pick', component.attributes['styleClass'], disabled ? component.attributes['disabledClass'] : '')}" style="#{component.attributes['style']}"
> cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover
> onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup">
> ...
> {code}
> used tabindex attribue for DIV.
> Why?
> DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]).
> I can create pull request :).
--
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, 1 month
[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 updated RF-11417:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> 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: 4.3.7
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> 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
10 years, 1 month
[JBoss JIRA] (RF-11427) rich:tab - actionListener
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11427:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> rich:tab - actionListener
> -------------------------
>
> Key: RF-11427
> URL: https://issues.jboss.org/browse/RF-11427
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1
> Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d
> Metamer 4.1.0-SNAPSHOT r.22728
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.16
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
> RichFaces 4.2.1-SNAPSHOT
> Metamer 4.2.1-SNAPSHOT
> Mojarra 2.1.7-jbossorg-1
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 18.0.1025.168 @ Linux i686
> Reporter: Jan Papousek
> Assignee: Brian Leathem
> Labels: ci_issue, patch_proposed
> Fix For: 4.3.7
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> It seems that the actionListener attribute doesn't work.
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # open tab2
> # open tab1 (action and action listener are invoked)
> # open tab2
> # open tab1 (action and action listener are *NOT* invoked)
> # open tab1 (action and action listener are invoked)
--
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, 1 month
[JBoss JIRA] (RF-13478) VDL documentation typos
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13478:
-------------------------------
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
> VDL documentation typos
> -----------------------
>
> Key: RF-13478
> URL: https://issues.jboss.org/browse/RF-13478
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.3.3, 4.3.4
> Reporter: Vasil Lukach
> Priority: Trivial
> Fix For: 4.3.7
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> RichFaces VDL documentation typos:
> 1) rich:fileUpload
> - uploadLabel attribute : Add -> Upload
> - execute attribute (proposal): remove "Some components make use of additional keywords"
> 2) a4j:mediaOutput
> element attribute: imj -> img
> 3) accordion: epand -> expand
--
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, 1 month
[JBoss JIRA] (RF-13619) RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request
by Wang Liyu (JIRA)
Wang Liyu created RF-13619:
------------------------------
Summary: RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request
Key: RF-13619
URL: https://issues.jboss.org/browse/RF-13619
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: base functionality
Affects Versions: 4.3.6
Environment: Richfaces 4.3.6.Final, Tomcat 7.0.53, JSF 2.1.27, Java7u55
Reporter: Wang Liyu
In AJAX Response Richfaces added RichFaces.javascriptServiceComplete(); at the end of the response, the default implementation is fire a event, so if I have $.ready() want to do something on delay-constructed Richfaces Objects, this would be the place, I can call $.one('javascriptServiceComplete', functionname);
But if the same page is called with GET/POST method (normal requestion), it won't call this method, is there any reason why is that?
Here is the discussion on the forum:
https://community.jboss.org/thread/240501
--
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, 1 month
[JBoss JIRA] (RF-13617) CDK - NPE getOutputFileName
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13617?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13617:
------------------------------------
[~lukindo], the issue is in AbstractChart, you've got:
bq. tag = @Tag(type = TagType.Facelets, *generate = true*)
this causes the CDK to try generating a handler class but since no handler is defined it throws the NPE. It builds fine without it (there's one checkstyle error in ChartRendererBase) but I don't know if there's supposed to be a handler or not.
> CDK - NPE getOutputFileName
> ---------------------------
>
> Key: RF-13617
> URL: https://issues.jboss.org/browse/RF-13617
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component
> Reporter: Lukáš Macko
> Priority: Blocker
>
> During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok.
> {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at com.sun.tools.javac.main.Main.compile(Main.java:469)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132)
> at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47)
> at org.richfaces.cdk.Generator.execute(Generator.java:155)
> at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48)
> at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28)
> at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157)
> at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133)
> at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824)
> at com.sun.tools.javac.main.Main.compile(Main.java:439)
> ... 25 more
> Caused by: java.lang.NullPointerException
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49)
> at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39)
> at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45)
> at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211)
> at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206)
> at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95)
> ... 43 more
> [ERROR]}}
--
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, 1 month
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13615:
------------------------------------
The column-resizing issue was RF-13287, my solution does indeed use {{setColumnWidth}}, causing the second request.
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
> Reporter: Holger Walter
> Attachments: edt.png
>
>
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
> Best regards
> wlh
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 1 month
[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13615:
-------------------------------
Assignee: (was: Pavol Pitonak)
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
> Reporter: Holger Walter
> Attachments: edt.png
>
>
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered.
> Best regards
> wlh
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 1 month