[ http://jira.jboss.com/jira/browse/DNA-62?page=all ] Randall Hauch updated DNA-62: ----------------------------- Fix Version/s: 0.3 (was: 0.2) Pushing to 0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-62: ----------------------------- Fix Version/s: 1.0 (was: 0.5) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-62: ------------------------------- Attachment: DNA-62_draft.patch Added first (working) version of this sequencer. The sequencer calls a Reader implementation (a la the MS Office sequencer) that parses a class file into a metadata object. The metadata object is then passed to a (customizable) recorder object that creates the relevant graph entries. The patch integrates the sequencer with the getting started sequencers example to help verify that it works. The current version has extensive testing of the class file reader implementation, but very little testing of the default recorder (the object that converts the metadata into a series of graph nodes and properties). For the defect to be resolved properly, I think these things would need to happen (in no particular order): 1. Align the default output for the class sequencer and the Java sequencer so that they are as identical as possible. This will be very helpful for future analyzer writers. 2. Align the metadata objects between the class sequencer and the Java source sequencer. Both are parsing into objects with the same name. It seems like they could probably be moved to share a common interface and then reuse recorder implementations (solving issue 1). 3. Move the sequencer into the same package and namespace as the java sequencer. This is a nice to have, but the two sequencers are so tightly related that it makes a lot of sense (to me, anyway) 4. Clean up/add Javadoc, add more testing for the default recorder implementation, and update the reference guide for the new sequencer As always, any feedback is appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin.... ] Randall Hauch edited comment on DNA-62 at 12/27/09 12:31 PM: ------------------------------------------------------------- It'd be interesting to demonstrate how having multiple sequencers allows us to chain things together. For example, the ZIP file sequencer should create the nodes representing the contents of a ZIP (and JAR) file, which means we'd create nt:file nodes representing each .class file in the JAR file (or .java source file if a source JAR). The act of creating those file nodes should activate the Java classfile sequencer for .class files or the Java source sequencer for .java files. This way, we don't actually have to wire together the ZIP/JAR sequencer to invoke the Java source or classfile sequencer. was (Author: rhauch): It'd be interesting to demonstrate how having multiple sequencers allows us to chain things together. For example, the ZIP file sequencer should create the nodes representing the contents of a ZIP (and JAR) file, which means we'd create nt:file nodes representing each .class file in the JAR file (or .java source file if a source JAR). The act of creating those file nodes should activate the Java classfile sequencer for .class files or the Java source sequencer for .java files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-62: ------------------------------- Attachment: DNA-62_ref_guide.patch Attached a reference guide page for this sequencer. The page specifically lists the sequencer as a technology preview and nodes that the default output and associated CNDs are subject to change in future versions to better align with the Java sequencer. If no one objects, I'll check in all of the -62 changes to get them into SVN while Serge and I work out the details of the alignment. Any feedback is appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-62?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-62: ------------------------------- Attachment: DNA-62_sequenced_date.patch Added a sequenced date to the output -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira