3 Replies Latest reply on Jun 27, 2008 5:03 PM by rg64

    CXF binding component guide

    Eric Johnson Newbie

      I've added a guide to using the CXF (Fuse Services Framework) binding component to the ESB docs. The guide does not yet cover using the WS-* features of the binding component.

      As always feedback is welcome.

        • 1. Re: CXF binding component guide
          rg64 Newbie

          Thanks much for the CXF-BC documentation. Four pieces of initial feedback.

           

          1. Section I.6.3 is incorrectly entitled "Consumer Configuration" when it should really be "Provider Configuration".

           

          2. Section I.6.4 entitled "Using the HTTP Transport in Decoupled Mode" discusses "Decoupled Mode" exclusively in the Consumer context. First, I would recommend renaming the section to "Using the Consumer HTTP Transport in Decoupled Mode". Second, I would like to see a section I.6.5 added entitled "Using the Provider HTTP Transport in Decoupled Mode". As far as I know, this is completely undocumented and potentially not even supported. I am very interested to know how to configure the CXF-BC Provider in "Decoupled Mode". In particular, I presume this mode would be automatically triggered when an asynchronous message exchange is sent from the NMR to the CXF-BC Provider. Is this correct?

           

          3. The CXF-BC Provider documentation should mention the need to explicitly specify an operation on the incoming messageExchange if the desired portType has more than one operation.

           

          4. The documentation should describe how to configure SSL for both the Provider and Consumer.

           

          Thanks again.

           

          - Ron

          • 2. Re: CXF binding component guide
            Eric Johnson Newbie

            Thanks for the feedback.

             

            I'm fixing the typo on the section heading ASAP.

             

            In reference to the decoupled HTTP endpoints... CXF(Service Framework) HTTP provider endpoints only require that they are configured to use WS-Addressing to support decoupled use cases. When they receive a message with a non-anonymouns wsa:ReplyTo header the provider endpoint will do the right thing.

             

            I'll try to clarify that section of the doc.

             

            I'm also looking into the other two areas you mentioned. The updates will likely show up in early June.

            • 3. Re: CXF binding component guide
              rg64 Newbie

              Hi Eric,

               

              A few more feedback items on the CXF-BC Guide.

               

              1. The document does not currently do a good job distinguishing between consumers and providers in the CXF standalone and CXF-BC contexts. This is extremely confusing for JBI newcomers since a CXF standalone consumer/client is a CXF-BC provider and vice-versa. For example, chapters I.6 and I.7 discuss CXF standalone consumers and providers while chapters II.9, II.10, Appendix A and Appendix B discuss CXF-BC consumers and providers. When configuring buscfg for a CXF-BC provider endpoint, you use CXF standalone consumer terminology. The consumer/provider terminology should be clarified throughout the document.

               

              2. Appendix A is missing some attributes that are currently available, including the "timeout" attribute.

               

              3. Sections II.9 & II.10 should show at least one example of a fully-configured CXF-BC endpoint, including both an xbean.xml file and its referenced buscfg file. Maybe the buscfg file might show how to set the ReceiveTimeout attribute for example. If you could show both a JMS and an HTTP transport example, that would be great.

               

              Thanks,

               

              - Ron