In EclipseIDE there was a bug[1] where the absolute classnames was used in click.xml even when the page packages was defined. The problem comes from XmlConfigService which automatically prefixes classnames with the package name to create the absolute class name. The Netbeans plugin has the same problem.
Our docs isn't very clear on this issue either, some snippets uses absolute classnames and others use relative classnames. This all makes me think that XmlConfigService should be enhanced slightly to load page classes in the following order: 1. prefix the page classname with the package and attempt to load it 2. if #1 fails use the classname "as is" and attempt to load it 3. if both #1 and #2 fails throw a RuntimeException with a message that neither classes were found on the classpath. Thoughts? Bob [1]: https://issues.apache.org/jira/browse/CLKE-39
