The trace(…) method is a useful little tool to log any information in the log files for debugging your Extension code.<\/p>\n
It is available in the main Extension class and in every Request or Event handler. However, often times, developers need to log messages from other places in their code such as data classes, or any other object that doesn’t extend the Request\/Event base classes.<\/p>\n
How can we call trace(…) from somewhere else?<\/p>\n
1) Refer to the Extension main class.<\/strong><\/p>\n We can grab a reference to the Extension itself in the constructor of our class.<\/p>\n There is \u00a0probably one\u00a0small downsides with this approach:\u00a0there is a dependency on the zone name, which could be resolved by moving the string outside of the class as a static member of another class, which takes care of the constants in the game.<\/p>\n 2)\u00a0Inject the logger when constructing new objects.<\/strong><\/p>\n Instead of referencing the Extension we could pass the Extension’s underlying logger to all those objects that need to use it.<\/p>\n\r\npublic class SpaceShip\r\n{\r\n\tprivate SFSExtension ext;\r\n\tprivate float currentSpeed = 0;\r\n\r\n\tpublic SpaceShip()\r\n\t{\r\n\t\text = (SFSExtension) SmartFoxServer.getInstance().getZoneManager().getZoneByName("GameZone").getExtension();\r\n\t}\r\n\r\n\tpublic void setSpeed(float speed)\r\n\t{\r\n\t\tthis.currentSpeed = speed;\r\n\t\text.trace("Current speed is now: ", currentSpeed);\r\n\t}\r\n}\r\n<\/pre>\n\r\nimport org.slf4j.Logger;\r\n\r\npublic class SpaceShip\r\n{\r\n\tprivate final Logger logger\r\n\tprivate float currentSpeed = 0;\r\n\r\n\tpublic SpaceShip(Logger logger)\r\n\t{\r\n\t\tthis.logger = logger;\r\n\t}\r\n\r\n\tpublic void setSpeed(float speed)\r\n\t{\r\n\t\tthis.currentSpeed = speed;\r\n\t\tlogger.info("Current speed is now: " + currentSpeed);\r\n\t}\r\n}\r\n<\/pre>\n