Community
Participate
Working Groups
When working "top down" and developing Entities without a database selecting any connection will result in numerous erroneous errors. Obviously working top down there are no tables for your Entities and errors to that effect are just noise. Once you are ready to generate DDL you should choose a connection. Then validation of mappings against the data model make sense. The fix is simple--provide a "<None>" choice for Connection in the JPA Project Wizard just like is available for JPA Implementation Library.
Workaround: Errors do not occur if you don't log into the DB, which is a user directed action. If logged in, logging out will remove the errors. Post 1.0 change.
<None> option should be available, and should also be the default when creating a new project.
Created attachment 95508 [details] Added <None> to the connection combo
Looks good, I've checked this patch in to HEAD
mass change to add 'contributed' keyword based on bugzilla query, please correct if that's not accurate (by marking patches as obsolete and removing the 'contributed' keyword.
Verified in wtp-sdk-I-I20080501032258-20080501032258.zip