Ah..A formality really. Though I don't really want to be an ognl commiter. Nothing is for sure though. Maybe my patches / code will suck. who knows..
On 1/3/07, andyhot <[EMAIL PROTECTED]> wrote:
Jesse Kuhnert wrote: > No, just what I have on my local hard drive. I'm all done with it now > but need to do some code cleanup/etc tomorrow before showing anyone > else and playing... heh... I figured you had something going on... as soon as i replied, i went at http://www.opensymphony.com/ognl/members.action to see if they also got you listed as a member :) They don't !!! > > It supports all of the same things ognl already does with 0 overhead. > (it's all compiled with javassist bytecode > enhancements...well...mostly all. I didn't have the stomach for some > things like projects / etc. Maybe later ) It'll be faster than any > other expression library out there. :) > > On 1/3/07, andyhot <[EMAIL PROTECTED]> wrote: >> Jesse Kuhnert wrote: >> > I don't mind (not that that matters ;) ) , but there are some other >> > things going on in the ognl world that would probably render tap-prop >> > obsolete... >> >> hmm... wasn't aware of that... any links? >> > >> > So , if you think it should be done to support more expression >> > languages in general then so be it, but if it's strictly for tap prop >> > it may not be worth the effort. >> > >> > On 1/2/07, andyhot <[EMAIL PROTECTED]> wrote: >> >> Howard M. Lewis Ship (JIRA) wrote: >> >> > [ >> >> >> http://issues.apache.org/jira/browse/TAPESTRY-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461781 >> >> >> ] >> >> > >> >> > Howard M. Lewis Ship commented on TAPESTRY-1153: >> >> > ------------------------------------------------ >> >> > >> >> > A simple fix would be to use "ognl:" explicitly inside the >> >> ExceptionDisplay component. >> >> > >> >> >> >> Yes, but this would really ignore the issue... >> >> >> >> On the other hand, going over the .page files and making them >> tap-prop >> >> friendly >> >> is a good idea. Expressions that can be handled by tap-prop should be >> >> left with no >> >> prefix, while those incompatible with it should be prefix by ognl. >> >> >> >> Anyone minds me going over our current components and making sure >> they >> >> comply with >> >> the above statement ? >> >> >> >> >> >> >> >> -- >> >> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr >> >> Tapestry / Tacos developer >> >> Open Source / J2EE Consulting >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> >> >> -- >> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr >> Tapestry / Tacos developer >> Open Source / J2EE Consulting >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
