• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Protect code from reverse engineering

 
Bartender
Posts: 1357
39
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi to everybody,

i'd like to know your opinion about a potential issue I'm facing. I'm developing some applications - a large application - in which I have a classical Swing GUI (deployed via Java Web Start) which communicates with a remote Application Server. To pass data between application layers, my team has developed an extension of classical Value Object, of which we augmented semantic by adding a number of annotations.

These annotations contain some info I'd like not to make public, for examples details on how a single attribute is bounded to a field on the Gui or on a specific column of a certain database table. I'd like to use obfuscators, but 'cause the objects are really the "data" traversing our apps, and these instances are used by remote EJBs, I think that obfuscate ValueObjects (whit consequent renaming of attributes) can't be really the way to achive this purpose.

So, I'd like to get your suggestions on this issue. By the way, I'm wondering if this may be really a re-enginering problem:if all business logic resides on a remote and (unaccessible!) application Server, even with database schemas, tables, and views (without actual data), I don't think that a complete retro-engineering may be done
on our products. What happens, for example, with Entity in EJB 3.0 apps, when these are "exposed" via a AppClient ?

Thank you in advance.


 
Marshal
Posts: 79177
377
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please do a search of the fora; this topic comes up about once a month, I would say.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic