Hi
Thank you for reading my post.
I want to replace Sun jsf implementation which is with Creator Studio
with myface.
Problem with Original implementation (I think) is that it does not works
OK with unicode entered date.
for example if i enter some unicode characters in one form and submit it
Hi Matthias,
Does the book have some good examples of building components that are
based on child components, e.g. a PhoneNumber component with 3
InputText child components?
-KenOn 12/16/05, Matthias Wessendorf [EMAIL PROTECTED] wrote:
PS: The book is cool, I have read it already ;)On 12/16/05,
Hi
I had the similar (may be same) problem as the collection for the dataTable
was empty at the Restore View Phase. Since it is empty it could not restore
the command link components and hence nothing happens.
You should
1. Store the dataTable's collection value in saveState
The myfaces-api.jar and myfaces-impl.jar are from
1.1.1 release. Component nav_1 is a navigationMenuItem:
t:navigationMenuItem id=nav_1 itemLabel=#{bundle['nav_Home']} action=go_home /
I also tried using the nightly built of
myfaces-impl and myfaces-api but they gave me other
Hi,
I don't know whether my is the similar issue. When I click the CommandLink, the value selection changes in SelectOneRadio never get changed in the backing bean. Any idea?
Thanks!!
On 12/18/05, Balaji Kalyansundaram [EMAIL PROTECTED] wrote:
HiI had the similar (may be same) problem as the
Here is my code:
jsp page:
f:view
h:form
/h:form
/f:view
On 12/18/05, Balaji Kalyansundaram [EMAIL PROTECTED] wrote:
You need to send the code to analyse it.
-Original Message-From: Emily Gu [mailto:
[EMAIL PROTECTED]]Sent: Monday, 19 December 2005 1:08 PMTo: MyFaces
Here is my code:
jsp page:
f:view
h:form
h:selectOneRadio value=
#{choice.choiceEntry}
f:selectItems value=#{choiceList.choiceMap}
/
/h:selectOneRadio
h:commandLink immediate=
true value=Create action=#{choice.createEntry}
/
/h:form
/f:view
Bean:
public class Choice {
private String
Emily Gu wrote:
Here is my code:
jsp page:
f:view
h:form
h:selectOneRadio value= #{choice.choiceEntry}
f:selectItems value=#{choiceList.choiceMap} /
/h:selectOneRadio
h:commandLink immediate= true value=Create
action=#{choice.createEntry} /
Sorry, that was a typo. It is a setter method. Do you see anything else wrong?
Thanks!!
On 12/18/05, Simon Kitching [EMAIL PROTECTED] wrote:
Emily Gu wrote: Here is my code: jsp page: f:viewh:form
h:selectOneRadio value= #{choice.choiceEntry} f:selectItems value=#{choiceList.choiceMap} /
Yeah, that was it. Thank you very much!!
One more question, if I put that SelectOneRadio template into an include file as
f:view
h:form
%@ include file=myTemp.jspf %
h:commandLink immediate=
false action=#{choice.createEntry}
h:outputText value=
Create /
/h:commandLink
/h:form
/f:view
Hi,
I have a bean that is NOT serializable but yet I am able to
set its scope to session. So does that mean that putting a bean to session
scope does not requires serialization? Or is it a myfaces bug?
I am raising this question because I have a piece of code
that worked in 1.1.1
Title: How to force user to press a Button
Hi
Yee!
No,
that's not what I want.
I want
to have the following:
A
CommandButton, which the user must press, otherwise no other actions are made in
the form. So to say I need something similiar than a required attribute for the
CommandButton.
you are right - if you put a bean to session scope, it will usually
not be serialized.
(except the servlet container does it on closing down or passing on
the session to another servlet container instance).
regards,
Martin
On 12/19/05, Yee CN [EMAIL PROTECTED] wrote:
Hi,
I have a bean
You are correct. Putting a bean to session scope does not
require serialization.
Original message
Date: Mon, 19 Dec 2005 14:09:08 +0800
From: Yee CN [EMAIL PROTECTED]
Subject: Session Scope Bean does NOT require serialization.
Myfaces bug?
To: 'MyFaces Discussion'
14 matches
Mail list logo
