[JBoss JIRA] (RF-13102) rich:calendar with date pattern- input gets cleared on click
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13102:
--------------------------------
Affects Version/s: 4.3.2
> rich:calendar with date pattern- input gets cleared on click
> ------------------------------------------------------------
>
> Key: RF-13102
> URL: https://issues.jboss.org/browse/RF-13102
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.2.3.Final, 4.3.2
> Reporter: Jonáš Trantina
>
> When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date).
> However, when the form is sent, the value is correctly assigned to the binded value.
> Example:
> {noformat}
> <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/>
> {noformat}
--
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, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-13107:
----------------------------------------------
Jonáš Trantina <jtrantin(a)redhat.com> made a comment on [bug 988401|https://bugzilla.redhat.com/show_bug.cgi?id=988401]
Description of problem:
We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
Note that:
1) switchType must be set to server to ensure the A's rich:message is really not on the page.
2) button in B must re-render only content of B
This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
Please find the enclosed reproducer.
Version-Release number of selected component (if applicable):
RichFaces 4.3.2.Final
How reproducible:
Download reproducer and
1) mvn clean package and deploy on JBoss
2) go to http://localhost:8080/bug_reproducer/index.jsf
3) fill in surname longer that 10 chars & click-open the second tab
4) enter short name (shorter than 6)
5) click submit - no message is shown
Workaround:
1) Add ajaxRendered="false" to the first rich:message in index.xhtml.
2) follow the steps above
3) rich:message is shown
> rich:message in tabPanel is not shown if other message is not rendered
> ----------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
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, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated RF-13107:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=988401
> rich:message in tabPanel is not shown if other message is not rendered
> ----------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
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, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13107:
--------------------------------
Attachment: bug_reproducer.zip
> rich:message in tabPanel is not shown if other message is not rendered
> ----------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
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, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by Jonáš Trantina (JIRA)
Jonáš Trantina created RF-13107:
-----------------------------------
Summary: rich:message in tabPanel is not shown if other message is not rendered
Key: RF-13107
URL: https://issues.jboss.org/browse/RF-13107
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.3.2
Reporter: Jonáš Trantina
We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
Note that:
1) switchType must be set to server to ensure the A's rich:message is really not on the page.
2) button in B must re-render only content of B
This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
Please find the enclosed reproducer.
--
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, 9 months
[JBoss JIRA] (RF-13106) Quickstart names in the POM files are not consistent and often are not clear
by Sande Gilda (JIRA)
Sande Gilda created RF-13106:
--------------------------------
Summary: Quickstart names in the POM files are not consistent and often are not clear
Key: RF-13106
URL: https://issues.jboss.org/browse/RF-13106
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: examples
Reporter: Sande Gilda
Quickstart names in the pom.xml files are not consistent and often are too generic and not clear which quickstart is building.
When you run `mvn clean install '-Pdefault,!complex-dependencies'` from the root directory of the quickstarts, it often is not clear which quickstart is compiling. Some start with "JBoss AS Quickstarts" and some do not. Some use the quickstart folder name in the description, some don't.
As described in the CONTRIBUTING.md file, the <name> in the quickstart pom.xml file should follow the template:
JBoss <target-product> Quickstart: <quickstart-name> < - optional-subfolder-name> where target-product is the Target Product metadata specified in the README.md file, quickstart-name is the quickstart folder name, and optional-subfolder-name is the name of any nested subfolder containing a pom.xml file.
JDF-430 addressed the EAP and WFK quickstarts. The root build not displays the following. Note the RichFaces and JDG quickstarts need to be updated.
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss EAP Quickstart: bean-validation
[INFO] JBoss EAP Quickstart: bmt
[INFO] JBoss WFK Quickstart: cdi-add-interceptor-binding
[INFO] JBoss EAP Quickstart: cdi-alternative
[INFO] JBoss EAP Quickstart: cdi-decorator
[INFO] JBoss EAP Quickstart: cdi-interceptors
[INFO] JBoss EAP Quickstart: cdi-injection
[INFO] JBoss EAP Quickstart: cdi-portable-extension
[INFO] JBoss EAP Quickstart: cdi-stereotype
[INFO] JBoss EAP Quickstart: cdi-veto
[INFO] JBoss WFK Quickstart: deltaspike-authorization
[INFO] JBoss WFK Quickstart: deltaspike-beanbuilder
[INFO] JBoss WFK Quickstart: deltaspike-beanmanagerprovider
[INFO] JBoss WFK Quickstart: deltaspike-deactivatable
[INFO] JBoss WFK Quickstart: deltaspike-exception-handling
[INFO] JBoss WFK Quickstart: deltaspike-helloworld-jms
[INFO] JBoss WFK Quickstart: deltaspike-partialbean-basic
[INFO] JBoss WFK Quickstart: deltaspike-partialbean-advanced
[INFO] JBoss WFK Quickstart: deltaspike-projectstage
[INFO] JBoss EAP Quickstart: ejb-asynchronous
[INFO] JBoss EAP Quickstart: ejb-asynchronous - ejb
[INFO] JBoss EAP Quickstart: ejb-asynchronous - client
[INFO] JBoss EAP Quickstart: ejb-in-ear
[INFO] JBoss EAP Quickstart: ejb-in-ear - ejb
[INFO] JBoss EAP Quickstart: ejb-in-ear - web
[INFO] JBoss EAP Quickstart: ejb-in-ear - ear
[INFO] JBoss EAP Quickstart: ejb-in-war
[INFO] JBoss EAP Quickstart: ejb-remote - server-side
[INFO] JBoss EAP Quickstart: ejb-remote - client
[INFO] JBoss EAP Quickstart: ejb-remote
[INFO] JBoss EAP Quickstart: ejb-security
[INFO] JBoss EAP Quickstart: ejb-security-plus
[INFO] JBoss EAP Quickstart: ejb-security-interceptors
[INFO] JBoss EAP Quickstart: ejb-throws-exception
[INFO] JBoss EAP Quickstart: ejb-throws-exception - ejb-api
[INFO] JBoss EAP Quickstart: ejb-throws-exception - ejb
[INFO] JBoss EAP Quickstart: ejb-throws-exception - web
[INFO] JBoss EAP Quickstart: ejb-throws-exception - ear
[INFO] JBoss EAP Quickstart: ejb-multi-server
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-one
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-one - ejb
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-one - ear
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-two
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-two - ejb
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-two - ear
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-main
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - ejb
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - web
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-main - ear
[INFO] JBoss EAP Quickstart: ejb-multi-server - app-web
[INFO] JBoss EAP Quickstart: ejb-multi-server - client
[INFO] JBoss EAP Quickstart: greeter
[INFO] JBoss EAP Quickstart: greeter-spring
[INFO] JBoss EAP Quickstart: helloworld
[INFO] JBoss WFK Quickstart: helloworld-errai
[INFO] JBoss WFK Quickstart: helloworld-gwt
[INFO] JBoss WFK Quickstart: helloworld-html5
[INFO] JBoss EAP Quickstart: helloworld-jms
[INFO] JBoss EAP Quickstart: helloworld-mdb
[INFO] JBoss EAP Quickstart: helloworld-osgi
[INFO] JBoss EAP Quickstart: helloworld-rs
[INFO] JBoss EAP Quickstart: helloworld-singleton
[INFO] JBoss EAP Quickstart: helloworld-ws
[INFO] JBoss EAP Quickstart: hibernate3
[INFO] JBoss EAP Quickstart: hibernate4
[INFO] CarMart Single Node (No Cluster)
[INFO] Transactional CarMart
[INFO] JBoss AS Quickstarts: JBoss Data Grid HelloWorld
[INFO] HotRod Endpoint Example
[INFO] Memcached Endpoint Example
[INFO] REST Endpoint Example
[INFO] JBoss Data Grid Quickstart Parent
[INFO] JBoss EAP Quickstart: kitchensink
[INFO] JBoss WFK Quickstart: kitchensink-angularjs
[INFO] JBoss WFK Quickstart: kitchensink-backbone
[INFO] JBoss WFK Quickstart: kitchensink-deltaspike
[INFO] JBoss EAP Quickstart: kitchensink-ear
[INFO] JBoss EAP Quickstart: kitchensink-ear - ejb
[INFO] JBoss EAP Quickstart: kitchensink-ear - web
[INFO] JBoss EAP Quickstart: kitchensink-ear - ear
[INFO] JBoss WFK Quickstart: kitchensink-html5-mobile
[INFO] JBoss EAP Quickstart: kitchensink-jsp
[INFO] JBoss EAP Quickstart: kitchensink-ml
[INFO] JBoss EAP Quickstart: kitchensink-ml-ear
[INFO] JBoss EAP Quickstart: kitchensink-ml-ear - ejb
[INFO] JBoss EAP Quickstart: kitchensink-ml-ear - web
[INFO] JBoss EAP Quickstart: kitchensink-ml-ear - ear
[INFO] JBoss EAP Quickstart: kitchensink-spring-asyncrequestmapping
[INFO] JBoss EAP Quickstart: kitchensink-spring-basic
[INFO] JBoss EAP Quickstart: kitchensink-spring-controller
[INFO] JBoss EAP Quickstart: kitchensink-spring-matrixvariables
[INFO] JBoss EAP Quickstart: kitchensink-spring-springmvctest
[INFO] JBoss EAP Quickstart: log4j
[INFO] JBoss EAP Quickstart: logging
[INFO] JBoss EAP Quickstart: logging-tools
[INFO] JBoss EAP Quickstart: mail
[INFO] JBoss EAP Quickstart: numberguess
[INFO] JBoss EAP Quickstart: payment-cdi-event
[INFO] JBoss EAP Quickstart: picketlink-authentication-http-basic
[INFO] JBoss EAP Quickstart: picketlink-authentication-http-digest
[INFO] JBoss EAP Quickstart: petclinic-spring
[INFO] JBoss EAP Quickstart: picketlink-authentication-idm-jsf
[INFO] JBoss EAP Quickstart: picketlink-authentication-idm-multi-tenancy
[INFO] JBoss EAP Quickstart: picketlink-authentication-jsf
[INFO] JBoss EAP Quickstart: picketlink-authentication-rs-endpoint
[INFO] JBoss EAP Quickstart: picketlink-authentication-two-factor
[INFO] JBoss EAP Quickstart: picketlink-authorization-idm-jpa
[INFO] JBoss EAP Quickstart: picketlink-authorization-rs-rbac
[INFO] JBoss WFK Quickstart: picketlink-deltaspike-authorization
[INFO] JBoss AS Quickstarts: Hello world with JSF front end
[INFO] JBoss AS Quickstarts: Kitchensink-rf
[INFO] JBoss AS Quickstarts: RichFaces Bean Validation
[INFO] JBoss EAP Quickstart: servlet-async
[INFO] JBoss EAP Quickstart: servlet-filterlistener
[INFO] JBoss EAP Quickstart: servlet-security
[INFO] JBoss EAP Quickstart: shopping-cart
[INFO] JBoss EAP Quickstart: shopping-cart - server
[INFO] JBoss EAP Quickstart: shopping-cart - client
[INFO] JBoss WFK Quickstart: shrinkwrap-resolver
[INFO] JBoss EAP Quickstart: tasks
[INFO] JBoss EAP Quickstart: tasks-jsf
[INFO] JBoss EAP Quickstart: tasks-rs
[INFO] JBoss EAP Quickstart: temperature-converter
[INFO] JBoss EAP Quickstart: wicket-ear
[INFO] JBoss EAP Quickstart: wicket-ear - ejb
[INFO] JBoss EAP Quickstart: wicket-ear - war
[INFO] JBoss EAP Quickstart: wicket-ear - ear
[INFO] JBoss EAP Quickstart: wicket-war
[INFO] JBoss EAP Quickstart: xml-dom4j
[INFO] JBoss EAP Quickstart: xml-jaxp
[INFO] JBoss EAP Quickstart: cmt
[INFO] JBoss EAP Quickstart: jts
[INFO] JBoss EAP Quickstart: jts - application-component-2
[INFO] JBoss EAP Quickstart: jts - application-component-1
[INFO] JBoss EAP Quickstart: jta-crash-rec
[INFO] JBoss EAP Quickstart: wsat-simple
[INFO] JBoss EAP Quickstart: wsba-coordinator-completion-simple
[INFO] JBoss EAP Quickstart: wsba-participant-completion-simple
--
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, 9 months
[JBoss JIRA] (RF-13105) Problem with expanded for collapsiblePanel inside dataTable
by Mahesh Bonagiri (JIRA)
Mahesh Bonagiri created RF-13105:
------------------------------------
Summary: Problem with expanded for collapsiblePanel inside dataTable
Key: RF-13105
URL: https://issues.jboss.org/browse/RF-13105
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-menu, component-tables
Affects Versions: 4.3.2
Environment: Windows 7, IE 8,
Reporter: Mahesh Bonagiri
https://community.jboss.org/message/818174
<rich:dataTable var="var" value="#{bean.someValue}" id="table">
<rich:column>
<rich:collapsiblePanel expanded="#{var.property}" switchType="client" id="panel">
<h:inputText value="#{var.editValue1}" />
...
<a4j:commandButton action="#{bean.someAction}"
value="save" render="table"/>
</rich:collapsiblePanel>
</rich:column>
</rich:dataTable>
if one of the collapsiblePanels ist expanded and another server action (pageination, button click,...) is done, all the collapsiblePanels are expanded.
--
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, 9 months
[JBoss JIRA] (RF-10793) ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first
by David Lee (JIRA)
[ https://issues.jboss.org/browse/RF-10793?page=com.atlassian.jira.plugin.s... ]
David Lee commented on RF-10793:
--------------------------------
Looks the best and most simple way to fix is edit the attributes "CLIENT_SELECTION" of extenddatatable.
But I cannot find it in javascript DOM...any idea for that?
Thanks!
> ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first
> -------------------------------------------------------------------------------------------------------------------
>
> Key: RF-10793
> URL: https://issues.jboss.org/browse/RF-10793
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 3.3.3.Final
> Environment: OS: SLES 10 SP2
> JBoss EAP 4.3.0.GA_CP03
> Application using JBoss Seam 2.1.2
> Reporter: Eduard Ereza
> Labels: extendedDataTable, richfaces, richfaces-showcase, selection
> Fix For: 3.Future
>
> Attachments: extdt_solution.txt
>
>
> Selecting rows with Ctrl+click on extendedDataTable just after rendering it (first time or reRender) selects them in the backing bean, but then deselecting the same rows with Ctrl+click does not deselect them in the backing bean. The same happens if there is a selection when the component is rendered: then, deselecting a value deselects it from the backing bean, but selecting it again does not select it in the backing bean.
> When you click (without Ctrl) for the first time, everything works as it should.
> This is also reproduceable on RichFaces Live Demo: http://livedemo.exadel.com/richfaces-demo/richfaces/extendedDataTable.jsf (see Steps to Reproduce).
> This is probably related to RF-8681.
--
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, 9 months
[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed
by Christoph W. (JIRA)
[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ]
Christoph W. commented on RF-13018:
-----------------------------------
Priority should be Blocker and the fix implemented in next 4.3.x asap, please!
> a4j:commandButton wrong actions performed
> -----------------------------------------
>
> Key: RF-13018
> URL: https://issues.jboss.org/browse/RF-13018
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.3.Final, 4.3.2
> Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15
> Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9
> Reporter: Rob Hare
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Attachments: RF-13018.zip
>
>
> When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired.
> For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions.
> {noformat}
> <h:form id="testForm">
> <a4j:commandButton id="button1" type="button" value="Button 1"
> action="#{richBean.function1}" />
> <a4j:commandButton id="button2" type="button" value="Button 2"
> action="#{richBean.function2}" />
> </h:form>
> {noformat}
> Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed.
--
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, 9 months