Hi Aki,
I haven't checked the jaxws/jaxrs endpoint implementations but I will.
My module is also implemented as a CXF feature with interceptors and
Spring integration the same way as ws-rm implementation and I'm quite
happy with that. The only thing I don't like is the way the RMEndpoint is
man
Hi folks, I just confirmed by testing Metro w/UsernameToken over SSL
transport (haven't tried UT via their symmetric binding yet), that if I
*don't* configure a server-side password callback handler like here:
https://github.com/gmazza/blog-samples/blob/master/metro_usernametoken_profile/service/sr
Forgot to mention that this is related to CXF-4600 :(
Follow up (thinking CXF way and for a while ignoring previous post):
The sources we're going to talk about are located here:
http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/src/test/java/org/jboss/test/ws/jaxws/jbws355
Hi CXF folks,
Below is copy/paste from JAXWS 2.2 spec, Section 3.7 - Service Specific
Exception:
---
For exceptions that do not match the pattern described in section 2.5,
JAX-WS maps those exceptions to Java
beans and then uses those Java beans as input to the JAXB mapping.
---
I'm wondering why
