Right, Seam2 uses JSF 1.2 features and JBoss EL to give a *much* better
implementation of the EL extensions.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064295#4064295
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4
You can't use extended EL in value bindings in Seam 1.2.1.GA (you can in Seam2)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064220#4064220
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064220
___
I have been unable to use it in a outputText tag. For example:
|
|
This give me the same exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064131#4064131
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=406
I believe I remember that el-enhancements don't work in richfaces dataTable.
(I've never gotten it to work in any case). Did you try it using a standard
dataTable?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064118#4064118
Reply to the post :
http://ww
I am getting this error as well with Seam 1.2.1GA.
seam-gen seems to put the SaemFaceletViewHandler in the web.xml:
| ...
|
| org.ajax4jsf.VIEW_HANDLERS
|
| org.jboss.seam.ui.facelet.SeamFaceletViewHandler
|
|
| ...
|
However, I am still getting the
"ebu" wrote : looks like that ajax4jsf's view handler specified in web xml
takes precedence
I don't know the answer to your question, but just for your information: when
using seam-gen then SeamFaceletViewHandler is commented-out (with a reference
to Ajax4JSF) in the generated faces-config.xml,
looks like that ajax4jsf's view handler specified in web xml takes precedence:
|
| org.ajax4jsf.VIEW_HANDLERS
|
org.jboss.seam.ui.facelet.SeamFaceletViewHandler
|
|
but even when seam handler is specified in faces-config only it's constructor
is being called, so the object is
If the action is parameterized, you can pass parameters to it.The biggest
gotcha to be aware of is that the expression is evaluated when the action is
invoked, which means local page state is not available. If you are trying to
select one entity out of a list, then you are better off with
Yeah... Thanks Gavin.. Stupid me ;-P
But another question...
Can I just pass some-entity.id as parameter to jsf action?
Like action="#{someBean.doSomething(entity.id)}"
or
Must the parameter be something special like "DataModelSelection" or Entity?
Br,
Juha
View the original p
You only need one of them ;-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013048#4013048
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013048
___
jboss-user mailing list
j
10 matches
Mail list logo
