Hi Joseph,
I appreciate your proactive approach. The problem here is however a bit more complicated. Let's forget about the IDE for a while, the issue here is that the whole ws-security policy support is contract based. Moreover, there's really a big set of possible configurations you can have for the ws-security policy assertions. So, something which might be worth evaluating is a functionality for generating templates / examples of ws-security assertions for common scenarios. We could have, e.g. a list of ws security configuration names each corresponding to a set of assertions to be added in the wsdl. That would allow providing a basic java-first ws-security policy support. The configuration name could then of course be specified either in the jaxws-endpoint-config.xml or using a new custom annotation in the endpoint class. Then, the IDE could be updated to pick up this functionality.
WDYT?