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.
This similar to issue 54867 but in that case it was not implemented yet and in this case it's a regression. Basics: - add/remove/rename cmp field, cmr field - add/remove/rename cmp bean - TBD: change field type such that it is no longer valid as field/cmr For now, since we have no ui and no default mapping, we can skip handling add events. For basics, handle remove or rename bean or field
This is partially fixed for - remove cmp field - remove/rename cmp bean <http://serverplugins.netbeans.org/source/browse/serverplugins/sun/appsrv/src/org/netbeans/modules/j2ee/sun/api/CmpMappingProvider.java?r1=1.2&r2=1.3> <http://serverplugins.netbeans.org/source/browse/serverplugins/sun/appsrvbridge/src/org/netbeans/modules/j2ee/sun/bridge/cmp/CmpMappingProviderImpl.java?r1=1.4&r2=1.5> <http://serverplugins.netbeans.org/source/browse/serverplugins/sun/sunddui/src/org/netbeans/modules/j2ee/sun/share/configbean/EjbJarRoot.java?r1=1.23&r2=1.24> <http://serverplugins.netbeans.org/source/browse/serverplugins/sun/sunddui/src/org/netbeans/modules/j2ee/sun/share/configbean/DescriptorListener.java?r1=1.4&r2=1.5> <http://serverplugins.netbeans.org/source/browse/serverplugins/sun/sunddui/src/org/netbeans/modules/j2ee/sun/share/configbean/SunONEDeploymentConfiguration.java?r1=1.63&r2=1.64>
Still to be done: - rename cmp field - remove/rename cmr field - TBD: change field type such that it is no longer valid as field/cmr The problem with these was that when we get the events/xpaths for cmp field name and for the cmr fields, there was no way to get back to the path for the bean, which would be needed to find the corresponding entry in the sun-cmp-mappings.xml. From a discussion with Peter: "As for CmpField->Entity, there is no way to track back to the parent. There are a couple of options. We can do some sort of lookup. I threw together some code that builds a mapping and holds a weak reference (GC -> rebuild on demand) but it would have to be maintained in case fields are deleted/added while the cache exists, which is overhead I'd prefer to avoid. Another possibility would be to add/remove listeners to entity beans themselves are they are created/destroyed and specifically handle this case --> no mapping to maintain. This is what the old (5.5) code did, but for all ddbeans and all xpaths, which I want to avoid. Doing it specifically for Entity/CmpField though isn't a big deal."
please close this issue if you forgot to earlier. If this issue is still open, please change the target milestone to reflect the current commitment.
This is only partially fixed - changing target milestone.
CMP support not used much in NB 6.
this is even less likely to be resolved
examine after 7.0