commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark R. Diggory" <>
Subject Re: [jelly] "Implement" taglib
Date Thu, 10 Mar 2005 22:53:27 GMT
There was some talk back when I started playing around with the 
taglibrary that using bcel for something like this should be actually 
placed back behind the Dynabean, so that we were making an 
implementation of DynaBean that was BCEL based. Maybe this somewhat 
applies to this case of JDK Proxies as well. Maybe a Proxy based 
DynaBean Implementation could be created too.

A solution like this might be more attractive to the Jelly developers 
for inclusion into the taglibraries, because then they would be just 
extensions of DynaBean. This would make such implementation/extending 
capabilities available where ever DynaBean is used.

I havn't had an opportunity to take it that far yet, but I'd like to 
attempt it sometime.

Eric Galluzzo wrote:

>On Thu, 2005-03-10 at 14:20, Mark R. Diggory wrote:
>>Hmm, I hadn't heard of JDK 1.3 Proxies before this point. This does 
>>sound very interesting to me, although I'm not a Jelly Commiter. I'd 
>>like to know more about it. I implemented my own sort of extensibility 
>>for some of my tags using BSF/BCEL. I'd be interested in knowing more on 
>>how you approached your solution.
>Here's a snippet of how you might use the "implement" tag library.  Note
>that you can only implement interfaces, not extend existing classes.
><impl:implement class="bar">
>	<impl:method name="test2">
>		<impl:parameter name="arg0" type="java.lang.String"/>
>		<impl:parameter name="arg1" type="int"/>
>		<impl:body>
>			<!-- Insert actual Jelly code here. -->
>			<impl:return value="${arg0 + arg1}"/>
>		</impl:body>
>	</impl:method>
>The difference, it would seem, between your BCEL taglib and my proxy
>taglib is that:
>        * yours can extend classes as well as implement interfaces
>        * mine uses regular Jelly tags to implement the method, whereas
>          yours uses BSF
>So it sounds like they're both useful. :)
>	- Eric
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message