The concept of default server is broken and does not work for a while.
This concept was abandoned since it did not work
anymore. The problem could occur for example if the default server was Tomcat
then the EJB project, which was set to use the default server could not be
deployed to it, etc.
You should use Deployment.getServerInstanceIDs() method to pick
a server they should be deployed to based on the projects requirements.
See issue 83934.
not critical for 6.1, and there were no objections from users as well; will target 6.5
Please, use Dev if you plan to fix this in 6.5. Future means post-6.5 now...
I agree it is not critical, however it is blocking the huge cleanup of the j2eeserver. Please at least do the quickfix
asap (remove the call - it can basically remove anything to your code including null).
This should be done soon enough to stabilize the code.
Fixed in trunk.