Certain error and warning messages are sent to the IDE Problems view.
- Problems view messages
- Application server console messages
Problems view messages
The errors in the Problems view include any builder error or any syntax and other errors in your Java code (for example, in the Method builder). By default, the Problems view is included in the IBM® WebSphere® Portlet Factory perspective. If it is not visible, click Window
-> Show View
For each problem logged in the Problems view, an icon in the first column indicates the severity of the problem.
indicates an error. Examples of errors are invalid values for builder call inputs and Java coding errors.
indicates a warning.
The following information is displayed in the other Problems view columns.
Text to describe the problem. If the text is too long to fit in the column, right-click on the problem entry in the Problems view and click Properties to read the entire description. Resource
Name of the model in which the problem occurred.Path
Full path of the model directory.Location
Name and type of builder in which the error occurred. If this column is blank, the problem is generic to the model. For example, syntax errors in Java code.Type
IDE component that logged the error (for example, WebSphere Portlet Factory)
If the problem occurred in a specific builder call, clicking on the Problems entry opens that builder call in the builder call editor. To get more information on the error, right-click the error in the Problems view and click Properties
If the error occurred during model generation, clicking the Problems entry opens a Generation Errors
dialog that gives an explanation of what caused the generation error. When this type of error occurs, no builder is opened in the builder call editor.
Application server console messages
Some error messages during model execution get written to the application server console (command) window. You can check the application server command window for any System.out.println()
statements that you include in any of your methods.
Parent topic: Enabling debug tracing