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 20051213] Steps to reproduce: 1) create EJB module 2) generate CMP beans from database 3) open visual editor of ejb-jar.xml file and add 1:M or M:N relationship 4) save changes 5) open sun-ejb-jar.xml and try to map new CMR field. User can't select related bean. Therefore, can't finish this wizard. I tested this and realized that this is working for 1:1 relationship. See screenshot.
Created attachment 27891 [details] screenshot
I can reproduce this issue with unidirectional relationship
If you restart the IDE, then repeat step 5, it works, so it appears there is some problem with the meta data coming from the schema2beans beans representing the ejb-jar.xml. Downgrading to P3.
User has confirmed that it works after restart. In fact, he says it even works after some delay: "Actually i noticed one more thing. I was working on my Netbeans project and then went away from the computer for a couple of hours without turning it off. After i came back, i suddenly could map the relationship field. Seems to me as if the information entered in the descriptor file by creating the relationship are net periodically updated in the graphical editor." This reinforces the belief I have that it is related to the validity of the ejb-jar.xml schema2beans metadata. I therefore think that this depends on recently filed issue 70649.
issue #70649 is allready fixed and verified in 5.0 branch but it didn't solve this issue. Before restart of IDE I'm not able to map CMR field and after restart of IDE I get NPE when expanding beans's nodes in sun-ejb- jar.xml. I therefore think that this now it depends on issue #70672.
See workaround. Defer to promo-G.
This issue affects the CMP UI present in the 5.5 config editor, which is not present in 6.0 and is deferred to post 6.0 if it ever comes back.
Please re-evaluate.
What's to reevaluate? It's a dead bug unless we put the CMP UI back into the sun-ejb-jar.xml editor. Admittedly not likely but if we did, this would presumably become a valid bug again. I will downgrade it to P4. It's certainly shouldn't against our P3 cap under the current circumstances (e.g it cannot be reproduced in 6.0 but only in some hypothetical future version that may never exist.)
CMP UI not present in NB 6. "cmp" in whiteboard can be used to find these issues if we reenable the CMP UI.