I figured this out. Apparently I needed to add the module dependency to my
EJB manifest:
Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export
After doing this and redeploying the interceptor registered and fired when
my EJB web service was called.
-
-Jeff
--
View this
Hi Tobi
Using CXFRS client with JMS is indeed uncommon with the main reason
being is that of course CXFRS is primarily meant to work with the HTTP
targets.
But with CXF being so flexible it ended up supporting non-HTTP targets
too with some minor updates.
So, ultimately, as far as the
Hi,
this morning I created this issue (which is already solved, thx again):
https://issues.apache.org/jira/browse/CXF-6810.
Note that in a comment, Sergey Beryozkin writes
"So now we have WebClient and proxies being able to use HTTP Api to send the
messages over JMS which is unusual ;-)"