Hi,
the problem stems from the fact that you're using SFSExtension's method
addEventHandler. If you check the docs it states that it works with one listener per event only. Thus by adding multiple handlers you're effectively overwriting the previous one.
There's a way around this, but it takes a little refactoring.
Take a look at this example:
Code: Select all
public class MultiReadyTestExtension extends SFSExtension
{
@Override
public void init()
{
trace("Init Success!");
addEventListener(SFSEventType.SERVER_READY, new Listener1());
addEventListener(SFSEventType.SERVER_READY, new Listener2());
}
}
And relative listeners:
Code: Select all
import com.smartfoxserver.v2.core.ISFSEvent;
import com.smartfoxserver.v2.core.ISFSEventListener;
import com.smartfoxserver.v2.exceptions.SFSException;
public class Listener1 implements ISFSEventListener
{
@Override
public void handleServerEvent(ISFSEvent event) throws SFSException
{
System.out.println("---> Listener 1 Ready event");
}
}
public class Listener2 implements ISFSEventListener
{
@Override
public void handleServerEvent(ISFSEvent event) throws SFSException
{
System.out.println("---> Listener 2 Ready event");
}
}This is basically invoking the SFSExtension parent class. The SFSExtension essentially extends the parent's mechanism by keeping track of all listeners and auto-removing them on Extension destroy(). However it does not support multiple listeners for the same event, so if you need the multi-listener approach you need to use the code above and manage your listeners manually. Meaning that your Extension's
destroy() method will need to look like this:
Code: Select all
@Override
public void destroy()
{
// This removes all event handlers added via addEventHandler()
super.destroy();
// Here we manually remove the listeners addede via the parent's addEventListener
removeEventListener(...);
...
...
}
Hope it helps
