Bug 258567 - invalid converter class defined in orm.xml leads to exception logging in
Summary: invalid converter class defined in orm.xml leads to exception logging in
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 454792
  Show dependency tree
 
Reported: 2008-12-11 17:12 EST by Karen Butzke CLA
Modified: 2022-06-09 10:02 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Butzke CLA 2008-12-11 17:12:57 EST
I have a converter defined in my eclipselink orm.xml file and when initializing the eclipselink project I get ClassNotFoundExceptions.  They tell me the class that was not found, but not where it came from.  I should instead get a validation exception something like this: converter class named model.Foo listed in the orm.xml file on line number 10 was not found.

<converter name="my-converter" class="model.Foo"/>

I assume the same problem exists for other classes in the orm.xml file.
Comment 1 Peter Krogh CLA 2009-11-27 13:40:49 EST
This bug fix did not make the cut off for 2.0.0. We are deferring the bugs to Future where we can properly sort them all together based on community votes and severity. We will then assign them accordingly to future patch sets and releases.
Comment 2 Peter Krogh CLA 2009-11-30 11:35:50 EST
Changing the priority of the bugs that have been recently triaged to future.  Targetting them to P2 will differentiate them from the P3s that have been triaged into future earlier.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:02:53 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink