cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Reopened] (CXF-5108) parameter beans feature not working through dynamic proxy based clients for JAXRS
Date Tue, 09 Jul 2013 10:21:48 GMT


Sergey Beryozkin reopened CXF-5108:

I think we should just ignore Map on the client side, as the proxy won't know how to serialize
a map like this one into URI
> parameter beans feature not working through dynamic proxy based clients for JAXRS
> ---------------------------------------------------------------------------------
>                 Key: CXF-5108
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Core, JAX-RS
>    Affects Versions: 2.7.3, 2.7.5
>            Reporter: Sambit Dikshit
>            Assignee: Sergey Beryozkin
> We have a resource method declared as below. 
> @Path("/books")
> @Produces({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
> Book searchBook(@QueryParam("") Book book) throws ServiceException;
> Here the query param can be any combination of property of the book bean which are searchable.

> When we construct the URL with appropriate query string and use the web client, it works
> But it does not work when some one is using the proxy based approach where the client
get hold of the interface for e.g BookStoreResourceI and try to get call the searchBook(Book
b) method on that resource interface.  
> When debug found that, the client side conversion for cases like @QueryParam("")
> @PathParam(""), @MatrixParam("")  are missing and its being implemented in the JAXRSInvoker.invoke
operation just before invoking the resource API/method. 
> We need to have this feature of conversion from these parameter types to actual URL so
that irrespective of which type of client is consuming your service, it will work. Otherwise
it will become a half baked client consumption model. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message