Hey,
I'm having a strange problem. In some environments, a resource EL expression in
a CSS file produces a path like "/javax.faces.resource/.." but on others it
produces "...gif.xhtml..".
I have 2 url paths configured for the FacesServlet "*.xhtml" and
"/ja
Dear all,
I am experiencing a strange behaviour with a composite component.
It seems to me that attributes values specified as el expressions are
computed only once, and very early, when the composite component
declaration specifies a componentType.
I published an example on
Hi
I have checked the problem and what you need to do is implement your
properties into your component class using StateHelper methods,
otherwise the properties will not be saved and restored.
Take a look at:
On 14/06/2012 12:40, Leonardo Uribe wrote:
Hi
I have checked the problem and what you need to do is implement your
properties into your component class using StateHelper methods,
otherwise the properties will not be saved and restored.
Take a look at:
expression can be retrieved
by attribute.getValue().
- new Metadata - within applyMetadata method, we put the EL expression on
the attributes of the UIComponent.
Then, you have always access to the expression string by looking at the
attributes of the component.
I have tested the approach with Myfaces
I generated a basic application from the maven archetype and deployed it to
tomcat 6. Although the Trinidad tags are evaluated, the EL expression in the
input text box is not evaluated. What am I missing?
Thanks,
Richard
Sent from my iPhone
it to
tomcat 6. Although the Trinidad tags are evaluated, the EL expression in the
input text box is not evaluated. What am I missing?
Thanks,
Richard
Sent from my iPhone
, at 1:25 AM, Richard Yee richard.k@gmail.com wrote:
I generated a basic application from the maven archetype and deployed it to
tomcat 6. Although the Trinidad tags are evaluated, the EL expression in the
input text box is not evaluated. What am I missing?
Thanks,
Richard
Sent from
archetype and deployed it
to tomcat 6. Although the Trinidad tags are evaluated, the EL expression in
the input text box is not evaluated. What am I missing?
Thanks,
Richard
Sent from my iPhone
, the EL expression in
the input text box is not evaluated. What am I missing?
Thanks,
Richard
Sent from my iPhone
moment to get the EL
expression.
regards,
Leonardo
2011/2/7 Rudy De Busscher rdebussc...@gmail.com
Hi all,
For an ExtVal-addon I need to have access to the expression string of the
actionListener property of a command button.
So when i have
*h:commandButton id=check value=Validate
a custom ComponentTagHandlerDelegate with a
special rule for ActionSource. I think it is the right moment to get the EL
expression.
regards,
Leonardo
2011/2/7 Rudy De Busscher rdebussc...@gmail.com
Hi all,
For an ExtVal-addon I need to have access to the expression string of the
actionListener
Hi all,
For an ExtVal-addon I need to have access to the expression string of the
actionListener property of a command button.
So when i have
*h:commandButton id=check value=Validate
actionListener=#{personBean.someActionListener}/*
I need #{personBean.someActionListener}.
In JSF 1.X, you could
]
Gesendet: Mi 10.02.2010 06:14
An: MyFaces Discussion
Betreff: el expression
Hi all
Can any one can help me how to pass a parameter to a method while
calling it in EL expression.
Im trying this
#{myBean.method('JAVA')}
But I m getting errors while rendering.
Thanks
Krishna Pandit
This email
/aboutJava/communityprocess/mrel/jsr245/index.html
--- Michael Kurz michi.k...@gmx.at schrieb am Mi, 10.2.2010:
Von: Michael Kurz michi.k...@gmx.at
Betreff: Re: el expression
An: users@myfaces.apache.org
Datum: Mittwoch, 10. Februar 2010, 9:33
Hi,
it is true that it is not possible to use method
: el expression
Hi all
Can any one can help me how to pass a parameter to a method while
calling it in EL expression.
Im trying this
#{myBean.method('JAVA')}
But I m getting errors while rendering.
Thanks
Krishna Pandit
This email and any files transmitted with it are confidential and intended
Thanks I am trying. :)
-Original Message-
From: Martin Monshausen [mailto:martin.monshau...@prodyna.de]
Sent: 10 February 2010 15:08
To: MyFaces Discussion
Subject: AW: el expression
Hi,
there are some further tricks which you can use to pass parameters:
http://wiki.apache.org/myfaces
done:
http://wiki.apache.org/myfaces/Parameters_In_EL_Functions
http://wiki.apache.org/myfaces/HowToEnableEl22
LieGrue,
strub
--- Matthias Wessendorf mat...@apache.org schrieb am Mi, 10.2.2010:
Von: Matthias Wessendorf mat...@apache.org
Betreff: Re: el expression
An: MyFaces Discussion users
Hello
I need to pass a param in plain html, but the el expression is not parsed.
How can I make it work!
..
tr:panelFormLayout
applet code=MyApplet.class archive=MyApplet.jar width=500
height=400
param name=paramName value=#{myBackingBean.paramName}/
/applet
/tr:panelFormLayout
/10 baeschtu baeschtu baesc...@gmail.com
Hello
I need to pass a param in plain html, but the el expression is not parsed.
How can I make it work!
..
tr:panelFormLayout
applet code=MyApplet.class archive=MyApplet.jar width=500
height=400
param name=paramName value
]
Sent: 10 February 2010 05:47
To: MyFaces Discussion
Subject: el expression in plain html
Hello
I need to pass a param in plain html, but the el expression is not
parsed.
How can I make it work!
..
tr:panelFormLayout
applet code=MyApplet.class archive=MyApplet.jar width=500
height=400
() of Bean named
myBackingBean then you can use this #{myBackingBean.paramName}.
If need any other thing please elaborate.
Thanks
Krishna Pandit
-Original Message-
From: baeschtu baeschtu [mailto:baesc...@gmail.com]
Sent: 10 February 2010 05:47
To: MyFaces Discussion
Subject: el expression
Hi all
Can any one can help me how to pass a parameter to a method while
calling it in EL expression.
Im trying this
#{myBean.method('JAVA')}
But I m getting errors while rendering.
Thanks
Krishna Pandit
This email and any files transmitted with it are confidential and intended
solely
for the child component is:
tr:inputText value=#{foo.bar}/
So far I have:
CoreInputText childComponent;
childComponent = (CoreInputText)
application.createComponent(CoreInputText.COMPONENT_TYPE);
// Set the value to an EL Expression
childComponent.setValue(#{foo.bar}); // Does
.
The equivalent tag for the child component is:
tr:inputText value=#{foo.bar}/
So far I have:
CoreInputText childComponent;
childComponent = (CoreInputText)
application.createComponent(CoreInputText.COMPONENT_TYPE);
// Set the value to an EL Expression
childComponent.setValue
childComponent;
childComponent = (CoreInputText)
application.createComponent(CoreInputText.COMPONENT_TYPE);
// Set the value to an EL Expression
childComponent.setValue(#{foo.bar}); // Does not work
ValueBinding vb = application.createValueBinding(elExpression);
vb.setValue(context, value
)
application.createComponent(CoreInputText.COMPONENT_TYPE);
// Set the value to an EL Expression
childComponent.setValue(#{foo.bar}); // Does not work
ValueBinding vb = application.createValueBinding(elExpression);
vb.setValue(context, value);
Will work, but iirc, this is deprecated, and there is an alternate
;
childComponent = (CoreInputText)
application.createComponent(CoreInputText.COMPONENT_TYPE);
// Set the value to an EL Expression
childComponent.setValue(#{foo.bar}); // Does not work
ValueBinding vb = application.createValueBinding(elExpression);
vb.setValue(context, value);
Will work, but iirc
the EL-expression.
The NPE occurs at
org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty(PropertyKey key)
final public Object getProperty(PropertyKey key)
{
Object o = getLocalProperty(key);
if (o != null)
return o;
// Look for a binding if and only if the key
be defined either inline with a static,
constant value, or with a JSF EL expression that is re-evaluated on each
request.
/quote
As you could see (marked with ) each property should accept EL-expressions.
Also the code implies that EL-binding is supported:
if (key.getSupportsBinding
with a static,
constant value, or with a JSF EL expression that is re-evaluated on
each request.
/quote
As you could see (marked with ) each property should accept
EL-expressions.
Also the code implies that EL-binding is supported:
if (key.getSupportsBinding())
{
... // EL
)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Additional debugging reveilled that FacesContext is null while evaluating
the EL-expression.
The NPE occurs at
org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty
simple XML structure that relies on the JSF
expression language (EL) for flexibility.
Each configurable property can be defined either inline with a
static, constant value, or with a JSF EL expression that is
re-evaluated on each request.
/quote
regards,
Martin
expression language (EL) for flexibility.
Each configurable property can be defined either inline with a
static, constant value, or with a JSF EL expression that is
re-evaluated on each request.
/quote
regards,
Martin
--
Matthias Wessendorf
further stuff:
blog: http
Hey Matthias -
On Jan 30, 2008 3:13 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
perhaps the doc is just wrong :-)
I believe you are correct - ie. the doc is not accurate. Looking at
RequestContextBean.java, it seems that the following properties cannot
be EL-bound:
-
Hey Andy,
I believe you are correct - ie. the doc is not accurate. Looking at
RequestContextBean.java, it seems that the following properties cannot
be EL-bound:
...
I think we should mark this as not-bindable and
update the doc accordingly.
However, I do not buy Matthias argument that
Oh, well - this fix sounds really simple then.
regards,
Martin
On Thu, Jan 31, 2008 at 12:38 AM, Andy Schwartz [EMAIL PROTECTED]
wrote:
On Jan 30, 2008 5:45 PM, Martin Marinschek [EMAIL PROTECTED]
wrote:
However, I do not buy Matthias argument that this is due to security
reasons
- if
On Jan 30, 2008 5:45 PM, Martin Marinschek [EMAIL PROTECTED] wrote:
However, I do not buy Matthias argument that this is due to security reasons
- if some intruder gets access to managed-beans, we are hosed anyways. I
think, from a perspective servicing the user, it would be a good thing if
the security was just a (wild) guess.
I see that the uploaded-file-processor is not designed to have EL.
The UPLOADED_FILE_PROCESSOR_KEY field in RequestContextBean class
does that by:
static public final PropertyKey UPLOADED_FILE_PROCESSOR_KEY =
TYPE.registerKey(uploaded-file-processor,
)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Additional debugging reveilled that FacesContext is null while evaluating the
EL-expression.
The NPE occurs at
org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty
)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
--
View this message in context:
http://www.nabble.com/null-EL-expression---%22ELResolver-cannot-handle-a-null
I am currently migrating our ADF project to Trinidad 1.2.1 and have a
question about the f:attribute. In our project we were using el expressions
for the name value in our f:attribute. This does not seem to be the same
for the Trinidad 1.2.1 /MyFaces 1.2/Facelets 1.1.6 combo. If I use a el
)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
--
View this message in context:
http://www.nabble.com/null-EL-expression---%22ELResolver-cannot-handle
So how do I make it work in MyFaces under Jetty? Why doesn't the
presence of commons-el or Jetty or whatever cause the RI to blow up?
On 7/18/07, Bruno Aranda [EMAIL PROTECTED] wrote:
Ah yes, actually the problem was not commons-el (which is necessary
for tomahawk to work) but a bug in jetty
Sorry for reviving a 2 week old thread, but I haven't had a chance to
try this again.
I've added the exclusions you have below and I'm still getting the
same error on Jetty. jetty:run-exploded shows that commons-el isn't
in WEB-INF/lib
If I try the war in Tomcat 6 I get NoClassDefFoundError:
Ah yes, actually the problem was not commons-el (which is necessary
for tomahawk to work) but a bug in jetty which I think it has already
been addressed.
Cheers,
Bruno
On 18/07/07, noah [EMAIL PROTECTED] wrote:
Sorry for reviving a 2 week old thread, but I haven't had a chance to
try this
are you talking about this one
h:outputText value=#{nullValue} /
?
I don't see it (in JSP)
On 7/18/07, Bruno Aranda [EMAIL PROTECTED] wrote:
Ah yes, actually the problem was not commons-el (which is necessary
for tomahawk to work) but a bug in jetty which I think it has already
been
I can confirm this issue. Could you add it to JIRA please?
Cheers,
Bruno
On 28/06/07, noah [EMAIL PROTECTED] wrote:
With the 1.2.0-SNAPSHOT for today
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
html
head
though it seems to be a problem with jetty having a dependency on
commons-el 1.0 ?
Bruno
On 05/07/07, Bruno Aranda [EMAIL PROTECTED] wrote:
I can confirm this issue. Could you add it to JIRA please?
Cheers,
Bruno
On 28/06/07, noah [EMAIL PROTECTED] wrote:
With the 1.2.0-SNAPSHOT for today
I cannot reproduce this in the current12/test-webapp, so I guess it is
a configuration issue whith the EL dependencies,
Bruno
On 05/07/07, Bruno Aranda [EMAIL PROTECTED] wrote:
though it seems to be a problem with jetty having a dependency on
commons-el 1.0 ?
Bruno
On 05/07/07, Bruno Aranda
Ok, found the problem. The issue is with tomahawk, that depends on
commons-el. Be sure that you don't have this dependency (commons-el)
in the classpath. If using maven, do this for tomahawk and the
sandbox:
dependency
groupIdorg.apache.myfaces.tomahawk/groupId
With the 1.2.0-SNAPSHOT for today
%@ taglib uri=http://java.sun.com/jsf/html; prefix=h %
%@ taglib uri=http://java.sun.com/jsf/core; prefix=f %
html
head
titleNull Test/title
/head
body
f:view
h:outputText value=#{nullValue} /
@myfaces.apache.org
Enviado: lunes, 28 de mayo, 2007 19:19:50
Asunto: Re: DataScroller - Rendering/Pagination problem when rendered attribute
is set to a conditional EL expression
This rendered stuff has even more problems:
Using:
rendered=#{not empty @managed-bean-name.users}
at my t:dataTable, does result
change the page - you are bound to page 1.
Deleting the rendered EL expression - paginator works again, but is
there all the time.
Should be a bug, shouldn't it?
Torsten
smime.p7s
Description: S/MIME cryptographic signature
shows 2 pages.
But you can't change the page - you are bound to page 1.
Deleting the rendered EL expression - paginator works again, but is
there all the time.
Should be a bug, shouldn't it?
Torsten
smime.p7s
Description: S/MIME cryptographic signature
Hi,
As I start my web I got such an error:
com.sun.facelets.tag.TagAttributeException: /jsp/content/myJSF.xhtml @58,59
value=#{myBean.accountNr EL Expression Unbalanced: ... #{myBean.accountNr
WHat does it mean?
Thanks
Thomas
-
Jetzt Mails
Sorry, I take my email back. I find where is the error in my code.
Thomas Chang [EMAIL PROTECTED] schrieb: Hi,
As I start my web I got such an error:
com.sun.facelets.tag.TagAttributeException: /jsp/content/myJSF.xhtml @58,59
value=#{myBean.accountNr EL Expression Unbalanced
Expression Unbalanced:
Hi,
As I start my web I got such an error:
com.sun.facelets.tag.TagAttributeException: /jsp/content/myJSF.xhtml @58,59
value=#{myBean.accountNr EL Expression Unbalanced: ... #{myBean.accountNr
WHat does it mean?
Thanks
Thomas
10:11 AM
To: MyFaces Discussion
Subject: Question about EL Expression Unbalanced:
Hi,
As I start my web I got such an error:
com.sun.facelets.tag.TagAttributeException: /jsp/content/myJSF.xhtml @58,59
value=#{myBean.accountNr EL Expression Unbalanced: ... #{myBean.accountNr
WHat does it mean
Hi all:
why f:attribute not support el expression?
thanks any response.
best regarts
--
View this message in context:
http://www.nabble.com/why-f%3Aattribute-not-support-el-expression--tf2619233.html#a7309664
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Using jsp for the views, i want to prefix some path, for example this:
link rel=stylesheet href=h:outputText
value=#{facesContext.externalContext.requestContextPath}//html/style/mystyle.css
/
The bad about that is, that i have to take a component, where an el
expression should be enough
this:
link rel=stylesheet href=h:outputText
value=#{facesContext.externalContext.requestContextPath}//html/style/mystyle.css
/
The bad about that is, that i have to take a component, where an el
expression should be enough, shouldnt it?
Is it possible to habe:
link rel=stylesheet
href
Hi Torsten,
you can't use jsf el expression outside jsf tag attributes!
link ... is not an jsf tag.
but this shoud work inside jsp:
link rel=stylesheet
href=%= request.getContextPath() + /html/style/mystyle.css% /
regards,
Volker
2006/10/11, Torsten Krah [EMAIL PROTECTED]:
http://mail
Title: Message
Hi,
I have to display
weekday name (Sunday, Monday etc.), given weekday number which isavailable
inbean.
Please help me how
to write EL _expression_ to get the weekday name from resource
bundle.
Any pointers in this
regard are also highly appreciated.
Thanks,
Kiran
The
Title: Message
If Weekday is an java 5 enumeration (the approach should be almost
the same if you just have an int) I have just created a converter
class.
that implements javax.faces.convert.Converter and
something like org.springframework.context.MessageSourceAware(MessageSource is a
Hi,
I need to test the existance of a element before to show it's value
I would like something like h:outputText value=if
#{row.productFamily}!= null #{row.productFamily.text} /
how to do it
regards
Try rendered attribute:
h:outputText value=#{row.productFamily.text}
rendered=#{row.productFamily != null}/
-Original Message-
From: Alexandre Jaquet [mailto:[EMAIL PROTECTED]
Sent: Montag, 14. August 2006 11:24
To: MyFaces Discussion
Subject: JSF and EL expression
Hi,
I need to test
h:outputText value=#{row.productFamily.text}
rendered=#{row.productFamily != null} /
Alexandre Jaquet wrote:
Hi,
I need to test the existance of a element before to show it's value
I would like something like h:outputText value=if
#{row.productFamily}!= null #{row.productFamily.text} /
h:outputText value=if #{ row.productFamily!= null ?
row.productFamily.text : \\ /
or
h:outputText value=#{row.productFamily.text}
rendered=#{row.productFamily != null}/
Hi,
I need to test the existance of a element before to show it's value
I would like something like h:outputText
=#{row.productFamily != null}/
-Original Message-
From: Alexandre Jaquet [mailto:[EMAIL PROTECTED]
Sent: Montag, 14. August 2006 11:24
To: MyFaces Discussion
Subject: JSF and EL expression
Hi,
I need to test the existance of a element before to show it's value
I would like something like
Then fristly you need to make sure that row.productFamily exists at all
Alexandre Jaquet wrote:
Hi,
I still get exception : Cannot get value for expression
'#{(row.productFamily == null)? row.productFamily.text : 'null-case'}'
regards
Bruno Aranda wrote:
Just use this:
h:outputText
71 matches
Mail list logo
