@BeanParam with proxy client does not work

[glassfishrobot]

@BeanParam with proxy client does not work

It does not send through the @HeaderParam's in the request... and the SmsResponse from the proxy method call is null.

For example...

@Path( "/" )
public interface ZengMessagingService
{
    @GET
    @Path( "/sms" )
    @BeanParam
    SmsResponse sendSms( @BeanParam SmsRequest request );

}

public class SmsRequest
extends OneTimePasswordRequest
{
    @HeaderParam( "delivery-mode" )
    private int deliveryMode;

    @HeaderParam( "categ" )
    private String subscriptionCategory;

...

public class SmsResponse
extends OneTimePasswordResponse
{
    @HeaderParam( "provisioning-code" )
    private String provisioningCode;

...

Client client = ClientFactory.newClient();
WebTarget target = client.target( "http://localhost:" + port + "/" ); ZengMessagingService zengMessagingService = WebResourceFactory.newResource( ZengMessagingService.class, target );
SmsResponse smsResponse = zengMessagingService.sendSms( smsRequest );

Environment

Glassfish 4.0 b72

Affected Versions

[2.0-m11]

[glassfishrobot]

Reported by aaronjwhiteside

[glassfishrobot]

Was assigned to svavra

[glassfishrobot]

aaronjwhiteside said:
Probably related to #1926

[glassfishrobot]

aaronjwhiteside said:
Even if I change the sendSms() method from @get to @post in my example, it still does not pass through the @HeaderParam's in SmsRequest.

[glassfishrobot]

walec51 said:
@BeanParam support is simply not implemented yet in Jersey Proxy Client
https://github.com/jersey/jersey/blob/master/ext/proxy-client/src/main/java/org/glassfish/jersey/client/proxy/WebResourceFactory.java

generally Jersey Proxy Client seams pretty week compared to RESTEasy's Client framework and adding @BeanParam will require a big refactoring of that WebResourceFactory

[glassfishrobot]

svavra said:
Hi,
while it seems to be a valid issue, it is not critical to core functionality and we do not plan to dedicate resources to fixing the issue at the moment. In case you feel strongly about the issue, please consider contributing a fix by submitting a Github pull request.

Thanks!
Stepan

[glassfishrobot]

Marked as won't fix on Monday, January 11th 2016, 5:33:04 am

[glassfishrobot]

lucastsa said:
I implemented this functionality on pull request https://github.com/jersey/jersey/pull/235
Not really sure if it will get merged, but you can use it to build your jersey-proxy-client artifact.

[glassfishrobot]

This issue was imported from java.net JIRA JERSEY-1653