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 the issue either way, an
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 the issue either way, and as far as I know
the AsyncResponse approach
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)
In the servlet container you may need to enable the async (via the
standard servlet param).
Cheers, Sergey
On 04/02/18 17:59, John D. Ament wrote:
Sergey,
I
Sergey,
I think you're mixing emails (the email on dev@ is unrelated).
On Sun, Feb 4, 2018 at 12:53 PM Sergey Beryozkin
wrote:
> That dependency you referred to should let you do:
>
> @Path("/")
> public class RestController {
>@GET
>@Produces(MediaType.APPLICATION_JSON)
>
That dependency you referred to should let you do:
@Path("/")
public class RestController {
@GET
@Produces(MediaType.APPLICATION_JSON)
public Flux doGet(@Suspended AsyncResponse asyncResponse) {
ClientBuilder.newClient()
.register(MyAppFeature.class
Why should be optional ?
Sergey
On 04/02/18 16:13, John D. Ament wrote:
I built a simple webapp (WAR file, deploying to Tomcat) that depends on the
CXF 3.2.2 libraries + Weld 3.0.2. I don't believe CDI has anything to do
with my problem though.
I registered a feature/server customizer that can
BTW, sample project can be found @
https://github.com/johnament/cxf-demo-reactive-cdi
On Sun, Feb 4, 2018 at 11:13 AM John D. Ament wrote:
> I built a simple webapp (WAR file, deploying to Tomcat) that depends on
> the CXF 3.2.2 libraries + Weld 3.0.2. I don't believe CDI has anything to
> do
