I'm playing around with deployment strategies and one thing we want to do is use an obfuscator to shrink the deployed files down some and offer a modicrum of security.
However, both Turbine and Velocity are very dynamic in loading classes. In particular, Velocity seems to have some problems with an obfuscated app.
I've deliberatly excluded all the classes that are put into the Velocity context from obfuscation. I've confirmed they are not being altered in any way. But when Velocity tries to access them, it fails saying there isn't any reference available. The exact same thing with the entire app un-obfuscated works fine.
Is anyone aware of any special issues when obfuscating a Velocity app? What else, beside the classes you drop into the context, do you need to keep from being obfuscated to make Velocity happy when trying to resolve references?
Any pointers or thoughts would be appreciated. This isn't a big deal right now, but eventually I'll have to face it :-)
Thanks,
Gerry
-- Gerry Duprey ________________________________________ SchoolsOPEN, LLC 123 North Ashley, Suite 120 Ann Arbor, MI 48104 Phone (877) 483-1944 Ext. 401 Fax (734) 661-0819
Visit us Online at www.Schools-OPEN.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
