Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 253676

Summary: Typo in org.hibernate.valitator.event.ValidateEventListener
Product: [JBoss] JBoss Enterprise Application Platform 4 Reporter: Aleksandar Kamburov <wise_guybg>
Component: doc-Hibernate_Reference_GuideAssignee: Vinu S Renish <vrenish>
Status: CLOSED NEXTRELEASE QA Contact: Content Services Development <ecs-dev-list>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0Keywords: Documentation
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/doc/hibernate/Entity_Manager_User_Guide/Setup_and_configuration-Event_listeners.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-17 05:47:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aleksandar Kamburov 2007-08-21 06:48:07 UTC 
Description of problem:
The package of the class ValidateEventListener is misspelled. Instead of
"validator" you have "valitator" on two occasions (pre-insert, pre-insert).

Version-Release number of selected component (if applicable):


How reproducible:
If you need to create a new listener you might want to copy-paste the default
values for pre-insert/pre-insert listeners and add your own classes. With the
current error you will introduce a bug in your code that will throw a runtime
exception on application startup.
 
Actual results:
org.hibernate.valitator.event.ValidateEventListener

Expected results:
org.hibernate.validator.event.ValidateEventListener

Additional info:
The same problem exists on this page
http://www.hibernate.org/hib_docs/entitymanager/reference/en/html/configuration.html
Comment 1 Michael Hideo 2008-01-17 05:49:38 UTC 
Mass Re-Assignment to Vinu for vetting. Investigate and migrate to JIRA if
necessary.
Comment 2 Vinu S Renish 2008-04-17 05:47:20 UTC 
Done. Will be available in the next CP release (4.2 CP03 and 4.3 CP01)