cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tobias Schöneberg (JIRA) <j...@apache.org>
Subject [jira] [Updated] (CXF-6810) Oneway with jms-transport not working
Date Tue, 01 Mar 2016 08:05:18 GMT

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

Tobias Schöneberg updated CXF-6810:
-----------------------------------
    Description: 
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

  was:
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 plan 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 "OnewayReques" 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


> Oneway with jms-transport not working
> -------------------------------------
>
>                 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
>         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