One answer I came across while googleing was that the build I am forced to use doesn't support the usage of a @WebServiceProvider, would anybody here be able to confirm/deny that? If anybody knows of a good workaround to the issue, that would also be appreciated. At the moment I am considering just making it a HttpServlet that trys to read the soap message.
1 of 1 people found this helpful
As far as I can remember (JBoss 4.0.4 came a lot of time before I started being involved in JBossWS), there was a partial/initial implementation of JAXWS available at that time. So it's might even be the @WebServiceProvider was not implemented. The reccomended solution here is to move to a recent JBoss/JBossWS version as soon as possible, not only for this reason.
Thank you for the information, we do plan on updating to a newer version but unfortunately it wasn't an option with our current timeframe. For now the solution was to deal with the requst with a servlet. So far it seems to be doing the job.