The current implementation of the Jboss Controller has no way of running 2
concurrent jboss application servers. It should look at the underlying Bindings
files to see what has been configured and what port to ping to see if it is
running. The implementation of the Jboss IDE works very well for this and the
open-source nature should allow you to reuse it.
Please provide description of the functionality you require. Please focus more
on the required feature, not on the solution proposal. Thank you.
This feature would need to:
-dynamic discovery of ports for a running server to verify start/stop
-be able to read the bindings in ..jboss/docs/examples/binding-manager and the
associated server.xml to determine display values if bindings are used
-a way a terminate a server (jvm kill)
-be able to use JMX service for configuration
Nice to have
> detect the port bindings for a server state detection
It cannot be reliable because there can be always some other process running
using the same resources. More complicated algorithm will not bring the better
results with the reasonable effort. There are plans to allow user to configure
the ports in a similar way as the Tomcat server plugin has. Now we detect the
server state via its JMX interface and additional checks for several ports are
run at the beginning of the Start action.
> server process termination
I filed the issue 71398. There are still some problems on Windows, see issue 63157.
> using JMX for the configuration
JBoss server has own JMX console, we will not duplicate this functionality.
Generally, NetBeans does not have the ambitions to replace the tools the servers
may already have. I filed the issue 71399 for running JMX console from the IDE.
> JNDI explorer
Again, the feature is already on the server. If you feel the need to allow
running it directly from the IDE, please file a new enhancement.
> Datasource manager
What do you exactly mean by this feature?
FYI, I am currently implementing generation of the datasource references into
the server-specific descriptors (the action is tied to 'Use database' action in
Servlet and EJB code). It will also contain data-source generation and deploying
to server along with the database driver. There will be also data-source
generation tied to EJB3-related functionality but it is not clear yet which
steps will be involved.