It is generally a good idea not to use Java collection types, such as Map, List, Set etc, as parameter or return types of methods that are exposed as web service operations.
While it may be possible to make it work with some web service stack(s), there is a significant risk of lock-in.
You are aware that you are using a web service stack that was built five years ago?
Unless there is a very good reason for using this particular web service stack, I strongly suggest using something more recent.
A lot has happened in that time, for instance the WS-I Basic Profile and JAX-WS.
In Eclipse, if you look in the Preferences, there is a section named Web Services.
Under that section there are subsections for CXF 2.x Preferences, JBossWS Preferences.
These two allow you to use at least Apache CXF and JBoss WS (these options may require installation of plugins).
It is very easy to write an Ant-file that, given annotated Java classes, generate a WSDL file and use this in Eclipse.
As you may suspect, the web service tooling in Eclipse is not as good as that in NetBeans.