Musachy Barroso wrote:
The plugin will scan the entire classpath, but that's not to large of an
issue and pretty fast (considering). The issue is when it starts loading
classes into the perm space to determine if the class is in fact an Action
or not. This is the part where your perm space can become full and then you
start getting strange errors.
It is not only about memory, but also dependencies. If you place the
JSPs on the root, and make the plugin scan the classpath you will
likely get a bunch of ClassNotFoundException(s)
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.
If you have a good set of locators that sufficiently excludes most
packages you won't ever run into issues. And if you do, the exclude
packages protect against other types of issues. There might still be
some tricky issues if your classes have interesting load time
dependencies, but then it is an issue with your classes and not the
surrounding 3rd party classes.
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
