I just encounterd this problem on JBoss 4.2.2 which includes an updated JBossWS. It seems to only occur after an error in a previous deployment. Restarting the Application Server seems to resolve the problem.