[jira] [Updated] (CXF-8383) cxf support for vertx destination

["Andriy Redko (Jira)" <ji...@apache.org>]

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

Andriy Redko updated CXF-8383:
------------------------------
    Summary: cxf support for vertx destination  (was: cxf support for vertx detination)

> cxf support for vertx destination
> ---------------------------------
>
>                 Key: CXF-8383
>                 URL: https://issues.apache.org/jira/browse/CXF-8383
>             Project: CXF
>          Issue Type: New Feature
>          Components: Transports
>            Reporter: olivier dufour
>            Priority: Major
>             Fix For: 3.4.1
>
>
> Hello,
> I am working on cxf quarkus extension. And quarkus is migrating from servlet to vertx routing system.  Anyway, I try to make a custom detination/conduit but it seems that cxf have tight integration with servlet. I try to make my own invoke with 
> HttpServerRequest req, HttpServerResponse res, RoutingContext ctx
> instead of
> invoke(final ServletConfig config, final ServletContext context, final HttpServletRequest req,
>  final HttpServletResponse resp)
> but when I see that InMessage store servlet request and servlet response as attribute, I am affraid that this not doable. 
> So, Another solution is to do a wrapper httpServletRequest class which wrap the vertx httpserverrequest. 
>  
> Anyway, in term of architecture, why inMessage do not store body, uri, query param, ... instead of the servlet objects (request, context)?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)