Stefan Kohler pisze:
Maybe some can explain this to me - it might be a general JSF
misunderstanding I am having.
Could be the latter.
I thought so, too! Thanks for the reply! This problem kept me thinking
about the same things you mentioned, do I really need a Faces Reqeust or
should I do a
Hi Carsten,
you probably have to implement your own TableRenderer (or TreeTableRenderer).
I.e. the renderer
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TableRenderer has a
static private class NavBar extends SelectRangeChoiceBarRenderer
This private class always extends the
Thank you guys!
@Harald:
I.e. the renderer
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TableRenderer has
a
static private class NavBar extends SelectRangeChoiceBarRenderer
That's a very good hint. So probably I'm just writing our own TableRenderer
and put our stuff
directly
I had this exact problem. My solution was to create a managed bean in the
application scope that implements the Map interface. You need to override the
get method and in there I use reflection to find the constant field value. Then
I store that in an actual HashMap (which is declared as final
If anyone is interested, here's the solution to the problem.
I did exactly what Harald advised (writing our own TableRenderer whose inner
private class
NavBar extends MySelectRangeChoiceRenderer).
But as TableRenderer is an abstract class I also had to write our own
version of the
Hi,
I'm using MyFaces 1.1.6. I have this declaration in my faces-config.xml
file ...
managed-bean
managed-bean-nameemailController/managed-bean-name
managed-bean-class
myco.util.jsf.controller.EmailController
/managed-bean-class
Hi Dave,
I guess it is possible. I just wanted to point out though that on a first
glance it looks like a design flaw. In my opinion a managed bean should
always be related to a JSF page. If it is not related, it should not be
declared as a bean of the presentation layer.
Eg. a bean responsible
There may certainly be a design flaw and I definitely want to fix that at
some point. But for now, regarding your comment ...
I guess it is possible
How?
Thanks, - Dave
Rene Guenther wrote:
Hi Dave,
I guess it is possible. I just wanted to point out though that on a first
glance it
Dummy, but works as requested
Make a dependency in a faces config between a bean which appears on the
first page and session bean.
2009/11/25 laredotornado laredotorn...@gmail.com
There may certainly be a design flaw and I definitely want to fix that at
some point. But for now, regarding
I agree with the others that it's better to redesign the application, however
it's possible to access a managed bean as long as you can have the faces
context available.
You need to do something like this, I don't remember the exact syntax...
Hi,
currently i'm using MyFaces 1.1.7 and Tobago 1.0.23.
I'm trying to include an applet into my togabo page using the jsf:plugin
tag. But for some reason it doesn't seem to work. No code is generated for
this tag. When i use the jsf:plugin tag outside of the tc:page from
Tobago it works, but
I tried out Matt's solution and it works well (as a short term fix until I
can redesign the application). The exact syntax was
EmailController ectrl = (EmailController)
facesContext.getApplication().getVariableResolver().resolveVariable(facesContext,
emailController);
Thanks a million, -
Hi there,
as our applications still have to be compatible to IE6 we're quite unhappy
with
the tr:selectOneChoice as is makes use of the HTML select component which
is a pain in IE6 (IE6 being the culprit, not the select, of course; e.g. the
good
old z-index bug...).
So, here's my question:
13 matches
Mail list logo