commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert McIntosh <rob...@bull-enterprises.com>
Subject Re: [jelly] "Implement" taglib
Date Mon, 10 Mar 2003 23:00:56 GMT
And here I thought you had come back to save us!

- Robert

Mark R. Diggory wrote:

> My appologies to all those people who thought I was actually writting 
> to them from 2 years in the future, somehow the date got set to 2005 
> on my workstation.  ;-)
>
> -Mark
>
> Mark R. Diggory wrote:
>
>> 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.
>> -Mark
>>
>>
>> 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>
>>> </impl:implement>
>>>
>>> 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: commons-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>>
>>>  
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message