The Shale Tiger library uses annotations to declare meta-data that in some
cases would have been configured using a central XML configuration file.
Shale gathers the annotation data at the startup of the application by loading
the classes. Some have expressed concern that loading the classes
Hi!
Try out the current support by setting context init parameter
org.apache.shale.tiger.SCAN_PACKAGES. The value is a comma delimited
list
of individual JAR filenames (shale-tiger.jar) and package prefixes (
org.apache.shale.foo).
As far as I remember I just implemented the package prefix
From: Mario Ivankovits [EMAIL PROTECTED]
Hi!
Try out the current support by setting context init parameter
org.apache.shale.tiger.SCAN_PACKAGES. The value is a comma delimited
list
of individual JAR filenames (shale-tiger.jar) and package prefixes (
org.apache.shale.foo).
As
On 12/12/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Mario Ivankovits [EMAIL PROTECTED]
Hi!
Try out the current support by setting context init parameter
org.apache.shale.tiger.SCAN_PACKAGES. The value is a comma delimited
list
of individual JAR filenames (shale-tiger.jar) and