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.
The EJB project (and probably Ejb freeform project as well btw) does not initialize the server configuration when loading an existing EJB module. The SJSAS plugin works around some common cases, but there are places where we simply can't so this needs to be fixed. One example: Create an ejb module project. Add a session bean that does not have remote interfaces. Open ejb-jar.xml in the Multiview editor. Close the Configuration Files node in the project explorer. (Very important.) Restart the IDE. Once restarted, ejb-jar.xml will be opened again. Go to the EJB Implementation & Interfaces section for the session bean added previously and check "remote interfaces" and say yes to generating them. When is said and done, no JNDI name will be generated for this session bean (or even an entry for it) in sun-ejb-jar.xml The reason is that the configuration editor has not been initialized for this project and no DConfigBeans have been created to listen to event changes. The workaround is to open the configuration editor on sun-ejb-jar.xml before adding the remote interfaces. There is a similar issue wrt/ new EJB projects created in the same IDE session. I suspect that if the problem with opened projects is fixed, it will also fix the problem with new projects, but if not, I can work around this one.
Fixed in both EJB project and EJB free-form project. J2eeModuleProvider.getConfigSupport().ensureConfigurationReady() is called when the project is opened. Let me know if it fixed the issue wrt new EJB projects you mentioned or if I can help with it. Checking in EjbJarProject.java; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/EjbJarProject.java,v <-- EjbJarProject.java new revision: 1.55; previous revision: 1.54 done Checking in EJBProjectNature.java; /cvs/j2ee/ejbfreeform/src/org/netbeans/modules/j2ee/ejbfreeform/EJBProjectNature.java,v <-- EJBProjectNature.java new revision: 1.18; previous revision: 1.17 done
I added some additional code to the SJSAS deployment configuration object's initialization routine that was required for this all to work properly. Should be fine now.