I have entered bug report JBWS-1859 to describe a bug we experienced when JBoss
is restarted. If client applications are still actively making web service
requests during the restart, the handler chain was usually populated with too
many copies of the handlers. This doesn't seem to cause a maj
"[EMAIL PROTECTED]" wrote : The question is, whether the incomming message
conforms to the abstract contract published by the endpoint. If the message is
invalid with that respect it simply is invalid
At this point we're much more concerned about consistency. Updating to a newer
server version
I've recently updated a web service from JBoss 4.0.2 to 4.0.5 with JBossWS
1.2.1, and it's causing problems. The new setup enforces the proper naming of
method parameters, instead of just taking them positionally.
Some older clients don't send the proper parameter names. For example, Axis
gen
