I tried your suggestion. I now have 3 handlers in my chain. That is, two from the standard-jbossws-endpoint-config.xml and one from my webservices.xml.
However, none of them are getting their methods invoked at runtime.
My webservices.xml now reads:
I changed to JBoss-4.0.4-RC2 and the handler's handleRequest method is being invoked.
Sadly handleFault() isn't, which is the one I wanted to be invoked.
Posting a bug with JBossws....
I am experiencing a similar behavior with 4.04.GA. Has anyone else run into this? My handler's init method is called, but the handleRequest method is not.
I'm also experiencing a similar behaviour under JBoss AS 4.0.4
I've tried all kind of handlers, mainly Handler and Generic Handler.
None of them is being triggered, as I'm placing a log call under each one of them and checking the server log for info but none of them shows up.
Have you tried jbossws-1.0.3.GA (this installs onto 4.0.4)?
If you guys find a problem, and can produce a small test case that shows it, file a jira issue and we will take a look at it. (jira.jboss.com)
I've solved this problem by:
1º Generating the artifacts first (JbossIDE WS Pluggin (2.0 Beta2))
2º Manually editing webservices.xml to include the following lines:
.... </service-impl-bean> <handler> <handler-name>ServiceAttachmentHandler</handler-name> <handler-class>provisioning.ServiceAttachmentHandler</handler-class> </handler> </port-component> .....
Handler is now properly interpreted as shown in the jboss log.
To further clear my previous post, here's my complete description:
I've got 3 java files
1 - My WS interface
2 - My WS Implementacion
3 - My Handler class (in this case a class for handling attachments)
With the WS Plugin, I've generated my WS artifacts (WSDL file, web.xml, webservices.xml and jaxrpc-mapping.xml).
Problem is that webservices.xml didn't include any link to the handler, so I had to manually insert them (see above post).
Then it was just a case of packagin my files into a .WAR file (ant - f packaging-build.xml) and deploy it to my JBoss AS.
Hope this helps anyone with this sort of problem.
We'll add handler support to the JBossIDE plugin before the final release... thanks for your feedback.