Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Efxclipse/Runtime/Recipes"

(Logging)
(Logging)
Line 4: Line 4:
 
== Logging ==
 
== Logging ==
  
e(fx)clipse has it's own logging facade which allows to plug-in different log frameworks in the back. Currently available are:
+
e(fx)clipse has its own logging facade <code>org.eclipse.fx.core.log.Logger</code> which allows to plug-in different log frameworks.
  
* java.util.Logging (default)
+
Currently available are:
 +
 
 +
* <code>java.util.Logging</code> (default)
 
* log4j by adding <code>org.eclipse.fx.core.log4j</code>
 
* log4j by adding <code>org.eclipse.fx.core.log4j</code>
  
 
=== Usage ===
 
=== Usage ===
 +
 +
There are different ways to use get a logger.
 +
 +
==== Factory ====
 +
 +
<source lang="java">
 +
</source>
  
 
== DI ==
 
== DI ==

Revision as of 17:02, 6 December 2013

This page holds best practice recipes when writing JavaFX application using e(fx)clipse

Core

Logging

e(fx)clipse has its own logging facade org.eclipse.fx.core.log.Logger which allows to plug-in different log frameworks.

Currently available are:

  • java.util.Logging (default)
  • log4j by adding org.eclipse.fx.core.log4j

Usage

There are different ways to use get a logger.

Factory

 

DI

Back to the top