Just to follow up for the archive, it looks like the notification
handling was never fully implemented. I've worked around this by
duplicating some of the code from the
org.apache.cxf.management.jmx.InstrumentationManagerImpl class to create
the RequiredModelMBean and register that directly.
Hi Dan,
Just confirm that proposed solution works!
Thanks,
Andrei.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Montag, 26. August 2013 20:40
To: dev@cxf.apache.org; Andrei Shakirin
Subject: Re: extensions dynamically added/removed from exited bus
On
Hi
I've started seeing today the following error in JAXRSSoapBookTest:
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to
create service.
at com.ibm.wsdl.util.xml.DOMUtils.getQName(DOMUtils.java:309)
at
Isn't JAXRS and SOAP an oxymoron?
On 9/12/2013 8:25 AM, Sergey Beryozkin wrote:
Hi
I've started seeing today the following error in JAXRSSoapBookTest:
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstructionException: Failed to
create service.
at
On 12/09/13 13:27, Bill Burke wrote:
Isn't JAXRS and SOAP an oxymoron?
I've just learned a new word, lol.
FYI, the test stresses the endpoint which offers both WS RS capabilities.
Generally speaking, I agree both styles can be difficult to support in a
single implementation, but I reckon
On 12/09/13 13:43, Bill Burke wrote:
On 9/12/2013 8:40 AM, Sergey Beryozkin wrote:
On 12/09/13 13:27, Bill Burke wrote:
Isn't JAXRS and SOAP an oxymoron?
I've just learned a new word, lol.
Was just trying to be funny... Sorry for trolling, couldn't resist. See
you on the 339 list Serg.
I'm looking for an example code written using Apache CXF WebClient API and
requesting an access token using the Password Access grant Type.
The
documentation(http://cxf.apache.org/docs/jax-rs-oauth2.html#JAX-RSOAuth2-ClientCredentials).
is really very poor about this subject .
The only input
