Re: Pretty Logging

Thanks. Do you actually mean to instantiate it: LoggingFeature logging = new LoggingFeature(); logging.setPrettyLogging(true); The github example is a Server - I want to do it in a client and print to log4j and console? So after the above two lines how do I write to console

Re: Pretty Logging

See CXF Message Logging docs at http://cxf.apache.org/docs/message-logging.html and https://github.com/apache/cxf/blob/master/rt/features/logging/src/main/java/org/apache/cxf/ext/logging/LoggingFeature.java You can simply instantiate the LoggingFeature class and set properties on it: logging =

Re: Remove obsolete RxJava code and keep RxJava2 only one

I was just about to remove the optional marking on reactive streams, and noticed that rxjava was still around. I guess it was decided to keep it? I'll point out, this now makes the dependency chain even harder to follow (since rxjava2 uses reactive streams, but rxjava does not). John On Wed,

Re: JAX-RS 2.1 SSE transport - SseTransportCustomizationExtension is not CDI autodiscoverable

Thanks for the quick response! I am in the process of creating an integration test for Meecrowave that demonstrates a successful configuration of this transport and I will note this future enhancement. Regards, Aaron On Monday, February 5, 2018 8:14 AM, John D. Ament

Re: JAX-RS 2.1 SSE transport - SseTransportCustomizationExtension is not CDI autodiscoverable

BTW you can find the open PR here: https://github.com/apache/cxf/pull/369 And to be clear, no, the class shouldn't have a CDI scope as we don't want a hard dependency on CDI in this module. John On Mon, Feb 5, 2018 at 9:12 AM John D. Ament wrote: > Hi Aaron, > > Yes,

Re: JAX-RS 2.1 SSE transport - SseTransportCustomizationExtension is not CDI autodiscoverable

Hi Aaron, Yes, already aware of this limitation. It's probably because the bean discovery mode is ignored in these JARs. Can you try adding it as a scanned JAR in meecrowave? For CXF 3.2.3 (didn't have enough time to finish in 3.2.2) the default discovery mechanism will move from being CDI to

JAX-RS 2.1 SSE transport - SseTransportCustomizationExtension is not CDI autodiscoverable

Hi All, I was able to successfully configure the CXF 3.2.1 SSE transport on Meecrowave (Tomcat 9/OpenWebBeans 2) but something that took me a long time to figure out was that the  SseTransportCustomizationExtension CDI class was not being auto-detected by CDI. This class has no CDI annotations

Re: relative path to WSDL in CXF

Yes, for example: https://github.com/apache/cxf/blob/master/systests/ws-security/src/test/resources/alice.properties Colm. On Sat, Feb 3, 2018 at 6:50 AM, Al Grant wrote: > Can the crypto properties file use relative paths. Instead of: > >

Pretty Logging

How do I enable pretty output of the XML to the console? All the examples on StackOverflow seem to use a XML configuration file, but everything I am doing is in code. -- Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html

Re: Reactive Services & CDI

Hi John On 04/02/18 19:19, John D. Ament wrote: On Sun, Feb 4, 2018 at 2:01 PM Sergey Beryozkin wrote: I thought I'd point to the utility of that module anyway (by the way, in the updated code below the AsyncResponse is also not needed) Yep, I know that. Was seeing