> The scanning doesn't have anything to do with the location of the JSP files.
> It is entirely based on the set of package locators and exclude packages. It
> uses the classpath scanning mechanism that simply opens all the JAR files
> and looks at them. It only loads a class into the JVM if it is in a
> correctly named package that is not excluded.
No, what I meant is, if you have your templates under root, like in
rest-showcase and you add:
@ResultPath("/")
then it will scan the whole classpath(unless like you said, the
package locators are modified), which can cause some trouble.
musachy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
