After some searches my case was resolved by using the jbossws-native-3.0.4. Since jbossws-native-3.0.5 the issue was introduced and resolved in jbossws-native-3.1.1 which unfortunatelly introduced a side effect, hence 3.0.4 did the fix.
Reply to this message by going to Community
Start a new discussion in JBoss Portal at Community