Studio - Debugging Errors

Design-Time Errors

The most common design-time errors are:

• Unmapped Tasks
• Malformed XSL Elements

XSL syntax is based on XML, which means that it must be "well-formed" to conform to basic XML rules:

• Every opening tag must have a matching closing tag
• Elements may nest but may not overlap
• There must be exactly one root element
• Attribute values must be closed in quotation marks (")
• Elements may not have two attributes with the same name
• Comments and processing instructions may not appear inside tags
• No unescaped "special" characters may appear inside tag or attribute contents
  • & should be coded as &
  • < should be coded as &lt;
  • > should be coded as &gt;
  • " should be coded as &quot;
  • ' should be coded as &apos;

Even if XSL is well-formed, there may be other mistakes that result in errors or bad output.

• Element names are case-sensitive, so any references must match

Design-time errors related to invalid XSL will result in errors when trying to run teh Solution. For example, a missing quotation mark from an attribute will generate the following error: 2006-06-07 12:14:31.390 [ERROR] /// `Error loading solution. (From file: 'C:\ActiveLink_4.1.0\data\solutions\lookup-key.xcs'.)` com.activecore.al.common.exceptions.AlRuntimeException: com.activecore.al.common.exceptions.AlException: org.xml.sax.SAXParseException: Element type "xsl:key" must be followed by either attribute specifications, ">" or "/>".

Run-Time Errors

Stylesheet Errors

Template Errors

Alert Settings

Information Logging

Warning Logging and Alerts

Error Logging and Alerts

Debug Logging