Bug 822209 - RichFaces kitchensink archetype - creating already registered user throws server side error - it should be caught and user should be noticed
Summary: RichFaces kitchensink archetype - creating already registered user throws ser...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Examples, RichFaces
Version: 2.0.0.ER6
Hardware: All
OS: All
low
low
Target Milestone: CR1
: 2.1.0
Assignee: Brian Leathem
QA Contact: Pavol Pitonak
URL:
Whiteboard: rf-kitchensink
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-16 16:09 UTC by Juraj Huska
Modified: 2014-09-30 23:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
project generated from kitchensink archetype
Last Closed: 2012-11-30 15:34:47 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RF-12252 0 Minor Resolved kitchensink archetype - creating already registered user throws server side error - it should be caught and user should ... 2012-11-08 11:43:49 UTC

Description Juraj Huska 2012-05-16 16:09:13 UTC 
Description of problem:
When creating an already registered user there is server side error, because of the not unique email:

javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: Unique index or primary key violation: "CONSTRAINT_INDEX_8 ON PUBLIC.MEMBER(EMAIL)"; SQL statement:

There is also no error message rendered to the user. There should be some notice that such a user have been already registered.

Version-Release number of selected component (if applicable):
Richfaces 4.2.1.Final
Comment 1 JBoss JIRA Server 2012-05-31 08:55:11 UTC 
Juraj Húska <jhuska> made a comment on jira RF-12252

I have created [this|https://github.com/jbossas/quickstart/issues/286] upstream issue.
Comment 2 JBoss JIRA Server 2012-05-31 08:56:12 UTC 
Juraj Húska <jhuska> updated the status of jira RF-12252 to Resolved
Comment 3 JBoss JIRA Server 2012-05-31 08:56:17 UTC 
Juraj Húska <jhuska> updated the status of jira RF-12252 to Closed
Comment 5 JBoss JIRA Server 2012-10-29 16:57:50 UTC 
Brian Leathem <bleathem> updated the status of jira RF-12252 to Reopened
Comment 6 JBoss JIRA Server 2012-10-29 16:58:45 UTC 
Brian Leathem <bleathem> made a comment on jira RF-12252

I have created the upstream issue: [jboss-as-quickstart/issues/286|https://github.com/jboss-jdf/jboss-as-quickstart/issues/286]
Comment 7 JBoss JIRA Server 2012-10-29 16:59:25 UTC 
Brian Leathem <bleathem> made a comment on jira RF-12252

This issue has been resolved upstream, we'll have to pull that change into our quickstart.
Comment 8 JBoss JIRA Server 2012-10-30 23:38:14 UTC 
Brian Leathem <bleathem> updated the status of jira RF-12252 to Resolved
Comment 9 JBoss JIRA Server 2012-10-30 23:38:14 UTC 
Brian Leathem <bleathem> made a comment on jira RF-12252

This has been resolved with an upstream merge.
Comment 11 Karel Piwko 2012-11-30 15:34:47 UTC 
Distributed as a part of WFK 2.1.0.GA release.
Note You need to log in before you can comment on or make changes to this bug.