One of the minor things I was playing with was printing a standard "service version> STARTED" banner in log files when the SipXecsService-derived classes start. On the C++ side this is easy. On the Java side, it seems that the best way to get the compiled version is via the MANIFEST.MF from the jar file (I think this is how sipXconfig displays it on the screen). However, currently only sipXconfig.jar has the extra entries in its MANIFEST.MF:
Specification-Title: sipXconfig Specification-Version: 4.3.0 Specification-Vendor: SIPfoundry Implementation-Title: neoconf Implementation-Version: 4.3.0-018728 2010-04-28T15:13:27 cbeetonscs.com cbeeton Implementation-Vendor: SIPfoundry Questions: - does anyone care if the version is logged on startup, or if it is only logged for C++ services? - should the sipXecs jars all have the extra stuff in the MANIFEST.MF? Carolyn
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
