20 May 2011 05:30
Re: Mechanics of enhancing Joe-E taming database?
Adrian Mettler <amettler@...>
2011-05-20 03:30:13 GMT
2011-05-20 03:30:13 GMT
Hi Andy and e-lang. Sorry for taking so long to reply on this. It slipped off my radar. I've put a page on the Joe-E wiki regarding the taming database and how to customize it. Please email me if you have any suggestions for improving the documentation as it now stands. http://code.google.com/p/joe-e/wiki/Taming -Adrian To directly answer the questions given: > 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. > There is commented-out code in the verifier distribution to do this, but it's not super convenient. You can uncomment some lines in SafeJImport.java to select a desired package and recompile the plugin. > (2) Read a collection of .safej files, and write a Policy.java source file. > This is a user-accessible option in the plugin, a per-project preference option described in (4) below. > (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. > No. The Policy class is used only at runtime. > 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? > From the safej files. > (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? > There is code to read the safej files and output a version of Javadoc with the safej information. The output of this tool, as run on the distributed safej files is online at http://www.cs.berkeley.edu/~daw/joe-e/api/ The source code for this doesn't appear to be in the public repository, probably because it's based on Sun's code and thus couldn't be released under the same license as the rest of the Joe-E distribution. I should be able to get it for you, though, if you want it. > Thanks, > Andy Fingerhut > > > _______________________________________________ > e-lang mailing list > e-lang@... > http://www.eros-os.org/mailman/listinfo/e-lang