Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 114824 - CMP mapping not updated for events
CMP mapping not updated for events
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8
All All
: P4 (vote)
: 6.x
Assigned To: Rochelle Raccah
Depends on:
  Show dependency treegraph
Reported: 2007-09-06 00:13 UTC by Rochelle Raccah
Modified: 2009-05-25 21:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description Rochelle Raccah 2007-09-06 00:13:46 UTC
This similar to issue 54867 but in that case it was not implemented yet and in this case it's a regression.

- 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
Comment 2 Rochelle Raccah 2007-10-12 01:00:43 UTC
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

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."
Comment 3 Vince Kraemer 2007-12-07 16:20:15 UTC
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.
Comment 4 Rochelle Raccah 2007-12-10 19:35:45 UTC
This is only partially fixed - changing target milestone.
Comment 5 Rochelle Raccah 2008-01-08 22:19:13 UTC
CMP support not used much in NB 6.
Comment 6 Vince Kraemer 2008-10-18 03:42:59 UTC
this is even less likely to be resolved
Comment 7 Vince Kraemer 2008-12-24 21:58:25 UTC
examine after 7.0

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo