[Moose-dev] Issue 895 in moose-technology: Lack of entities in verveineJ model

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.7 New issue 895 by andreho...(a)gmail.com: Lack of entities in verveineJ model http://code.google.com/p/moose-technology/issues/detail?id=895 I'm parsing the single .java attached file (I have also copied in the end of this message), and I have some points: - A stub class FileUtils is not created. As consequence the receiver os the static invocation "FileUtils.close(ti)" (see last line) is "nil". - A stub class ArchiveScanner (superclass) is not created. What do you think about that? In addition (I believe it is OK): - A stub class Map is created as FAMIXParameterizableClass (it should just be used to Generics, no?). - A 'V' FAMIXParameterType is created - A Comparable is created as FAMIXParameterizedType Maybe these three points are coming from the class Map in Java, then it is OK. Basically this is the code attached: ========= public class TarScanner extends ArchiveScanner { ... protected void fillMapsFromArchive(Resource src, String encoding, Map fileEntries, Map matchFileEntries, Map dirEntries, Map matchDirEntries) { TarEntry entry = null; TarInputStream ti = null; try { try { ti = new TarInputStream(src.getInputStream()); } catch (IOException ex) { throw new BuildException("problem opening " + srcFile, ex); } while ((entry = ti.getNextEntry()) != null) { Resource r = new TarResource(src, entry); String name = entry.getName(); if (entry.isDirectory()) { name = trimSeparator(name); dirEntries.put(name, r); if (match(name)) { matchDirEntries.put(name, r); } } else { fileEntries.put(name, r); if (match(name)) { matchFileEntries.put(name, r); } } } } catch (IOException ex) { throw new BuildException("problem reading " + srcFile, ex); } finally { FileUtils.close(ti); } } ... =========