3 Replies Latest reply on Jan 17, 2011 3:56 PM by kcbabo

    Module java package naming

    mageshbk

      I raised this earlier in a call, but now it seem to be the right time to have a general opinion. Currently Bean component has it's package at

       

      org.switchyard.component.bean
      

       

      Whereas the SOAP/HTTP component's package is at

       

      org.switchyard.soap
      

       

      Wondering if we should maintain the component prefix evrywhere or to get rid of it. Please let me know your opinions.

        • 1. Module java package naming
          dward

          My opinion is to move it into the component prefix.  I want it to be clear that org.switchyard.* is API, org.switchyard.internal.* is runtime, and org.switchyard.component.* holds optional components.

          • 2. Module java package naming
            kcbabo

            Hey Magesh,

             

            Sorry for not replying earlier.  Forum notifications FAIL again.

             

            We should use org.switchyard.component as the base package for all components.  So SOAP gateway will be org.switchyard.component.soap, Bean component will be org.switchyard.component.bean, etc.

             

            thanks,

            keith

            • 3. Module java package naming
              kcbabo

              David Ward wrote:

               

              My opinion is to move it into the component prefix.  I want it to be clear that org.switchyard.* is API, org.switchyard.internal.* is runtime, and org.switchyard.component.* holds optional components.

               

              Yep, that's right.