One of the most common problems is parse exceptions. These are thrown by the parser when it is constructing a tree component from a String. They indicate that the String is not a valid expression according to the grammar defined. Here is an example of such an exception:

com.djinnsoft.jade.sitetree.treebuilder.ParseException: Encountered "b.rs/sitetree/test.jsp" at line 3, column 9.
Was expecting:
  <NAME> ...

    at com.djinnsoft.jade.sitetree.treebuilder.Builder.generateParseException(Builder.java:460)
    at com.djinnsoft.jade.sitetree.treebuilder.Builder.jj_consume_token(Builder.java:399)
    at com.djinnsoft.jade.sitetree.treebuilder.Builder.location(Builder.java:290)
    at com.djinnsoft.jade.sitetree.treebuilder.Builder.component(Builder.java:131)
    at com.djinnsoft.jade.sitetree.treebuilder.Builder.BuildArray(Builder.java:48)
    ...

This exception was created by removing the white space between the "b.rs" and "/sitetree/test.jsp" tokens in the example application.

The only solution in such a case is to examine the String you are passing in and compare it to the grammar definition provided. Remember that the location of the error (in this case 'line 3, column 9') is relative to the beginning of the string that you pass in.

A 404 error usually means that your Sitetree URLs and the deployment parameters into the servlet container are not aligned. One of the following may be the problem:

1. Requests are not being passed from the web server to the servlet container.
2. Requests are not being directed to the RootServlet when they arrive at the container. This is because the servlet mapping in the deployment file is incorrect or the Sitetree URLs are not using the proper extensions.
3. Requests are not being forwarded to the required resource. This is because the servlet mapping in the deployment file is incorrect (for the resource extensions this time) or the Sitetree resource URLs are not using the proper extensions.