Currently after some action which somehow modifies ws from wsdl or ws client
(for example adding handler to ws client, editing ws attribute,...) user have to
manually run clean & build on the project to reflect these changes in generated
sources/binaries.

Current behaviour is based on the existence of the ws from wsdl/ws client
package - if ws from wsdl/ws client's package exists (in eg.
build/generated/wsimport/client) then do nothing otherwise run wsimport. There
are following problems w/ this solution:
-if I add a ws client to a project, add a handler to it and build a project then
handler is not added to the project (clean & build fixes this)
-if I create ws client, change its package name in customization editor and
build project, I end up w/ unnecessarry classes in final jar/war (client's
classes are there two times - once in original package, second in new package)
(again clean & build fixes this)
...

It would be great if ws/ws client node will be able to (somehow) remember
whether it was changed in a way that requires running wsimport task or not and
if so then automatically run it.
It is just an implementation detail how to do this - one possible way could be
setting some "magic property" when running ws from wsdl/ws client targets from
the IDE (see eg. J2SEActionProvider and search for "debug.class" or "run.class"
there for example) depending on the return value of something like
"JaxWSNode.isDirty()"