|
List Info
Thread: RE: Groovy or El expressions?
|
|
| RE: Groovy or El expressions? |

|
2007-10-19 13:22:58 |
|
Zied,
You will want to look at creating an ExpressionFactory instead of an ELResolver. ELResolvers are products of the client of the expression syntax, where I believe your desire is to implement groovy expression syntax.
Even a general ExpressionFactory wrapper over the SE 6 Script API would be pretty advantageous for everyone involved such that rhino (jscript), groovy, etc could be included.
Good luck, sounds exciting!
Jacob
| | Hi all,
Thinking I've found a great idea for a small open source project as soon as I'll finish with the currnent product I'm writing: an adapter to use Groovy instead of (in some conf file) el expressions. I took a look at the web and I see that the general movance is already in that sense:
I'm know to JSF (6 months) But I know in the 1.2, El resolvers have been externalized so it's easy to imagine we adapt a Groovy resolver in that place. Seen what el does, I think theresn't a lot to do to have all interfaces implemented with the Groovy counterpart.
Does anyone know if there's currently a project in that sens?
I think facelets is a great candidate to support Groovy natively (or to define an entry point to scripts in general): that way it'd have both view (data) templating (as it already has) but also function templating (if I can say it like this). In fact this could resolve a lot of issues like 'why can't we pass a method as a prameter' and so on...
Any votes? ;-p
|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe facelets.dev.java.net
For additional commands, e-mail: users-help facelets.dev.java.net
|
| Re: Groovy or El expressions? |

|
2007-10-20 15:30:06 |
|
Hi all,
Sorry I've labeled my facelets mails (in gmail) and forgot to look in labels instead of the inbox: I didn't see your answers till now.
Matthias:
> I was thinking about extending the MyFaces ManagedBean facility to > have support for groovy files as backing beans
It sounds good, but I thought more about the issues we have to call methods dynamically even under facelets, there are complex workarounds to be able to call a method dynamically and it's even more complex to have parameters (
http://blogs.nuxeo.com/sections/blogs/anahide_tchertchian/2007_09_04_how-to-invoke-method-expressions-with-parameters-in-jsf
). I thougth: facelets is very good in templating, it shouldn9;t focus on El expressions, it should delegate that to a specialized product, even if facelets wants to have it own mecanism, this one will unavoidably be separated as a stand alone project as soon as it'll grow. We can have analogy with Keith's economy theorics where two states will both win more money if everyone focuses on the business he does the best (and they exchange the products), even if one of the states is better in both businesses than the other (he should leave the product that the other does more efficiently, and focus on the other). I don't say that facelets is better than Groovy nor the opposite but I say it's better for both to focus each on what they do the best.
Jacob:
> You will want to look at creating an ExpressionFactory instead of an ELResolver
You don't even know how I'd like to do this project, but I must earn money to eat too  . Today I'm trying to develop a commercial product, if it works (and I hope it'll work after all this time spent on it), I'll have time to do what I like, I preferred to share the idea so it can be used by someone in a better position than me to catch it. Thanks for the precision, I expected the responsible object it couldn';t contain 'El9; if it is there to adapt another technology but I didn't know which name it has. So I said EL Resolver hoping I'll be understood . So thanks for correcting me : you made the idea clearer by using the correct vocablary
Regards,
Zied
2007/10/19, jacob hookom.net">jacob hookom.net < jacob hookom.net">jacob hookom.net>:
Zied, You will want to look at creating an ExpressionFactory instead of an ELResolver. ELResolvers are products of the client of the expression syntax, where I believe your desire is to implement groovy expression syntax.
Even a general ExpressionFactory wrapper over the SE 6 Script API would be pretty advantageous for everyone involved such that rhino (jscript), groovy, etc could be included.
Good luck, sounds exciting!
Jacob
| |
Hi all,
Thinking I've found a great idea for a small open source project as soon as I'll finish with the currnent product I'm writing: an adapter to use Groovy instead of (in some conf file) el expressions. I took a look at the web and I see that the general movance is already in that sense:
I'm know to JSF (6 months) But I know in the 1.2, El resolvers have been externalized so it's easy to imagine we adapt a Groovy resolver in that place. Seen what el does, I think theresn9;t a lot to do to have all interfaces implemented with the Groovy counterpart.
Does anyone know if there's currently a project in that sens?
I think facelets is a great candidate to support Groovy natively (or to define an entry point to scripts in general): that way it'd have both view (data) templating (as it already has) but also function templating (if I can say it like this). In fact this could resolve a lot of issues like 'why can't we pass a method as a prameter39; and so on...
Any votes? ;-p
| --------------------------------------------------------------------- To unsubscribe, e-mail:
facelets.dev.java.net" target="_blank">users-unsubscribe facelets.dev.java.net For additional commands, e-mail: facelets.dev.java.net" target="_blank">
users-help facelets.dev.java.net
-- Zied Hamdi zatreex.sourceforge.net
|
[1-2]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|