Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Hyperjaxb3 column naming override #2

Open
GoogleCodeExporter opened this issue Mar 15, 2015 · 1 comment
Open

Hyperjaxb3 column naming override #2

GoogleCodeExporter opened this issue Mar 15, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

The specified column names in an XSD are not necessarily used in the generated 
annotations. HJ3 seems to mangle the names in order to avoid conflicts with 
reserved names for different DBMSs.
However, it is possible to override this behaviour using customisations. 
Perhaps an idea for 2.0?

Original issue reported on code.google.com by freeke...@gmail.com on 3 Jul 2011 at 3:02
@GoogleCodeExporter
Copy link
Author 

Can you give more detail?
<orm:column name="CUSTOMER_ORDER__ID" nullable="true" />
etc works fine for me.
Thanks

Original comment by roger.parkinson35 on 22 Feb 2012 at 6:21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter