Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-9783

Allow ConnectionConfiguration to be be injected to endpoint during connection creation

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

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.15.1
    • 2.18.0
    • camel-xmpp
    • None
    • Unknown

    Description

      I was playing around with camel-xmpp and Google Cloud Messaging. I was able to connect to GCM servers using the sample codes in Google's website but was not able to connect when using the camel-xmpp component.

      I did some reading and discovered that the ConnectionConfiguration in GCM's sample has some configurations:

      config.setSocketFactory(SSLSocketFactory.getDefault());
      config.setSecurityMode(SecurityMode.disabled);
      config.setReconnectionAllowed(true);
      config.setRosterLoadedAtLogin(false);
      config.setSendPresence(false);

      However in camel-xmpp the configuration cannot be injected:

      if (connection == null) {
      if (port > 0) {
      if (getServiceName() == null)

      { connection = new XMPPTCPConnection(ConnectionConfiguration(host, port)); }

      else

      { connection = new XMPPTCPConnection(new ConnectionConfiguration(host, port, serviceName)); }

      } else

      { connection = new XMPPTCPConnection(host); }

      }

      I am thinking if we could make the endpoint to allow Smack's ConnectionConfiguration to be injected before the connection creation.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davsclaus Claus Ibsen
            allancth Allan Cheong Tyng Huei
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment