This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102263

Summary:	Create Entity Class from Database fails on attached schema
Product:	javaee	Reporter:	Chris Webster <cwebster>
Component:	Persistence	Assignee:	Erno Mononen <emononen>
Status:	RESOLVED FIXED
Severity:	blocker
Priority:	P1
Version:	5.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	db schema file causing the issue exception stack trace

Description Chris Webster 2007-04-24 03:00:04 UTC

When running the create entity class from database wizard, an exception dialog
is shown, but the error message is not very helpful. 

Additional information: JDK 1.6_01
The subversion plugin was installed and the generation directory was a
subversion controlled directory.

Comment 1 Chris Webster 2007-04-24 03:00:54 UTC

Created attachment 41514 [details]
db schema file causing the issue

Comment 2 Chris Webster 2007-04-24 03:01:38 UTC

Created attachment 41515 [details]
exception stack trace

Comment 3 Erno Mononen 2007-04-24 08:43:58 UTC

I'll take a look at this.

Comment 4 Erno Mononen 2007-04-24 10:04:36 UTC

I can't reproduce with the latest build nor with 6.0 M8 on JDK 6 / Linux. The 
generator has changed quite a bit since 5.5, so perhaps this has been fixed 
already. What is a bit strange is that the stack trace indicates that the 
generation failed when generating "DbLiteral" entity class, but I can't see any 
corresponding table in the attached schema - should it include such table? 
Also, please try if you can reproduce this with the latest build.

Comment 5 Chris Webster 2007-04-24 15:29:06 UTC

This problem is not there in 6.0, this was encountered using 5.5. We added Db to
all the generated class names in the last panel of the wizard, so the table in
question is LITERAL.

Comment 6 Erno Mononen 2007-04-24 15:47:38 UTC

OK, thanks for the info. I'm closing this as fixed - if there will be 5.5.2, 
perhaps this issue should be considered to be fixed for it.