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.
Reproduced with JSE 8.1, 2006.02.25 Steps to reproduce: - Register WebLogic server. I had it stopped when this issue was catched - Press New Project - Select Web > Web Application. Click Next - Select BEA WebLogic as target Server. Click Finish - Result: java.lang.RuntimeException: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: Cannot create weblogic DeploymentManager instance.
Created attachment 29067 [details] Exception
Please try it with NetBeans 5.0 or later. If it happens, please reopen. Btw, only Weblogic 9.0 is supported. And it seems that there is some problem with your configuration. That part throws exception intentionally when it is trying to access some class placed in some server library and exception occurs.
Still reproducible with Coco 20060320 build. The exception was thrown when New Enterprise Application was created. Moreover, mouse cursor changed to hourglass and didn't change back.
When WL server is not running then all calls to InstancePropertiesImpl.getDeploymentManager() correctly throw DeploymentManagerCreationException because connection to a running instance is needed by the WL implementation. The solution is to call get*Disconnected*DeploymentManager(). The client code calling InstancePropertiesImpl.getDeploymentManager() needn't access non-API method at all. If a server recognition is required then J2eeModuleProvider.getServerID() method should be called.
Still reproducible with JSE 8.1 (2006.05.31).
Please reopen if the exception is different than in the attachment 29067 [details]. This exception is not caused by NetBeans as I already described in my last comment.
The exception is completely identical. Could you, please, provide more comments. Even it is not NB-related exception it is still shown within NB while the user tries to perform some reasonable action. This is not the acceptable behavior both the exception and the way the IDE handles it.
This looks like an issue in the Enterprise Profiler. Can this be assigned to a developer responsible for this component?
Reopened as far as this behavior is not acceptable. Please, fix or re-assign the issue.
Changing Version to 'Other' (not reproducible with NetBeans 5.0; we have no specific version value for JSE 8.1).
Probably, we should add a version value for JSE 8.1.
Will be tracked as CR 6434455
removing JSE 8.1 version