FUSE ESB
  1. FUSE ESB
  2. ESB-212

FUSE SMX4 as deployment platform for CXF

    Details

    • Type: Enhancement Enhancement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0.0.0-fuse
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Treating SMX4 as the deployment platform of choice for CXF.
      The cxf-cpi should be migrated to smx4, where each cxf demo (where applicable) is converted into a camel-cxf endpoint and deployed to smx4.

      This will
      1) validate Smx4 as the conatiner of choice
      2) provide functional tests for camel-cxf
      3) provide additional camel-cxf and cxf demos (ie: smx4 variants of existing cxf demos)

        Gliffy Diagrams

          Activity

          Hide
          Daniel Kulp added a comment -

          Umm... why would they be a camel-cxf endpoint? That seems strange.

          Why wouldn't it be a spring-dm module plugged into SMX4 as per gnodet's sample?

          Show
          Daniel Kulp added a comment - Umm... why would they be a camel-cxf endpoint? That seems strange. Why wouldn't it be a spring-dm module plugged into SMX4 as per gnodet's sample?
          Hide
          Gary Tully added a comment -

          sure, spring-dm, what ever works best. (at the time of jira creation camel-cxf was supposed to be the method of choice but in fairness i think there was alot of flux. gnodets example did not exist yet.)

          top priority is to validate smx4 as container of choice, if it is indeed the container of choice.

          Show
          Gary Tully added a comment - sure, spring-dm, what ever works best. (at the time of jira creation camel-cxf was supposed to be the method of choice but in fairness i think there was alot of flux. gnodets example did not exist yet.) top priority is to validate smx4 as container of choice, if it is indeed the container of choice.
          Hide
          Seumas Soltysik added a comment -

          This is exactly the kind of testing that needs to be done to validate SMX4 as the deployment environment of choice for CXF endpoints. I would agree with Dan that we should focus on deployment of endpoints using Spring DM. An ideal SMX/Fuse CPI would be to run all the CXF demos as Spring DMs in SMX. We made need some kind of Ant target to create the application bundles for these demo. In addition we may need to alter the CXF config a bit to add a jaxws:endpoint to existing config.

          Show
          Seumas Soltysik added a comment - This is exactly the kind of testing that needs to be done to validate SMX4 as the deployment environment of choice for CXF endpoints. I would agree with Dan that we should focus on deployment of endpoints using Spring DM. An ideal SMX/Fuse CPI would be to run all the CXF demos as Spring DMs in SMX. We made need some kind of Ant target to create the application bundles for these demo. In addition we may need to alter the CXF config a bit to add a jaxws:endpoint to existing config.

            People

            • Assignee:
              Unassigned
              Reporter:
              Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: