Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-8383

cxf support for vertx destination

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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)?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              dufoli olivier dufour

              Dates

              • Created:
                Updated:

                Issue deployment