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.
Steps to reproduce: - install the IDE - run IDE - switch to runtime tab - unplug the computer from the net - expand Servers/SunJavaSystemApplicationServer/JBI - expand any of JBI subnodes Result: All subnodes are empty whereas some of them sould contain subnodes. e.g. Service Engines should contain JavaEEServiceEngine and bpelse
Previously, JBI Manager used the MBeanServerConnection from the app server code but it had some problem in providing detailed error message when a remote invokation fails. (See IZ 79392, 80251) To address those issues, JBI Manager now creates its own Connector to talk to the MBeanServer. To create the connector, it needs to parse some config file (${nbuserdir}/config/J2EE/InstalledServers/.nbattrs). Apparently, there is some offline XML catalog issue here. The app server uses a special class loader to load the JBI Manager module. One option to fix this issue is to update that class loader to load NetBeans XML catalog. The particular public ID that I am interested in is "-//NetBeans//DTD DefaultAttributes 1.0//EN" and it's available in DTD and XML Schema Catalog/NetBeans Catalog. I will ask for Ludo's opinion.
I am not sure ${nbuserdir}/config/J2EE/InstalledServers/.nbattrs is a public, available interface to use. Instead, one must use the J2EEServer module and only its publics APIs. Or maybe some friend apis from the App server plugin. What do you need from this .nbattr file? The 2 issues mentioned do not help to understand how they've been fixed.
My experience in coke milestone build 17 is: - unplug the computer from the net - expand the Servers/SunJavaSystemApplicationServer/JBI node and its subnodes. ==> Those subnodes are still listed. - Stop App Server and re-start App Server. - expand the Servers/SunJavaSystemApplicationServer/JBI node and its subnodes. ==> Those subnodes are disappeared.
This problem is fixed now by using the NetBeans catalog to resolve entity. Ludo, we need the httpportnumber, among other things from the .nbattrs file, to create a HttpServerConnector (org.netbeans.modules.sun.manager.jbi.management.connectors.HttpServerConnector). The MBeanServerConnection we get from this connector is user friendly. We will investigate friend apis from the app server plugin later.
The bug is still reproducible in build 060806_1
The bug is only fixed in release55 branch. I will need to get permission before checking in into the beta branch.
Fixed in cokebeta too.
verified in RC1 build