cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-6810) JAX-RS Client one way requests do not work with jms-transport
Date Tue, 01 Mar 2016 12:05:18 GMT

     [ https://issues.apache.org/jira/browse/CXF-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin updated CXF-6810:
----------------------------------
    Priority: Minor  (was: Major)
     Summary: JAX-RS Client one way requests do not work with jms-transport  (was: Oneway
with jms-transport not working)

Thanks for experimenting, I've updated the JIRA description a bit. 
Originally, only the server JAX-RS code could receive JMS requests - the idea was simply to
let people reuse the same code in multi-transport servers. Next there was a contribution made
to make the client code work with JMS, mainly with Camel CXFRS I believe. 
So now we have WebClient and proxies being able to use HTTP Api to send the messages over
JMS which is unusual :-).
I've had a single one way test so far and there JMS API is used, never tried to do one way
JMS with WebClient. That said, the fix is trivial    

> JAX-RS Client one way requests do not work with jms-transport
> -------------------------------------------------------------
>
>                 Key: CXF-6810
>                 URL: https://issues.apache.org/jira/browse/CXF-6810
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.4, 3.1.5, 3.0.8
>            Reporter: Tobias Schöneberg
>            Priority: Minor
>         Attachments: cxf-jms-oneway-issue.zip
>
>
> I'm trying to call a jax-rs service interface in a one-way fashion, using jms transport.

> I think this should work because of this documentation: http://cxf.apache.org/docs/jax-rs-advanced-features.html#JAX-RSAdvancedFeatures-Onewayinvocations
> There, i read that both the Oneway annotation and the "OnewayRequest" client header play
a role. 
> However, I didn't get it to work. 
> I'm attaching junit tests where i basically iterate through these threee variables:
>  * header "OnewayRequest" set/not set
>  * calling a method anotated/not annotated with "Oneway"
>  * calling a method returning Result vs. calling a void method
> => i.e. 8 individual tests
> From those scenarios, only the two ones with "OnewayRequest not set" that call a not-annotated
method work as i would have expeced.
> Basically with "Oneway" i get a java.lang.NullPointerException at org.apache.cxf.jaxrs.client.AbstractClient.setResponseBuilder(AbstractClient.java:398)
> and with the header being set i eventually get a client timeout.
> So there might be two issues, or i'm getting something wrong with the config, but probably
there is something to fix here..
> Best regards, Tobias



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message