IMHO unsubscribing from durable subscriptions is a management task. So I
would consider this to be out of scope.
Christian
On 26.09.2014 17:34, Andrei Shakirin wrote:
It seems that configuration option for (1: ClientId) is already in place.
Client or service can register a feature containing
I’ve just pushed (to 3.1) a new class in ft-management that enables some more
advance metric tracking for CXF endpoints and operations. The current
CounterRepository provides some very basic min/max/avg/count type metrics.
That’s useful, but more advanced information like stddevs and percen
Yeah, I incline to leave it out of scope as well.
If there are no objections, I will update JMS documentation in this way.
Regards,
Andrei.
> -Original Message-
> From: Christian Schneider
> Sent: Freitag, 26. September 2014 17:43
> To: Andrei Shakirin; dev@cxf.apache.org
> Subject: Re: c
It seems that configuration option for (1: ClientId) is already in place.
Client or service can register a feature containing properties to be overriding.
This feature will retrieve Conduit or Destination from client or sever and
replace configured properties in JMSConfiguration of Conduit or Dest
By the way, I took the "java_first_spring_support" coming in the samples
folder of my apache-cxf-2.7.12 installation and the only thing I did was
adding Thread.dumpStack() in the Web Service plus create a
weblogic-application.xml file etc as stated here:
http://cxf.apache.org/docs/application-serv
I don't have any jaxws-api jar.
api's that I see are:
cxf-services-ws-discovery-api-2.7.12.jar
cxf-services-wsn-api-2.7.12.jar
javax.ws.rs-api-2.0-m10.jar
slf4j-api-1.7.7.jar
stax2-api-3.1.4.jar
this weblogic configuration is being a total nightmare
--
View this message in context:
http://
Do you have a jaxws-api jar in your war/ear? If so, try removing it (and
pretty much all the other api jars) and use the version provided by the
jre/weblogic. That may help.
That said, not sure why it’s still trying to create the
weblogic.wsee.jaxws.spi.WLSProvider thing.
Dan
On Sep 26
Hi
Daniel, I tried what you said, this is declaring an endpoint in my
cxf-servlet.xml. I added the following lines:
And now, when I deploy in WebLogic 12c I am getting this error:
java.lang.ClassCastException: weblogic.wsee.jaxws.spi.WLSProvider cannot be
cast to javax.xml.ws.sp
Thanks Krzysztof
I tried but still not working
--
View this message in context:
http://cxf.547215.n5.nabble.com/Why-Apache-CXF-not-being-used-in-WebLogic-12c-tp5749219p5749273.html
Sent from the cxf-dev mailing list archive at Nabble.com.
