[ 
https://issues.apache.org/jira/browse/CXF-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779934#comment-13779934
 ] 

Sambit Dikshit commented on CXF-5108:
-------------------------------------

[~sergey_beryozkin] Is this fixed already in 2.7.7.
                
> parameter beans feature not working through dynamic proxy based clients for 
> JAXRS
> ---------------------------------------------------------------------------------
>
>                 Key: CXF-5108
>                 URL: https://issues.apache.org/jira/browse/CXF-5108
>             Project: CXF
>          Issue Type: Bug
>          Components: Core, JAX-RS
>    Affects Versions: 2.7.3, 2.7.5
>            Reporter: Sambit Dikshit
>            Assignee: Sergey Beryozkin
>             Fix For: 2.7.6, 3.0.0
>
>
> 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 fine.  
> 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: http://www.atlassian.com/software/jira

Reply via email to