[JBoss JIRA] (RF-12474) rich:select with enableManuelInput="true": Validation message is not displayed when the submitted value is not on the list.
by Ray Yan (JIRA)
[ https://issues.jboss.org/browse/RF-12474?page=com.atlassian.jira.plugin.s... ]
Ray Yan commented on RF-12474:
------------------------------
This is still broken in v4.3.4. When change the value and invalid value had been keyed in, only the text color had been changed to red but not nullify the value. So once submitted, the previous value will be submitted instead of null.
> rich:select with enableManuelInput="true": Validation message is not displayed when the submitted value is not on the list.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12474
> URL: https://issues.jboss.org/browse/RF-12474
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.2.2.Final
> Reporter: Ilia Vassilev
> Assignee: Jan Papousek
> Priority: Critical
> Fix For: 4.2.4, 4.3.0.M2
>
>
> Per the [RichFaces documentation|https://access.redhat.com/knowledge/docs/en-US/JBoss_Web_Fr...]:
> {quote}
> ...If an invalid value is entered, it is highlighted as erroneous and validation messages appear with the submission...
> {quote}
> The validation message is not displayed when entering an invalid value (which is not on the list) and submitting it.
> Test code:
> {code}
> <rich:select id="idSelect" value="#{backingBean.value}" enableManualInput="true">
> <f:selectItem itemLabel="Option 1" itemValue="Option 1" />
> <f:selectItem itemLabel="Option 2" itemValue="Option 2" />
> </rich:select>
> {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
12 years, 3 months
[JBoss JIRA] (RF-13239) Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13239?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13239:
------------------------------------
Fixed and pushed to the main development branches for 4.3, 4.5, and 5.0
[~lfryc] We'll have to cherry-pick or merge master to the release branch before re-staging the 4.3.5 release.
> Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x
> -------------------------------------------------------------------
>
> Key: RF-13239
> URL: https://issues.jboss.org/browse/RF-13239
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Minor
> Labels: needs-qe
> Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml
> # check browser console
> result:
> * Invalid CSS property name: repeat-x (in popupPanel.ecss, line 40)
> possible solution:
> * replace
> {code}
> .rf-pp-hdr {
> background: url(...);
> repeat-x: top left #BED6F8;
> ...
> }
> {code}
> * with
> {code}
> .rf-pp-hdr {
> background: url(...) repeat-x top left #BED6F8;
> ...
> }
> {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
12 years, 3 months
[JBoss JIRA] (RF-13487) Photoalbum: viewing FB albums improvements
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13487?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13487:
----------------------------------
The first four steps are resolved.
The last one, the dataSctroller behaves similarly as in this [comment|https://issues.jboss.org/browse/RF-13486?focusedCommentId=1293637...]
> Photoalbum: viewing FB albums improvements
> ------------------------------------------
>
> Key: RF-13487
> URL: https://issues.jboss.org/browse/RF-13487
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
> # album view: there is no slideshow button, when browsing album (but it is there, when you are browsing images)
> # photo view: cannot browse between album's images after an image has been selected
> # photo view: 'Original size' button's text underflows the image
> # photo view: breadcrumbs contains bad album group ('Event: Rock concert of the decade')
> # photo view: dataScroller needs to be fixed as the dataScrollers used in public/own shelves (when scrolling to next page and selecting an image from there, the dataScroller's actual page returns to previous page)
--
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
12 years, 3 months
[JBoss JIRA] (RF-13486) Photoalbum: viewing g+ albums improvements
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13486?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13486:
----------------------------------
The first and third case are resolved.
But the second one, the dataScroller, don't behaves like the one used in own or predefined albums.
# login with g+ (use account I've put here)
# open the last picture in g+ album
* the dataScroller shows pictures from 2 to 6, not just only the last one (as in own or predefined albums)
> Photoalbum: viewing g+ albums improvements
> ------------------------------------------
>
> Key: RF-13486
> URL: https://issues.jboss.org/browse/RF-13486
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
> # album view: there is no slideshow button, when browsing album (but it is there, when you are browsing images)
> # photo view: dataScroller needs to be fixed as the dataScrollers used in public/own shelves (when scrolling to next page and selecting an image from there, the dataScroller's actual page returns to previous page)
> # photo view: breadcrumbs contains bad album group ('Event: Rock concert of the decade')
--
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
12 years, 3 months
[JBoss JIRA] (RF-13483) Photoalbum: Hibernate error during deployment
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13483?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek closed RF-13483.
----------------------------
closing.
> Photoalbum: Hibernate error during deployment
> ---------------------------------------------
>
> Key: RF-13483
> URL: https://issues.jboss.org/browse/RF-13483
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.5
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
> # build photoalbum and deploy to EAP 6.1.1
> result:
> * there is error during deployment
> * the application and basic functionality works
> {code}
> 09:42:16,051 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000227: Running hbm2ddl schema export
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Album drop constraint FK3C68E4F938C4E8E
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK3C68E4F938C4E8E [42102-168]
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Album drop constraint FK3C68E4F1C054E63
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK3C68E4F1C054E63 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Comment drop constraint FK9BDE863F390C8611
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK9BDE863F390C8611 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Comment drop constraint FK9BDE863FE13B4C3
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK9BDE863FE13B4C3 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A3EBF919D
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A3EBF919D [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A756B16E3
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A756B16E3 [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A1C054E63
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A1C054E63 [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event_remoteAlbumIds drop constraint FK13ED749451AFB863
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT_REMOTEALBUMIDS" not found; SQL statement:
> alter table Event_remoteAlbumIds drop constraint FK13ED749451AFB863 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image drop constraint FK437B93B9C30AC43
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE" not found; SQL statement:
> alter table Image drop constraint FK437B93B9C30AC43 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FKA5ED44315922EB44
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FKA5ED44315922EB44 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FKA5ED4431D066A86
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FKA5ED4431D066A86 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Shelf drop constraint FK4C26E0A51AFB863
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "SHELF" not found; SQL statement:
> alter table Shelf drop constraint FK4C26E0A51AFB863 [42102-168]
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Shelf drop constraint FK4C26E0A443A43E9
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "SHELF" not found; SQL statement:
> {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
12 years, 3 months
[JBoss JIRA] (RF-13483) Photoalbum: Hibernate error during deployment
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13483?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13483:
----------------------------------
Yes, you are true, I have misread the original issue (RF-13205).
> Photoalbum: Hibernate error during deployment
> ---------------------------------------------
>
> Key: RF-13483
> URL: https://issues.jboss.org/browse/RF-13483
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.5
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
> # build photoalbum and deploy to EAP 6.1.1
> result:
> * there is error during deployment
> * the application and basic functionality works
> {code}
> 09:42:16,051 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000227: Running hbm2ddl schema export
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Album drop constraint FK3C68E4F938C4E8E
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK3C68E4F938C4E8E [42102-168]
> 09:42:16,058 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Album drop constraint FK3C68E4F1C054E63
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "ALBUM" not found; SQL statement:
> alter table Album drop constraint FK3C68E4F1C054E63 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Comment drop constraint FK9BDE863F390C8611
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK9BDE863F390C8611 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Comment drop constraint FK9BDE863FE13B4C3
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "COMMENT" not found; SQL statement:
> alter table Comment drop constraint FK9BDE863FE13B4C3 [42102-168]
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A3EBF919D
> 09:42:16,059 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A3EBF919D [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A756B16E3
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A756B16E3 [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event drop constraint FK403827A1C054E63
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT" not found; SQL statement:
> alter table Event drop constraint FK403827A1C054E63 [42102-168]
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Event_remoteAlbumIds drop constraint FK13ED749451AFB863
> 09:42:16,060 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "EVENT_REMOTEALBUMIDS" not found; SQL statement:
> alter table Event_remoteAlbumIds drop constraint FK13ED749451AFB863 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image drop constraint FK437B93B9C30AC43
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE" not found; SQL statement:
> alter table Image drop constraint FK437B93B9C30AC43 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FKA5ED44315922EB44
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FKA5ED44315922EB44 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Image_MetaTag drop constraint FKA5ED4431D066A86
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "IMAGE_METATAG" not found; SQL statement:
> alter table Image_MetaTag drop constraint FKA5ED4431D066A86 [42102-168]
> 09:42:16,061 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Shelf drop constraint FK4C26E0A51AFB863
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "SHELF" not found; SQL statement:
> alter table Shelf drop constraint FK4C26E0A51AFB863 [42102-168]
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) HHH000389: Unsuccessful: alter table Shelf drop constraint FK4C26E0A443A43E9
> 09:42:16,062 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 4) Table "SHELF" not found; SQL statement:
> {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
12 years, 3 months
[JBoss JIRA] (RF-12865) Correct deferred partial response ending by leveraging PVC wrapper chain
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12865:
---------------------------------
We have addresses the concerns there and make the EPVC extend PartialViewContextWrapper and additionally we use PartialResponseWriterWrapper for rendering our extensions, which is library-compatibility friendly approiach.
On the other way, we haven't get rid of DIRECT/WRAPPER mode yet as mentioned here:
{quote}
--I recommend to get rid of `finallyEndDocument()` and perform the job in `endDocument()`. I also recommend to let your partial view context impl extend from javax.faces.context.PartialViewContextWrapper to keep RichFaces friendly towards other JSF libraries which also offer a PVC wrapper.-- This should also eliminate verbose/strange ContextMode.DIRECT/WRAPPED boilerplate. As to "encoding issues" which the class' javadoc is talking about, I'm not sure what exactly you mean there, but I believe that it has the same grounds as this PrimeFaces problem: http://stackoverflow.com/a/9839362/157882 If this is true, just don't do that and clearly document to the enduser that it's his responsibility to explicitly configure the webapp and/or the server to use UTF-8 as request parameter/body encoding, which is at most a matter of a servlet fitler with an oneliner. This way you do not need to introduce wrapper modes in your partial view context (at least, I did not see a clear reason why you are doing that, other than the comment on top of the class).
{quote}
This approach makes sure that when some library renders own components, their approach for PVC (or default JSF impl one) will be used, instead of the approach that RichFaces takes. This is silly, but out approach (rewriting processPartial() method) is required in order to support meta-component and AjaxOutput rendering as discussed in RF-13317.
> Correct deferred partial response ending by leveraging PVC wrapper chain
> ------------------------------------------------------------------------
>
> Key: RF-12865
> URL: https://issues.jboss.org/browse/RF-12865
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: third-party
> Affects Versions: 4.3.1
> Environment: weblogic 10.3.4, Myfaces 2.1.10, Richfaces 4.3.1, OmniFaces1.3
> Reporter: blam lam
> Assignee: Lukáš Fryč
> Labels: jsf, needs-qe
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> After submit from a a4j:commandButton, it fail to re-render / update other component on the page.
> This problem only appear in MyFaces. It does not happens in Mojarra.
--
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
12 years, 3 months