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.
build 200503291900 -create EJB module -create CMP beans from database -update database table, add column -recapture schema from database -open sun-ejb-jar editor /Cmp Mapping ---new column is not available for mapping!
Part of the problem is that the newly captured dbschema has the wrong name and is therefore put into the cache under a different name. Petr J., I will send you what I have found about this so far. Unfortunately, even correcting that - it is still not showing up in the mapping screens. I propose that Petr try to fix the first part and I will look into it some more after that.
Committed the part with wrong name of schema, contributed by Rochelle. /cvs/db/model/src/org/netbeans/modules/dbschema/jdbcimpl/wizard/RecaptureSchema.java,v <-- RecaptureSchema.java new revision: 1.3; previous revision: 1.2
I've spent the whole day investigating and found that this is still a dbschema problem - the name being used to put it in the cache is almost the absolute path the file instead of the relative path under the config/source root in the project. The problem is in SchemaElementUtil.forName: forName(getPackageName(schemaFO, '/'), null); This code used to work in NB 3.6, but produces the wrong result in project based NB 4.x. I'll send Petr J. more info on my investigation directly.
Setting TM to 4.1 - serious issue that must be fixed.
Partially fixed in trunk. The fix only addresses the case when the schema file is directly in conf; I don't know how to fix for the subdirectories of conf. Checking in src/org/netbeans/modules/dbschema/SchemaElementUtil.java; /cvs/db/model/src/org/netbeans/modules/dbschema/SchemaElementUtil.java,v <-- SchemaElementUtil.java new revision: 1.5; previous revision: 1.4 done Checking in src/org/netbeans/modules/dbschema/jdbcimpl/wizard/CaptureSchema.java; /cvs/db/model/src/org/netbeans/modules/dbschema/jdbcimpl/wizard/CaptureSchema.java,v <-- CaptureSchema.java new revision: 1.2; previous revision: 1.1 done Checking in RelatedCMPHelper.java; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/ejb/wizard/cmp/RelatedCMPHelper.java,v <-- RelatedCMPHelper.java new revision: 1.10; previous revision: 1.9 done Diff for review: http://db.netbeans.org/source/browse/db/model/src/org/netbeans/modules/dbschema/SchemaElementUtil.java?r1=1.4&r2=1.5 http://db.netbeans.org/source/browse/db/model/src/org/netbeans/modules/dbschema/jdbcimpl/wizard/CaptureSchema.java?r1=1.1&r2=1.2 http://j2ee.netbeans.org/source/browse/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/ejb/wizard/cmp/RelatedCMPHelper.java?r1=1.9&r2=1.10
similar to http://www.netbeans.org/issues/show_bug.cgi?id=57460 ?
No, they are not related
verifyed in NB 20050408-0935 trunk
Partial fix is in trunk; not marking as fixed as this is not fixed completely. Need to integrate the partial fix to 4.1 branch too.
reopen
Partial fix also put into the release41 branch. The rest of this issue is a P3, downgrading. Checking in SchemaElementUtil.java; /cvs/db/model/src/org/netbeans/modules/dbschema/SchemaElementUtil.java,v <-- SchemaElementUtil.java new revision: 1.4.2.1; previous revision: 1.4 done Checking in jdbcimpl/wizard/CaptureSchema.java; /cvs/db/model/src/org/netbeans/modules/dbschema/jdbcimpl/wizard/CaptureSchema.java,v <-- CaptureSchema.java new revision: 1.1.20.1; previous revision: 1.1 done Checking in RelatedCMPHelper.java; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/ejb/wizard/cmp/RelatedCMPHelper.java,v <-- RelatedCMPHelper.java new revision: 1.9.4.1; previous revision: 1.9 done
Since it is not usual to put dbschema files outside of conf, and since there were no user reports of this problem, this is probably not very serious. Downgrading to P4.
TM 5.0 -> TBD
Reassigned to new owner.