Message Facility is an internationalisation infrastructure for computer softwares developed in the Java™ Programming Language. It is far more than just making Java applications Internationalizable , but emphasises the ease of development of internationalizable Java applications. This includes the ease of coding, ease of translation and the most important — ease of collaboration between various authors (coders, translators and coordinators) of the final software application.
Even further, Message Facility provides ad hoc logging supports. Logging records can be easily made internationalizable in the same way of other parts.
Logging with Message Facility has several advantages:
- Each Messager can have its own XML file for logging configuration, and the format is universal.
In contrast, if based on other logging systems, the Logger s within an entire execution context (i.e. JVM or WebApp instance) will have to be configured through a single file.- A log record of Message Facility will not get constructed (formatted by the Messager) unless the configured LogLevel admits it. This minimizes the unwanted logging cost in production execution.
- All logging methods of Messager return
trueconstantly. So if you want extreme logging overheads avoidance, and accept restarts to enable certain log levels, you can prefix logging statements at those levels with theassertkeyword so that they will not even get loaded by JVM unless assertion is enabled.- The message patterns and messager configurations are loaded through Meta Facility , so entirely reloadable without shutting down the JVM.
This is an intuitive example, your first glance at Message Facility enabled Java programs.
The work done by Message Facility, and further localization support.
The benefits after going the Message Facility way.
