the basic design outlined below should be simple and quick to implement. please feel free to jump in with questions, comments or improvements.
i was wondering whether this output stuff would be a better match for the util module than the main jSieve library opinions? - robert On Thu, Dec 4, 2008 at 9:26 PM, Robert Burrell Donkin (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/JSIEVE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653491#action_12653491 > ] > > Robert Burrell Donkin commented on JSIEVE-43: > --------------------------------------------- > > Had a little think about design. Would like to be flexible enough to support > various output pipelines: should be able to write out a Sieve script or xml. > > Implementing SieveParserVisitor seems like the best place to start. This > visitor is designed to perform it's own tree recursion which suits well. > > The classic first stage of the pipeline is to turn the tree recursion into a > linear series of start and end events. For flexibility, these should be node > based. This will end up a rather large API with each start and end calls for > each concrete node type. > > This would probably be enough to plugin custom output to strings including > basic XML rendering. More stages in the pipeline would be required for more > sophisticated such as XML pipelining. > > On balance should be very do-able. > >> Add API for generating a Sieve script from a parse tree >> -------------------------------------------------------- >> >> Key: JSIEVE-43 >> URL: https://issues.apache.org/jira/browse/JSIEVE-43 >> Project: JAMES jSieve >> Issue Type: New Feature >> Affects Versions: 0.2, 0.3, 1.0 >> Reporter: Boris Burtin >> >> There's currently no way to generate a Sieve script from a jSieve Node tree. >> This would be very helpful for cases where you need to parse a script, >> modify some nodes, and then generate a new script that incorporates the >> changes. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
