XML Interface Toolkit - Revision history

KNO: Text replacement - "{{UBIKSTUDIO" to "{{UBIK Studio"

2015-05-08T10:09:34Z

Text replacement - "{{UBIKSTUDIO" to "{{UBIK Studio"

2015-02-02T16:28:19Z

2014-02-14T15:27:13Z

‎Log level

2014-02-14T15:10:05Z

‎Log level

2014-02-14T14:46:12Z

‎Parameters

2014-02-14T13:07:29Z

‎Parameters

2014-02-11T19:32:13Z

‎Encoding

2014-02-11T19:31:50Z

‎Encoding

2014-02-11T19:31:41Z

‎Encoding

2014-02-11T19:31:27Z

@@ Line 12: / Line 12: @@
 == Parameters ==
-The general parameters, marked by Import/Export, are equivalents of the settings used by {{UBIKSTUDIO}} to connect to a database, please refer to its [[UBIK_Studio_Basics#Settings|settings section]] for a detailed description.
+The general parameters, marked by Import/Export, are equivalents of the settings used by {{UBIK Studio}} to connect to a database, please refer to its [[UBIK_Studio_Basics#Settings|settings section]] for a detailed description.
 The parameter ''DataView'' is used only for export purposes and defines the name of a {{UBIK}} [[view]] object. In an export process the XML toolkit

@@ Line 326: / Line 326: @@
 * [[XML Interface Toolkit (Example)]]
-[[Category:UBIK Studio]]
+[[Category:XML]]
-[[Category:Interfacing]]

@@ Line 57: / Line 57: @@
 ! Log level !! Label !! Description
 |-
-| -1 || System || Name of the SQL Server (DataSource)
+| -1 || SYSTEM || Name of the SQL Server (DataSource)
 |-
 | 0 || ERROR || Runtime errors or unexpected conditions

@@ Line 55: / Line 55: @@
 {| class="wikitable" | width = "88%"
 |-
-! Log level !! Description
+! Log level !! Label !! Description
 |-
-| -1 || Name of the SQL Server (DataSource)
+| -1 || System || Name of the SQL Server (DataSource)
 |-
-| 0 || Name of the SQL Server (DataSource)
+| 0 || ERROR || Runtime errors or unexpected conditions
 |-
-| 10 || Name of the SQL Server (DataSource)
+| 10 || WARNING || Almost errors, runtime situations that are undesirable or unexpected
 |-
-| 20 || Name of the SQL Server (DataSource)
+| 20 || INFO || Interesting runtime events (startup/shutdown)
 |-
-| 25 || Name of the SQL Server (DataSource)
+| 25 || DETAIL || Similar to INFO, but more detailed information
 |-
-| 30 || Name of the SQL Server (DataSource)
+| 30 || DEBUG || Detailed information on system relevant conditions
 |-
-| 40|| Name of the SQL Server (DataSource)
+| 40|| TRACE || Everything is logged
 |-
 |}

@@ Line 50: / Line 50: @@
 |-
 | LogLevel || Import/Export|| Optional: defines a certain log level
 |-
 |}

@@ Line 48: / Line 48: @@
 |-
 | LogFile || Import/Export|| Optional: defines a certain log file name; it not set the system will create an arbitrary one
 |-
 |}

@@ Line 297: / Line 297: @@
 ==== Encoding ====
-The XML data file must use the correct encoding, for example UTF-8!
+The XML files must use the correct encoding, for example UTF-8!
 == See also ==

@@ Line 1: / Line 1: @@
 The XML interface toolkit provides mechanisms to import and export data in XML format. Arbitrary structured XML data is mapped to according {{UBIK}} objects and its properties by a mapping specified in a separate mapping configuration file. Both files have to be specified in the interface command file additional to the [[Interface_Manager#Configuration|default parameters]].
 == Workflow ==
@@ Line 296: / Line 295: @@
 ==== UseHierarchy ====
 Be aware of the different usage of the '''UseHierarchy''' attribute in import / export processes. In an export the system will try load all objects related to the current exported object via the given relations / refernces. To skip the current view parent enable UseHierarchy, this exports all related objects except the view parent. If relational information should not be exported do not include a relation element in this section at all. Nevertheless, certain hierarchical information will always be exported due to the view hierarchy.
 == See also ==