Dennis Byrne wrote:
Are you under the impression that EL functions cannot accept
parameters?
Just again to this point of the discussion:
I tried myself to write a function that would return the size of a
java.util.List passed as parameter. However, it works fine with JSTL
(core),
There's no way to force someone to use a tool the correct way.
However, I think EL is a good example of how to force someone to use
the tool incorrectly.
Instead of a simple
#{backingBean.viewMethod(viewDependentVariable[s])}, you now have to
perform horrible convolutions and tricks to accomplish
-
From: alex [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 21, 2005 10:26 AM
To: MyFaces Discussion
Subject: Re: Replacing JSF EL with JavaScript
Dennis Byrne wrote:
Are you under the impression that EL functions cannot accept
parameters?
Just again to this point of the discussion:
I tried
On 7/21/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
The point was that you can't use JSTL functions in JSF method bindings.
Actually, you can. It's just difficult to do with the Myfaces EL
resolver. You have to hardcode the association.
You can also do so if you're using myfaces + facelets
Never mind.
You said method bindings, not value bindings.
On 7/21/05, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 7/21/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
The point was that you can't use JSTL functions in JSF method bindings.
Actually, you can. It's just difficult to do with
Craig,
It sounds like your saying the spec
aims at discouraging certain bad practices of the past. During the
spec's childhood were there ever any arguments about it encouraging
new bad practices. I ask this because I have found myself wanting
to abuse FacesContext.getCurrentInstance() as a
On 7/21/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Craig,
It sounds like your saying the spec aims at discouraging certain bad
practices of the past. During the spec's childhood were there ever any
arguments about it encouraging new bad practices. I ask this because I have
found
Hi.
Instead, IMHO, the expression language should encourage you to
manipulate server side model data with model tier techniques ... it
was designed to serve as a *binding* between the tiers, rather than as
a general purpose computational technology. If we had wanted that, we
would likely have
Aleksei Valikov wrote:
Hi.
Instead, IMHO, the expression language should encourage you to
manipulate server side model data with model tier techniques ... it
was designed to serve as a *binding* between the tiers, rather than as
a general purpose computational technology. If we had wanted
Hi.
Well, probably I'm missing something.
Here's a simple example. I have a documentDao with the possibility to
load document and give back the document list. I want to display a
table, where rows correspond to the documents returned by the dao. In
every row, I'd like to have a Load button
Aleksei Valikov wrote:
I don't think that simple EL helps the simplicity of application.
I agree with you, I stumbled upon several cases in my last few apps
where I cursed the EL for what it was, and spent hours to program
workarounds for simple things like you mentioned.
I think the force
Can this be satisfied w/ a static method call. If so, try
mapping one to a EL function.
Original message
Date: Tue, 19 Jul 2005 09:49:05 +0200
From: Aleksei Valikov [EMAIL PROTECTED]
Subject: Re: Replacing JSF EL with JavaScript
To: MyFaces Discussion users@myfaces.apache.org
Hi
Hi.
Can this be satisfied w/ a static method call. If so, try
mapping one to a EL function.
Of course not. The action must be executed within a certain context (for
instance, with a Spring-configured DAO), with a certain parameter (for
instance, current row object). No way this could be
Are you under the impression that EL functions cannot accept
parameters?
Original message
Date: Tue, 19 Jul 2005 18:23:29 +0200
From: Aleksei Valikov [EMAIL PROTECTED]
Subject: Re: Replacing JSF EL with JavaScript
To: MyFaces Discussion users@myfaces.apache.org
Hi.
Can
You wanna say, that an EL-function call can accept a parameter? How that?
Give me an example pls.
Rgds
Alex
Dennis Byrne wrote:
Are you under the impression that EL functions cannot accept
parameters?
Hi.
Are you under the impression that EL functions cannot accept
parameters?
I am. At least when uspecified as method bindings. There are exceptions
like action listeners which receive events as arguments, but I have
found no way to implement something like:
x:dataTable ... var=document
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html
Look at the bottom.
The JSF expression language does not accept parameters for functions,
you are right. The new specification for the JSP and JSF common
expression language might have a possibility to do that, though.
There are workarounds for this: implement the map interface. Provide
as a key the parameter you
Hi.
The JSF expression language does not accept parameters for functions,
you are right. The new specification for the JSP and JSF common
expression language might have a possibility to do that, though.
There are workarounds for this: implement the map interface. Provide
as a key the parameter
Hi.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html
Look at the bottom.
1. This does not work in method bindings.
2. This is a call to static function. Implementing do(A a, B b)
statically for every A.do(B b) is hardly to be called convenient.
So far I have not seen a better
On 7/19/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
Hi.
Instead, IMHO, the expression language should encourage you to
manipulate server side model data with model tier techniques ... it
was designed to serve as a *binding* between the tiers, rather than as
a general purpose
Aleksei,
On 7/19/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
Hi.
Instead, IMHO, the expression language should encourage you to
manipulate server side model data with model tier techniques ... it
was designed to serve as a *binding* between the tiers, rather than as
a general purpose
Hi.
What would be the easiest way to implement this with standard EL,
without JS?
Let's assume...
[skip]
Thank you, your answer is the most complete of all I've seen in the
thread. I only miss one fragment:
When the commandLink is clicked for a particular row in the table, the
current
On 7/19/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
Hi.
What would be the easiest way to implement this with standard EL,
without JS?
Let's assume...
[skip]
Thank you, your answer is the most complete of all I've seen in the
thread. I only miss one fragment:
When the
Aleksei,
On 7/19/05, Aleksei Valikov [EMAIL PROTECTED] wrote:
Hi.
What would be the easiest way to implement this with standard EL,
without JS?
Let's assume...
[skip]
Thank you, your answer is the most complete of all I've seen in the
thread. I only miss one fragment:
Glad to
Hi.
For me, EL-like languages always missed some functionality. Calling
methods with parameters or simply doing things above average were
always a pain.
As an experiment, I've tried to replace JSF EL (like
#{mybean.myAccessor}) with JavaScript. At least to achieve the
possibility to
Without commenting one way or the other on whether the MyFaces folks
might like the proposed technology (that's up to them), I would like
to point out one important factor -- the expression language in JSTL
(and JSF) omits method calls *deliberately*.
One of the most common negative feedbacks
27 matches
Mail list logo
