You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2020/12/01 03:14:00 UTC
[jira] [Commented] (CXF-8383) cxf support for vertx destination
[ https://issues.apache.org/jira/browse/CXF-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241223#comment-17241223 ]
Andriy Redko commented on CXF-8383:
-----------------------------------
Hello [~dufoli] ,
The CXF destination design is not coupled with Java's Servlet spec but the HTTP destination implementations are (due to the fact that CXF implements JAX-WS, JAX-RS and primarily is deployed in servlet containers). The in-message in the CXF contains a lot of information (uri, query strings, input stream, headers, ...) along with request itself.
I am not sure at this point what is the best way to integrate with Vert.x transport but some inspiration you may find in Websocket implementation: org.apache.cxf.transport.websocket.jetty.WebSocketVirtualServletRequest / org.apache.cxf.transport.websocket.jetty.WebSocketVirtualServletResponse
Another, probably better example would be org.apache.cxf.transport.http.netty.server.NettyHttpDestination & related classes.
> 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)