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 77553

Summary: Add db model validation to inline verifier
Product: javaee Reporter: Rochelle Raccah <raccah>
Component: PersistenceAssignee: Tomasz Slota <tslota>
Status: NEW ---    
Severity: blocker    
Priority: P2    
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description Rochelle Raccah 2006-06-08 00:10:18 UTC
From a discussion with Sahoo and Ludo:

... validation of field names that wouldn't match the default column name
annotations. If we add the option of skipping annotations in our generator,
would our validation catch that? 

... Now, if a user deletes this mapping annotation, then the inline verifier
should find this, no? 

Sahoo: No, inline verifier currently does not do any dbmodel verification. It
was too late to do this for 5.5.
Comment 1 Tomasz Slota 2006-06-27 07:32:20 UTC
*** Issue 79166 has been marked as a duplicate of this issue. ***
Comment 2 Tomasz Slota 2006-06-27 07:34:06 UTC
Description of #79166, which has been marked as duplicate for this issue:

Whenever we remove relationships or rename the variables which constitute an old
existing relationship, the old variables are nether removed or renamed instead
new variables are created with new names. Under similar circumstances when
variable names in multiple relationships clash i.e. when two variables in the
same class have same name no error is shown in the relationship editor instead
the original methods for the variable remain abstract and a new set of methods
non-abstract are created for the repeat. This is clearly a lack of
synchronization between the source code and the ejb-jar.xml file.