XMPP Connection Server for FCM (Upgrade from Smack 3.x to 4.x)

This is an upgrade of my last FCM XMPP Connection Server application. Now, this project uses the latest version at this time of the Smack library (4.1.8). If you had some problems check my troubleshooting section!

The new version has introduced new terminology, deprecated some older methods and enriched the library in general. The problem started when there is a no working example out there using the new version to build a XMPP CCS for FCM. In summary, the API changes from the 3.x to the 4.x version are:

1. XMPPConnection is now an interface. Use either AbstractXMPPConnection or one of its subclasses (XMPPTCPConnection).
2. XMPPConnection.addPacketListener is deprecated: use either addAsyncPacketListener or addSyncPacketListener.
3. Packet became a deprecated interface. Use the new Stanza class.
4. The Packet Extension term is now Extension Element.

For more information you must read the following documentation:

• The upgrade guide
• New Smack Terminology
• The Smack Javadoc

##New Smack libraries

• Smack java 7
• Smack tcp
• Smack extensions

##How to start the server Just because it is the same project as my prior solution, the way to start the server is exactly the same. You can read my how to start the server.

##Troubleshooting This is a simple java code. You can integrate with just spring or spring in a container (Tomcat for example). In any case you need to take into account 3 issues:

1. If using a simple java application, keep the application alive listening messages. This problem occurs when you use a simple java code as a daemon in linux (that's why I put the while true workaround).

2. If using a java server (with spring boot at least), close the XMPP connection when the server goes down. This problem occurs when even if you shutdown the server the XMPP connection is still open and handling incoming messages. I do not know yet if this is a spring boot problem. The thing is like we are wrapping the XMPP CCS Server into a HTTP interface just to treat it as a normal server. My workaround was putting the disconnection in the spring preDestroy. @PreDestroy public void springPreDestroy() { //ccsConnection.disconnect(); }

3. Reconnection when connection draining. The reconnection should be handled to connect again to the FCM using the same parameters with a backoff strategy. Smack can handle the automatic reconnection if you enable it but if the connection will be closed from the FCM side you should call your reconnection method when FCM sends connection draining control message or connection draining error message.

##About me I am Carlos Becerra - MSc. Softwware & Systems. You can contact me via:

• Google+
• Twitter

##Thanks To tell the truth. I was really worried looking for the right solution. Finally, I made a list of useful links (apart from the above documentation links).

• gcm server
• stanza
• a problem
• other gcm server

Any improvement or comment about the project is always welcome! As well as others shared their code publicly I want to share mine! Thanks!

##License

Copyright 2016 Carlos Becerra

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.