James Strachan wrote:
From: "James Strachan" <[EMAIL PROTECTED]>
OK I understand. So I'd say your choices are
* write your own tag library handling the mapping of tags -> beans and
properties however you wish with whatever code you wish.
* we could refactor BeanTagLibrary to make the things you don't want
optional (or move the reusable stuff to a base class etc). In particular
it'd be good if you could reuse UseBeanTag (from core) or BeanTag together
with BeanProperty tag.
* take a look at the betwixt tag library and see if thats more suitable to
your needs.
Just thought of another option...
* try make your beans Ant Tasks and use the Ant Jelly library
but I am trying to move *away* from Ant... I thought this was a common
use case and therefore would make sense to be provided by the base
framework. I think inheritance should be avoided, however.
James
-------
http://radio.weblogs.com/0112098/
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
