Re: [Stripes-users] Code obfuscation

2011-11-25 Thread Janne Jalkanen
Um... Why would you obfuscate a web app? If an attacker has enough access to your server to read your JAR files, you've already got way worse problems than having the user decompile your app... Anyway, Stripes uses Reflection quite heavily and depends on the method and field names to be the

Re: [Stripes-users] Code obfuscation

2011-11-25 Thread Sylvain Brejeon
@Janne Why would you obfuscate a web app? the web app will not be installed on our server but rather distributed to many companies. and we are in a beta/proof-of-concept/no-contract-yet phase where we need to release it to a few trusted partners and trusted beta-test customers and we would like

Re: [Stripes-users] Code obfuscation

2011-11-25 Thread Iwao AVE
You are right, the symptom doesn't fit...sorry. Another thought. Do you use @HandlesEvent annotation to declare event name explicitly? Because if you don't, obfuscation may change the event handler method name and it would break the event resolution. Regards, Iwao 2011/11/25 Sylvain Brejeon

Re: [Stripes-users] Code obfuscation

2011-11-25 Thread Janne Jalkanen
Make sure that your setters aren't mangled either, or your parameters won't be transmitted. /Janne On 25 Nov 2011, at 14:14, Sylvain Brejeon wrote: no need to be sorry mate. the two of you convinced me that it ought to be that the method names have changed. of course it can't be