commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: [digester] proposal: plugins module
Date Wed, 23 Apr 2003 17:10:01 GMT
hi simon

sounds interesting but i don't think that the attachment made it through.

IIRC there will be certain legal formalities that have to be undertaken 
before this work would be included so it's probably best to repost the 
attachment (maybe zipping it first) or post it up on the web somewhere and 
mail the url.

i'd also like to encourage you to subscribe to the commons-dev list and 
post the offer there. (i know that the volume is large but once you set up 
mail filters to select the [digester] posts, it's not too bad.)

- robert

On Sunday, April 20, 2003, at 08:01 AM, Simon Kitching wrote:

> Hi,
> I've been working for a while now on a "plugins" module for Digester,
> which allows the *input* xml to specify concrete classes to instantiate
> at certain points.
> It's been in production at my workplace for over 6 months (and has gone
> through several architectural changes that time). So it is reasonably
> robust, and has proved useful to me at least.
> I would be happy to contribute this to the digester project if it is
> wanted; I also have permission from my employers to do so.
> Rather than describe its functionality here, I have attached the package
> documentation (package.html).
> However, here's a teaser from that doc:
> <test>
>   <!-- declare plugins -->
>   <plugin id="print" class=""/>
>   <plugin id="block" class=""/>
>   <plugin id="if" class=""
> ruleinfo="StmtIfRuleInfo"/>
>   <!-- tags which may reference plugins -->
>   <statement plugin-id="print" stmt-label="1">msg1</statement>
>   <statement plugin-id="block">
>     <statement plugin-id="print" stmt-label="2.1">msg2a</statement>
>     <statement plugin-id="print" stmt-label="2.1">msg2b</statement>
>   </statement>
> ....
> The code for this is completely separate from Digester (no patches to
> core digester code required to run it).
> However while developing this, I did identify a number of ways in which
> Digester could potentially be enhanced to make life easier for this
> module (and hopefully others). I will post that as a separate email.
> I am happy to post code if there is interest. Currently the code follows
> my coding style (which is not apache style) and of course has non-apache
> package names, etc. However it should be no big deal to convert that all
> over.
> If you are interested in incorporating this module into the digester, I
> suggest that it could become an "org.apache.commons.digester.plugins"
> package, like xmlrules has been incorporated. When not in use, there is
> no performance impact to Digester. In size, the binary code is 29Kb when
> jar'ed of which about 30% is test harness.
> Regards,
> Simon
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message