How to use own Themes and Stylesheets with JSCookMenu? I tried to follow
instructions which I found on
http://myfaces.apache.org/components/jscookmenu.html . But all the CSS and
JS are part of the packages. Do I have to overwrite the files of the package
myfaces-extensions.jar? Is it possible to ad
2005/5/28, Werner Punz <[EMAIL PROTECTED]>:
> Actually the problem is caused by this, in a midnight debugging session
> it seemed to me, that only the visible elements get submitted over
> the tab change, but the problem itself is much deeper nested, than on
> the tabbing pane, I have not debugged
Ok thanks, I am currently thinking about another solution
to the problem which might make x:saveState and Serialisation
obsolete in the long run. Maybe I will find time after the 15th to
implement it.
Sort of what shale does with their dialog system.
The idead would be to have some kind of scope t
Yes, you have to ;-)
On 5/28/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> Enrique Medina wrote:
> > Yes, I experienced that problem with request scoped beans and tabbed
> > panes. There are several solutions to the problem:
> >
> > a) Scope the beans as being session scoped
> > b) Use some kind of
sureshbabu thyvalappil wrote:
Hi,
My requirement is to setup an environment which will
help me to extend myfaces code and debug.
I prefer an open source IDE environment. Any tips will
be appreciated.
Please advise.
I am using MyEclipse in my project here,
the setup is like that, that I run m
Broekelmann, Mathias wrote:
Hi Werner,
Sylvain is right but you can not use the aliased bean in a component
binding. Component bindings are resolved at creation time of the
component which is currently not handled by the alias component.
will not
work if controller is aliased.
Ok thanks as w
Lorenzo Sicilia wrote:
Craig McClanahan wrote:
One of my developers on the Sun Java Studio Creator team, Edwin Goei,
has collected a set of information needed by third party component
libraries for successful import into Creator. There are issues to pay
attention to with both the components th
Csík Norbert wrote:
Hi!
I think this is becase your backing beans are request scope. When you
display the second tab it is empty, because submitting the page with
the first tab doesn't set those values.
Actually the problem is caused by this, in a midnight debugging session
it seemed to me, th
Enrique Medina wrote:
Yes, I experienced that problem with request scoped beans and tabbed
panes. There are several solutions to the problem:
a) Scope the beans as being session scoped
b) Use some kind of object that holds the model of the tabbed beans,
put it in session and inject it to the req
Csík Norbert wrote:
Hi!
I think this is becase your backing beans are request scope. When you
display the second tab it is empty, because submitting the page with
the first tab doesn't set those values.
Yes that sounds reasonable they are indeed request scoped.
I think what we need is somethin
10 matches
Mail list logo