1 Apr 2011 21:00
Mechanics of enhancing Joe-E taming database?
If one wished to help enhance the Joe-E SafeJ database, what would the recommended mechanics be? That is, should I check out the Subversion repository for Joe-E, edit one or more .safej files in the safej directory, make a diff/patch, and email it to this email list? Or would some other method be preferable? Is there any documentation on the "flows" of this SafeJ information in the software developed so far? Below are some guesses I have, but if some details could be fleshed out, it would be greatly appreciated. I'd be happy to write out some documentation for this as I learn about how it works. I believe there is some software for each of the following things. Is this true, and if so, is there already a way to run such code from the command line? If not, is there already some Java code in the Joe-E subversion repository that can do it, and which source file(s) is it in? (1) Take a collection of Java source files, and from them generate one or more .safej files with default deny for every constructor, method, and field. (2) Read a collection of .safej files, and write a Policy.java source file. (3) Is this correct? Policy.java files can be compiled to .class files, then packaged in a .jar file, then used as a taming database in Eclipse. If so, I don't see anything in Policy.java source files that contain the comments from the .safej files. Where do the error messages reported within Eclipse's use of Joe-E come from, if not from a Policy.java file? (4) Some code that is invoked from Eclipse, when one enables the check box for "Automatically build Policy class" in the project's Joe-E properties, that writes a Policy.java file, starting from the taming database Joe-E is currently configured to use. (5) Is there anything else already developed missing from this list? Thanks,(Continue reading)
RSS Feed